** Changed in: qemu
Status: New => Confirmed
** Changed in: qemu
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1779634
Title:
qemu-x86_64 on aarch64 repo
thanks Peter, yes I tried to run an x86 strace under QEMU.
I'll stop this experiment since you are right this won't work for
utilities with device-level I/O and memory operations, I will raise this
requirement to Intel support website firstly.
Best Regards, Yi
--
You received this bug notificat
> /usr/bin/strace: ptrace(PTRACE_TRACEME, ...): Function not implemented
This indicates that you're trying to run an x86 strace under QEMU. That
won't work. You want to either (a) run QEMU + guest binary under the
host strace or (b) run QEMU + guest binary with the QEMU -strace option.
--
You re
Thanks very much @Peter Maydell, when invoking these tools through
docker/qemu-user I really saw syscall disorders, even strace fails. You
are right these tools have x86_64 syscall numbers & perhaps mmaps of
/dev/mem to allocate contiguous memory region for DMA transactions.
Then the goal cannot b
You could confirm this hypothesis by using strace and looking for
whether it's doing mmap() of /dev/mem or /dev/kmem. If it's true, then
the program would not work even if you had the source and recompiled it
for aarch64 -- it would require bugfixes (code changes) to achieve
whatever it's trying to
qemu-x86_64 is just a userspace program. If the kernel is getting
Synchronous External Aborts then this is not a QEMU problem. Either
there's a bug in the host kernel, or the guest binary is attempting to
mmap /dev/mem and do wrong things to it because it's expecting it to be
an x86 system. I suspe
