kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Jagane Sundar <jagane@sundar.org>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	Anthony Liguori <aliguori@us.ibm.com>,
	Badari Pulavarty <pbadari@us.ibm.com>,
	Stefan Hajnoczi <stefanha@gmail.com>
Subject: Re: Livebackup feature for qemu/qemu-kvm
Date: Mon, 02 May 2011 16:36:05 +0200	[thread overview]
Message-ID: <4DBEC155.6010307@redhat.com> (raw)
In-Reply-To: <4DBDDD67.5010208@sundar.org>

On 05/02/11 00:23, Jagane Sundar wrote:
> Having a live backup feature for kvm will make it a better solution for
> IaaS clouds compared to xen. I would like to solicit feedback from all
> of you folks involved in the block subsystem of qemu. Stefan mentioned
> that Jes is the person most intimately involved in the block subsystem,
> so Jes - your feedback is particularly important.

Jagane,

Reading your page, the first thing I stumble upon under 'Use Cases' is
the reference to EBS storage. What is that?

Under details, I think it is not a good idea to rely on QEMU looking for
any files with specific file name suffixes. It really should be
specified on the command line by the user or admin tool.

Other questions, how do you plan to handle crashes or loss of network
connection in the middle of a livebackup? How about handling corrupted
livebackup files?

In general it looks interesting, you could consider submitting a
presentation about Livebackup to the KVM Forum 2011.

Cheers,
Jes



  reply	other threads:[~2011-05-02 14:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-01 22:23 Livebackup feature for qemu/qemu-kvm Jagane Sundar
2011-05-02 14:36 ` Jes Sorensen [this message]
2011-05-03  5:58   ` Jagane Sundar
2011-05-03  6:59     ` Jes Sorensen
2011-05-03  7:19       ` Jagane Sundar

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=4DBEC155.6010307@redhat.com \
    --to=jes.sorensen@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=jagane@sundar.org \
    --cc=kvm@vger.kernel.org \
    --cc=pbadari@us.ibm.com \
    --cc=stefanha@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).