From: Stefan Hajnoczi <stefanha@redhat.com>
To: Andy Grover <agrover@redhat.com>
Cc: "Benoît Canet" <benoit.canet@irqsave.net>,
kwolf@redhat.com, qemu-devel@nongnu.org, pbonzini@redhat.com
Subject: Re: [Qemu-devel] tcmu-runner and QEMU
Date: Wed, 3 Sep 2014 14:11:59 +0100 [thread overview]
Message-ID: <20140903131159.GM28095@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <54065EE7.4080601@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1226 bytes --]
On Tue, Sep 02, 2014 at 05:20:55PM -0700, Andy Grover wrote:
> On 09/02/2014 02:25 AM, Stefan Hajnoczi wrote:
> > The qemu-lio tool would live in the QEMU codebase and reuse all the
> > infrastructure. For example, it could include a QMP monitor just like
> > the one you are adding to qemu-nbd.
>
> Benoit and I talked a little about QMP on another part of the thread... I
> said I didn't think we needed a QMP monitor in qemu-lio-tcmu, but let me
> spin up on qemu a little more and I'll be able to speak more intelligently.
The QEMU block layer has useful features that are available as QMP
commands:
For example, the drive-mirror QMP command copies a disk image to a new
location while still servicing I/O requests. This is used when an
administrator needs to migrate disk images to a new file system or
storage devices without downtime.
There are other commands for snapshots and backup which are issued via
QMP.
It might even make sense to make the tcmu interface available at
run-time in QEMU like the run-time NBD server. This allows you to get
at read-only point-in-time snapshots while the guest is accessing the
disk. See the nbd-server-start command in qapi/block.json.
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-09-03 13:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 17:22 [Qemu-devel] tcmu-runner and QEMU Benoît Canet
2014-08-29 18:38 ` Andy Grover
2014-08-29 18:51 ` Benoît Canet
2014-08-29 22:36 ` Andy Grover
2014-08-29 22:46 ` Benoît Canet
2014-08-30 14:46 ` Richard W.M. Jones
2014-08-30 15:53 ` Benoît Canet
2014-08-30 16:02 ` Richard W.M. Jones
2014-08-30 16:04 ` Richard W.M. Jones
2014-08-30 17:22 ` Benoît Canet
2014-08-30 21:50 ` Benoît Canet
2014-08-30 16:51 ` Benoît Canet
2014-08-31 20:03 ` Andy Grover
2014-08-31 20:38 ` Benoît Canet
2014-09-01 8:32 ` Paolo Bonzini
2014-09-01 8:08 ` Paolo Bonzini
2014-09-02 9:25 ` Stefan Hajnoczi
2014-09-03 0:20 ` Andy Grover
2014-09-03 7:34 ` Paolo Bonzini
2014-09-03 13:11 ` Stefan Hajnoczi [this message]
2014-09-04 13:24 ` Benoît Canet
2014-09-04 15:15 ` Andy Grover
2014-09-04 15:59 ` Benoît Canet
2014-09-04 20:16 ` Stefan Hajnoczi
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=20140903131159.GM28095@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=agrover@redhat.com \
--cc=benoit.canet@irqsave.net \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.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).