Re: [libvirt] [PATCH 00/16 v5] Implement migration v3 protocol

On Tue, May 17, 2011 at 05:56:36PM +0800, Wen Congyang wrote: > At 05/16/2011 10:24 PM, Daniel P. Berrange Write: >> On Thu, May 12, 2011 at 05:04:36PM +0100, Daniel P. Berrange wrote: >>> An update of >>> >>> http://www.redhat.com/archives/libvir-list/2011-May/msg00605.html >>> >>> Changes in this series >>> >>> - Fix comments from previous review >>> - Rebase to latest GIT >>> >>> Also pullable from >>> >>> http://gitorious.org/~berrange/libvirt/staging/commits/migrate-locking-3 >>> >>> NB, this branch includes the migration + lock manager series >>> in one big set. >> >> I've pushed this series now. There will be a couple of follow up patches >> to add some further enhancements before next release. > > I test migration 3 times. libvirtd crashed twice and may be deadlock once. > I do not find the reason of the problem. > > Here is command line: > # virsh migrate --p2p --tunnelled vm1 qemu+tls://<dest OS>/system Is 'vm1' a transient, or persistent guest ?

I have identified a flaw with handling of transient guests, which has the same behaviour you describe. Persistent guests though are reliable unless the --undefine-source flag is set with virsh. Daniel