Bug 874235
| Summary: | libvirt: no event is sent to vdsm in case vm is terminated on signal 15 after hibernate failure | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Chris Pelland <cpelland> |
| Component: | libvirt | Assignee: | Michal Privoznik <mprivozn> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 6.3 | CC: | acathrow, cpelland, dallan, dron, dyasny, dyuan, hateya, jturner, mburns, mprivozn, mzhan, pm-eus, rwu, whuang, zpeng |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | libvirt-0.9.10-21.el6_3.6 | Doc Type: | Bug Fix |
| Doc Text: |
Cause:
Certain operations in libvirt can be done only when domain is paused so its memory doesn't change, e.g. saving onto disk. Otherwise it may lead to data corruption. In order to prevent this, libvirt translates domain to paused state itself whenever needed. The domain should be resumed then ASAP.
Consequence:
If the resuming operation failed, management application wasn't notified since no event was sent.
Fix:
The new VIR_DOMAIN_EVENT_SUSPENDED_API_ERROR event was invented. This event is fired every time the resuming operation fails.
Result:
Management applications can keep closer track of domain state and act accordingly.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-11-22 09:40:24 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 866388 | ||
| Bug Blocks: | |||
|
Description
Chris Pelland
2012-11-07 18:41:16 UTC
Moving to POST: http://post-office.corp.redhat.com/archives/rhvirt-patches/2012-November/msg00079.html verified on libvirt-0.9.10-21.el6_3.6 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-1484.html |