Hi Mr. Kiszka, >To enable Jailhouse on the Coral board as well, you likely have three >options: >- ad-hoc compilation on the board, using their "Mendel Linux" (also > Debian) >- integrating Jailhouse into Mendel Linux > - defining a new target "Coral dev board" in jailhouse-images, porting > the integration from Mendel Linux over I have just got the Coral board and I think I would go with the first option. The planed workflow is: 1- duplicate imx8mm.c /imx8mm-inmate-demo.c/ imx8mm-linux-demo.c and edit it with the memory addresses in Coral Board, which is also using an imx8m. 2- compile jailhouse on the board. 3- insemod jailhouse and run. I am only asking, whether I am going in the right path. Thanks in Advance Moustafa Noufale
-----Ursprüngliche Nachricht----- Von: Jan Kiszka <[email protected]> Gesendet: Sonntag, 2. Mai 2021 14:28 An: Moustafa Noufale <[email protected]>; Ralf Ramsauer <[email protected]>; [email protected] Betreff: Re: [EXT] AW: AW: Inquiry On 02.05.21 10:40, Moustafa Noufale wrote: > Hi Mr. Kiszka and Mr. Ramsauer, > I would like to thank you for your previous support. We are planning to try > jailhouse on a Coral Dev Board with i.MX quad-core Arm Cortex A53. I have > some questions and some conclusions, you can ignore my conclusions if it is > correct: > 1- Docker group is only required to build jailhouse-images in case of > virtual-machine demo, the reason is avoiding running start-image.sh with root > privileges. Am I right? Docker is needed on the host for the Isar build system that jailhouse-images uses, irrespective of the selected target image. To enable Jailhouse on the Coral board as well, you likely have three options: - ad-hoc compilation on the board, using their "Mendel Linux" (also Debian) - integrating Jailhouse into Mendel Linux - defining a new target "Coral dev board" in jailhouse-images, porting the integration from Mendel Linux over Simplest approach will likely be the first (but possibly not easy to reproduce). Cleanest would be one of the other two. Which of them will be simpler I cannot predict. > 2- Communication between cells is possible, but how? Can you recommend me any > reading about this part. https://github.com/siemens/jailhouse/blob/master/Documentation/inter-cell-communication.md > 3- How can I build the inmate or the .cell file? I found in > /jailhouse-master/configs/x86 c files, object files and .cell files but the > procedure to build a customised image is not still clear to me. I read your > reply on jailhouse-dev.narkive.com and I think I should use "jailhouse config > create" to build an inmate. I would appreciate any help or any information > regarding this question. I've already shared the tutorial with you. That describes the principles. The config generator so far only supports x86. For ARM/ARM64, study or derive from existing configs (configs/arm64/imx8mm* might be helpful for the Coral dev board). Any own config source file (*.c) placed in the configs/<arch>/ folders will be built along the rest of Jailhouse. If you want a non-root Linux inmate, also check configs/arm64/dts/imate-*.dts. Maybe inmate-imx8mm-evk.dts will be of help as well. And also here: any *.dts file in those dts/ folders will be automatically picked up by the build system. 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/0f730442242846238f7a5695a4a04f2f%40uni-rostock.de.
