I've been struggling with this with no luck. Any ideas of why this could happen? I've found no info at all about this two checkitems, apparently with the VT-x virtualization enabled should be enough...
Markel. -----Mensaje original----- De: Sainz Markel Enviado el: miércoles, 2 de diciembre de 2020 11:38 Para: Jan Kiszka <[email protected]>; [email protected] Asunto: RE: JAILHOUSE_ENABLE: Input/output error The ouput of the command on the VMWare guest: msainz@ubuntu:~$ sudo jailhouse hardware check [sudo] contraseña para msainz: Lo sentimos, vuelva a intentarlo. [sudo] contraseña para msainz: Feature Availability ------------------------------ ------------------ Number of CPUs > 1 ok Long mode ok x2APIC ok VT-x (VMX) ok VMX outside SMX ok VMX inside SMX missing (optional) IA32_TRUE_*_CLTS ok NMI exiting ok Preemption timer MISSING I/O bitmap ok MSR bitmap ok Secondary controls ok Optional CR3 interception ok Virtualize APIC access MISSING RDTSCP ok Unrestricted guest ok INVPCID ok XSAVES ok EPT ok 4-level page walk ok EPTP write-back ok 2M pages ok 1G pages missing (optional) INVEPT ok Single or all-context ok VM-exit save IA32_PAT ok VM-exit load IA32_PAT ok VM-exit save IA32_EFER ok VM-exit load IA32_EFER ok VM-entry load IA32_PAT ok VM-entry load IA32_EFER ok Activity state HLT ok VT-d (IOMMU #0) ok 39-bit AGAW missing (optional) 48-bit AGAW ok 2M pages missing (optional) 1G pages missing (optional) Queued invalidation ok Interrupt remapping ok Extended interrupt mode ok Check FAILED! -----Mensaje original----- De: Jan Kiszka <[email protected]> Enviado el: miércoles, 2 de diciembre de 2020 11:35 Para: Sainz Markel <[email protected]>; [email protected] Asunto: Re: JAILHOUSE_ENABLE: Input/output error CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. 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/PA4PR03MB71846A56477610902A29AE7DB6F20%40PA4PR03MB7184.eurprd03.prod.outlook.com.
