All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Liran Schour <LIRANS@il.ibm.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH 0/3 v4] Live migration without shared storage
Date: Tue, 13 Oct 2009 10:18:45 +0200	[thread overview]
Message-ID: <4AD437E5.2060607@redhat.com> (raw)
In-Reply-To: <OF6E792584.2B56D7A3-ONC225764E.002BE6F5-C225764E.002D145F@il.ibm.com>

>>> Hmm. How about something like:
>>>
>>> migrate exec:"rsync file1 file2 ... remote:&&  nc remote port"
>>
>> That can surely work to copy the base files, but it is a task for an
>> upper level like libvirt.  For qemu, copying the copy-on-write data is
>> enough.
>
> I agree that it can be useful to let an upper level component to copy the
> storage
> but you will need a way to synchronize with that layer: 1. qemu -->  upper
> layer:
> vm suspended,no more writes to disk.
> 2. upper layer -->  qemu: storage replication is done.
> I don't see how without it you will have a valid copy of the storage.
>
> However make use of the copy on write data and cut the amount of
> transferred data
> can be done only from inside qemu.

Yes, I understand the reason for this feature.  What I meant was that 
you could use rsync to copy the base files from an upper level 
component, before the actual migration is started and qemu transfers the 
copy-on-write data live.

If Michael was saying instead "why is this needed at all", then you 
answered him.

Paolo

      reply	other threads:[~2009-10-13  8:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-12 16:24 [Qemu-devel] [PATCH 0/3 v4] Live migration without shared storage lirans
2009-10-12 16:09 ` Michael Tokarev
2009-10-12 16:51   ` [Qemu-devel] " Paolo Bonzini
2009-10-13  8:14     ` Liran Schour
2009-10-13  8:18       ` Paolo Bonzini [this message]

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=4AD437E5.2060607@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=LIRANS@il.ibm.com \
    --cc=mjt@tls.msk.ru \
    --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.