On Tue, 8 Sep 2020 at 17:29, Jan-Marc Stranz <[email protected]> wrote:
> So I still don't have "a booting setup for Jailhouse"! > > What do you mean exactly with "you will still need the Intel IOMMU > parameters"? > Do you mean the kernel configuration option "CONFIG_INTEL_IOMMU" or do you > mean the kernel comand line entry " intel_iommu=on"? > > Why is the option "CONFIG_INTEL_IOMMU" not included in the configuration > fragment "jailhouse.cfg", if this is required? > > I hope that at some point I will come to a system configuration that is > useful for jailhouse. > I am already using everything that is provided in the "meta-agl-devel" > layer with regard to linux kernel and jailhouse. > That's my work. I created the jailhouse.cfg by comparing the configuration I had in the AGL setup with the one from jailhouse-images. My goal was to get it working on RPi4, so I might have skipped IOMMU-related stuff. However, the configuration was working under QEMU on x86, but in the AGL setup where it might have been set from elsewhere. I will check it with pure Yocto and QEMU. I haven't tested the Yocto layer on a physical (non-QEMU) machine, so you're the pioneer here. I would generally recommend first trying to get Jailhouse working in the jailhouse-images system to figure out the Jailhouse stuff before using the Yocto layer. If you find out some missing bits in the layer, let me know, I will fix that. By the way, the layer is now on my GitHub [1] to prepare it for upstreaming. But there shouldn't be any related difference from the one you have. I'm not sure if the IOMMU will behave the same in QEMU and I don't have a spare x86 machine to play with Jailhouse, so I can't test that. [1] https://github.com/Limoto/meta-jailhouse Jakub -- 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/CAGdCPws-hbNUhzANvTyOgWcogiAimRvBTmwOk1rxOnVU5srDqg%40mail.gmail.com.
