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: Tue, 03 May 2011 08:59:17 +0200 [thread overview]
Message-ID: <4DBFA7C5.1030607@redhat.com> (raw)
In-Reply-To: <4DBF9978.8060609@sundar.org>
On 05/03/11 07:58, Jagane Sundar wrote:
> On 5/2/2011 7:36 AM, Jes Sorensen wrote:
>> Reading your page, the first thing I stumble upon under 'Use Cases' is
>> the reference to EBS storage. What is that?
> EBS stands for Elastic Block Storage - Amazon EC2's shared storage
> solution. This is the storage that comes with guarantees, since it is
> replicated across machines.
I see, it would be good if you made that more explicit in the document
for those who aren't as experienced with EC2, like me.
>> 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.
> That's a good idea. Perhaps another attribute in the drive description
> list,
> just like type=virtio, maybe backup=livebackup.
I think that is the right way to go.
>> In general it looks interesting, you could consider submitting a
>> presentation about Livebackup to the KVM Forum 2011.
>
> Glad to know that you think it is interesting. Also, thanks for the
> pointer to KVM Forum 2011, Jes. It looks like I have a few more weeks
> to get an abstract in for KVM forum 2011. I will do so.
Excellent, please go ahead and submit it!
Cheers,
Jes
next prev parent reply other threads:[~2011-05-03 7:00 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
2011-05-03 5:58 ` Jagane Sundar
2011-05-03 6:59 ` Jes Sorensen [this message]
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=4DBFA7C5.1030607@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).