Bug 1283696
Summary: | [vdsm] Can't live migrate a VM from 3.6 cluster to 3.5 cluster in 3.6 engine | ||
---|---|---|---|
Product: | [oVirt] vdsm | Reporter: | Jiri Belka <jbelka> |
Component: | General | Assignee: | Dan Kenigsberg <danken> |
Status: | CLOSED WORKSFORME | QA Contact: | Aharon Canan <acanan> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.16.29 | CC: | bugs, gklein, jbelka |
Target Milestone: | --- | Flags: | rule-engine:
planning_ack?
rule-engine: devel_ack? rule-engine: testing_ack? |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | virt | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-11-26 12:46:09 UTC | Type: | Bug |
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: | |||
Bug Blocks: | 1285700 |
Description
Jiri Belka
2015-11-19 15:34:16 UTC
1. Why is this a low severity bug? 2. Are we sure it's not a QEMU bug? 2015-11-19T15:07:06.995285Z qemu-kvm: error while loading state section id 2(ram) 2015-11-19T15:07:06.995594Z qemu-kvm: load of migration failed: Input/output error 3. Does it happen all the time? (In reply to Yaniv Kaul from comment #2) > 1. Why is this a low severity bug? There is bold red warning that live migration during clusters can cause unexpected behaviour. > 2. Are we sure it's not a QEMU bug? > 2015-11-19T15:07:06.995285Z qemu-kvm: error while loading state section id > 2(ram) > 2015-11-19T15:07:06.995594Z qemu-kvm: load of migration failed: Input/output > error It is engine which instructs libvirt which instructs qemu about how to construct final command. > 3. Does it happen all the time? Only for this specific VM. Anyway, there's strange traceback. Raising severity, cause this was well tested for 3.5, and should work just fine for 3.6 can't reproduce anymore on vdsm-4.17.11-0.el7ev.noarch (3.6.0-22) -> vdsm-4.16.30-1.el7ev.x86_64 (3.5.6) while using engine from 3.6.0-22. |