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 989996 - doc-feat-req-650-documentation required for how to shutdown guest via libvirt-guests
Summary: doc-feat-req-650-documentation required for how to shutdown guest via libvirt...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Virtualization_Administration_Guide
Version: 6.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Laura Novich
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks: 999483
TreeView+ depends on / blocked
 
Reported: 2013-07-30 08:58 UTC by Laura Novich
Modified: 2016-01-27 01:57 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 999483 (view as bug list)
Environment:
Last Closed: 2013-11-27 12:28:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 2 Andrew Cathrow 2013-07-30 15:04:09 UTC
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.

Comment 3 Laura Novich 2013-07-30 15:21:21 UTC
Will do a full evaluation of the libvirt-guests service

Comment 6 Laine Stump 2013-08-14 13:10:44 UTC
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?

Comment 7 Cole Robinson 2013-08-14 13:54:33 UTC
(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

Comment 8 Jiri Denemark 2013-08-15 12:22:42 UTC
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.

Comment 14 Laura Novich 2013-11-27 12:28:04 UTC
Closing as CURRENTRELEASE since this is now available in RHEL 6.5 GA.


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