On Wed, Jun 30, 2021 at 11:53 AM Michael Neises <neisesmich...@gmail.com> wrote: > > Kent, > > > > I tried using those extra arguments and got the same error regarding kvm I > reported a few minutes ago: > > > > ./simulate: qemu-system-x86_64 -machine q35,accel=kvm,kernel-irqchip=split > -cpu > Nehalem,+vme,+pdpe1gb,-xsave,-xsaveopt,-xsavec,-fsgsbase,-invpcid,+syscall,+lm,enforce,+vmx > -nographic -serial mon:stdio -m size=2G -enable-kvm -device > intel-iommu,intremap=off -net nic,model=e1000 -net tap,script=no,ifname=tap0 > -kernel images/kernel-x86_64-pc99 -initrd > images/capdl-loader-image-x86_64-pc99 Could not access KVM kernel module: No > such file or directory > > qemu-system-x86_64: failed to initialize KVM: No such file or directory >
There are instructions on how to setup KVM and nested virtualization on the tutorial that I've pasted here: "Note if you are using QEMU it is important to ensure that your host machine has VT-x support and KVM (https://www.linux-kvm.org/page/Main_Page) installed. You also need to ensure you have enabled nested virtulisation with KVM guests as described here (https://www.linux-kvm.org/page/Nested_Guests)." A quick way to check if nested virtualization is enabled (and therefore supported) on your host is to run `cat /sys/module/kvm_intel/parameters/nested`. `Y` should be returned if it's enabled. It may be easier to run the image on an actual machine instead of in qemu. The images produced can be loaded by a multiboot loader such as grub or pxelinux. (https://docs.sel4.systems/Hardware/VMware/#add-grub2-option-to-run-sel4) has an example grub config. _______________________________________________ Devel mailing list -- devel@sel4.systems To unsubscribe send an email to devel-leave@sel4.systems
