From: Blue Swirl <blauwirbel@gmail.com>
To: Andi Kleen <ak@linux.intel.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu user x86 working?
Date: Sat, 12 Feb 2011 00:05:31 +0200 [thread overview]
Message-ID: <AANLkTikKDNRGiBU+7RonvaQ09qv9_p=GFdGvP30be3Zf@mail.gmail.com> (raw)
In-Reply-To: <20110211194953.GA19467@tassilo.jf.intel.com>
On Fri, Feb 11, 2011 at 9:49 PM, Andi Kleen <ak@linux.intel.com> wrote:
> Hi,
>
> Is the linux-user qemu for x86-64/i386 supposed to work?
>
> For example running it with a simple hello world on FC14 in gdb:
>
> /home/ak/tsrc/hello: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, not stripped
>
> [Thread debugging using libthread_db enabled]
> ERROR: ioctl(SNDCTL_DSP_MAPINBUF): target=0x80085013 host=0x80105013
> ERROR: ioctl(SNDCTL_DSP_MAPOUTBUF): target=0x80085014 host=0x80105014
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x000000006021f854 in static_code_gen_buffer ()
> (gdb) disp/3i $pc
> 1: x/3i $pc
> => 0x6021f854 <static_code_gen_buffer+162660>: mov (%rbx),%rbp
> 0x6021f857 <static_code_gen_buffer+162663>: mov 0x28(%r14),%rbx
> 0x6021f85b <static_code_gen_buffer+162667>:
> add $0xffffffffffffff88,%rbx
> (gdb) p $rbx
> $2 = 0
>
> I tested a few releases back, 0.13 and also 14-rc0 and they
> all segfault, although they are not all in the same place.
> The qemu-user shipped by Fedora also seems to have the same problem.
>
> Is this a known issue or am I doing something obviously wrong?
I don't have any problems running a statically linked x86_64
helloworld program in an i386 chroot. Dynamically linked programs try
to use wrong libraries, but at least running
/lib64/ld-linux-x86-64.so.2 directly works.
next prev parent reply other threads:[~2011-02-11 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 19:49 [Qemu-devel] qemu user x86 working? Andi Kleen
2011-02-11 22:05 ` Blue Swirl [this message]
2011-02-11 22:27 ` Andi Kleen
2011-02-12 1:04 ` Mulyadi Santosa
2011-02-12 8:08 ` Blue Swirl
2011-02-15 12:20 ` Andi Kleen
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='AANLkTikKDNRGiBU+7RonvaQ09qv9_p=GFdGvP30be3Zf@mail.gmail.com' \
--to=blauwirbel@gmail.com \
--cc=ak@linux.intel.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).