On 2018-05-04 05:58, [email protected] wrote: > On Tuesday, May 1, 2018 at 10:23:21 PM UTC+5:30, Jan Kiszka wrote: >> On 2018-04-30 15:26, [email protected] wrote: >>> Hey Thanks jan, that's worked I am able ping from root-cell to non-root >>> cell and vice-versa. >>> >>> suppose i want to boot the non-root cell with different kernel image how >>> can i proceed? is their any option to copy our images to pre-built qemu >>> machine(i want know how to copy files from host machine to qemu)? >> >> The demo image is configured with virtual networking to the host. You >> can do ssh 10.0.2.2 from within the VM, or you forward the ssh port of >> the guest to the host (see QEMU documenation for host forwards). >> >> Jan > > Thanks jan for your help, > Now I am able to copy my images(kernel,rootcell, nonrootcell &initrd) to the > qemu-setup which you provided. > I tried with my kernel image to boot your non-root cell it is not booting, it > got stuck in the middle of booting. > Then I compiled kernel image using your .config(got it from your kernel > source directory), with this image I am able to boot non-root cell and I can > see the interrupts also. > > From above experiment I understand there is no problem with our jailhouse > rootcell & non rootcell configs. > > I tried loading demo images(kernel & initrd) which you provided on our qemu > setup. with this I am able to boot and I can enable rootcell and i can boot > the non-root cell also but I am not able to see the interrupts. > So we want to understand what we are missing. Is there any dependency on Qemu > setup to make it work? Is there any kernel config required to make shared > memory working?
Yes, there are dependencies: The version requirement is described, and the command line is - for a reason - encoded into the startup script we ship (and also the README.md from jailhouse). If you change the command line, you may need your own system config for Jailhouse. But then you lose the tunings for ivshmem we added. It's still very hard for us to understand what is the key as we do not know what exactly you did, what you changed from the original setup. Again, do one step at a time towards the configuration you want to achieve. Why "X" makes a difference is much easier to explain than "X Y Z", of which you may only describe "X Y" here. > one more observation is you are running some scripts to make interface up and > some modifications in rootfs(I didnt find any document or description for > this). All customizations are done by recipes-core/customizations/customizations.bb. That recipe generates a customizations.deb which installs a number of files (from .../files) and runs .../files/postinst. But that are just plain Debian customizations. 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]. For more options, visit https://groups.google.com/d/optout.
