** Changed in: qemu
Status: New => 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/1771948
Title:
aarch64 msr CNTFRQ_EL0
Status in QEMU:
Invalid
Bug description:
Hello,
I'm
Thank you for your reply. Sorry to take so long (was on vacations).
Your comment seems correct to me. I tried with the ELF file instead of
the binary file and it worked perfectly (and all the cores were running
instead of just core 0).
>From my point of view, this bug can be marked as invalid.
Looking more closely at this, I think this is because you've passed QEMU
a file which it is treating as a Linux kernel. (-kernel treats raw
binaries and uimage files as Linux kernels; it treats ELF files as not
being Linux kernels). Linux expects to be started in EL2, so although
the emulated CPU
** Tags added: arm
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1771948
Title:
aarch64 msr CNTFRQ_EL0
Status in QEMU:
New
Bug description:
Hello,
I'm running qemu 2.12 on a raspberry pi
On Tue, May 22, 2018 at 05:00:52PM -, Peter Maydell wrote:
> Mmm, that's not really supposed to happen. Do you have a test guest
> binary you can attach that I can reproduce with?
You can hack kvm-unit-tests to make one pretty quickly.
$ git clone
Mmm, that's not really supposed to happen. Do you have a test guest
binary you can attach that I can reproduce with?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1771948
Title:
aarch64 msr
