Bug 1170106

Summary: RFE: [virtio-win][qxl-win] Add windows 2008R2 QXL to the .vfd
Product: Red Hat Enterprise Linux 7 Reporter: Mike Cao <bcao>
Component: virtio-winAssignee: Jeff Nelson <jen>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1CC: crobinso, dblechte, jherrman, juzhang, michen, rbalakri, virt-maint, vrozenfe, wyu
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: virtio-win-1.8.0-1.el7 Doc Type: Enhancement
Doc Text:
The virtio-win package now contains the qxl driver for Windows Server 2008 R2, and the driver thus does not have to be downloaded manually.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-24 08:48:16 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:

Description Mike Cao 2014-12-03 09:49:00 UTC
Description of problem:


Version-Release number of selected component (if applicable):
virtio-win-1.7.1.el7

How reproducible:
100%

Steps to Reproduce:
1.The qxl driver for win2k8R2 is not added in virtio-win package ,as the drivers for win7 is here ,I suggest to add the win2k8R2 qxl driver in virtio-win_amd64.vfd as well

Mike

Comment 3 Cole Robinson 2015-04-30 23:07:54 UTC
The current build scripts seem to do this, it must have been fixed at some point before the switch over. Either way, the next RPM build should have all qxl drivers on the vfd images.

Comment 5 Jeff Nelson 2015-10-01 20:30:29 UTC
Fixed in virtio-win-1.8.0-1.el7

Comment 7 Yu Wang 2015-10-14 08:19:54 UTC
The qxl driver for win2k8R2 is added in virtio-win-1.8.0_amd64.vfd win2008R2 folder.

Above all, the bug has been fixed , change the status to verified.

Comment 10 errata-xmlrpc 2015-11-24 08:48:16 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2513.html