This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/164
** Changed in: qemu
Status: New => Expired
** Bug watch
Of course it’s open source, I get that. When I say „xyz should be done“
then in the sense of „2+2 should be 4“ not in the sense of „you must
implement xyz right now“ ;)
Nonetheless, if you run e.g. on an ARM platform the command
qemu-system-x86_64 -cpu help
then it shouldn’t list a slew of CPUs
QEMU, like most open source projects, relies on contributors who have
motivation, skills and available time to work on implementing particular
features. They naturally tend to focus on features that result in the
greatest benefit to their own use cases. Thus simply declaring that an
open source pro
We do care about emulation; but as always with open source software
projects, the parts that get more care and attention are the parts that
people are either paid to work on or are personally interested in. x86
guest emulation in particular is not very well maintained (though it is
better than some
If I may be so free:
It seems that QEMU has stopped emphasizing the EMU part of the name, and
is too much focused on virtualization.
My interest is at running legacy operating systems, and as such, they must run
on foreign CPU platforms. m68 on intel, intel on ARM, etc.
Time doesn't stand still,
Further debugging on IRC reveals that QEMU itself is not hanging, but
the guest code is looping infinitely, because QEMU doesn't implement the
AVX instruction set and isn't generating an undefined-instruction
exception either. So the %rdx output from the AVX insn is wrong and the
guest code never e
** Summary changed:
- qemu-user-x86-64 hangs at vcvttsd2si
+ qemu x86 TCG doesn't support AVX insns
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1818075
Title:
qemu x86 TCG doesn't support AVX in
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 0x4000b4ee
