I added the "-k 10" to the command and unfortunately it did not make a difference with the unpacking. If I add "root=/dev/ram0" it does get past the unpacking, but throws the panic for "System is deadlocked on memory".
I have attached my current non-root kernel config. Should I expect to be able to log in to the non-root if I use the same initramfs as the root linux? Wayne On Thu, Jun 13, 2019 at 2:06 PM Jan Kiszka <[email protected]> wrote: > On 13.06.19 20:01, Wayne wrote: > > Jan/Ralf: > > > > I tried your suggestion with using the root node initramfs for the > non-root, > > with two different scenarios. Both of them end in kernel panic for > different > > reasons. > > > > Note that my root node is currently: > > vanilla 4.16 kernel > > "CONFIG_JAILHOUSE_GUEST=y" > > > > Non-root linux: > > jailhouse enabling 4.19 kernel from Siemens > > "CONFIG_JAILHOUSE_GUEST=y" > > "CONFIG_SERIO is not set" > > > > 1. If I don't provide a root arg to the command line, like this: > > ./tools/jailhouse cell linux configs/x86/linux-x86-demo.cell > > /boot/vmlinuz-4.19.46_GuestMin-dbg -i /boot/initramfs-4.16.0Guest+.img > -c > > "console=jailhouse" > > Try adding "-k 10" to that command. If you have enough RAM, that will move > the > kernel and initrd further apart so that the former does not step on the > latter > while unpacking itself. > > Which config are you using for your non-root kernel now? > > Jan > > -- > 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/CA%2B%2BKhc0whU3%3DU86WGNEtLUZoOkKuYLiEA%2BnqOjW1UFcRDeGTRQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
config_kernel_non-root
Description: Binary data
