kvm migration fails with large-memory VMs
Bug #362013 reported by
Brent Nelson
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
QEMU |
Fix Released
|
High
|
Unassigned | ||
kvm (Ubuntu) |
Won't Fix
|
Low
|
Unassigned | ||
qemu-kvm (Ubuntu) |
Fix Released
|
Low
|
Dustin Kirkland |
Bug Description
Binary package hint: kvm
In Hardy, an attempt to migrate a 6GB VM results in:
migration: memory size mismatch: recv 2168467456 mine 2168467456
migrate_incoming_fd failed (rc=232)
Migration failed rc=232
I ran across a thread which suggests that this is a known KVM bug that has since been fixed (when Qemu fixed it in their source, and KVM pulled in the new code):
http://
I'm planning to test the KVM 84 Hardy backport to see if it is fixed there...
Changed in kvm (Ubuntu): | |
assignee: | nobody → kirkland |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in qemu: | |
importance: | Undecided → High |
milestone: | none → 0.11.0 |
status: | New → Confirmed |
To post a comment you must log in.
I just tried with the Hardy PPA KVM:84. It doesn't have this migration issue, and migration claims to go to completion, however:
1) The first time I tried migrating, after migration completed, the guest VM, also running Hardy, had done a fresh boot.
2) I tried migrating again, this time with a vncviewer attached to the destination. The vncviewer went away on migration completion, but when I started the vncviewer again, the guest VM, now on the destination, had panicked. See screenshot, attached, for what I was able to see of the kernel panic.
PS A minor nuisance with KVM:84, as packaged: if you don't specify script= in your -net options, kvm looks for /etc/kvm-ifup, which does not exist, rather than /etc/kvm/kvm-ifup.