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 870708 - win7 sp1 guest need to login again when resume from doing S3/S4
Summary: win7 sp1 guest need to login again when resume from doing S3/S4
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-28 05:34 UTC by Sibiao Luo
Modified: 2012-10-30 10:07 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-30 10:07:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Screenshot-Resume form do S3. (466.50 KB, image/png)
2012-10-28 05:34 UTC, Sibiao Luo 		no flags Details
View All

Description Sibiao Luo 2012-10-28 05:34:18 UTC 
Description of problem:
Boot a win7 sp1 64bit guest and then do S3, it need to login again when resume it. 

Version-Release number of selected component (if applicable):
host info:
# uname -r && rpm -q qemu-kvm
2.6.32-335.el6.x86_64
qemu-kvm-0.12.1.2-2.331.el6.x86_64
guest info:
win7 sp1 64bit
virtio-win-prewhql-0.1-41

How reproducible:
always

Steps to Reproduce:
1.sync the host time with ntp server.
# ntpdate $ntp_server
2.boot guest with " -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0"
3.sync guest system clock same to host.
4.Suspend guest to memory inside guest:
click Star ---> sleep
5.Wakeup guest by send "system_wakeup" qemu command.
  
Actual results:
after the step 5, it resume to login interface which is not the same desktop as before do S3. I will attach the detail login interface (Screenshot-Resume form do S3).

Expected results:
resume to the desktop as before S3 successfully. 

Additional info:
# /usr/libexec/qemu-kvm -M rhel6.4.0 -cpu SandyBridge -enable-kvm -m 2048 -smp 4,sockets=2,cores=2,threads=1 -usb -device usb-tablet,id=input0 -name sluo_acpi -uuid 990ea161-6b67-47b2-b803-19fb01d30d30 -rtc base=localtime,clock=host,driftfix=slew -device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x3 -chardev socket,id=channel1,path=/tmp/helloworld1,server,nowait -device virtserialport,chardev=channel1,name=com.redhat.rhevm.vdsm,bus=virtio-serial0.0,id=port1 -chardev socket,id=channel2,path=/tmp/helloworld2,server,nowait -device virtserialport,chardev=channel2,name=com.redhat.rhevm.vdsm,bus=virtio-serial0.0,id=port2 -drive file=/home/windows_7_ultimate_sp1_x64.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio-disk0,id=virtio_drive,bus=pci.0,addr=0x4,bootindex=1 -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup -device virtio-net-pci,netdev=hostnet0,id=virtio-net-pci0,mac=08:2E:5F:0A:0D:B1,bus=pci.0,addr=0x5 -device usb-ehci,id=ehci,addr=0x6 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -spice port=5931,disable-ticketing,seamless-migration=on -vga qxl -global qxl-vga.vram_size=67108864 -device intel-hda,id=sound0,bus=pci.0,addr=0x8 -drive file=/home/my-data-disk.qcow2,if=none,id=drive-ide0-0-0,format=qcow2,cache=none,werror=stop,rerror=stop -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -serial unix:/tmp/ttyS0,server,nowait -qmp tcp:0:4444,server,nowait -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -boot menu=on -monitor stdio
Comment 1 Sibiao Luo 2012-10-28 05:34:59 UTC 
Created attachment 634431 [details]
Screenshot-Resume form do S3.
Comment 2 Sibiao Luo 2012-10-28 05:43:08 UTC 
(In reply to comment #0)
> Description of problem:
> Boot a win7 sp1 64bit guest and then do S3, it need to login again when
> resume it. 
> 
I tried the 'spicec -h $ip_addr -p $port'  and 'remote-viewer spice://$ip_addr:$port', both of them can hit this issue.
Comment 4 Sibiao Luo 2012-10-28 07:51:38 UTC 
(In reply to comment #0)
> Description of problem:
> Boot a win7 sp1 64bit guest and then do S3, it need to login again when
> resume it. 

Do S4, it also hit this issue.
Comment 5 Mike Cao 2012-10-30 02:32:21 UTC 
I don't think it is bug 

Pls do following configurations and retest.

1.click Start -> Control Panel -> Power Options ，“Require a password on wakeup”--->make "Don’t require a password” checked in the "Password protection on wakeup fields" ---> save changes
2.click Start -> Control Panel -> Presonalization,-->“Screen Saver”，in the “Screen Saver Settings”，uncheck “On resume, display logon screen” ---> apply -->OK
Comment 6 Sibiao Luo 2012-10-30 07:43:55 UTC 
(In reply to comment #5)
> I don't think it is bug 
> 
> Pls do following configurations and retest.
> 
> 1.click Start -> Control Panel -> Power Options ，“Require a password on
> wakeup”--->make "Don’t require a password” checked in the "Password
> protection on wakeup fields" ---> save changes
> 2.click Start -> Control Panel -> Presonalization,-->“Screen Saver”，in the
> “Screen Saver Settings”，uncheck “On resume, display logon screen” ---> apply
> -->OK

yes, make sense. it can resume to the desktop as before S3/S4 successfully as your indication.
Note You need to log in before you can comment on or make changes to this bug.