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

-- 
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 jailhouse-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to