Bug 1654732
| Summary: | VIR_DOMAIN_EVENT_SUSPENDED_POSTCOPY is never used in postcopy migration [rhel-7.6.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | RAD team bot copy to z-stream <autobot-eus-copy> |
| Component: | libvirt | Assignee: | Jiri Denemark <jdenemar> |
| Status: | CLOSED ERRATA | QA Contact: | Fangge Jin <fjin> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.6 | CC: | fjin, jdenemar, lizhu, mtessun, smoroney, xuzhang, yafu, yalzhang, yanqzhan |
| Target Milestone: | rc | Keywords: | Reopened, ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | libvirt-4.5.0-10.el7_6.4 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, the libvirt daemon did not recognize when QEMU switched a migration to post-copy mode. As a consequence, the statistics of a completed migration were incorrect, or libvirt tried to resume the domain on the source host if the migration failed during post-copy mode. This update improves the detection of post-copy mode. As a result, the post-copy migration statistics are accurate, and libvirt does not attempt to resume a partially-migrated domain.
|
Story Points: | --- |
| Clone Of: | 1647365 | Environment: | |
| Last Closed: | 2019-01-29 17:25:03 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: | 1647365 | ||
| Bug Blocks: | |||
|
Description
RAD team bot copy to z-stream
2018-11-29 14:57:54 UTC
Verified with: qemu-kvm-rhev-2.12.0-19.el7_6.2.x86_64 libvirt-4.5.0-10.virtcov.el7_6.4.x86_64 Steps are same as comment 4-8 of bug 1649169 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. https://access.redhat.com/errata/RHBA-2019:0197 |