qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: lirans@il.ibm.com
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3 v5] Live migration without shared storage
Date: Mon, 02 Nov 2009 20:47:34 +0200	[thread overview]
Message-ID: <4AEF2946.1030207@redhat.com> (raw)
In-Reply-To: <12571692252385-git-send-email-lirans@il.ibm.com>

On 11/02/2009 03:40 PM, lirans@il.ibm.com wrote:
> This series adds support for live migration without shared storage, means
> copy the storage while migrating. It was tested with KVM. Supports 2 ways
> to replicate the storage during migration:
> 1. Complete copy of storage to destination
> 2. Assuming the storage is cow based, copy only the allocated
> data, time of the migration will be linear with the amount of allocated
> data (user responsibility to verify that the same backend file reside
> on src and destination).
>
> Live migration will work as follows:
> (qemu) migrate -d tcp:0:4444 # for ordinary live migration
> (qemu) migrate -d blk tcp:0:4444 # for live migration with complete storage copy
> (qemu) migrate -d blk inc tcp:0:4444 # for live migration with incremental storage copy, storage is cow based.
>    

I'd like to see the syntax generalized.  For one, the guest may have 
several disks; an install image cdrom might be available as an nfs image 
but the main storage is local.  Secondly, there can be several levels of 
cow and we want to control which one we copy.

I'll leave the exact details to the qpeople, but if we can specify a 
copy depth for each device, where 0=copy nothing, n=copy everything, 
1=copy the last level (equivalent to -d blk inc) I think we'll have 
covered everything.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

  reply	other threads:[~2009-11-02 18:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-02 13:40 [Qemu-devel] [PATCH 0/3 v5] Live migration without shared storage lirans
2009-11-02 18:47 ` Avi Kivity [this message]
2009-11-03  9:40   ` Liran Schour
2009-11-03 10:38     ` Avi Kivity
2009-11-23 18:47       ` [Qemu-devel] " Jan Kiszka
2009-11-24 14:11         ` Pierre Riteau
2009-11-24 14:17           ` Jan Kiszka
2009-11-24 14:27             ` Anthony Liguori
2009-11-24 14:52               ` Liran Schour
2009-11-03  7:33 ` [Qemu-devel] " Liran Schour
  -- strict thread matches above, loose matches on Subject: below --
2010-03-16 19:57 jz4

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=4AEF2946.1030207@redhat.com \
    --to=avi@redhat.com \
    --cc=lirans@il.ibm.com \
    --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).