qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: guestfwd option doesn't allow supplementary , server, nowait
Date: Tue, 21 Jul 2009 19:39:39 +0200	[thread overview]
Message-ID: <4A65FD5B.6050509@siemens.com> (raw)
In-Reply-To: <20090721143936.GA18061@amd.home.annexia.org>

Richard W.M. Jones wrote:
> The option formerly known as -net channel was changed to:
> 
>   -net user,guestfwd=[tcp]:server:port-dev
> 
> which in general would be an improvement.  libguestfs currently uses:
> 
>   -net channel,6666:unix:/some/path,server,nowait
> 
> which works (probably by accident, because the code happens not to use
> get_param_value).

I suspect so...

>  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.

> 
> It seems like the code tries to do the right thing for the hostfwd and
> guestfwd parameters.  There is a while loop which seems to check for
> these parameters explicitly, but it doesn't work -- I'm not sure why.

What is your precise qemu command line? I noticed that omitting "-net
user" while specifying "-net channel" seems to miss instantiating a
default slirp stack. That should be easy to fix, will have a look. If
your problem is a different one, please describe the details.

> 
> libguestfs is continuing to use the old, working -net channel form of
> this parameter, so please don't remove it.

It won't be removed in the foreseeable future for backward
compatibility. But we also need to fix the new format as the old one
does not allow to specify the slirp stack it should be apply to.

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux

  parent reply	other threads:[~2009-07-21 15:39 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 [this message]
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

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=4A65FD5B.6050509@siemens.com \
    --to=jan.kiszka@siemens.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).