qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: thayne@c2.net, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Insta-segfault! i386-linux-user
Date: Tue, 18 Sep 2007 21:11:17 +0200	[thread overview]
Message-ID: <CBFECEFB-D5C5-4F8C-9AAB-F96DCD9DF326@suse.de> (raw)
In-Reply-To: <1190139947.9564.60.camel@phantasm.home.enterpriseandprosperity.com>


On Sep 18, 2007, at 8:25 PM, Thayne Harbaugh wrote:

> On Tue, 2007-09-18 at 15:53 +0200, Ronald wrote:
>> Thayne Harbaugh schreef:
>>> Has anyone seen an insta-segfault with i386-linux-user qemu?  I've
>>> compiled qemu-0.9.0 as well as qemu-cvs (2007-09-18) with gcc-3.4  
>>> and
>>> -fno-strict-aliasing on an amd64 and I get this:
>>>
>>> ./i386-linux-user/qemu-i386 --help
>>> Segmentation fault
>>>
>>>> From GDB:
>>>
>>> Program received signal SIGSEGV, Segmentation fault.
>>> 0x0000000000000000 in ?? ()
>>> (gdb) bt
>>> #0  0x0000000000000000 in ?? ()
>>> #1  0x00000000600575ed in __libc_csu_init ()
>>> #2  0x00002b826c660ade in __libc_start_main () from /lib/libc.so.6
>>> #3  0x00000000600050e9 in _start ()
>
> <SNIP>
>
>>>
>> Yes, I had this problem too. U only compiled the program using the
>> 'user' parameters.
>
> I only compiled the 'user' portion because that's all I want.
>
>>  But to get the virtualisation going, you need to
>> compile at least one 'softmmu' (whatever that is). Doing that will
>> create the executable: qemu    (this is the executable you  
>> want :)   )
>
> Err, no.  I don't want full virtualization.
>
>> So I run Linux and I compile it with (and I really need it):
>>
>> i386-linux-user AND i386-softmmu     (i386 can be replaced with your
>> arch such as: ppc, sparc, x86_64, mips, mipsel and arm)
>>
>> That should create an executable called qemu (as stated before) which
>> should not segfault immediatly lol :)
>
> Thank you for your comments.  User virtualization doesn't require
> softmmu.  User virtualization translates the ops in the user space
> program and then jumps into the real kernel of the host operating  
> system
> when a syscall is made - it therefore doesn't need to virtualize  
> all of
> the hardware for I/O and the like.  Obviously this only works for
> running linux executables of one architecture on linux of possibly
> another architecture.
>
> I might mention that none of the other user-space architectures  
> segfault
> - just i386 - e.g. arm-linux-user/qemu-arm works just fine.
>
>
>
>

We had this on the list some months ago. As far as I recall this  
correctly the problem is the linker script. Just take a look at the  
suse source rpm where we replace that one, so it works with x86_64.  
Be prepared for breakage though, as linux-user on 64-Bit hosts does  
not work properly.

Cheers,

Alex

  reply	other threads:[~2007-09-18 19:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-18 12:32 [Qemu-devel] Insta-segfault! i386-linux-user Thayne Harbaugh
2007-09-18 13:53 ` Ronald
2007-09-18 18:25   ` Thayne Harbaugh
2007-09-18 19:11     ` Alexander Graf [this message]
2007-09-18 21:49       ` Thayne Harbaugh
2007-09-18 22:07         ` Alexander Graf
2007-09-18 22:41           ` J. Mayer
2007-09-18 22:57             ` Alexander Graf

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=CBFECEFB-D5C5-4F8C-9AAB-F96DCD9DF326@suse.de \
    --to=agraf@suse.de \
    --cc=qemu-devel@nongnu.org \
    --cc=thayne@c2.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).