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:
Try to shutdown rhel3u9 i386 guest via virsh command, but guest have no any response.

Version-Release number of selected component (if applicable):
libvirt-0.8.1-3.el6.x86_64
qemu-kvm-0.12.1.2-2.53.el6.x86_64
# uname -a
Linux dhcp-66-70-178.nay.redhat.com 2.6.32-24.el6.x86_64 #1 SMP Mon May 3 20:30:40 EDT 2010 x86_64 x86_64 x86_64 GNU/Li

How reproducible:
Always

Steps to Reproduce:
1. Install a guest with RHEL3U9 i386 release via virt-manager.
2. Log into guest to check guest is working fine.
3. Issuing "virsh shutdown" command to gracefully shutdown rhel3u9 i386 guest.
  
Actual results:
# virsh list --all
 Id Name                 State
----------------------------------
 17 rhel3u9_i386_test1   running
# virsh shutdown rhel3u9_i386_test1
Domain rhel3u9_i386_test1 is being shutdown

But found that guest has no any response using virt-manager, guest still running happily.

Expected results:
"virsh shutdown" command should racefully shutdown rhel3u9 i386 guest successfully.

Additional info:
If guest is rhel3u9 x86_64, "virsh shutdown" command racefully shutdown guest successfully.

The RHEL-3  OS does not support ACPI power events. The KVM shtudown process uses ACPI power events to shutdown the guest. Thus it is impossible for RHEL3 to do a controlled shutdown.