On Tue, Nov 05, 2019 at 04:58:34PM -0700, Alex Williamson wrote:
> On Wed, 6 Nov 2019 00:29:52 +0100
> Samuel Ortiz wrote:
>
> > On Tue, Nov 05, 2019 at 01:21:48PM -0700, Alex Williamson wrote:
> > > On Fri, 18 Oct 2019 05:48:49 +
> > > "Boeuf, Sebastien" wrote:
> > >
> > > > Hi folks,
>
ication below. Thanks,
Alex
On Mon, 28 Oct 2019 08:13:23 +
"Liu, Yi L" wrote:
> Hi Sebastien,
>
> That’s great it works for you. I remember there was an effort
> to fix it in community. But I cannot recall if it was documented.
> If not, I think I can co-work wi
On Tue, Nov 05, 2019 at 01:21:48PM -0700, Alex Williamson wrote:
> On Fri, 18 Oct 2019 05:48:49 +
> "Boeuf, Sebastien" wrote:
>
> > Hi folks,
> >
> > I have been recently working with VFIO, and particularly trying to
> > achieve device passthrough through multiple layers of virtualization.
>
On Fri, 18 Oct 2019 05:48:49 +
"Boeuf, Sebastien" wrote:
> Hi folks,
>
> I have been recently working with VFIO, and particularly trying to
> achieve device passthrough through multiple layers of virtualization.
>
> I wanted to assess QEMU's performances with nested VFIO, using the
> emulat
Hi folks,
I have been recently working with VFIO, and particularly trying to
achieve device passthrough through multiple layers of virtualization.
I wanted to assess QEMU's performances with nested VFIO, using the
emulated Intel IOMMU device. Unfortunately, I cannot make any of my
physical device
