On 29.12.19 13:16, [email protected] wrote:
Am Sonntag, 29. Dezember 2019 11:48:45 UTC+1 schrieb Jan Kiszka:Are you using jailhouse-images master, ie. -cpu host,...? Or was this -cpu kvm64? pure master, ie, "-cpu host..." This may still be a limitation of the host CPU. quite convinced about that :) , after trying to solve/understand the mess about x2APIC on these processors for the last days (sidenote, I have to start my host system (see above) with kernel parameter nox2apic, because the up-to-date BIOS still forbids it. x2APIC is emulated by qemu) Could you try "jailhouse hardware check" with this patch on the host? sure, reflects exactly what I found by fiddling in vmx.c: with default start-qemu.sh -> "XSAVES MISSING" ... "Check FAILED!" with "-xsaves" added to qemu's -cpu param -> "XSAVES missing (optional)" ... "Check passed!" (and it seems usable) jh_hw_chk_wPatch-xsaves.png jh_hw_chk_wPatch.png <about:invalid#zClosurez>
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. Jan -- 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/1244a8aa-25d4-b475-9371-681939ebae8d%40web.de.
