Bug 981817

Summary: virtio-win drivers seemingly incompatible with Windows 2008 R2 during installation
Product: Red Hat Enterprise Linux 6 Reporter: Bryan Yount <byount>
Component: virtio-winAssignee: Vadim Rozenfeld <vrozenfe>
Status: CLOSED CANTFIX QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 6.4CC: acathrow, bcao, bsarathy, kzhang, lijin, mdeng, michen, rhod, virt-bugs
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-29 10:18:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Selecting the proper VirtIO driver folder
none
Warning message none

Description Bryan Yount 2013-07-06 00:22:17 UTC
Created attachment 769451 [details]
Selecting the proper VirtIO driver folder

Description of problem:
When installing a Windows 2008 R2 (64-bit) guest, the virtio storage drivers in the Win2008R2 folder do not appear to be "automatically compatible" with this particular OS which causes the user to have to go through additional steps that may not be apparent.

Version-Release number of selected component (if applicable):
virtio-win-1.6.4-1.el6_4

How reproducible:
Very

Steps to Reproduce:
1. Begin installation of Windows 2008 R2 64-bit guest
2. Attach virtio-win-1.6.4_amd64.vfd to VM using "Run once" menu
3. Select Load driver when prompted
4. Browse to A:\amd64\Win2008R2
5. Click OK

Actual results:
A warning message appears informing the user that "No device drivers were found." as shown in the win2008r2-virtio-02.png screenshot.

Expected results:
VirtIO SCSI controller should appear in the list

Additional info:
After dismissing the warning message. If the user unchecks "Hide drivers that are not compatible..." and clicks rescan, they are able to choose the VirtIO scsi controller for Windows 2008 and proceed with installation.

Comment 1 Bryan Yount 2013-07-06 00:23:39 UTC
Created attachment 769452 [details]
Warning message

I just tested with the latest "virtio-win-1.6.5-5.el6_4" and the issue persists.

Comment 2 Mike Cao 2013-07-08 08:54:19 UTC
I can reproduce but let developer decide it whether it is a bug .
BTW ,We reports some bugs about virtio serial/balloon can not be installed during guest installation .but they all closed as notabug at last

Comment 3 Vadim Rozenfeld 2013-07-08 09:35:12 UTC
It's not a bug. Vista and higher, do not honor the floppy disk layout anymore.

Comment 4 Mike Cao 2013-07-08 09:45:13 UTC
(In reply to Vadim Rozenfeld from comment #3)
> It's not a bug. Vista and higher, do not honor the floppy disk layout
> anymore.

FYI, I tried to attach the virtio-win.iso  steps same as comment #0 

Actual Results:
A warning message appears informing the user that "No device drivers were found." as shown in the win2008r2-virtio-02.png screenshot.

Additional Info:
After dismissing the warning message. If the user unchecks "Hide drivers that are not compatible..." and clicks rescan, *still* can not find driver

Comment 5 Vadim Rozenfeld 2013-07-08 11:37:00 UTC
(In reply to Mike Cao from comment #4)
> (In reply to Vadim Rozenfeld from comment #3)
> > It's not a bug. Vista and higher, do not honor the floppy disk layout
> > anymore.
> 
> FYI, I tried to attach the virtio-win.iso  steps same as comment #0 
> 
> Actual Results:
> A warning message appears informing the user that "No device drivers were
> found." as shown in the win2008r2-virtio-02.png screenshot.
> 
> Additional Info:
> After dismissing the warning message. If the user unchecks "Hide drivers
> that are not compatible..." and clicks rescan, *still* can not find driver

Mike, can you please check if it the only win2008r2 problem? What about Win7/32-bit does it have the same problem?

Thanks,
Vadim.

Comment 6 Ronen Hod 2013-07-29 10:18:52 UTC
Closing,
It is known that Microsoft's scanning does not work and that the user has to select the driver manually.
The only way to fix it is to build an ISO per guest OS, and we prefer not to.