From: Kashyap Chamarthy <kchamart@redhat.com>
To: Alberto Garcia <berto@igalia.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [RFC] Making 'block-stream', and 'block-commit' accept node-name
Date: Thu, 1 Jun 2017 16:03:52 +0200 [thread overview]
Message-ID: <20170601140352.lcfv55eaba775zbm@eukaryote> (raw)
In-Reply-To: <20170531145720.lc5tlssve5eeyyf4@eukaryote>
On Wed, May 31, 2017 at 04:57:20PM +0200, Kashyap Chamarthy wrote:
> On Tue, May 30, 2017 at 04:53:23PM +0200, Alberto Garcia wrote:
> > On Mon 29 May 2017 09:03:22 PM CEST, Kashyap Chamarthy wrote:
[...]
> > > While we have `blockdev-{mirror, backup}` as 'node-name'-alternatives
> > > for `drive-{mirror, backup}`, as the eagle-eyed will, the
> > > `block-stream` and `block-commit` commands still operate on file names
> > > for parameters 'base' and 'top'.
> >
> > block-stream does accept a node name for the top and base images (see
> > 554b614765090f47d and 312fe09cc8af86c).
Indeed it does. The key here is the 'base-node' parameter. Thanks!
Test
----
To turn this:
[A] <-- [B] <-- [C] <-- [D]
Into:
[A] <-- [C] <-- [D]
#----------------------------------------------------------------------
Check the backing file depth of image [D]:
$ qemu-img info --backing-chain d.qcow2 | grep "backing file:"
backing file: c.qcow2
backing file: b.qcow2
backing file: ./a.qcow2
#----------------------------------------------------------------------
Perform intermediate streaming:
(QEMU) block-stream device=node-C base-node=node-A job-id=job0
{
"execute": "block-stream",
"arguments": {
"device": "node-D",
"job-id": "job0",
"base-node": "node-A"
}
}
{
"return": {}
}
(QEMU)
{u'timestamp': {u'seconds': 1496325065, u'microseconds': 808768}, u'data': {u'device': u'job0', u'type': u'stream', u'speed': 0, u'len': 41126400, u'offset': 41126400}, u'event': u'BLOCK_JOB_COMPLETED'}
#----------------------------------------------------------------------
Check the backing file depth, it is now: A <- C <- D:
$ qemu-img info --backing-chain d.qcow2 | grep "backing file:"
backing file: c.qcow2
backing file: ./a.qcow2
#----------------------------------------------------------------------
[...]
--
/kashyap
prev parent reply other threads:[~2017-06-01 14:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 19:03 [Qemu-devel] [RFC] Making 'block-stream', and 'block-commit' accept node-name Kashyap Chamarthy
2017-05-30 14:53 ` Alberto Garcia
2017-05-31 14:57 ` Kashyap Chamarthy
2017-06-01 14:03 ` Kashyap Chamarthy [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=20170601140352.lcfv55eaba775zbm@eukaryote \
--to=kchamart@redhat.com \
--cc=berto@igalia.com \
--cc=qemu-block@nongnu.org \
--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).