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?
Thx for the help,
-----Mensaje original-----
De: Jan Kiszka <[email protected]>
Enviado el: martes, 1 de diciembre de 2020 12:32
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 01.12.20 10:36, Sainz Markel wrote:
> After compiling with the suggested flag, the output of the enable command
> adds another line:
>
> ~/jailhouse/configs/x86 # jailhouse enable sysconfig.cell
>
> Initializing Jailhouse hypervisor v0.12 (197-g2f52a11d) on CPU 1 Code
> location: 0xfffffffff0000050 Using x2APIC
> /home/msainz/Projects/jailhouse/hypervisor/arch/x86/vmx.c:238:
> returning error -EIO
> JAILHOUSE_ENABLE: Input/output error
That means your host is missing some essential VMX (VT-x) features. Then it's
either a 10 years old machine, or you are running in a VM, and nesting does not
provide sufficient emulation (KVM would).
Jan
>
>
> -----Mensaje original-----
> De: [email protected] <[email protected]> En
> nombre de Sainz Markel Enviado el: martes, 1 de diciembre de 2020
> 10:07
> Para: Jan Kiszka <[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.
>
>
> I did not. I'm running this on a busybox based Linux. No Python installation
> possible. I'm going to check the mentioned docs, any other output I could
> upload for you, not dependant on Python?
>
> -----Mensaje original-----
> De: Jan Kiszka <[email protected]> Enviado el: martes, 1 de
> diciembre de 2020 10:04
> 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 01.12.20 08:48, Sainz Markel wrote:
>> Hi there,
>>
>> After being able to resolve the cmdline issue, the following error
>> comes up when trying to enable the cell:
>>
>> ~/jailhouse/configs/x86 # jailhouse enable sysconfig.cell
>>
>> Initializing Jailhouse hypervisor v0.12 (197-g2f52a11d) on CPU 5 Code
>> location: 0xfffffffff0000050 Using x2APIC
>> JAILHOUSE_ENABLE: Input/output error
>>
>
> Did your target pass "jailhouse hardware check"? If so, enable
> CONFIG_TRACE_ERROR (see Documentation/hypervisor-configuration.md) to get the
> origin of this.
>
> 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://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgrou
> ps.google.com%2Fd%2Fmsgid%2Fjailhouse-dev%2FPA4PR03MB718436DFE4DECCCDA
> 1A7DEBAB6F40%2540PA4PR03MB7184.eurprd03.prod.outlook.com&data=04%7
> C01%7CMsainz%40ikerlan.es%7Cdb91af85d2bf409dd8f508d895ecb1a7%7C910ac81
> 5f8554a08bf2990b46552cf11%7C0%7C0%7C637424191133061092%7CUnknown%7CTWF
> pbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6M
> n0%3D%7C1000&sdata=uYKKJ79wPc0OuxH2Q8KpmCvguFYDDyoLPOYbx5kuqg8%3D&
> amp;reserved=0
>
--
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/PA4PR03MB71849EE161653DBBA71FA26AB6F30%40PA4PR03MB7184.eurprd03.prod.outlook.com.
