Bug 619010

Please provide more information on the "doesn't work" symptom, for example:

1. What do you see in device manage? Is the driver installed or there are unrecognized devices? Or maybe there are not corresponding devices at all.

2. If network driver is installed, what do you see when running "ipconfig -a" and "getmac"? what happens to ping?


From the first glance - if the drivers where not signed , they might not be installed after reboot (as you use specific bus location for RHEL6.0 - device might switch its place on the bus). This is MS Windows behavior, please use only signed drivers for this test.

(In reply to comment #3)
> Please provide more information on the "doesn't work" symptom, for example:
> 
> 1. What do you see in device manage? Is the driver installed or there are
> unrecognized devices? Or maybe there are not corresponding devices at all.
> 
Forgot to mention there's an attachment in Comment 0.
Pls look at https://bugzilla.redhat.com/attachment.cgi?id=434978

> 2. If network driver is installed, what do you see when running "ipconfig -a"
> and "getmac"? what happens to ping?
The device is not configured correctly. No IP or MAC available.

> 
> 
> From the first glance - if the drivers where not signed , they might not be
> installed after reboot (as you use specific bus location for RHEL6.0 - device
> might switch its place on the bus). This is MS Windows behavior, please use
> only signed drivers for this test.    
The guest installed on RHEL5 with virtio-drivers-1.0.0-45801 (which is a signed version) couldn't be booted on RHEL6 (It got BSOD which was a known issue). I had to update the driver to 1.1.8 to boot the guest on RHEL6. Also the problem doesn't exist for win7/xp/2008.

The problem doesn't exist if I keep the PCI addr unchanged for the virtual NIC. (On RHEL5 under qemu monitor, I used "info pci" to get the pci addr of the NIC, which I later passed to CLI of RHEL6)

However, as mentioned in Comment 4, there's no need to do this for winXP/7/2008.

BTW, to boot on RHEL6 host Win-guests (2003/win7/2008) which were originally installed on RHEL5 host, we need to update virtio-win driver to 1.1.8. Or else, the guests will get BSOD (XP-32 seems to be an exception). Using Vadim's workaround (cache=writethrough) doesn't seem to work for win2003 SFAIK, see https://bugzilla.redhat.com/show_bug.cgi?id=609831#c2.

* Please provide screen shot of full device manger window.
* Please provide screen shot of "general" tab for NIC.

Created attachment 435192 [details]
device manager full screen shot

As it can be seen from the screen shot - driver is not installed.

Driver is not installed because the device changed its location and the driver is not signed. This is "by design" behavior for Windows OS.

Please either move the bug to QEMU component (why the device moved?) or close the bug.

OK, I will move this to qemu-kvm and change the title a bit.

On rhel5.5, the typical default PCI addresses assigned are:
 QEMU 0.9.1 monitor - type 'help' for more information
(qemu) info pci
 ...
  Bus  0, device   3, function 0:
    Ethernet controller: PCI device 1af4:1000
      IRQ 0.
      BAR0: I/O at 0xffffffff [0x001e].
  Bus  0, device   4, function 0:
    SCSI controller: PCI device 1af4:1001
      IRQ 0.
      BAR0: I/O at 0xffffffff [0x003e].
  Bus  0, device   5, function 0:
    RAM controller: PCI device 1af4:1002
      IRQ 0.
      BAR0: I/O at 0xffffffff [0x001e].

Whereas currently management tool like libvirt assigns pci addr=0x3 to virtio-balloon device by default. This will cause virtio net driver not to work when moving Win2003 guest from rhel5 to rhel6 host.
Therefore, a mechanism to keep PCI addr unchanged is in high demand.

I'll close this bug since libvirt will make sure to keep the pci slots the same when using -M rhel5.X so it should be fine.

Can you also make sure that the rhel5 virtio drivers will work w/o upgrade over new rhel6 host (from an image that run over rhel5 host).
Please keep the pci slots the same.

(In reply to comment #11)
> I'll close this bug since libvirt will make sure to keep the pci slots the same
> when using -M rhel5.X so it should be fine.
OK, still Old guests created by libvirt do not have their pci slots kept in xml configuration file.

> 
> Can you also make sure that the rhel5 virtio drivers will work w/o upgrade over
> new rhel6 host (from an image that run over rhel5 host).
> Please keep the pci slots the same.    

Tested with winxp(32)/7/2003/2008 and pci slots unchanged. All except XP got BSOD without virtio-win-driver being upgraded, and all seemed to work well with virtio-win-driver being upgraded to 1.1.9.

(In reply to comment #12)

> > Can you also make sure that the rhel5 virtio drivers will work w/o upgrade over
> > new rhel6 host (from an image that run over rhel5 host).
> > Please keep the pci slots the same.    
> 
> Tested with winxp(32)/7/2003/2008 and pci slots unchanged. All except XP got
> BSOD without virtio-win-driver being upgraded, and all seemed to work well with
> virtio-win-driver being upgraded to 1.1.9.    

We need to use the -M rhel5.5 flag when you run those.
Please run only one of them to see if it changes something.
Also please provide the BSOD details in case it fails

(In reply to comment #13)

> We need to use the -M rhel5.5 flag when you run those.

-M rhel5.5, not -M rhel5.4.0? SFAIK we used -M rhel5.4.0 by default for all guests hosted by rhel5.

> Please run only one of them to see if it changes something.
> Also please provide the BSOD details in case it fails    

No BSOD was found when using virtio-win-1.1.9 with either -M rhel5.4.0 or -M rhel6.0.0.

Still, one thing I should mention that there's a slot change when running the same guest with -M rhel5.4.0 and without assigning slot explicitly on rhel6 host. But libvirt may deal with it.
On rhel5 host, (qemu) info pci
"  Bus  0, device   3, function 0:
    Ethernet controller: PCI device 1af4:1000
      IRQ 11.
      BAR0: I/O at 0xc040 [0xc05f].
  Bus  0, device   4, function 0:
    SCSI controller: PCI device 1af4:1001
      IRQ 10.
      BAR0: I/O at 0xc080 [0xc0bf]."
while on rhel6 host with -M rhel5.4.0 and without assigning slot explicitly, (qemu) info pci
  Bus  0, device   3, function 0:
    SCSI controller: PCI device 1af4:1001
      IRQ 0.
      BAR0: I/O at 0xffffffffffffffff [0x003e].
      id "virtio-disk0"
  Bus  0, device   4, function 0:
    Ethernet controller: PCI device 1af4:1000
      IRQ 0.
      BAR0: I/O at 0xffffffffffffffff [0x001e].
      id "net0"

Details can be found through attachment of next Comment.

Created attachment 435948 [details]
pci slot change with -M rhel5.4.0 on rhel6 host

(In reply to comment #14)
> (In reply to comment #13)
> 
> > We need to use the -M rhel5.5 flag when you run those.
> 
> -M rhel5.5, not -M rhel5.4.0? SFAIK we used -M rhel5.4.0 by default for all
> guests hosted by rhel5.

Please switch to rhel5.5 (I think even rhel5.5.4 which is latest Z stream update). It contains some kvmclock and live migration fixes.

> 
> > Please run only one of them to see if it changes something.
> > Also please provide the BSOD details in case it fails    
> 
> No BSOD was found when using virtio-win-1.1.9 with either -M rhel5.4.0 or -M
> rhel6.0.0.
> 
> Still, one thing I should mention that there's a slot change when running the
> same guest with -M rhel5.4.0 and without assigning slot explicitly on rhel6
> host. But libvirt may deal with it.

That's expected, this is why libvirt is needed

> On rhel5 host, (qemu) info pci
> "  Bus  0, device   3, function 0:
>     Ethernet controller: PCI device 1af4:1000
>       IRQ 11.
>       BAR0: I/O at 0xc040 [0xc05f].
>   Bus  0, device   4, function 0:
>     SCSI controller: PCI device 1af4:1001
>       IRQ 10.
>       BAR0: I/O at 0xc080 [0xc0bf]."
> while on rhel6 host with -M rhel5.4.0 and without assigning slot explicitly,
> (qemu) info pci
>   Bus  0, device   3, function 0:
>     SCSI controller: PCI device 1af4:1001
>       IRQ 0.
>       BAR0: I/O at 0xffffffffffffffff [0x003e].
>       id "virtio-disk0"
>   Bus  0, device   4, function 0:
>     Ethernet controller: PCI device 1af4:1000
>       IRQ 0.
>       BAR0: I/O at 0xffffffffffffffff [0x001e].
>       id "net0"
> 
> Details can be found through attachment of next Comment.

Hi Dor,
According to my testing, using -M rhel5.5.0 also works for winxp/7/2003/2008/2008R2 with virtio-win-1.1.9 or 1.1.10.
If there's any problem later on, I will open new bug tracking it. (Currently I suspect switching to different machine types back and forth may cause problem over which I will test more).