> I want to use KVM on jetson nano and boot Raspbian Buster 32bit OS
with native machine emulation.
The raspi machine doesn't support KVM. You can choose either (1) boot on
a board model which does support KVM, which basically means "virt", or
(2) use emulation, not KVM.
If all you care about is
When I use gdb i see that the assert line uses:
/* KVM cannot currently support multiple address spaces. */
assert(asidx == 0 || !kvm_enabled());
the asidx is 1. So since KVM is not supporting multiple addresses spaces
that the Raspi3 requires the assertion occurs.
I wonder what the worka
I am having a similar problem. I want to use KVM on jetson nano and boot
Raspbian Buster 32bit OS with native machine emulation.
Run into a similar problem. I used latest QEMU.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1836501
Title:
cpu_address
I'm marking this bug 'incomplete' since as in comment #8 I was unable to
reproduce, and I'm no longer sure how the assert could be being hit. If
you can provide repro instructions and images that work on current head-
of-git I can investigate.
** Changed in: qemu
Status: Confirmed => Incom
** Tags added: kvm
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1836501
Title:
cpu_address_space_init fails with assertion
Status in QEMU:
Confirmed
Bug description:
qemu-system-arm does not
I can boot a KVM guest (either with the debian stretch qemu-system-arm
2.8.1, or with a head-of-upstream-git QEMU), which wouldn't work with
EL3 enabled, so I'm not sure what is going wrong for you. To try to
debug this further you'd need to build QEMU from source and start
running it under the deb
UPDATE: Kernel page handling seems to be related to the -smp 2
parameter. Any number > 1 leads to the paging error while omitting the
parameter lead to a running system (without KVM).
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
ht
My test setup is now Debian Buster with qemu-system-arm 3.1 and a host
with KVM-enabled Kernel 4.9.61 on Odroid XU4.
Following results:
qemu-system-arm -M vexpress-a15 -smp 2 -m 512 -kernel vmlinuz -initrd initrd.gz
-dtb vexpress-v2p-ca15-tc1.dtb -device virtio-blk-device,drive=inst-blk
I've now tested this with both current head-of-git and with the Debian
stretch 2.8.1 qemu-system-arm and I can't reproduce this. We
automatically don't enable the EL3 feature if we're using KVM, so a
guest runs and sees a non-secure only CPU, without needing to manually
add -machine secure=off to t
Thank you for the quick and complete investigation. I'll follow your
suggestions and will reply any succecss in the next days. I checked the
source of the vexpress and found the assert, but wasn't clever enough to
compare it to another board.
I would support the idea of checking the incompatible p
** 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/1836501
Title:
cpu_address_space_init fails with assertion
Status in QEMU:
Confirmed
Bug description:
qemu-system-arm does not
We do check for the incompatible option combination in hw/arm/virt.c:
if (vms->secure) {
if (kvm_enabled()) {
error_report("mach-virt: KVM does not support Security extensions");
exit(1);
}
we just don't have anything equivalent in vexpress.c. We should
Oh, I've just noticed -- we default to enabling EL3 on this board (like
the hardware), which won't work with KVM, so if you want KVM you need to
disable EL3 with the command line option -machine secure=off
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
2.6 is now very old -- can you check whether this is still a problem
with a more recent QEMU version, please?
The command line you're using should in theory work, but vexpress-a15 +
KVM is a bit of an obscure combination -- most people who want to use
virtualization use the 'virt' machine, which s
15 matches
Mail list logo
