On 2016-06-27 17:12, Raz wrote: > > > On Mon, Jun 27, 2016 at 4:43 PM, Jan Kiszka <[email protected] > <mailto:[email protected]>> wrote: > > On 2016-06-27 10:38, Raz wrote: > > Thanks Jan. > > You were right. > > As a user I have experience with RT-systems solution. So I am a bit > > puzzled because I would expect to see a cpu dropped from both the host > > and the guest. > > First of all, the QEMU setup is for testing purposes - do not confuse > with a real system (with potentially real RT requirements). > > Then, I do not yet understand which CPU should be dropped under with > conditions. Can you describe in more details what you mean? > > I thought the qemu guest would allocate a cpu for the host.
What is the host here? If we remove QEMU from the picture, the host is controlled by Jailhouse. And Jailhouse decides about which physical CPU can be used by which of its guests (cells). When you create a cell, Jailhouse will deny the root cell to use any of the CPUs that are now assigned to the new cell - try onlining one of them again while the non-root exists. > > > > Also, How do we continue ? What do we need to make this boot an OS ? > > > > Which OS? > > I want to boot linux or linux. If you can provide me with guidance how > to boot a linux guest over some ramdisk > that will be nice. I understand that jailhouse is not ready, this is why > I want to contribute - if possible. Look at Documentation/non-root-linux.txt. I currently use an initramfs for testing purposes created via buildroot, .config attached. I also attached a reference config for the kernel. HTH, 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]. For more options, visit https://groups.google.com/d/optout.
buildroot-config.xz
Description: application/xz
kernel-config.xz
Description: application/xz
