https://git.qemu.org/?p=qemu.git;a=commitdiff;h=95f875654ae8b433b5
** 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/1766896
Title:
The patch referred to in comment #4 has now been committed, so from QEMU
3.0 this will fail with a useful error message to tell the user their
choice of machine and CPU aren't compatible.
** Changed in: qemu
Status: New => Fix Committed
--
You received this bug notification because you
https://patchwork.ozlabs.org/patch/924145/ is a patch which improves our error
checking for this case. The command that previously segfaulted should now exit
with the error message:
qemu-system-arm: This board cannot be used with Cortex-M CPUs
--
You received this bug notification because you
** 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/1766896
Title:
qemu-system-arm segfault in arm_v7m_mmu_idx_for_secstate
Status in QEMU:
New
Bug description:
Attempting to
Yes; cortex-m3 will only work on machine types that are expecting it (ie
which instantiate the M profile NVIC interrupt controller, which is
really an integral part of the CPU).
We should catch this case and make QEMU exit with a more helpful
message.
--
You received this bug notification
follow-up to IRC discussions with stsquad and danpb : the problem is
"-machine none" which prevents all the data structures from being
initialized properly.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
You also did not specify any amount of RAM with the -m parameter and the
"none" machine does not have any RAM by default.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1766896
Title:
