On 22.09.21 12:15, Martin Kaistra wrote: > Hi all, > > > > I am currently trying to bring up Jailhouse on a ZynqMP ZU2CG-1I board > with two cores. I can see two different types of behaviour when trying > to start on of the inmate demos. Sometimes everything works fine and I > can see the output of the uart-demo running on the second cpu. In more > than half of my tests, however, the system gets stuck after calling > "jailhouse cell create inmate.cell". > > > > I added some debugging output to the hypervisor code and I can see, that > it gets stuck in the loop while (!target_data->cpu_suspended) in > suspend_cpu() which gets called from cell_create() -> cell_suspend() > with cpu_id=1 while this_cpu_id() is 0. > > > > In these non-working cases, check_events() in > hypervisor/arch/arm-common/control.c doesn't seem to be called. > > > > I am using Jailhouse master and a kernel based on xilinx-v2021.1 (5.10). > > > > Has anyone run into this before? > >
If suspend_cpu() does not progress, the target CPU is not reacting properly on the request to leave the guest and service the Jailhouse commands. Could be that you interrupts are not handles properly. Run "jailhouse config check" on your setup, maybe you are passing the interrupt controller through. Or are you using SDEI-based management interrupts? Would require a special TF-A version, so likely does not happen "by chance". 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jailhouse-dev/8092b487-f19d-dc89-98e0-cb68077792f9%40web.de.
