qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Fam Zheng <famz@redhat.com>, Markus Armbruster <armbru@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] Review of monitor commands identifying BDS / BB by name
Date: Wed, 03 Dec 2014 12:13:01 +0100	[thread overview]
Message-ID: <547EF03D.4090604@redhat.com> (raw)
In-Reply-To: <20141203055144.GA1179@ad.nay.redhat.com>



On 03/12/2014 06:52, Fam Zheng wrote:
>> > * drive-backup
>> > 
>> >   @device names a backend.
>> > 
>> >   Do we want to be able to back up any node, or only a backend?

If non-backend nodes are read-only, we can just copy them outside QEMU.

>> >   Note: documentation of @target sounds like it could somehow name a
>> >   backend, but as far as I can tell it's always interpreted as file
>> >   name.

I think block-backup should be added that takes a backend for target.
It could also take a node name for the source, letting you copy any node
if you really want to.

>> > * drive-mirror
>> > 
>> >   @device names a backend, @replaces names a node, and @node-name
>> >   defines the name of the new node.
>> > 
>> >   Do we want to be able to mirror any node, or only a backend?

Same as above.

>> >   Note: documentation of @target sounds like it could somehow name a
>> >   backend, but as far as I can tell it's always interpreted as file
>> >   name.

Again, block-mirror could be added that takes a backend for @target (and
if you want to, a node name for the source).

Paolo

  reply	other threads:[~2014-12-03 11:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-02 19:06 [Qemu-devel] Review of monitor commands identifying BDS / BB by name Markus Armbruster
2014-12-03  5:52 ` Fam Zheng
2014-12-03 11:13   ` Paolo Bonzini [this message]
2014-12-04 15:59   ` Markus Armbruster
2014-12-03 10:30 ` Kevin Wolf
2014-12-03 13:59   ` Eric Blake
2014-12-03 14:51     ` Markus Armbruster
2014-12-04 16:56       ` Markus Armbruster
2014-12-04 15:56   ` Markus Armbruster
2014-12-04 19:44     ` Eric Blake
2014-12-05  9:19       ` Kevin Wolf
2014-12-05 12:19         ` Markus Armbruster
2014-12-05  9:34       ` Markus Armbruster
2014-12-05  9:46         ` Kevin Wolf
2014-12-05 12:08           ` Markus Armbruster
2014-12-16 18:12 ` [Qemu-devel] Can we make monitor commands identify BDS / BB by name consistently? (was: Review of monitor commands identifying BDS / BB by name) Markus Armbruster
2014-12-17 14:12   ` Kevin Wolf
2014-12-17 16:17     ` [Qemu-devel] Can we make monitor commands identify BDS / BB by name consistently? Markus Armbruster
2014-12-19 18:27   ` Markus Armbruster
2014-12-18 15:25 ` [Qemu-devel] Review of ways to create BDSes (was: Review of monitor commands identifying BDS / BB by name) Markus Armbruster
2014-12-19 12:18   ` Kevin Wolf
2014-12-19 14:02     ` [Qemu-devel] Review of ways to create BDSes Markus Armbruster
2014-12-19 14:24   ` Markus Armbruster
2014-12-19 15:52 ` [Qemu-devel] Review of ways to reopen BDSes (was: Review of monitor commands identifying BDS / BB by name) Markus Armbruster

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=547EF03D.4090604@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=armbru@redhat.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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).