Just for clarity, could the RHEL 5 package please be update to have the exact same directory structure as the RHEL 6 package?
I can make this happen by 9/30.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
I'm granting dev ack based on comment #2.
Verified on virtio-win-1.0.0-13.45801.el5, passed. # rpm -qa | grep virtio-win virtio-win-1.0.0-13.45801.el5 #rpm -ql virtio-win ...... ...... /usr/share/virtio-win/drivers/i386/WinXP/viostor.cat /usr/share/virtio-win/drivers/i386/WinXP/viostor.inf /usr/share/virtio-win/drivers/i386/WinXP/viostor.sys /usr/share/virtio-win/drivers/txtsetup.oem /usr/share/virtio-win/virtio-drivers-1.0.0-45801.vfd /usr/share/virtio-win/virtio-drivers.vfd /usr/share/virtio-win/virtio-win-1.0.0-45801.iso /usr/share/virtio-win/virtio-win.iso virtio-drivers.vfd has been expanded. I installed a windows guest with virtio block using virtio-drivers.vfd, guest can be installed successfully. So, I will change the status to VERIFIED.
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: The content of the Virtual Floppy Disk (VFD) is now distributed as a part of the package installation, and can be found in the /usr/share/virtio-win/drivers directory.
(In reply to comment #8) > Verified on virtio-win-1.0.0-13.45801.el5, passed. > # rpm -qa | grep virtio-win > virtio-win-1.0.0-13.45801.el5 > #rpm -ql virtio-win > ...... > ...... > /usr/share/virtio-win/drivers/i386/WinXP/viostor.cat > /usr/share/virtio-win/drivers/i386/WinXP/viostor.inf > /usr/share/virtio-win/drivers/i386/WinXP/viostor.sys > /usr/share/virtio-win/drivers/txtsetup.oem > /usr/share/virtio-win/virtio-drivers-1.0.0-45801.vfd > /usr/share/virtio-win/virtio-drivers.vfd > /usr/share/virtio-win/virtio-win-1.0.0-45801.iso > /usr/share/virtio-win/virtio-win.iso > > virtio-drivers.vfd has been expanded. I installed a windows guest with virtio > block using virtio-drivers.vfd, guest can be installed successfully. > > So, I will change the status to VERIFIED. To be clear. Steps: 1.Install virtio-win package in host, and in /usr/share/virtio-win/ directory, there will be a VFD file generated. 2.Install a win2k8 or win7 guest with virtio block with the vfd attached. In the install stage of "Select the driver to be installed", browse the virtio block driver from the floppy disk. Expand the A:\ directory, check the virtio driver for specific OSes. Result: In old package virtio-win-1.0.0-12.45801.el5 and the previous version, there's only: -- amd64 --Win2003 --Win2008 --i386 --Win2003 --Win2008 --WinXP In virtio-win-1.0.0-13.45801.el5, there's following sub-directories: -- amd64 --Win2003 --Win2008 --Win7 --i386 --Win2003 --Win2008 --Win7 --WinXP So, this issue is fixed in the virtio-win-1.0.0-13.45801.el5.
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-0106.html