Re: [Qemu-devel] Jailhouse on Ultrascale+ (ZCU102)

[Constantin Petra]

Yes, I am using the QEMU version included by Xilinx in PetaLinux 2016.4.

On Wed, Apr 19, 2017 at 7:37 AM, Jan Kiszka <address@hidden> wrote:

> On 2017-04-19 05:48, Constantin Petra wrote:
> > Hello,
> >
> > I have tried the same binaries on a ZCU102 board and it seems to work.
> > Cannot be sure though, the board is remote and I don't have access to
> > the secondary UART as I understand it would be required for the
> uart-demo.
>
> You can always reconfigure this to the primary one. We share it in other
> setups as well.
>
> > So from some reason, under QEMU something is not in place, but what can
> > that be? It would be convenient from our perspective, if it would work...
>
> I fully agree, and I'm waiting for official EL2 support in QEMU in order
> to introduce a virtual target for ARM[64], just like we have on x86
> already.
>
> I suppose you are using Xilinx' version of QEMU, not upstream, correct?
> I didn't track recently what the state of upstream is. Just checking the
> list again, seeing some interesting patches from early this year...
> Peter, can you comment on what is still missing? I'm reading that you
> successfully booted KVM inside QEMU. Seems like we are pretty close now
> and it could make sense to debug the remaining issues.
>
> Jan
>
> >
> > address@hidden:~# jailhouse/usr/local/sbin/jailhouse cell list
> > ID      Name                    State           Assigned CPUs
> > Failed CPUs
> > 0       ZynqMP-ZCU102           running         0-2
> > 1       gic-demo                running         3
> >
> >
> > Best Regards,
> > Constantin
> >
> > On Tue, Apr 18, 2017 at 1:32 PM, Constantin Petra
> > <address@hidden <mailto:address@hidden>> wrote:
> >
> >     Hi,
> >
> >     Yes, that's correct, I'm trying to run the whole stack in QEMU, not
> >     hardware.
> >
> >     Best Regards,
> >     Constantin
> >
> >     On Tue, Apr 18, 2017 at 12:52 PM, Jan Kiszka <address@hidden
> >     <mailto:address@hidden>> wrote:
> >
> >         On 2017-04-18 10:22, address@hidden
> >         <mailto:address@hidden> wrote:
> >         > Hi,
> >         >
> >         > I have made the changes to pci.c, but QEMU seems to freeze
> after enabling Jailhouse after the "opening" message is displayed (I have
> previously started a SSH connection which also freezes - to make sure the
> Serial port is not somehow hijacked by hypervisor as described in the
> documentaiton). I cannot start GDB using petalinux tools due to a Python
> 2.6 dependency (the system has Python 2.7) so I don't really know what
> happens. Any ideas? (Attached also a log file with the boot messages; tried
> relying on configured dtb and here also tried memmap for the reserved
> memory, with the same result).
> >         >
> >
> >         Oh, now I get it: You are running the whole stack emulated in
> >         QEMU, not
> >         on real hardware, right? Maybe there is a subtle difference in
> >         the QEMU
> >         system configuration compared to the board, or Jailhouse is
> >         stressing
> >         some aspect of virtualization that the QEMU model does not yet
> >         handle
> >         correctly or at all.
> >
> >         Adding Edgar, maybe he can comment on the state of hypervisor
> >         execution
> >         in the Xilinx QEMU version. He will probably need some details
> >         about the
> >         setup (versions, configuration etc.).
> >
> >         Jan
> >
> >         > address@hidden:~# jailhouse/usr/local/sbin/jailhouse enable
> >         /home/root/jailhouse/configs/zynqmp-zcu102.cell
> >         >
> >         > Initializing Jailhouse hypervisor v0.6 (47-ge02403c-dirty) on
> >         CPU 0
> >         > Code location: 0x0000ffffc0200040
> >         > Page pool usage after early setup: mem 33/996, remap 64/131072
> >         > Initializing processors:
> >         >  CPU 0... OK
> >         >  CPU 1... OK
> >         >  CPU 2... OK
> >         >  CPU 3... OK
> >         > Adding virtual PCI device 00:00.0 to cell "ZynqMP-ZCU102"
> >         > Adding virtual PCI device 00:01.0 to cell "ZynqMP-ZCU102"
> >         > Page pool usage after late setup: mem 44/996, remap 69/131072
> >         > Activating hypervisor
> >         > [   71.547900] OF: PCI: host bridge //address@hidden ranges:
> >         > [   71.549101] OF: PCI:   MEM 0xfc100000..0xfc103fff ->
> 0xfc100000
> >         > [   71.552493] pci-host-generic fc000000.vpci: ECAM at [mem
> >         0xfc000000-0xfc0fffff] for [bus 00]
> >         > [   71.555644] pci-host-generic fc000000.vpci: PCI host bridge
> >         to bus 0001:00
> >         > [   71.556337] pci_bus 0001:00: root bus resource [bus 00]
> >         > [   71.556698] pci_bus 0001:00: root bus resource [mem
> >         0xfc100000-0xfc103fff]
> >         > [   71.569008] pci 0001:00:00.0: BAR 0: assigned [mem
> >         0xfc100000-0xfc1000ff 64bit]
> >         > [   71.570284] pci 0001:00:01.0: BAR 0: assigned [mem
> >         0xfc100100-0xfc1001ff 64bit]
> >         > [   71.576654] The Jailhouse is opening.
> >         > address@hidden:~#
> >         >
> >         > Best Regards,
> >         > Constantin
> >         >
> >
> >
> >
>
>