On Friday, February 1, 2019 at 12:32:40 AM UTC-7, J. Kiszka wrote: > You likely want > https://github.com/siemens/linux/commits/jailhouse-enabling/4.14 > or the 4.19-variant that is jailhouse-prepared. That's what jailhouse-images > is > building for you. > If you just rebuild the kernel that the original image was using, only adding > UIO, you should be fine with keeping the jailhouse kernel package untouched. > But > the cleanest way is reproducing the image via jailhouse-images after > adjusting > the parameter you want to change (CONFIG_UIO, ROOTFS_EXTRA etc.). > > Jan > > -- > Siemens AG, Corporate Technology, CT RDA IOT SES-DE > Corporate Competence Center Embedded Linux
That worked! I was able to figure out the correct kernel to build by looking at jailhouse-images/recipes-kernel/linux/linux-jailhouse.bb from when I last generated my image at 4.14.73 (https://github.com/siemens/linux/archive/1dd68658b3a8308a160b0786fc4e1e04d8ff5216.tar.gz). With that, I supplied QEMU with the new UIO-enabled kernel image and built jailhouse and uio_ivshmem.ko and ran the ivshmem jailhouse demo. However, I'm still not sure how to read in the data from the ivshmem-demo. Once I insmod uio_ivshmem.ko, shouldn't there be a device called /dev/uio0 that I can read "Hello From IVSHMEM" from and write back to? And shouldn't there be an entry in /sys/class/uio/? I don't see either of these, and I'm not quite sure how to debug this yet. The only documentation I can find on this is https://www.kernel.org/doc/html/v4.18/driver-api/uio-howto.html. Any help is appreciated. Sorry to be a bother. Thanks! -Michael -- 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.
