qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Lieven <pl@kamp.de>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Ashijeet Acharya <ashijeetacharya@gmail.com>,
	eblake@redhat.com, jcody@redhat.com, mreitz@redhat.com,
	armbru@redhat.com, qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v6 0/2] allow blockdev-add for NFS
Date: Thu, 19 Jan 2017 15:30:07 +0100	[thread overview]
Message-ID: <566d163c-eb70-718f-b04b-a86d6370a007@kamp.de> (raw)
In-Reply-To: <20170118095952.GA5258@noname.str.redhat.com>

Am 18.01.2017 um 10:59 schrieb Kevin Wolf:
> Am 17.01.2017 um 16:14 hat Peter Lieven geschrieben:
>> Am 31.10.2016 um 18:20 schrieb Kevin Wolf:
>>> Am 31.10.2016 um 16:05 hat Ashijeet Acharya geschrieben:
>>>> Previously posted series patches:
>>>> v5: https://lists.gnu.org/archive/html/qemu-devel/2016-10/msg07580.html
>>>> v4: https://lists.gnu.org/archive/html/qemu-devel/2016-10/msg07449.html
>>>> v3: https://lists.gnu.org/archive/html/qemu-devel/2016-10/msg06903.html
>>>> v2: https://lists.gnu.org/archive/html/qemu-devel/2016-10/msg05844.html
>>>> v1: https://lists.gnu.org/archive/html/qemu-devel/2016-10/msg04487.html
>>>>
>>>> This series adds blockdev-add support for NFS block driver.
>>> Thanks, fixed as commented on patch 1 and applied.
>> Hi,
>>
>> it seems this series breaks passing options via URI.
>>
>> 1) in nfs_parse_uri
>>
>> parse_uint_full(qp->p[i].value, NULL, 0)
>>
>> segfaults, as the routine wants to set *NULL = val.
> Yes, you're right.
>
>> 2) all parameters that have a different names in options and qdict
>> e.g. readahead-size vs. readahead cannot be passed via URI.
>>
>> $ qemu-img convert -p nfs://172.21.200.61/templates/VC_debian8-20170116.qcow2,linux\?readahead=131072 iscsi://172.21.200.56:3260/iqn.2001-05.com.equallogic:0-8a0906-69d384e0a-aa3004e55e15878d-XXX/0
>>
>> qemu-img: Could not open 'nfs://172.21.200.61/vcore-dev-cdrom/templates/VC_debian8-20170116.qcow2,linux?readahead=131072': Block protocol 'nfs' doesn't support the option 'readahead-size'
>>
>> Please let me know if the below fix would be correct:
> No, this needs to be fixed the other way round: runtime_opts must use
> the names as specified in the schema, and nfs_client_open() must access
> them as such. Without that, blockdev-add can't work (and the command
> line only with the "wrong" old option names from the URL, whereas it
> should be using the same names as the QAPI schema).

Shouldn't we support both for backwards compatiblity.?

Peter

  reply	other threads:[~2017-01-19 14:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-31 15:05 [Qemu-devel] [PATCH v6 0/2] allow blockdev-add for NFS Ashijeet Acharya
2016-10-31 15:05 ` [Qemu-devel] [PATCH v6 1/2] block/nfs: Introduce runtime_opts in NFS Ashijeet Acharya
2016-10-31 15:48   ` Kevin Wolf
2016-10-31 15:05 ` [Qemu-devel] [PATCH v6 2/2] qapi: allow blockdev-add for NFS Ashijeet Acharya
2016-10-31 17:20 ` [Qemu-devel] [PATCH v6 0/2] " Kevin Wolf
2017-01-17 15:14   ` Peter Lieven
2017-01-18  9:59     ` Kevin Wolf
2017-01-19 14:30       ` Peter Lieven [this message]
2017-01-19 14:59         ` Eric Blake
2017-01-19 15:20           ` Kevin Wolf
2017-01-19 15:34             ` Peter Lieven
2017-01-19 15:42               ` Kevin Wolf
2017-01-19 15:44                 ` Peter Lieven
2017-01-19 15:55                   ` Kevin Wolf
2017-01-19 15:58                     ` Peter Lieven
2017-01-19 17:08                       ` Kevin Wolf
2017-01-19 17:13                         ` Peter Lieven
2017-01-19 15:47                 ` Peter Lieven

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=566d163c-eb70-718f-b04b-a86d6370a007@kamp.de \
    --to=pl@kamp.de \
    --cc=armbru@redhat.com \
    --cc=ashijeetacharya@gmail.com \
    --cc=eblake@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.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).