Bug 1038547

Summary:	fail to change Resolution of guest with gpu card
Product:	Red Hat Enterprise Linux 7	Reporter:	FuXiangChun <xfu>
Component:	qemu-kvm	Assignee:	Alex Williamson <alex.williamson>
Status:	CLOSED WORKSFORME	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.0	CC:	acathrow, alex.williamson, juzhang, michen, virt-maint, xfu
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-12-19 14:26:28 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:

Description FuXiangChun 2013-12-05 10:19:26 UTC

Description of problem:
Boot guest with GPU card, then change Screen Resolution inside guest. guest is screen mess. and fail to change,  guest will resume old resolution.  emulate VGA card don't this issue by default.

Version-Release number of selected component (if applicable):
# uname -r
3.10.0-57.el7.x86_64
qemu-kvm-1.5.3-20.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1./usr/libexec/qemu-kvm -M q35 -cpu host -enable-kvm -m 8196 -smp 4,sockets=2,cores=2,threads=1 -usb -device usb-tablet,id=input0 -name gpu -uuid 990ea161-6b67-47b2-b803-19fb01d30d30 -rtc base=localtime,clock=host,driftfix=slew  -device ahci,id=ahci0 -drive file=/home/win2012-64.qcow2,if=none,id=drive-sata-disk-0-0,format=qcow2 -device ide-drive,bus=ahci0.0,unit=0,drive=drive-sata-disk-0-0,id=sata-disk-0-0 -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup -device e1000,netdev=hostnet0,id=virtio-net-pci0,mac=00:01:02:B6:40:21  -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -k en-us -boot menu=on -qmp tcp:0:4444,server,nowait -serial unix:/tmp/ttyS0,server,nowait -spice disable-ticketing,port=5932 -vga qxl -monitor stdio -device vfio-pci,host=06:00.0,id=GPU-k1,addr=06.0 -device vfio-pci,host=07:00.0,id=GPU-k2,addr=07.0 -device vfio-pci,host=08:00.0,id=GPU-k3,addr=08.0 -device vfio-pci,host=09:00.0,id=GPU-k4,addr=09.0

2.disable emulate VGA card
3.change resolution inside guest

Actual results:
guest screen mass and fail to change

Expected results:
successful 

Additional info:

Comment 2 FuXiangChun 2013-12-06 02:57:12 UTC

RHEL7 and win2008r2 guest don't hit this issue.

Comment 3 Alex Williamson 2013-12-09 14:58:27 UTC

This is a q35 guest, does 440fx have the same problem?

Comment 4 FuXiangChun 2013-12-10 15:36:03 UTC

(In reply to Alex Williamson from comment #3)
> This is a q35 guest, does 440fx have the same problem?

For windows2012 guest, 440fx machine type has the same problem.  windows2008r2 and rhel7 guest don't hit this problem whether q35 or 440fx machine type.

Comment 5 Alex Williamson 2013-12-18 22:56:29 UTC

Works for me.  I installed Windows Server 2012 Standard Edition, installed RealVNC server, and connected to the client based VNC server.  I then powered down the guest, added the GPU (GRID K2), and restarted it, making sure I could login via the guest-based VNC server.  I then installed the Nvidia driver (331.65), the guest rebooted and I again connected to the guest-based VNC server.  Logging in I notice that the VNC window is extra wide.  When I adjust screen resolution I can see that the display extends across both emulated VGA device and assigned GPU (this is the only guest that I've seen that does this).  I can independently adjust the screen resolution for either device or disable either device.  Note that my guest is configured to use the standard VGA device (not QXL/Cirrus), it's possible that you're having trouble changing the resolution on the emulated display.  Please retest and provide details if still having problems.

Comment 6 FuXiangChun 2013-12-19 10:01:07 UTC

Since didn't install auxiliary power connector of gup before host.  so I am trying to setup a new test hosts.  QE will re-test this issue asap, and update test result to bz.

Comment 7 Alex Williamson 2013-12-19 14:26:28 UTC

Let's close this then, the error was reported against mis-configured hardware.  Re-open or file new if it can be reproduced when the configuration is fixed.