From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Richard W.M. Jones" <rjones@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: guestfwd option doesn't allow supplementary , server, nowait
Date: Wed, 22 Jul 2009 11:46:14 +0200 [thread overview]
Message-ID: <4A66DFE6.5070407@siemens.com> (raw)
In-Reply-To: <4A66D830.7000704@redhat.com>
Gerd Hoffmann wrote:
> On 07/22/09 01:41, Anthony Liguori wrote:
>
>> completely swizzle the char device syntax. Something like:
>>
>> -char name=foo,type=unix,unix-path=/some/path,mode=server,wait=off
>>
>> Then allow a char:<name> url to be used anywhere that takes traditional
>> char device urls.
>>
>> -net user,guestfwd=tcp:10.0.2.4:6666-char:foo
>
> Also: -serial char=foo
>
> Very useful IMHO.
>
Yeah, I'm also starting to like this direction.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2009-07-22 9:46 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
2009-07-21 23:41 ` Anthony Liguori
2009-07-22 9:13 ` Gerd Hoffmann
2009-07-22 9:46 ` Jan Kiszka [this message]
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=4A66DFE6.5070407@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=kraxel@redhat.com \
--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).