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 994394 - Qemu monitor "system_powerdown" command does not work for ubuntu.12.04 guest
Summary: Qemu monitor "system_powerdown" command does not work for ubuntu.12.04 guest
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.5
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: 2013-08-07 08:07 UTC by ShupingCui
Modified: 2016-05-16 04:06 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-14 06:07:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description ShupingCui 2013-08-07 08:07:11 UTC
Description of problem:
Qemu monitor "system_powerdown" command does not work for ubuntu.12.04 guest

Version-Release number of selected component (if applicable):
Host:
# uname -r
2.6.32-402.el6.x86_64
# rpm -q qemu-kvm-rhev
qemu-kvm-rhev-0.12.1.2-2.382.el6.x86_64

Guest:
# uname -r
3.2.0-23-generic

How reproducible:
100%

Steps to Reproduce:
1. boot the ubuntu guest
/usr/libexec/qemu-kvm \
    -name 'virt-tests-vm1' \
    -nodefaults \
    -drive file='/root/staf-kvm-devel/autotest-devel/client/tests/virt/shared/data/images/ubuntu-12.04-server-64-virtio.qcow2',index=0,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,bootindex=0 \
    -device virtio-net-pci,netdev=idxlu4ZI,mac='9a:01:02:03:04:05',bus=pci.0,addr=0x3,id='idOZ6MbI' \
    -netdev tap,id=idxlu4ZI,vhost=on \
    -m 4096 \
    -smp 2,maxcpus=2,cores=1,threads=1,sockets=2 \
    -cpu 'Opteron_G3' \
    -M rhel6.5.0 \
    -device AC97,addr=0x6 \
    -vnc :0 \
    -vga cirrus \
    -global qxl-vga.vram_size=33554432 \
    -rtc base=utc,clock=host,driftfix=slew  \
    -boot order=cdn,once=c,menu=off   \
    -no-kvm-pit-reinjection \
    -enable-kvm \
    -monitor stdio

2. execute "system_powerdown" command after the guest boot up
(qemu) system_powerdown 
wait 1 min
(qemu) info status 
VM status: running

3.

Actual results:
guest cannot shutdown

Expected results:
guest shutdown successful

Additional info:
1. tested qemu-kvm-rhev-0.12.1.2-2.384.el6.x86_64, hit same problem
2. tested rhel guest, guest shutdown successful after execute "system_powerdown" command

Comment 2 Xiaoqing Wei 2013-08-07 09:04:02 UTC
Hi Shuping,

pls update rhel guest behaviour here and, set the priority/serverity,

Thanks
Xiaoqing.

Comment 5 Amit Shah 2013-08-08 06:11:44 UTC
The best way to check a guest's behaviour for acpi shutdown is to boot the same OS on a physical host, and in the same state (i.e. logged into desktop or just waiting at login screen), hit the power button and see what happens.  If the same behaviour is shown when the OS is running as a guest, we don't have any problem.

However, in general, for shutdown, reboot, etc., to work, we have to rely on the guest agent.

Comment 6 Suqin Huang 2013-08-08 06:56:20 UTC
scui,
According to comment5, can you try it on host, can provide the screenshort where the guest stay.

Comment 7 ShupingCui 2013-08-14 06:07:11 UTC
According to comment3 and comment5, not found acpi module in guest. Qemu monitor "system_powerdown" command works fine when i install the acpi module. So it's not a bug, close it.


Note You need to log in before you can comment on or make changes to this bug.