On 2016-11-07 17:43, Henning Schild wrote: >>> 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). > > The pci code is a helper for safe shrinking of the root cell, but does > not care too much about giving the devices back. > > No there is no rescanning just like there is no hotplugging. The > jailhouse driver can act as a dummy driver but it will not give devices > back to their original drivers or issue anything that has the potential > for BAR reprogramming. It also does not forget device/vendor ids > automatically. > > https://github.com/siemens/jailhouse/blob/master/driver/pci.c#L40 > After a disable you could > "rmmod jailhouse; echo 1 /sys/bus/pci/rescan" > Or you manually write the correct strings to > /sys/bus/pci/drivers/jailhouse/remove_id > and > /sys/bus/pci/drivers/<nicdrv>/bind
Right, forgot this (and we even discussed that back then). Thanks, 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.
