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.
Document URL: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/virtualization_deployment_and_administration_guide/sect-starting_suspending_resuming_saving_and_restoring_a_guest_virtual_machine-starting_a_defined_domain
Section Number and Name: 20.6. STARTING, RESUMING, AND RESTORING A VIRTUAL MACHINE
Describe the issue:
The section talks about options which can be used for guest shutdown/reboot with --mode .
I had a customer who tried these options but it failed with error, it did not work on my test machine too, gave errors like below:
~~~
[root@ ~]# virsh reboot test_qemu --mode initctl
error: Failed to reboot domain test_qemu
error: unsupported flags (0x4) in function qemuDomainReboot
[root@ ~]# virsh reboot test_qemu --mode signal
error: Failed to reboot domain test_qemu
error: unsupported flags (0x8) in function qemuDomainReboot
[root@ ~]# virsh reboot test_qemu --mode paravirt
error: Failed to reboot domain test_qemu
error: unsupported flags (0x10) in function qemuDomainReboot
[root@ ~]# virsh shutdown test_qemu --mode initctl
error: Failed to shutdown domain test_qemu
error: unsupported flags (0x4) in function qemuDomainShutdownFlags
[root@ ~]# virsh shutdown test_qemu --mode signal
error: Failed to shutdown domain test_qemu
error: unsupported flags (0x8) in function qemuDomainShutdownFlags
[root@ ~]# virsh shutdown test_qemu --mode paravirt
error: Failed to shutdown domain test_qemu
error: unsupported flags (0x10) in function qemuDomainShutdownFlags
~~~
Upon checking on the mail list we got below inputs:
~~~
libvirt's QEMU driver, used to manage KVM guests, only supports
the 'agent' and 'acpi' reboot modes because those are the ones QEMU
itself supports, so that's why customer is getting an error message when
trying to use any other mode.
The 'signal' and 'initctl' modes are used by the LXC driver.
~~~
So these details should be mentioned in the documentation.
Suggestions for improvement: add the details below in the documentation to get clarity on when to use these options: initctl,signal,paravirt,agent,acpi
~~~
libvirt's QEMU driver, used to manage KVM guests, only supports
the 'agent' and 'acpi' reboot modes because those are the ones QEMU
itself supports
The 'signal' and 'initctl' modes are used by the LXC driver.
~~~
Additional information: