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

On Tue, Jul 21, 2009 at 07:39:39PM +0200, Jan Kiszka wrote:
> 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.

This is my full command line, where $qemudir is my qemu git directory.

$qemudir/i386-softmmu/qemu -L $qemudir/pc-bios \
  -drive file=/tmp/test.img,cache=off,if=ide \
  -m 500 -no-reboot \
  -kernel /tmp/libguestfsivUi3g/kernel -initrd /tmp/libguestfsivUi3g/initrd \
  -append 'panic=1 console=ttyS0 udevtimeout=300 noapic acpi=off guestfs=10.0.2.4:6666 guestfs_verbose=1' \
  -nographic -serial stdio \
  -net channel,6666:unix:/tmp/libguestfsivUi3g/sock,server,nowait \
  -net user,vlan=0 \
  -net nic,model=virtio,vlan=0 \
  -no-hpet -rtc-td-hack

The above works with qemu 0.10.4, but not with qemu 0.10.5 where there
is a hang (which I'm investigating - first send from guest -> host
works, response from host -> guest disappears into the ether
somewhere).

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

Good to know, thanks.

Rich.

-- 
Richard Jones, Emerging Technologies, Red Hat  http://et.redhat.com/~rjones
virt-p2v converts physical machines to virtual machines.  Boot with a
live CD or over the network (PXE) and turn machines into Xen guests.
http://et.redhat.com/~rjones/virt-p2v

  reply	other threads:[~2009-07-21 16:17 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 [this message]
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=20090721161642.GA18957@amd.home.annexia.org \
    --to=rjones@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --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).