On Thu, 29 Jun 2017 17:37:30 +0200
Andrea Bolognani wrote:
> On Wed, 2017-06-28 at 18:22 -0400, Laine Stump wrote:
> [...]
> [...]
>
> Right, I hadn't considered that case. I'll make sure it is
> handled correctly.
>
> [...]
>
> Hm, that's quite a pickle.
>
> Choosing a synthetic iso
On Thu, 2017-06-29 at 17:37 +0200, Andrea Bolognani wrote:
> > I can see one problem here - a device that is a hostdev network
> > interface won't be properly recognized.
> >
> > We can solve the problem for plain by just
> > checking for that in addition to here.
>
> Right, I hadn't considere
On Wed, 2017-06-28 at 18:22 -0400, Laine Stump wrote:
> > +static int
> > +qemuDomainFillDeviceIsolationGroupIter(virDomainDefPtr def
> > ATTRIBUTE_UNUSED,
> > + virDomainDeviceDefPtr dev,
> > + virDomainDeviceInfoPtr info
On 06/23/2017 11:03 AM, Andrea Bolognani wrote:
> All the pieces are now in place, so we can finally start
> using isolation groups to achieve our initial goal, which is
> separating hostdevs from emulated PCI devices while keeping
> hostdevs that belong to the same host IOMMU group together.
Set i
All the pieces are now in place, so we can finally start
using isolation groups to achieve our initial goal, which is
separating hostdevs from emulated PCI devices while keeping
hostdevs that belong to the same host IOMMU group together.
Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=128054
