Bug 915186

Summary: win8 guest resume form s4, display driver not load normally, the guest display with no colour
Product: Red Hat Enterprise Linux 7 Reporter: yunpingzheng <yunzheng>
Component: qemu-kvmAssignee: Alon Levy <alevy>
Status: CLOSED CURRENTRELEASE QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: acathrow, dblechte, hhuang, juzhang, mazhang, michen, rhod, virt-maint, yunzheng
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: qemu-kvm-1.5.1-2.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-12 08:02:33 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:
Bug Depends On:    
Bug Blocks: 923626    

Description yunpingzheng 2013-02-25 08:03:43 UTC
Description of problem:
when run guest(s4) win8-64 guest, after the guest resume, seems the display driver not load normally. the guest display with wrong resolution and have no colour. 

when i using -vga cirrus if works ok, if using std or qxl display error.
Version-Release number of selected component (if applicable):
kernel-3.7.0-0.34.el7.x86_64
qemu-kvm-1.3.0-4.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.boot guest with "-vga std" or "-vga qxl" 
2.do guest s4,and then resume the guest.connect with spicec
3.
  
Actual results:
the guest can resume, but the guest can not display normally. the screen with no colour

Expected results:
display normally

Additional info:

qemu-command:
qemu-kvm \
-name 'vm1' \
-nodefaults \
-chardev socket,id=qmp_id_qmpmonitor1,path=/tmp/monitor-qmpmonitor1-20130218-181439-LwkhJejQ,server,nowait \
-mon chardev=qmp_id_qmpmonitor1,mode=control \
-chardev socket,id=serial_id_serial1,path=/tmp/serial-serial1-20130218-181439-LwkhJejQ,server,nowait \
-device isa-serial,chardev=serial_id_serial1 \
-chardev socket,id=seabioslog_id_20130218-181439-LwkhJejQ,path=/tmp/seabios-20130218-181439-LwkhJejQ,server,nowait \
-device isa-debugcon,chardev=seabioslog_id_20130218-181439-LwkhJejQ,iobase=0x402 \
-device ich9-usb-uhci1,id=usb1,bus=pci.0,addr=0x4 \
-drive file='/root/win8-64-virtio.qcow2',if=none,id=drive-virtio-disk1,media=disk,cache=none,snapshot=off,format=qcow2,aio=native \
-device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk1,id=virtio-disk1  \
-m 4096 \
-smp 4,maxcpus=4,cores=2,threads=1,sockets=2 \
-cpu 'SandyBridge',+sep \
-device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \
-vnc :0 \
-vga cirrus \
-rtc base=localtime,clock=host,driftfix=slew \
-boot order=cdn,once=d \
-enable-kvm \
-device virtio-net,netdev=g_nic1,mac=00:11:22:33:44:66,id='idBD44vM' \
-netdev tap,vhost=on,sndbuf=1048576,id=g_nic1,script=/root/qemu-ifup-switch \
-monitor stdio \
-spice port=3000,disable-ticketing  \
-global PIIX4_PM.disable_s3=0 \
-global PIIX4_PM.disable_s4=0

2. cpuinfo:
[root@intel-e7420-128-1 ~]# lscpu 
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                16
On-line CPU(s) list:   0-15
Thread(s) per core:    1
Core(s) per socket:    4
Socket(s):             4
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 29
Stepping:              1
CPU MHz:               2127.860
BogoMIPS:              4255.63
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              3072K
L3 cache:              8192K
NUMA node0 CPU(s):     0-15

Comment 2 Hai Huang 2013-03-06 13:27:27 UTC
Please feel freel to re-assign as appropriate.

Comment 3 Alon Levy 2013-08-08 13:49:24 UTC
The command line contains both vnc and spice, and uses cirrus. I would like to know:
1. does this happen when using only vnc, without spice?
2. is there any difference when using qxl or cirrus?

There is no qxl driver for win8, and I suspect it has nothing to do with spice either.

Alon

Comment 4 yunpingzheng 2013-08-12 06:01:46 UTC
hi Alon Levy

Now can not reproduce this bug:
kernel: 3.9.0-0.55.el7.x86_64
qemu-kvm: qemu-img-1.5.1-2.el7.x86_64

Comment 5 Alon Levy 2013-08-12 08:02:33 UTC
Thanks Yun Ping Zheng.

Based on your comment (comment 4) I'm closing as CURRENT_RELEASE (it was either that or INSUFFICIENT_DATA) with 'fixed in' of 1.5.1-2.el7 (btw you said qemu-kvm but copy pasted a qemu-img version string - but since they have the same version and release, it's good enough).

Alon