my guess is we're doing something unhelpful with the AVX insn,
and so the guest code which is checking the result and using it as its
loop condition for the jns is just looping forever
in_asm log just stopped with this as the last line
0x4000b4ef4a: 79 9ejns
Public bug reported:
I'm trying to execute code that has been built with -march=skylake
-mtune=generic -mavx2 under qemu-user x86-64 with -cpu Skylake-Client.
However this code just hangs at 100% CPU.
Adding input tracing shows that it is likely hanging when dealing with
an AVX instruction:
Public bug reported:
I've a binary I'm running in qemux86-64 but it is segfaulting. Whilst
qemu writes the core dump for that, qemu itself is segfaulting.
(gdb) bt full
#0 0x7efdd962e32e in sigsuspend () from
/data/poky-tmp/master/build/sysroots-uninative/x86_64-linux/lib/libc.so.6
No
Public bug reported:
Currently qemu's configure requires Python 2 to build. As Python 2 is
rapidly approaching its EOL, it should be possible to build qemu with
Python 3.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a
We need to be able to run qemu as not root. Has anyone tried using qemu
with fakechroot?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1245703
Title:
LD_PREFIX option reads directories
We're (Yocto Project) hit this often. We're building a root file system
and then using userspace qemu to run binaries inside it (such as fc-
cache). If a cyclic symlink appears in the rootfs, it blows up.
--
You received this bug notification because you are a member of qemu-
devel-ml, which
of Linux in Qemu is too slow.
It uses about one hour to boot GUI system.
Can anybody tell me this performance is proper or not?
On my laptop -- a Intel Core Duo 1.8GHz -- I can boot an OpenEmbedded
image (with X, matchbox, udev, etc) in a minute or so.
Ross
--
Ross Burton
