Has anyone tried using KVM with the Juno board? It doesn't look like the bootloader starts the cores in hypervisor mode, so it's not clear to me whether the current system software will support a hypervisor at the moment, even with the appropriate kernel options selected. Are there any plans to support it?
Hi Aniudipi,
If you don't mind sharing what you had to do to get this running, I'd appreciate it. I had to step away from this for a bit, hence the slowness in my reply, but I just pulled the most recent mainline kernel and wasn't able to get it booting on my Juno board. This is kernel version 3.18-rc3, so it's not from Linaro or ARM. Can you share what kernel version you're using and/or what changes were needed to get things going?
I'm successfully running ARM's 3.15.0-rc8, but as the other posters imply, that's apparently too old to support the A53 cores.
JP
Hi JP,
You can try the Juno support patches posted by Liviu on ALKML[1] on top of v3.18-rc2
Regards,
Sudeep
[1] https://lkml.org/lkml/2014/10/31/372
I believe that I'm very nearly there, but the KVM tool is segfaulting. As suggested, I'm running 3.18.0-rc2 with the patches. The kernel builds fine and I see that /dev/kvm is exposed. I separately pulled down the kvm-tool and built it for my kernel. I run it as follows:
taskset -c 4 ./lkvm run --kernel Image -d disk_oe64.img -m 512 --console virtio --params "earlyprintk=smh console=hvc0 root=/dev/vda init=/bin/sh"
Unfortunately, I immediately see a kernel oops. The full output is pasted here:
Unable to handle kernel NULL pointer dereference at virtual address 00000000 pg - Pastebin.com
I pulled down the guest kernel binary and file system from one of the Virtual Open Systems guides:
guide to set up a KVM development environment on 64-bit ARMv8 processors
Any thoughts?
Thanks!
I have no idea as what kernel you are running. So my suggestion would
be to run the same host kernel as guest and check first.
It could be issue with your guest kernel.