Description of problem: VirtIO drivers for windows does not show specific OS: Windows 7, Windows 2003. It shows only windows 2008. There is only one driver compatible for Win2k3 and up. But it confuses a user when he tries to install win7 and cannot find his OS on the available drivers list. According to Yan V (output from a mail-thread): [YV] We don’t have “special” drivers for Windows 7 as we use binary compatible drivers. For virtio-block we have two types of drivers: 1. Windows XP 2. Windows 2003 (driver model changed and thus the second set is needed). Windows 2003 drivers are compatible with all the newest Windows OSes. What might be confusing is the current text descriptions from text based Windows installation: [Disks] d1 = "OEM DISK (SCSI) WinXP/32-bit",\disk1,\i386\WinXP d2 = "OEM DISK (SCSI) Win2003/32-bit",\disk1,\i386\Win2003 d3 = "OEM DISK (SCSI) Win2003/64-bit",\disk1,\amd64\Win2003 [YV] So the questions is: Did you try those on Windows 7? Regarding the guest tools it is the same, binary compatible drivers are packed in the MSI installers. MSI installer know how to unpack appropriate driver version according to OS.
Could you please clarify the meaning of this bug? What is wrong and how it supposes to work. If it is a MSI problem, than please reassign it to the someone, who deals with installer. Thanks, Vadim.
Vadim, I'm talking about drivers installation during Windows installation, not MSI. Other description is clear, I believe: >> VirtIO drivers for windows does not show specific OS: Windows 7, Windows 2003. >> It shows only windows 2008. >> There is only one driver compatible for Win2k3 and up. But it confuses a user when he tries to install win7 and cannot find his OS on the available drivers list. Marina.
(In reply to comment #2) > Vadim, > > I'm talking about drivers installation during Windows installation, not MSI. > > Other description is clear, I believe: > >> VirtIO drivers for windows does not show specific OS: Windows 7, Windows 2003. > >> It shows only windows 2008. > >> There is only one driver compatible for Win2k3 and up. But it confuses a user when he tries to install win7 and cannot find his OS on the available drivers list. > > Marina. ISO or virtual floppy image?
Virtual floppy image.
Thanks, But textsetup.oem file, which is a part of floppy image, works only for XP and W2K3. There is no setup text instillation phase for Vista and higher.
Attaching a screenshot from Win7 installation. You can see that there is no Win7 or XP for 64bit and no Win7 for 32bit drivers. This is incorrect. If the driver is present, it should be available on this list. If not - it should be created and added to the list ;) The customer cannot guess what driver should he choose for his non-existing OS.
Created attachment 439137 [details] Win7 virtio driver installation
I see, thanks. Initially, vfd image was created for XP/W2K3 windows virtio block drivers ONLY. I need to figure out who and why decided to abuse floppy image this way, by adding W2K8 drivers there. In my understanding, starting from VISTA viostor drivers should be installed from iso image. In any case, I do not build or packaging drivers. Hence, I think, this issue should be addressed to release engineering team. Regards, Vadim.
Vadim, When installing an OS on a VM, we are using an ISO image for this. I do not see a way installing the required drivers from another ISO image in parallel to OS installation. So I do think it is ok having those drivers on the floppy, which is attached to the VM in addition to the ISO images. Thank you.
Vadim please outline what the new VFD directory tree should look like and where the drivers are coming from. I'll update the scripts on my end to satisfy your requirements.
For viostor driver must be like this: A:\ amd64---+ | +---Win2003 <------ ..\viostor\wnet\amd64\ | +---Win2008 <------ ..\viostor\wlh\amd64\ | +---Win7 <------ ..\viostor\win7\amd64\ | +---WinXP <------ ..\viostor\wnet\amd64\ i386----+ | +---Win2003 <------ ..\viostor\wnet\x86\ | +---Win2008 <------ ..\viostor\wlh\x86\ | +---Win7 <------ ..\viostor\win7\x86\ | +---WinXP <------ ..\viostor\wxp\x86\ But I'm not sure about WinXP 64-bit. Technically, for WinXP 64-bit we need to use Win2003 64-bit driver. And it works and works fine. The question is: do we support WinXP 64-bit or not?
According to documentation of 2.2, we don't: http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Virtualization_for_Desktops/2.2/html/Administration_Guide/Administration_Guide-Manage_Objects.html#Types-of-vms
(In reply to comment #15) > According to documentation of 2.2, we don't: > http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Virtualization_for_Desktops/2.2/html/Administration_Guide/Administration_Guide-Manage_Objects.html#Types-of-vms OK. So it must be like this: A:\ amd64---+ | +---Win2003 <------ ..\viostor\wnet\amd64\ | +---Win2008 <------ ..\viostor\wlh\amd64\ | +---Win7 <------ ..\viostor\win7\amd64\ i386----+ | +---Win2003 <------ ..\viostor\wnet\x86\ | +---Win2008 <------ ..\viostor\wlh\x86\ | +---Win7 <------ ..\viostor\win7\x86\ | +---WinXP <------ ..\viostor\wxp\x86\
Yeah. Looks ok.
Fixed on my end. You should see this in 1.1.16.
please check the latest build from: http://download.lab.bos.redhat.com/devel/RHEV/virtio-win/1.1.16/
The above was fixed for rhel6 but not for rhel5. I guess this bug should be cloned to rhel6 where it is on_qa and on rhel5 it is still assigned.
Yes it was, in 1.0.0-12. See #636516
Reminder: virtio-win is in supplementary, so there doesn't need to be a cloned bug if we want this in 5.5 async and 5.6.
Argh, I apologize, I confused myself. This is NOT fixed for RHEL 5. Once the flags are set I'll commit the changes needed and build another virtio-win RPM.
Committed and in built in Brew. https://brewweb.devel.redhat.com/buildinfo?buildID=146124
Reproduced in virtio-win-1.0.0-12.45801.el5 and the previous version. And verified pass in virtio-win-1.0.0-13.45801.el5. 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, 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.
> So, this issue is fixed in the virtio-win-1.0.0-13.45801.el5. Can you close it? Thanks, Vadim.
According to Comment 26, 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: When installing the VirtIO driver, the relevant dialog window did not offer Windows 7 as the target operating system. With this update, Windows 7 has been added to the list of supported operating systems, and this error no longer occurs.
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