From: Thomas Huth <1591611@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1591611] Re: chroot using qemu-x86_64-static fails on ppc64el
Date: Tue, 28 Nov 2017 08:43:02 -0000 [thread overview]
Message-ID: <151185858282.3366.5687132391413054055.launchpad@gac.canonical.com> (raw)
In-Reply-To: 20160612061620.2663.17249.malonedeb@chaenomeles.canonical.com
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1591611
Title:
chroot using qemu-x86_64-static fails on ppc64el
Status in QEMU:
Fix Released
Bug description:
When attempting to use qemu-x86_64-static from qemu 2.5.0 on a ppc64el
host to chroot into an amd64 environment, all commands fail with an
assertion error. /usr/bin/qemu-x86_64-static from the host was copied
into the chroot /usr/bin, and the host has multiformat support in the
kernel.
Sample output illustrating the problem, as well as bash builtins
working:
# chroot /virtualbox/scratchdisks_local_001/amd64_chroot qemu-x86_64-static /bin/bash
# ls
bash: ../sysdeps/nptl/fork.c:136: __libc_fork: Assertion `({ __typeof (self->tid) __value; if (sizeof (__value) == 1) asm volatile ("movb %%fs:%P2,%b0" : "=q" (__value) : "0" (0), "i" (__builtin_offsetof (struct pthread, tid))); else if (sizeof (__value) == 4) asm volatile ("movl %%fs:%P1,%0" : "=r" (__value) : "i" (__builtin_offsetof (struct pthread, tid))); else { if (sizeof (__value) != 8) abort (); asm volatile ("movq %%fs:%P1,%q0" : "=r" (__value) : "i" (__builtin_offsetof (struct pthread, tid))); } __value; }) != ppid' failed.
setup_frame: not implemented
setup_frame: not implemented
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault
setup_frame: not implemented
setup_frame: not implemented
# echo TEST
TEST
# cat test
bash: ../sysdeps/nptl/fork.c:136: __libc_fork: Assertion `({ __typeof (self->tid) __value; if (sizeof (__value) == 1) asm volatile ("movb %%fs:%P2,%b0" : "=q" (__value) : "0" (0), "i" (__builtin_offsetof (struct pthread, tid))); else if (sizeof (__value) == 4) asm volatile ("movl %%fs:%P1,%0" : "=r" (__value) : "i" (__builtin_offsetof (struct pthread, tid))); else { if (sizeof (__value) != 8) abort (); asm volatile ("movq %%fs:%P1,%q0" : "=r" (__value) : "i" (__builtin_offsetof (struct pthread, tid))); } __value; }) != ppid' failed.
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault
It is currently unknown if other host architectures (e.g. aarch64) are
also affected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1591611/+subscriptions
prev parent reply other threads:[~2017-11-28 8:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 6:16 [Qemu-devel] [Bug 1591611] [NEW] chroot using qemu-x86_64-static fails on ppc64el Timothy Pearson
2016-06-12 22:05 ` [Qemu-devel] [Bug 1591611] " Peter Maydell
2016-06-13 1:05 ` Timothy Pearson
2016-06-13 8:59 ` Peter Maydell
2016-06-13 14:18 ` Timothy Pearson
2016-06-13 14:37 ` Peter Maydell
2016-06-16 18:29 ` Timothy Pearson
2016-06-16 20:20 ` Peter Maydell
2016-06-16 20:30 ` Timothy Pearson
2016-06-16 20:59 ` Peter Maydell
2016-06-17 0:33 ` Timothy Pearson
2016-06-17 1:02 ` Timothy Pearson
2016-06-17 11:05 ` Peter Maydell
2016-06-17 16:37 ` Timothy Pearson
2016-06-17 22:01 ` Timothy Pearson
2016-06-18 7:45 ` Timothy Pearson
2016-06-19 0:18 ` Timothy Pearson
2016-08-25 9:13 ` atul
2017-03-01 0:53 ` pranith
2017-07-21 14:27 ` Thomas Huth
2017-11-28 1:28 ` Timothy Pearson
2017-11-28 8:43 ` Thomas Huth [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=151185858282.3366.5687132391413054055.launchpad@gac.canonical.com \
--to=1591611@bugs.launchpad.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.