qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Vajna <vmiklos@frugalware.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qemu-ppc (user mode) and chroot
Date: Tue, 19 Aug 2008 14:24:18 +0200	[thread overview]
Message-ID: <20080819122418.GA17582@genesis.frugalware.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]

Hello,

I recently found a mailing list post:

http://osdir.com/ml/emulators.qemu/2004-02/msg00162.html

That's exactly what I'm trying to set up.

I have a ppc chroot on an x86 machine - both Linux, with nptl-enabled
glibc.

I'm trying to run the following test app:

#include <stdio.h>
#include <unistd.h>

int main()
{
 int pid;
 pid = fork();
 printf("child is %d\n", pid);
 if (pid == -1)
  perror("fork() failed");
 return 0;
}

When I link this statically to a linuxthreads-enabled libc on ppc, then
I can run this using qemu-ppc without any problem:

$ sudo chroot . /qemu-ppc /hello-static
child is 0
child is 29207

However, when I link it dynamically (so it will use the nptl-enabled
libc from the chroot), I get:

$ sudo chroot . /qemu-ppc /hello
child is -1
fork() failed: Invalid argument

and yes, I just checked, when I run the same dynamic executable on a
real ppc, it works just fine, so I think this is a bug in qemu.

I tried qemu-0.9.1 and svn trunk, with the same results.

Is this a known issue?

Thanks!

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2008-08-19 12:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-19 12:24 Miklos Vajna [this message]
2008-08-19 12:31 ` [Qemu-devel] qemu-ppc (user mode) and chroot Miklos Vajna

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=20080819122418.GA17582@genesis.frugalware.org \
    --to=vmiklos@frugalware.org \
    --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).