Re: GPLPV Drivers

[Dustin Marquess <dmarquess%gmail.com@localhost>]

On Sun, Jun 13, 2010 at 10:51 AM, Stephen Borrill
<netbsd%precedence.co.uk@localhost> wrote:
> On Thu, 10 Jun 2010, Stephen Borrill wrote:
>>>>>
>>>>> For me it hangs the same way with 3.3.2. I tried to install only a
>>>>> minimal
>>>>> subset (pci, vbd, net) but it doesn't help. It seems to hang installing
>>>>> the PCI driver, because with the device manager I can't see any other
>>>>> xen-related device. Nothing show up in event logs, nor in qemu-dm log.
>>>>> I've no idea on how to debug this ...
>>>>
>>>> What guest OS? I used Windows Server 2003 R2 32-bit.
>>>
>>> This is the same version as my install CD it seems.
>>> Did you do some updates before installing the PV drivers ?
>>> I do in on a clean install without updates.
>>
>> Yes, I had a working domU which I did a full set of MS updates on before
>> installing the drivers.
>
> So I tried again on the Xen installation on my laptop. I did a clean
> installation of Windows Server 2003 R2 32-bit and applied all major Windows
> updates (i.e. not optional components such as .NET framework or IE8).
>
> When I install the PV drivers, I get all the relevant dialogs, but when
> installing the Xen Block Device Driver I get "This device cannot start.
> (Code 10)". The Network device driver installs fine. When I reboot, I get a
> BSOD. I can't see any obvious difference between the two VMs. If I do a
> custom install and skip XenVbd, then the VM is happy (with "Xen vbd devuce
> #768" remaining in Device Manager with no driver loaded).

If I remember correctly, it's normal for the cannot start error to
show before the first reboot.  The BSOD isn't good though.  Do you
happen to remember what the STOP code was?  0x0000007B  is what I was
getting with the stock drivers.

> I tried a clean install of Server 2008 32-bit with all major updates. The PV
> driver install completed, but there were no "Found new hardware" dialogs. I
> rebooted, the vif claimed a cable was unplugged and the vbd driver failed to
> start. When I rebooted a second time (after disabling the original emulated
> network card), I got a BSOD. After reverting to a backup, I did a custom
> install, skipped XenVbd and rebooted. Again the first time, the vif claimed
> the cable was unplugged, but after disabling the emulated card and rebooted
> it worked.
>
> So the problem, for me, seems to be down to the XenVbd driver.
>
>>> I never see the "Found new hardware" dialog, the install hang with the
>>> progress par near the end.
>>> I've keep the windows install cd and the 'boot="d"' lines in my xen
>>> config file, did you remove theses after install ?
>>
>> Yes, I did. If I want access to a particular iso, I tend to use xm
>> block-configure to add it while the vm is running.
>
> I had the hardrive on hda always on the working VM, on the VM(s) that XenVbd
> did not work on, I originally used hdc and then changed to hda. Probably
> unrelated, but you never know...

Sounds like their might either be deeper issues than the state
problems, or there are more state problems than I thought there was.

Is there any chance you can follow the debug instructions at
http://wiki.xensource.com/xenwiki/XenWindowsGplPv and capture the
output?  It'll help determine where the problem is.

I wish the original author would help, but he doesn't seem to be too
interested in supporting non-Linux dom0s.  Windows driver programming
isn't exactly my forte :).

-Dustin