From: Eric Blake <eblake@redhat.com>
To: Ashish Mittal <ashmit602@gmail.com>,
qemu-devel@nongnu.org, pbonzini@redhat.com, kwolf@redhat.com,
armbru@redhat.com, berrange@redhat.com, jcody@redhat.com,
famz@redhat.com, ashish.mittal@veritas.com, stefanha@gmail.com,
Rakesh.Ranjan@veritas.com, Buddhi.Madhav@veritas.com
Cc: Ketan.Nilangekar@veritas.com, Abhijit.Dey@veritas.com,
Venkatesha.Mg@veritas.com
Subject: Re: [Qemu-devel] [PATCH v4] This patch adds support for a new block device type called "vxhs".
Date: Mon, 31 Oct 2016 14:05:11 -0500 [thread overview]
Message-ID: <03bd59d7-8aae-9448-11ab-3b1f4accd008@redhat.com> (raw)
In-Reply-To: <1477723631-8700-1-git-send-email-ashish.mittal@veritas.com>
[-- Attachment #1: Type: text/plain, Size: 3001 bytes --]
On 10/29/2016 01:47 AM, Ashish Mittal wrote:
> Source code for the qnio library that this code loads can be downloaded from:
> https://github.com/MittalAshish/libqnio.git
For now, just an interface review:
>
> Sample command line using the JSON syntax:
> ./qemu-system-x86_64 -name instance-00000008 -S -vnc 0.0.0.0:0 -k en-us
> -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
> -msg timestamp=on
> 'json:{"driver":"vxhs","vdisk_id":"c3e9095a-a5ee-4dce-afeb-2a59fb387410",
This doesn't match the code, which spelled it "vdisk-id".
> "server":{"host":"172.172.17.4","port":"9999"}}'
>
> Sample command line using the URI syntax:
> qemu-img convert -f raw -O raw -n
> /var/lib/nova/instances/_base/0c5eacd5ebea5ed914b6a3e7b18f1ce734c386ad
> vxhs://192.168.0.1:9999/c6718f6b-0401-441d-a8c3-1f0064d75ee0
>
> Signed-off-by: Ashish Mittal <ashish.mittal@veritas.com>
> ---
> +++ b/qapi/block-core.json
> @@ -1704,12 +1704,13 @@
> # @host_device, @host_cdrom: Since 2.1
> # @gluster: Since 2.7
> # @nbd: Since 2.8
> +# @vxhs: Since 2.8
Please rebase on top of the latest block pull request:
https://lists.gnu.org/archive/html/qemu-devel/2016-10/msg08089.html
In particular, your patch should look something like:
-# @nbd, @nfs, @replication, @ssh: Since 2.8
+# @nbd, @nfs, @replication, @ssh, @vxhs: Since 2.8
> #
> # Since: 2.0
> ##
> { 'enum': 'BlockdevDriver',
> 'data': [ 'archipelago', 'blkdebug', 'blkverify', 'bochs', 'cloop',
> - 'dmg', 'file', 'ftp', 'ftps', 'gluster', 'host_cdrom',
> + 'dmg', 'file', 'ftp', 'ftps', 'gluster', 'host_cdrom', 'vxhs',
> 'host_device', 'http', 'https', 'luks', 'nbd', 'null-aio',
> 'null-co', 'parallels', 'qcow', 'qcow2', 'qed', 'quorum', 'raw',
> 'replication', 'tftp', 'vdi', 'vhdx', 'vmdk', 'vpc', 'vvfat' ] }
Please keep this enum sorted alphabetically (your entry should be after
vvfat, not in the random middle).
> @@ -2238,6 +2239,20 @@
> '*export': 'str',
> '*tls-creds': 'str' } }
>
> +# @BlockdevOptionsVxHS
Missing a leading ## marker.
> +#
> +# Driver specific block device options for VxHS
> +#
> +# @vdisk-id: UUID of VxHS volume
> +#
> +# @server: vxhs server IP, port
> +#
> +# Since: 2.8
> +##
> +{ 'struct': 'BlockdevOptionsVxHS',
> + 'data': { 'vdisk-id': 'str',
> + 'server': 'InetSocketAddress' } }
> +
> ##
> # @BlockdevOptions
> #
> @@ -2302,7 +2317,8 @@
> 'vhdx': 'BlockdevOptionsGenericFormat',
> 'vmdk': 'BlockdevOptionsGenericCOWFormat',
> 'vpc': 'BlockdevOptionsGenericFormat',
> - 'vvfat': 'BlockdevOptionsVVFAT'
> + 'vvfat': 'BlockdevOptionsVVFAT',
> + 'vxhs': 'BlockdevOptionsVxHS'
> } }
>
> ##
>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2016-10-31 19:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-29 6:47 [Qemu-devel] [PATCH v4] This patch adds support for a new block device type called "vxhs" Ashish Mittal
2016-10-31 19:05 ` Eric Blake [this message]
2016-10-31 20:15 ` ashish mittal
2016-10-31 21:55 ` Jeff Cody
2016-11-01 6:37 ` ashish mittal
2016-11-04 13:04 ` Stefan Hajnoczi
2016-11-08 1:39 ` ashish mittal
2016-11-08 1:52 ` Fam Zheng
2016-11-08 8:56 ` ashish mittal
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=03bd59d7-8aae-9448-11ab-3b1f4accd008@redhat.com \
--to=eblake@redhat.com \
--cc=Abhijit.Dey@veritas.com \
--cc=Buddhi.Madhav@veritas.com \
--cc=Ketan.Nilangekar@veritas.com \
--cc=Rakesh.Ranjan@veritas.com \
--cc=Venkatesha.Mg@veritas.com \
--cc=armbru@redhat.com \
--cc=ashish.mittal@veritas.com \
--cc=ashmit602@gmail.com \
--cc=berrange@redhat.com \
--cc=famz@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).