From: jz4@rice.edu
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3 v5] Live migration without shared storage
Date: Tue, 16 Mar 2010 14:57:54 -0500 [thread overview]
Message-ID: <20100316145754.17202atrkf8w4udc@webmail.rice.edu> (raw)
[Qemu-devel] [PATCH 0/3 v5] Live migration without shared storage
I tested the live migration without shared storage for the patch of
the block migration. It succeeds for several times but sometimes it
fails. I used the qemu-kvm-0.12.3 and the kvm 2.6.33 module on the
ubuntu latest version.
In the failure case, i can see the shell on the destination site
showed the correct content for the migrated VM, but it just hanged
there without any response to the mouse and the keyboard. I can see it
prints "migration completes" twice. Is it a bug or did I do anything
wrong?
Another question is about the command line for the destination site.
For memory
migration, i will start the vm based on the shared image. For block
migration, there is no shared image. What i did is creating an empty
image with the same format (e.g. raw or qcow2) as the source migrated
VM. Is it correct or it doesn't matter which format it is in the
destination site?
For the memory migration, it emphasizes that the path for the VM
should be the same as the source path. But for the block migration, i
change the destination path to a different one and it also works. Does
that mean path is not important now?
The command line must be "migrate -d -b ..". If it is "-b -d", the
qemu-monitor doesn't understand. Does that intend to be designed like
this or will it be modified in the future?
Thanks!
-Jie
next reply other threads:[~2010-03-16 19:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 19:57 jz4 [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-11-02 13:40 [Qemu-devel] [PATCH 0/3 v5] Live migration without shared storage lirans
2009-11-02 18:47 ` Avi Kivity
2009-11-03 9:40 ` Liran Schour
2009-11-03 10:38 ` Avi Kivity
2009-11-03 7:33 ` Liran Schour
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100316145754.17202atrkf8w4udc@webmail.rice.edu \
--to=jz4@rice.edu \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).