On 02.12.20 10:37, Sainz Markel wrote: > Well, I've been checking the related components. My env is being deployed > into Qemu, using the same commands exposed on the Jailhouse Github docs: > > qemu-system-x86_64 -machine q35,kernel_irqchip=split -m 2G -enable-kvm \ > -smp 6 -device intel-iommu,intremap=on,x-buggy-eim=on \ > -cpu host,-kvm-pv-eoi,-kvm-pv-ipi,-kvm-asyncpf,-kvm-steal-time,-kvmclock \ > -serial stdio -serial vc \ > -netdev user,id=net0,hostfwd=tcp::5555-:22 -device e1000,netdev=net0 \ > -device intel-hda,addr=1b.0 -device hda-duplex \ > -kernel vmlinuz -append "root=/dev/sda intel_iommu=off > memmap=0x5200000\$0x3a000000 vga=0x305 console=ttyS0" \ > -initrd initrd.cpio.gz \ > -display none \ > -parallel none \ > -serial tcp:127.0.0.1:1234,server,nowait > > The Qemu env is inside a Docker container which is being run in --privileged > mode to share the kernel with the host: > > docker run -it --privileged --net=host --volume ~/docker_tmp:/tmp > selene-qemu:1.0 > > The mentioned host is a VMWare Ubuntu VM which has KVM enabled with nesting=1 > parameter: > > $ sudo modprobe kvm_intel nested=1 > > and all the virtualization configs are active in the VMWare config panel: > > Virtualize Intel VT -x/EPT or AMD-V/RVI yes > Virtualize CPU performance counters yes > Virtualize IOMMU yes > > Any other thing I should check? Any change that must be done in the outermost > Windows host? >
Run "jailhouse hardware check" in a first-level guest (can be any normal Linux distro). It will tell you where VMware falls short in emulating VT-x. Jan -- Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux -- You received this message because you are subscribed to the Google Groups "Jailhouse" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jailhouse-dev/965e7e12-274d-42fd-2303-8a4b82ae8fa8%40siemens.com.
