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.
Description of problem:
several guest life cycle results are not expect
Version-Release number of selected component (if applicable):
libvirt-0.10.2-18.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
This comes from Jiri's reply:
>
> Hi, Jiri
>
> I have a question about guest lifecycle control and want your help.
> Many content of element not works, i don't know if i use it in a wrong way.
Well, not all life cycle controls are applicable to all hypervisors.
What works for Xen may not even make sense for qemu. However, I suspect
we failed to document it properly.
> #virsh shutdown aaa
>
> <on_poweroff>destroy</on_poweroff>
> Domain aaa shut off and not power up again. -----> expect
Good.
> <on_poweroff>restart</on_poweroff>
> should power up again but not. -----> not expect
This looks like a bug in qemu driver.
> <on_poweroff>preserve</on_poweroff>
> guest poweroff, nothing happend. ----> how to use it ?
This makes sense for Xen but I doubt it is doable with qemu. However, we
should probably tell that when a user tries to create such domain.
> <on_poweroff>rename-restart</on_poweroff>
> guest poweroff, and should boot up again with newname? but it's only powered off. --->not expect
Does not make sense for qemu. Again, we should not silently ignore this
option.
> #virsh reboot aaa
>
> <on_reboot>destroy</on_reboot>
> guest not boot up again. it works.
Good.
> <on_reboot>restart</on_reboot>
> guest boot up again. it works.
Good.
> <on_reboot>preserve</on_reboot>
> guest poweroff, nothing happend. -----> how to use it ?
Likely not doable but the result is bad anyway. We take it as "destroy",
which is wrong.
> <on_reboot>rename-restart</on_reboot>
> guest poweroff, and should boot up again with newname. but it's only powered off. --->not expect
The same as with on_poweroff.
Actual results:
As steps
Expected results:
As steps
Additional info:
> should power up again but not. -----> not expect
This looks like a bug in qemu driver.
I'll attach libvirt debug log for this.
We decided not to rebase libvirt in RHEL 6.5 to avoid stability issues
we faced in 6.4. This bug has already been fixed upstream but it is
considered unsuitable for backporting to RHEL 6.5 because at least one
of the following conditions is met:
- this bug requires new API(s), which we cannot introduce without
rebasing libvirt
- the patches required to address this bug are complex or invasive
causing the backport to be too risky
- this bug is not important enough to justify backporting non-trivial
patches for it
Thus I'm pushing this bug to RHEL 6.6 (and setting Upstream keyword to
indicate we have patches upstream) for now. If you don't agree with
this resolution, please, give us reasons which you think are strong
enough for us to reevaluate the decision not to backport patches for
this bug.
Comment 9RHEL Program Management
2014-04-04 20:58:46 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.