From: Anthony Liguori <aliguori@us.ibm.com>
To: "Daniel P. Berrange" <berrange@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: Wenchao Xia <xiawenc@linux.vnet.ibm.com>,
stefanha@linux.vnet.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] let qemu-img info genereate json output
Date: Fri, 27 Jul 2012 08:52:51 -0500 [thread overview]
Message-ID: <87r4rxe2fg.fsf@codemonkey.ws> (raw)
In-Reply-To: <20120727105245.GT2225@redhat.com>
"Daniel P. Berrange" <berrange@redhat.com> writes:
> On Fri, Jul 27, 2012 at 12:49:53PM +0200, Paolo Bonzini wrote:
>> Il 27/07/2012 12:33, Daniel P. Berrange ha scritto:
>> > #qemu-img info -j /var/lib/libvirt/images/bar.qcow2
>> > {
>> > "information": {
>> > "actual_size": "139264",
>> > "fmt": "qcow2",
>> > "virtual_size": "10485760",
>> > "filename": "/var/lib/libvirt/images/bar.qcow2",
>> > "cluster_size": 65536,
>> > "encrypted": 0,
>> > "snapshot_list": [
>> > ],
>> > "dirty_flag": 0,
>> > "backing_filename": "/dev/sda1"
>> > },
>> > "return": 0
>> > }
>> >
>> > IIUC,the 'return' element here is just duplicating the qemu-img
>> > exit status. I think this is rather dubious, and would rather
>> > just see the stuff in the 'information' sub-block be output
>> > directly. It also seems to forget to mention the backing
>> > file format.
>>
>> I wonder if we could add this also to the QEMU monitor ("info
>> block-image foo"), so that the code would be shared between qemu-img.c
>> and QEMU.
>
> It would certainly make sense to have the code & data format shared
> between the two, so apps don't need to have 2 different JSON parsers
We should definitely describe the output in qapi-schema.json. Whether
we also expose a QMP command--I'm not really convinced.
It seems a bit unusual to me to want to get this info from an arbitrary
image file from within QEMU. I'm not sure I see the use-case.
I can definitely see it become exposed as part of query-block though as
an image-info parameter.
Regards,
Anthony Liguori
>
>
> Daniel
> --
> |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
> |: http://libvirt.org -o- http://virt-manager.org :|
> |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
> |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2012-07-27 13:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 10:20 [Qemu-devel] [PATCH] let qemu-img info genereate json output Wenchao Xia
2012-07-27 10:33 ` Daniel P. Berrange
2012-07-27 10:49 ` Paolo Bonzini
2012-07-27 10:52 ` Daniel P. Berrange
2012-07-27 13:52 ` Anthony Liguori [this message]
2012-07-27 13:50 ` Anthony Liguori
2012-08-15 8:49 ` Benoît Canet
2012-08-15 13:17 ` Eric Blake
2012-07-30 14:34 ` 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=87r4rxe2fg.fsf@codemonkey.ws \
--to=aliguori@us.ibm.com \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
--cc=xiawenc@linux.vnet.ibm.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).