On 21.05.19 15:45, Ralf Ramsauer wrote:
Hi,
we have some issues enabling Jailhouse on a Intel with a pretty new CPU
(Xeon Gold 5118).
First, the CPU supports PKE and Linux will enable it (CR4, Bit 22).
Jailhouse won't start, as this bit is marked in X86_CR4_RESERVED. Didn't
have a deeper look into this on how it affects the hypervisor or
allowing it needs some special treatment, so adding nopku to the
commandline will keep the feature disabled and suffices for the moment.
Known issue, see https://github.com/siemens/jailhouse/pull/23
Anyway, after enabling Jailhouse, our system freezes and we have some
IOMMU faults on a Broadcom ethernet card (04:00.0). Find the error
message below.
We have fault reason 0x22. But according to Intel documentation (latest
version from 2018)… There is no 0x22. :-) I already checked if decoding
of the fault register is correct -- nothing suspicious.
Table 13, 22h: "The Present (P) field in the IRTE entry corresponding to the
interrupt_index of the interrupt request is Clear."
Wrong IOMMU unit set for that device?
Jan
Any ideas?
Thanks
Ralf
Page pool usage after late setup: mem 704/975, remap 65560/131072
Activating hypervisor
VT-d fault event reported by IOMMU 3:
Source Identifier (bus:dev.func): 04:00.0
Fault Reason: 0x22 Fault Info: 19000000000 Type 0
VT-d fault event reported by IOMMU 3:
Source Identifier (bus:dev.func): 04:00.0
Fault Reason: 0x22 Fault Info: 18000000000 Type 0
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
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/fd82641f-4f35-3674-af69-68fb41624fd8%40siemens.com.
For more options, visit https://groups.google.com/d/optout.
