Am Thu, 23 Mar 2017 01:36:59 -0700 schrieb Harison <[email protected]>:
> Hi. > In the last days, i asked repeated questions because i didn't see > kernel start up on Jetson-tx1 board. Fortunately, the problem at that > time was confirmed to be a problem on the device tree side. After > finishing, i made two initrd using buildroot and ubuntu-base for > non-root cell's root filesystem. After finishing, i can see boot > kernel and initrd normally. I know that i only use initrd for > non-root cell's rootfs. But, initrd is a ramdisk and i know that it > can not save change points. If so, is there any other way to have all > of the functionality of read / write like the existing rootfs? As far as i understand you want writes to the second rootfs to be persistent. You could use a rw filesystem in ram and copy it back out after the cell shut down. However that way persistency could be reached only if you always have a clean shutdown and get a chance to write the dirty image back to disk before host shutdown. Another way could be device assignment where you assign a host controller with a storage device to your non-root cell. You would have to check whether your board has multiple such host-controllers (USB, AHCI ..). The third and maybe easiest way is to establish a virtual network between the root and non-root cell and use NFS-root for the non-root cell. But you should keep in mind that this approach has severe implications on the isolation of the two worlds. regards, Henning -- 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]. For more options, visit https://groups.google.com/d/optout.
