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.
I'd recommend extending the scope of this to cover the full scope of the (not well documented) libvirt-guests service
including /etc/sysconfig/libvirt-guests configurations, etc.
libvirt-guests won't be run to shutdown guests if the host is "stuck" or "powered off" as suggested in the introduction to this note - it will only shutdown the guests if the host is shutdown properly.
Also you had asked (in email I think) if the file that needs to be edited is on the host or the guest - it is on the host.
Beyond that, probably someone with a better knowledge of the libvirt-guests service should look over your addition. Cole - weren't you the original author?
(In reply to Laine Stump from comment #6)
> libvirt-guests won't be run to shutdown guests if the host is "stuck" or
> "powered off" as suggested in the introduction to this note - it will only
> shutdown the guests if the host is shutdown properly.
>
> Also you had asked (in email I think) if the file that needs to be edited is
> on the host or the guest - it is on the host.
>
> Beyond that, probably someone with a better knowledge of the libvirt-guests
> service should look over your addition. Cole - weren't you the original
> author?
Original author was Jiri
Step 2 should rather be:
2. Start the libvirt-guests service
If you have not started the service, start the libvirt-guests service.
That is, if the service has already been started, it should not be restarted because stopping the service would cause shutdown of all running domains.