OK, Changed configs for inmate to UART0, and the messages appeared on the console (on the ZCU102 board, not QEMU), so it is indeed functional. root@plnx_aarch64:~# jailhouse/usr/local/sbin/jailhouse cell start ZynqMP-linux-demo Started cell "ZynqMP-linux-demo" Hello 1 from cell! Hello 2 from cell! Hello 3 from cell! --- etc
Edgar, are the images I have sent of any help? Let me know if you need any other information about the setup. Best Regards, Constantin P.S. Sent the above previously by chance only to Edgar, reposted again for the larger audience :) On Thu, Apr 20, 2017 at 11:19 AM, Constantin Petra < constantin.pe...@gmail.com> wrote: > Hi, > > Sure, I have added the archive containing the image files and jailhouse > build here (the archive contains the /tftpboot folder directly) > https://drive.google.com/file/d/0B2bhbcx8eg-caTBNdnZ4cWhJcWc/view?usp= > sharing > > I use the following sequence to start qemu / kernel / jailhouse, provided > the /tftpboot folder has the structure in the previously archive and, of > course, there is tftp access to the host) > petalinux-boot --qemu --uboot --qemu-args "-redir tcp:10022:10.0.2.15:22" > > In QEMU: > setenv bootargs 'console=ttyPS0,115200'; tftpboot 0x10000000 image.ub; > bootm > > tftp -g 10.0.2.2 jailhouse.tar.gz -r jailhouse.tar.gz > > tar zvxf jailhouse.tar.gz > > mv tftpboot/jailhouse jailhouse > > mkdir -p /lib/firmware > > cp ./jailhouse/lib/firmware/jailhouse.bin /lib/firmware > > insmod ./jailhouse/lib/modules/4.11.0-rc4/extra/driver/jailhouse.ko > > sleep 2 > > jailhouse/usr/local/sbin/jailhouse enable /home/root/jailhouse/configs/ > zynqmp-zcu102.cell > > > Thank you, > > Constantin > > > On Apr 19, 2017 23:30, "Edgar E. Iglesias" <edgar.igles...@xilinx.com> > wrote: > >> On Wed, Apr 19, 2017 at 11:02:21AM +0200, Jan Kiszka wrote: >> > On 2017-04-19 10:45, Peter Maydell wrote: >> > > On 19 April 2017 at 05:37, Jan Kiszka <jan.kis...@web.de> wrote: >> > >> On 2017-04-19 05:48, Constantin Petra wrote: >> > >>> 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. >> > > >> > > This has been in upstream QEMU for a little while now, >> > > and will be in the upcoming 2.9 release. (Applies only for >> > > AArch64 hosts using GICv3, needs some board support changes >> > > which have currently only been done for 'virt'.) >> > >> > Ah, v3 - oversaw this "minor" detail. Too bad that there is still no >> > GICv3 silicon in our hands that we could test against (do you know some >> > recommendable board?). I'm pretty sure Jailhouse's GICv3 support is >> > broken by now (due to lacking tests), plus it is not yet enabled for our >> > ARM64 port. But I'm a bit reluctant to enable this only over QEMU... >> >> Hi, >> >> Xilinx QEMU has support for the virtualization extensions in the GICv2 but >> we're seeing issues with running hypervisors in multi-core setups. >> It seems like guest migration between cores is causing trouble but we >> haven't pinpointed the exact cause. >> >> I'd be interested in debugging the problem seen with Jailhouse. >> Can the images and instructions on howto run be shared with me? >> >> Thanks, >> Edgar >> >
