Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 696066

Summary: guest's monitor wont work after resume from s3
Product: Red Hat Enterprise Linux 6 Reporter: Xiaoqing Wei <xwei>
Component: qemu-kvmAssignee: Gleb Natapov <gleb>
Status: CLOSED WONTFIX QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: juzhang, knoel, kraxel, michen, mkenneth, tburke, virt-maint
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: 2011-04-13 13:28:27 UTC Type: ---
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
display is no work none

Description Xiaoqing Wei 2011-04-13 07:57:13 UTC
Created attachment 491673 [details]
display is no work

Description of problem:
after resume from S3 ,guest's display cant work normally
pls see attached snapshot
Version-Release number of selected component (if applicable):
vgabios-0.6b-3.6.el6.noarch

How reproducible:
100%

Steps to Reproduce:
1.start guest using default vga type:
qemu-kvm -name xp -monitor stdio -drive file='winXP-32-virtio.qcow2',if=none -device ide-drive -device rtl8139 -netdev tap -m 4096 -smp 2,cores=1,threads=1,sockets=2  -cpu cpu64-rhel6,+sse2,+x2apic -spice port=8000,disable-ticketing  -rtc base=localtime,clock=host,driftfix=none -M rhel6.1.0 -boot c   -usbdevice tablet -enable-kvm


2.do s3 and wait for it resumed
3.
  
Actual results:
guest display wont work ,please see attached snapshots.

Expected results:
guest displays normally after resume from S3.

Additional info:
host:
kernel-2.6.32-130.el6.x86_64
qemu-kvm-0.12.1.2-2.156.el6.x86_64
vgabios-0.6b-3.6.el6.noarch
seabios-0.6.1.2-3.el6.x86_64

processor	: 3
vendor_id	: GenuineIntel
cpu family	: 6
model		: 26
model name	: Intel(R) Xeon(R) CPU           E5504  @ 2.00GHz
stepping	: 5
cpu MHz		: 1596.000
cache size	: 4096 KB
RAM 12G


guest:WinXP-32

Comment 2 Dor Laor 2011-04-13 13:12:10 UTC
Is this a blocker? What happens if you restart X in the guest or move the windows?

Comment 3 Gleb Natapov 2011-04-13 13:28:27 UTC
Knone issue. No plans to fix it.

Comment 4 Xiaoqing Wei 2011-04-14 02:34:17 UTC
(In reply to comment #2)
> Is this a blocker? What happens if you restart X in the guest or move the
> windows?



have test rhel6-32 guest,do not trigger this bug.


but Win guest: move windows does not help anything.