Am Sun, 24 Oct 2021 23:26:06 -0700 (PDT) schrieb Moustafa Nofal <[email protected]>:
> I was not able to find a documentation about this jailhouse command > "Jailhouse cell linux" , what I understand it takes the following > arguments: > - linux configuration file .cell > - kernel image .img > - device tree file .dtb Might well be very little documentation on that. The code would be under tools/jailhouse-cell-linux which might give a little more insight on what it does and how. And "./jailhouse-cell-linux --help" might help. > -rootfs.cpio, It might be not clear to me, is it necessary to load > this file, how can it be built? As seen in --help that is an optional argument. That would be your root filesystem as cpio archive. But unless you have nfs or assign a mass storage device you will very likely want that. But rootfs could be embedded in the kernel as well. Easiest way to get one for your architecture is to take one generated by jailhouse-images. (where internally buildroot is used to generate a minimal demo-rootfs) > - console , baud rate and IP. things that would go on the kernel cmdline. Imagine the tool like a bootloader, it will need kernel, cmdline, possibly initrd (that cpio) and possible device tree. > Another question: I used Jailhouse-images and started a > linux-non-root-cell, but the UART terminal hangs at this point, is > there any solution for this. So, I tried to ping/SSH IP from another > terminal over LAN but it is unreachable. Maybe start with the virtual qemu target, in which things should work. Not sure if that second linux will have its own uart there, but it should come up and be reachable via network a few secs after start. regards, Henning > Thanks in advance > Moustafa Noufale > -- 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/20211025161715.61aa35fe%40md1za8fc.ad001.siemens.net.
