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.
Description of problem:
Qemu monitor "system_powerdown" command fail to power down guest, th VM will be in paused (suspended) status, but cann't to wakeup successully via system_wakeup command.
If run 'poweroff' in guest terminal which can power down guest succefully.
Version-Release number of selected component (if applicable):
host info:
3.10.0-60.el7.x86_64
qemu-kvm-rhev-1.5.3-21.el7.x86_64
seabios-1.7.2.2-4.el7.x86_64
guest info:
3.10.0-60.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1.boot up a rhel7.0 guest.
2.login guest using root user.
3.send "system_powerdown" qemu monitor command.
Actual results:
after step 3, the guest screen will be in blank screen and fail to powerdown, the guest kernel message output nothing after send "system_powerdown". check the VM status is paused(suspended) but fail to wakeup via 'system_wakeup'.
(qemu) system_powerdown
(qemu) info status
VM status: paused (suspended)
(qemu) cont
(qemu) info status
VM status: paused (suspended)
(qemu) system_wakeup
(qemu) info status
VM status: running
Expected results:
it should power down guest successfully.
Additional info:
# /usr/libexec/qemu-kvm -M pc -S -cpu SandyBridge -enable-kvm -m 2048 -smp 4,sockets=2,cores=2,threads=1 -no-kvm-pit-reinjection -usb -device usb-tablet,id=input0 -name sluo -uuid 990ea161-6b67-47b2-b803-19fb01d30d30 -rtc base=localtime,clock=host,driftfix=slew -device virtio-serial-pci,id=virtio-serial0,max_ports=16,vectors=0,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=iscsi://10.66.90.100:3260/iqn.2001-05.com.equallogic:0-8a0906-4c41f7d03-453f49b421052a57-s2-sluo-270305-1/0,if=none,id=drive-system-disk,cache=none,format=raw,aio=native,werror=stop,rerror=stop,discard=on -iscsi id=iqn0 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4,num_queues=4 -device scsi-block,drive=drive-system-disk,bus=scsi0.0,id=libiscsi-system-disk,bootindex=1 -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup -device rtl8139,netdev=hostnet0,id=rtl8139-net-pci0,mac=00:01:02:B6:40:21,bus=pci.0,addr=0x5 -device virtio-balloon-pci,id=ballooning,bus=pci.0,addr=0x6 -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 -vnc :1 -spice disable-ticketing,port=5931 -monitor stdio
Also tried the rhel6.5 guest in the host with the same testing that did not reproduce this issue, it will prompt a dialog box for selection buttons: suspend, hibernate, restart, cancel and shut down.
According to above, this issue is not qemu-kvm issue, so move to gnome-session component. Please correct me if any mistake, thanks.
OS tree: RHEL-7.0-20131127.1
# rpm -qa | grep gnome-session
gnome-session-xsession-3.8.4-2.el7.x86_64
gnome-session-3.8.4-2.el7.x86_64
Best Regards,
sluo
(In reply to Matthias Clasen from comment #2)
> I don't see anything in this bug that implicates gnome-session
Please refer to bug 907711#c7 and bug 980692, please help to move to the right component if possible, thanks in advance.
Best Regards,
sluo
Comment 4Ray Strode [halfline]
2014-01-29 21:14:18 UTC
So the issue here is that in rhel7 the power off button is assigned to "suspend the machine" where in rhel6 the power off button was assigned to "pop up a dialog and ask the user".
You can verify this is happening by looking at the Status in the hardware details tab of virt-manager. it says "suspended" instead of "running". I don't know how to resume. Suspend/Resume seem to be separate concepts from the pause button.
This is tweakable to make power off do a shutdown by running:
gsettings set org.gnome.settings-daemon.plugins.power button-power "shutdown"
though maybe we should shutdown instead of suspend if running in a VM regardless of that setting, not sure.
reassigning to g-s-d