Hi,
thank you for your report and already identifying some related commits.
I was testing similar things and for me it worked, so I checked what we
do differently.
I found that we called it differently.
I always found the decisions weird to start it in precopy but with postcopy
logic enabled.
To then use migrate-postcopy from another shell to change the mode.
IMHO that is far too fragile and unreproducible when this switch hits and what
it does in that case.
I very much prefer the documented --postcopy-after-precopy which you can
combine to let it swicth automatically after the first precopy passed.
Not to nack the patches you reported, but to see if the postcopy migration
actually works in your environment could you run it like this in your env?:
virsh migrate --live --postcopy --postcopy-after-precopy avocado-vt-vm1-Bala
qemu+ssh://9.40.192.182/system
I'd be interested if at least that works - it does for me on x86 and a
4.4 kernel.
** Changed in: libvirt (Ubuntu)
Status: New => Incomplete
** Changed in: libvirt (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620908
Title:
[Ubuntu1610][Libvirt] Postcopy migration with --postcopy fails with
error: internal error: early end of file from monitor
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1620908/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
