From: Stefan Hajnoczi <stefanha@gmail.com>
To: Yaodong Yang <yaodong.yangy@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] vm live storage migration approach.
Date: Fri, 30 Jan 2015 20:37:40 +0000 [thread overview]
Message-ID: <CAJSP0QUsfCotP2GE7gDnAsvLyhe4hyZdUirp7wE60CULXD+y9Q@mail.gmail.com> (raw)
In-Reply-To: <CAJ3ZQbMVMwtGUuYtr8-=xynhdkP=6vWGZqqdbu3bui95iUZ2eg@mail.gmail.com>
On Fri, Jan 30, 2015 at 8:13 PM, Yaodong Yang <yaodong.yangy@gmail.com> wrote:
> An follow up questions.
>
> Suppose I have a running VM with two virtual disks, I would like to migrate
> the vm from host A to host B. Both host A and host B have their own isolated
> storage devices. Is there anyway to migrate the vm's memory, two virtual
> disk images and other states together from host A to host B? Can
> drive_mirror command itself finish this job? I noticed that drive_mirror
> only mirror for one virtual disk and require both the source and destination
> share the same storage namespace. I do not know how to migrate the whole VM
> (memory, storage, network ) together from host A to host B, given that host
> A and host B have NO shared storage resource.
>
> Could you show me an example, if possible?
>
> I know "migrate -b" works well for this purpose. But the downside is
> "migrate -b" does not mirror Write Requests to both host A and host B during
> migration. In this case, "migrate -b" has a higher VM downtime during the
> migration.
Hi Yaodong,
The answers to these questions are in libvirt's source code. It
orchestrates live migration between two hosts.
Multiple independent drive_mirror jobs can run. That's how you handle
multiple disks.
The regular migrate command (without -b) can be used if drive_mirror
is in place and fully synced.
Libvirt sets up an NBD server on the destination host. The source
host runs drive_mirror to copy over the contents of the disk images.
Once the drive_mirror command has completed syncing data the regular
'migrate' command can be used to send device state and RAM over to the
destination host.
See qemuMigrationDriveMirror() in libvirt.
migrate -b is a legacy feature that is being replaced by drive_mirror.
Stefan
next prev parent reply other threads:[~2015-01-30 20:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 16:25 [Qemu-devel] vm live storage migration approach Yaodong Yang
2015-01-30 19:21 ` Eric Blake
2015-01-30 20:13 ` Yaodong Yang
2015-01-30 20:37 ` Stefan Hajnoczi [this message]
2015-01-30 20:39 ` Yaodong Yang
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=CAJSP0QUsfCotP2GE7gDnAsvLyhe4hyZdUirp7wE60CULXD+y9Q@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=yaodong.yangy@gmail.com \
/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).