All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francesco Romani <fromani@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	Luiz Capitulino <lcapitulino@redhat.com>,
	qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
	mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [RFC][PATCH v2] block: add write threshold reporting for block devices
Date: Fri, 21 Nov 2014 10:32:06 -0500 (EST)	[thread overview]
Message-ID: <781769647.2018010.1416583926495.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20141121101126.GA3956@noname.redhat.com>

----- Original Message -----
> From: "Kevin Wolf" <kwolf@redhat.com>
> To: "Francesco Romani" <fromani@redhat.com>
> Cc: qemu-devel@nongnu.org, "Stefan Hajnoczi" <stefanha@gmail.com>, mdroth@linux.vnet.ibm.com, "Luiz Capitulino"
> <lcapitulino@redhat.com>, "Stefan Hajnoczi" <stefanha@redhat.com>
> Sent: Friday, November 21, 2014 11:11:26 AM
> Subject: Re: [Qemu-devel] [RFC][PATCH v2] block: add write threshold reporting for block devices
[...]
> > 1. I'm running a simple test using the attached script -
> > which is a qemu command line adapted from libvirt ouput driven
> > by oVirt. There is a way to attach a name at this stage, using a QMP
> > command?
> 
> No, node-name is assigned at the BlockDriverState (BDS) creation and
> can't be changed later on.

Makes sense to me.

> > 2. (related to the former) it seems from a not-so-deep look that the
> > blessed (only?)
> > way to set a proper node_name is using blockdev-add.
> > If so, I'm not sure I follow how the qemu boot flow would look like.
> > It will not be anymore as simple as crafting a command line and run the
> > qemu, right?
> > IIUC some interaction with QMP will be needed (sorry for asking silly
> > question,
> > trying to fill gaps in my knowledge).
> 
> -drive on the command line can do everything that blockdev-add can do.
> So let's assume you have a qcow2 image on a filesystem. Then you end up
> with two BDSes, one for the format driver and one for accessing the
> filesystem:
> 
>     BlockBackend (virtual device) -> qcow2 BDS -> file BDS (raw-posix.c)
> 
> For assigning a node name to the qcow2 BDS, you simply specify it in the
> obvious way:
> 
>     -drive file=test.qcow2,node-name=foo
> 
> Now if you want to assign a node name to the file BDS as well, you would
> get nested dicts in the blockdev-add call. In -drive a dot syntax is
> used to represent this:
> 
>     -drive file=test.qcow2,node-name=foo,file.node-name=bar
> 
> Are things a bit clearer with this?

Yes, thanks a lot. I was a bit misleaded by the lack of the reference (after a very quick
look) in the man page.
Maybe the manpage is out of date, but this is a different story -and maybe a different patch :)

New revision will come in a few days.

Bests,

-- 
Francesco Romani
RedHat Engineering Virtualization R & D
Phone: 8261328
IRC: fromani

  reply	other threads:[~2014-11-21 15:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-07 13:12 [Qemu-devel] [RFC][PATCH v2] add write threshold reporting for block devices Francesco Romani
2014-11-07 13:12 ` [Qemu-devel] [RFC][PATCH v2] block: " Francesco Romani
2014-11-17 16:49   ` Stefan Hajnoczi
2014-11-18  8:12     ` Francesco Romani
2014-11-19 15:52       ` Stefan Hajnoczi
2014-11-20  8:23         ` Francesco Romani
2014-11-20 10:30     ` Kevin Wolf
2014-11-20 11:04       ` Stefan Hajnoczi
2014-11-20 11:34         ` Kevin Wolf
2014-11-21  8:43           ` Francesco Romani
2014-11-21 10:11             ` Kevin Wolf
2014-11-21 15:32               ` Francesco Romani [this message]
2014-11-21 16:24             ` Eric Blake
2014-11-21  0:10         ` Eric Blake

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=781769647.2018010.1416583926495.JavaMail.zimbra@redhat.com \
    --to=fromani@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.