Bug 1313606

Summary:	Cannot boot graphic interface both on spice or vnc but serial can work after resume from s3 and s4
Product:	Red Hat Enterprise Linux 7	Reporter:	xiywang
Component:	qemu-kvm-rhev	Assignee:	Ademar Reis <areis>
Status:	CLOSED WONTFIX	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.2	CC:	chayang, juzhang, knoel, michen, qzhang, 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:	2016-03-08 18:57:48 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 xiywang 2016-03-02 03:00:54 UTC

Description of problem:
When recovering from s4 or s3 test, cannot boot graphic interface both on spice or vnc while only serial can work.
After waitting a few minutes in serial, call trace appread.

Version-Release number of selected component (if applicable):
host and guest kernel:
3.10.0-351.el7.x86_64
host qemu-kvm:
qemu-kvm-rhev-2.3.0-31.el7_2.8.x86_64

How reproducible:
100%

Steps to Reproduce:
1. boot a guest
/usr/libexec/qemu-kvm -name RHEL7.3-Guest -cpu SandyBridge -m 4G -smp 2 \

-drive id=drive_image1,if=none,cache=none,snapshot=off,format=qcow2,file=/home/virtkvmqe-x86-cpu-hotplug.qcow2 -device virtio-blk-pci,id=image1,drive=drive_image1 \

-netdev tap,id=hostnet0,vhost=on,script=/etc/ovs-ifup,downscript=/etc/ovs-ifdown -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:55:01:77:89:40 \

 -device qxl-vga,id=video0 -spice port=5900,disable-ticketing \

-monitor stdio -qmp tcp:0:4444,server,nowait -serial unix:/tmp/console,server,nowait \

-global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -vnc :1

2. do s4 or s3 in guest
echo disk > /sys/power/state
or
echo mem > /sys/power/state

3. resume

Actual results:
only serial can work
guest GUI doesn't work
guest show call trace

Expected results:
both vnc, spice and serial should work fine

Additional info:

1.RHEL7.2 release version qemu-kvm-rhev-2.3.0-31.el7 hit the same issue

2.get call trace in guest:
#dmesg
...
[  199.625945] INFO: task kworker/0:1:30 blocked for more than 120 seconds.
[  199.627056] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  199.628293] kworker/0:1     D 0000000000000246     0    30      2 0x00000000
[  199.628388] Workqueue: events qxl_fb_work [qxl]
[  199.628391]  ffff880139617bb8 0000000000000046 ffff880139475c00 ffff880139617fd8
[  199.628393]  ffff880139617fd8 ffff880139617fd8 ffff880139475c00 ffff8801397e2700
[  199.628396]  ffffc9000072d00c ffff8801397e2720 ffff880139617c48 0000000000000246
[  199.628399] Call Trace:
[  199.628405]  [<ffffffff816438d9>] schedule+0x29/0x70
[  199.628411]  [<ffffffffa0125e35>] qxl_ring_push+0x255/0x2a0 [qxl]
[  199.628414]  [<ffffffff810a8440>] ? wake_up_atomic_t+0x30/0x30
[  199.628419]  [<ffffffffa0125eed>] qxl_push_command_ring_release+0x6d/0x90 [qxl]
[  199.628424]  [<ffffffffa0127748>] qxl_draw_opaque_fb+0x2a8/0x3c0 [qxl]
[  199.628428]  [<ffffffffa0123ee2>] qxl_fb_dirty_flush+0x1a2/0x260 [qxl]
[  199.628432]  [<ffffffffa0123fb9>] qxl_fb_work+0x19/0x20 [qxl]
[  199.628435]  [<ffffffff8109ef4b>] process_one_work+0x17b/0x470
[  199.628437]  [<ffffffff8109fd1b>] worker_thread+0x11b/0x400
[  199.628439]  [<ffffffff8109fc00>] ? rescuer_thread+0x400/0x400
[  199.628442]  [<ffffffff810a744f>] kthread+0xcf/0xe0
[  199.628444]  [<ffffffff810a7380>] ? kthread_create_on_node+0x140/0x140
[  199.628446]  [<ffffffff8164e8d8>] ret_from_fork+0x58/0x90
[  199.628448]  [<ffffffff810a7380>] ? kthread_create_on_node+0x140/0x140
[  319.627936] INFO: task kworker/0:1:30 blocked for more than 120 seconds.
[  319.629014] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  319.630213] kworker/0:1     D 0000000000000246     0    30      2 0x00000000
[  319.630228] Workqueue: events qxl_fb_work [qxl]
[  319.630230]  ffff880139617bb8 0000000000000046 ffff880139475c00 ffff880139617fd8
[  319.630233]  ffff880139617fd8 ffff880139617fd8 ffff880139475c00 ffff8801397e2700
[  319.630235]  ffffc9000072d00c ffff8801397e2720 ffff880139617c48 0000000000000246
[  319.630238] Call Trace:
[  319.630244]  [<ffffffff816438d9>] schedule+0x29/0x70
[  319.630249]  [<ffffffffa0125e35>] qxl_ring_push+0x255/0x2a0 [qxl]
[  319.630253]  [<ffffffff810a8440>] ? wake_up_atomic_t+0x30/0x30
[  319.630258]  [<ffffffffa0125eed>] qxl_push_command_ring_release+0x6d/0x90 [qxl]
[  319.630262]  [<ffffffffa0127748>] qxl_draw_opaque_fb+0x2a8/0x3c0 [qxl]
[  319.630266]  [<ffffffffa0123ee2>] qxl_fb_dirty_flush+0x1a2/0x260 [qxl]
[  319.630271]  [<ffffffffa0123fb9>] qxl_fb_work+0x19/0x20 [qxl]
[  319.630273]  [<ffffffff8109ef4b>] process_one_work+0x17b/0x470
[  319.630276]  [<ffffffff8109fd1b>] worker_thread+0x11b/0x400
[  319.630278]  [<ffffffff8109fc00>] ? rescuer_thread+0x400/0x400
[  319.630280]  [<ffffffff810a744f>] kthread+0xcf/0xe0
[  319.630282]  [<ffffffff810a7380>] ? kthread_create_on_node+0x140/0x140
[  319.630285]  [<ffffffff8164e8d8>] ret_from_fork+0x58/0x90
[  319.630287]  [<ffffffff810a7380>] ? kthread_create_on_node+0x140/0x140

Comment 2 Ademar Reis 2016-03-08 18:57:48 UTC

We do not support S3/S4, so I'm closing it as wontfix.