From: Jan Kiszka <jan.kiszka@web.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "Richard W.M. Jones" <rjones@redhat.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: guestfwd option doesn't allow supplementary , server, nowait
Date: Wed, 22 Jul 2009 01:10:05 +0200 [thread overview]
Message-ID: <4A664ACD.9070208@web.de> (raw)
In-Reply-To: <4A661F7C.5030105@codemonkey.ws>
[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]
Anthony Liguori wrote:
> Jan Kiszka wrote:
>>
>>> However in the new syntax that would be:
>>>
>>> -net user,guestfwd=tcp:10.0.2.4:6666-unix:/some/path,server,nowait
>>>
>>> This gives errors like:
>>>
>>> qemu: invalid parameter 'server,nowait' in
>>> 'vlan=0,guestfwd=tcp:10.0.2.4:6666-unix:/tmp/libguestfshRZgxr/sock,server,nowait'
>>>
>>>
>>
>> Yep, that case does not fit into the syntax of comma-separated
>> arguments. We need to find a new syntax within the given constraints.
>> Need to think about it.
>>
> The syntax I proposed early for -drive could address this.
>
> -net user,name=foo,guestfwd=tcp:10.0.2.4:6666
> -net.foo.guestfwd-arg unix:/some/path,server,nowait
>
I general yes, but I would rate this particular suggestion as a bad
example for intuitive argument splitting (guestfwd is useless without a
target like unix:/bla). If at all, we would have to push server and
nowait into the additional args. Still, this requires more thoughts.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2009-07-21 23:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 14:39 [Qemu-devel] guestfwd option doesn't allow supplementary , server, nowait Richard W.M. Jones
2009-07-21 14:57 ` [Qemu-devel] " Richard W.M. Jones
2009-07-21 17:39 ` Jan Kiszka
2009-07-21 16:17 ` Richard W.M. Jones
2009-07-21 16:20 ` Jan Kiszka
2009-07-21 16:39 ` Richard W.M. Jones
2009-07-21 19:23 ` Richard W.M. Jones
2009-07-21 23:15 ` Jan Kiszka
2009-07-22 8:42 ` Richard W.M. Jones
2009-07-22 8:55 ` Jan Kiszka
2009-07-22 9:19 ` Richard W.M. Jones
2009-07-22 9:05 ` Richard W.M. Jones
2009-07-22 9:33 ` Jan Kiszka
2009-07-22 8:51 ` Jan Kiszka
2009-07-21 20:05 ` Anthony Liguori
2009-07-21 23:10 ` Jan Kiszka [this message]
2009-07-21 23:41 ` Anthony Liguori
2009-07-22 9:13 ` Gerd Hoffmann
2009-07-22 9:46 ` Jan Kiszka
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=4A664ACD.9070208@web.de \
--to=jan.kiszka@web.de \
--cc=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
--cc=rjones@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 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).