All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: lirans@il.ibm.com
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH 0/3 v3] Live migration without shared storage
Date: Thu, 17 Sep 2009 17:38:59 +0200	[thread overview]
Message-ID: <4AB25813.8040604@redhat.com> (raw)
In-Reply-To: <4AB24198.5070707@siemens.com>

Am 17.09.2009 16:03, schrieb Jan Kiszka:
> 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).
> 
> For my understanding: Does it require the use of qcow[2] or does it also
> work with raw images?

This leads me to the question what the block migration is doing with
qcow2 images (or better: images in any format but raw). What happens
with non-standard image options (like cluster size)? Are snapshots
copied over or won't they be available any more on the destination host?

Kevin

  parent reply	other threads:[~2009-09-17 15:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17 13:31 [Qemu-devel] [PATCH 0/3 v3] Live migration without shared storage lirans
2009-09-17 14:03 ` [Qemu-devel] " Jan Kiszka
2009-09-17 14:43   ` Liran Schour
2009-09-17 15:08     ` Jan Kiszka
2009-09-17 15:38   ` Kevin Wolf [this message]
2009-09-21  7:42     ` 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=4AB25813.8040604@redhat.com \
    --to=kwolf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.