Bug 634529

If installed guest on rhel5 host with *RHEL6 virtio driver* then boot the guest
on RHEL6 hosts, this issues does not exist. Guest can boot up under this
condition.

Created attachment 448272 [details]
Device error when booting winXP

Created attachment 448273 [details]
Unknown Devices

Description of problem:

While tring to reproduce this BUG using both rhel5-virtio-driver and rhel6-virtio-driver on RHEL5 host and coping the image to RHEL6(AMD Opteron2).

The BSOD appears for both environment,whose content of error is the same.

As well, the WinXP prompts some error.(See Attachment)

RHEL guests are not impacted, this issue only happens on windows guests.

Update:
Using the rhel5 virtio-win driver "virtio-win-1.0.0-13.45801.el5"
The issue happens for all windows guest except Winxp-32.
There's more detail information in:
https://bugzilla.redhat.com/show_bug.cgi?id=636342#c6

BTW, check the "virtio-win-1.0.0-13.45801.el5", winxp version is different with others.

# rpm -qa | grep virtio-win
virtio-win-1.0.0-13.45801.el5
# cd /usr/share/virtio-win/
# ls
drivers                         virtio-drivers.vfd          virtio-win.iso
virtio-drivers-1.0.0-45801.vfd  virtio-win-1.0.0-45801.iso
# mount virtio-drivers-1.0.0-45801.vfd /mnt -o loop
# cd /mnt/i386/WinXP
# cat viostor.inf
the winxp driver version is: DriverVer   = 01/25/2010,4.5.0.42220
While other guests' version are:
DriverVer   = 12/30/2009,4.5.0.41217

(In reply to comment #8)
> RHEL guests are not impacted, this issue only happens on windows guests.

Sure. What I meant is that windows viostor drivers, created for Windows guests and installed on VMs running on top RHEL5 will not work when you try to run them on top of RHEL6. You need to update your Windows VM with the latest drivers from rhel6 virtio-win package before switching from RHEL5 to RHEL6.

Best regards,
Vadim.

I asked Rich Jones about this problem, and it's possible to use libguestfs to install the updated driver.  He pointed me to a blog post he wrote:

http://rwmj.wordpress.com/2010/04/30/tip-install-a-device-driver-in-a-windows-vm/

(In reply to comment #11)
> I asked Rich Jones about this problem, and it's possible to use libguestfs to
> install the updated driver.  He pointed me to a blog post he wrote:
> 
> http://rwmj.wordpress.com/2010/04/30/tip-install-a-device-driver-in-a-windows-vm/

Yes, one way or another we just need to update binaries and Registry.
btw, I'm not sure that patching ControlSet001 will work in all situations. I don't know for sure how it works in the latest Windows OSs, but on NT4 I remember situation when we had more than two ControlSets and the current one wasn't ControlSet001.

Regards,
Vadim.

This bug was originally against rhel6 qemu-kvm but eventually the faulty component is virtio-blk of el5. We need to rebase virtio-blk of el5 to the one that is used in el6. This was proven to work w/o regressions for el5 host.

Re-opening over rhel5 virtio-win

I'm getting the following message while trying to save a new advisory

"1 error prohibited this errata from being saved

There were problems with the following fields:

    * Idsfixed Bug 634529 does not have the correct flags. Requires rhel-5.7.0,fast,devel_ack,qa_ack but only has devel_ack+, fast?, pm_ack+, qa_ack?, rhel-5.7.0?."

Who has enough rights to adjust all these flags as required?

Verified with the new build virtio-win-1.0.1-2.52454.el5, instaled win2k3-32 and win2k8-64, this problem does not exist.
Checked the inf file of other guests, all have changed to the rhel6.0 version.
So, the bug is verified pass. 

Vadim and Jay
Could you anyone please help to change the status to ON_QA from errata tool?
Then I could change to VERIFIED.

Thanks,
Qunfang

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Under certain circumstances, when a user installed a Windows guest on a Red Hat Enterprise Linux 5 host and then copied the image, an attempt to boot this image from virtio block device on a Red Hat Enterprise Linux 6 host could fail with an error screen. This error has been fixed, and such images now boot as expected on both Red Hat Enterprise Linux 5 and 6.

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0280.html