From: Jan Kiszka <jan.kiszka@web.de>
To: Rob Landley <rob@landley.net>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Segmentation fault with -net socket in 0.10.2.
Date: Sun, 26 Apr 2009 18:55:47 +0200 [thread overview]
Message-ID: <49F49213.3070507@web.de> (raw)
In-Reply-To: <200904240009.57667.rob@landley.net>
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
Rob Landley wrote:
> When I add this to the qemu command line:
>
> -net socket,listen=127.0.0.1:1234,connect=:22
>
> It goes "Segmentation fault" immediately instead of booting.
>
> How to reproduce this yourself:
>
> 1) Grab a prebuilt arm system image from
> http://impactlinux.com/fwl/downloads/binaries/system-image/system-image-armv4l.tar.bz2
>
> 2) Try the following command line, which should boot you to a command prompt,
> and is just to prove it's working. Type "exit" to get back out:
>
> qemu-system-arm -M versatilepb -nographic -no-reboot -kernel \
> zImage-armv4l -hda image-armv4l.ext2 -append "root=/dev/sda rw \
> init=/usr/sbin/init.sh panic=1 PATH=/usr/bin console=ttyAMA0" -net \
> nic,model=rtl8139 -net user
>
> 3) Add the -net socket bit to the end of that command line and run it again.
> It should segfault immediately.
>
> I don't think this is specific to arm, that's just what I tested with.
>
> Any clues what I'm doing wrong?
Nothing, it was a QEMU bug, already fixed in stable_0.10 and master
(latter currently suffers from a -net socket regression I added :) ).
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
prev parent reply other threads:[~2009-04-26 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 5:09 [Qemu-devel] Segmentation fault with -net socket in 0.10.2 Rob Landley
2009-04-26 16:55 ` 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=49F49213.3070507@web.de \
--to=jan.kiszka@web.de \
--cc=qemu-devel@nongnu.org \
--cc=rob@landley.net \
/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).