[Qemu-devel] Re: guestfwd option doesn't allow supplementary , server, nowait

[Jan Kiszka <jan.kiszka@siemens.com>]

Richard W.M. Jones wrote:
> 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

So this particular issue is (also?) a -stable regression? That should be
easily bisectible.

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

Jan

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