Am Sonntag, 29. Dezember 2019 17:51:00 UTC+1 schrieb Jan Kiszka:
>
> [..]
> Actually, I'm more interested in the feature set of the host CPU, not
> the one QEMU presents. I strongly suspect, though, that it will be
> equivalent to what the guest sees in this regard.
>
I believe the issue with this processor model is only in regards to nested
virtualization. I did run the hardware check directly on the host system
and the flags come up ok (see attached)
However, the (unmodified) host Debian-Linux-Kernel *expectedly* locks up
when I try to enable jailguard. To prepare a trimmed down setup would take
me a little more time, so I rather spend it in the cosy qemu-world.
thanks, Thorsten
--
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/a343e68e-1b20-4e30-92b3-9c43a5a5a3e1%40googlegroups.com.
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 ok
I/O bitmap ok
MSR bitmap ok
Secondary controls ok
Optional CR3 interception ok
Virtualize APIC access ok
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 ok
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
Skipping MMIO tests, your kernel might have CONFIG_STRICT_DEVMEM enabled.
Disable for thorough testing.
VT-d (IOMMU #1) ok
Skipping MMIO tests, your kernel might have CONFIG_STRICT_DEVMEM enabled.
Disable for thorough testing.
Check passed!
BUT: Some essential checks had to be skipped!
