On 2016-11-07 17:23, [email protected] wrote: >> >>> >>> But if I may, I have a couple more questions that I would like to clarify: >>> 1. When running a non-root linux cell for the first time, would it be >>> necessary to supply a initrd.img file for example from my PC's >>> /boot/initrd.img-xxx? >> >> The non-root Linux needs a rootfs, and the most simple source for that >> can be an initrd. I've built mine via buildroot. You distro's initrd may >> not give you the desired features and bark at you as it wants to boot a >> full system afterwards, but it may also be a simple starting point for >> tests. > > If my understanding is correct, as of now, it is impossible to deploy a full > system linux, say ubuntu, to a jailhouse non root cell?
No, but you need to give some mass storage for that to the cell, either via a separate physical storage controller (with some disks) or via network (NFS, NAS, you name it). > > I'll try buildroot tomorrow and inform you of my results. > >> >>> >>> 2. Also, if my understanding is correct, it is necessary to perform a >>> passing/passthrough of my separate GPU (pci) to the non-root linux cell in >>> order to view or display the now running non-root linux cell? (when i tried >>> to pass through my gpu, i encountered a "!!! unknown header type 7f" error >>> but i was also able to see the log where jailhouse was able to claim the >>> gpu. My PC froze upon doing so >> >> There are a number of ways to talk to your non-root Linux cell. The >> simplest one is passing through a physical UART and using that as >> console. Then you could assign a physical NIC to the cell that is >> attached to the same network as the root cell and do ssh etc. Last but >> not least, we are working on shared-memory based inter-cell networks so >> that there is no need for closing that loop externally. >> >> GPU device assignment, in contrast, is a complex topic. Just check what >> Linux (via VFIO) is doing for that - if it is possible at all for your >> particular GPU. We are not looking into that topic for that reasons. >> >>> >>> 3. I was able to pass my extra NIC to the non-root linux cell with the same >>> unknown header message above but this time the PC did not freeze. But as >>> soon as i performed jailhouse disable, the control of the NIC was not >>> returned successfully to the root cell. Upon performing lspci, it no >>> longer display a kernel driver in use and the memory regions were disabled >> >> That indicates something is either inconsistent in your configuration >> files, or the device somehow got upset while being using in the non-root >> cell and is not coming back. Normally, the Jailhouse Linux driver >> initiates a rescan after destroying non-root cells with assigned devices >> (which includes the shutdown case). >> >>> >>> Im sorry if im not able to provide any logs as of now since i do not have a >>> serial port. Is it possible to setup a vga-console on my integrated gpu >>> which uses a DVI connection? (but in bios it mentions that it is a vga >>> adapter) >> >> You don't have any UART at all, or just no separate one for the non-root >> cell? You definitely want at least on for the hypervisor output, or you >> are blind. That can practically be shared with a non-root cell. >> >> Do you have free PCI[e] slots? Try to get some UARTs as PCI extension card. > > As for this, I currently do not have any UART available and might not be able > to get one soon. Least I could try is get the NIC working and SSH. You may miss hypervisor reports of cell boundary violations and find locked up systems without being able to diagnose them. Therefore more recommendation. Jan -- Siemens AG, Corporate Technology, CT RDA ITP 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.
