Please see inline
On Thu, Feb 19, 2015 at 4:43 PM, Steve Gordon wrote:
> - Original Message -
> > From: "Irena Berezovsky"
> > To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>,
> >
> > On Thu, Feb 5, 2015 at 9:01 PM, Steve Gordon
- Original Message -
> From: "Irena Berezovsky"
> To: "OpenStack Development Mailing List (not for usage questions)"
> ,
>
> On Thu, Feb 5, 2015 at 9:01 PM, Steve Gordon wrote:
>
> > - Original Message -
> > > From: "Przemyslaw Czesnowicz"
> > > To: "OpenStack Development Mail
On Thu, Feb 5, 2015 at 9:01 PM, Steve Gordon wrote:
> - Original Message -
> > From: "Przemyslaw Czesnowicz"
> > To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> >
> > Hi
> >
> > > 1) If the device is a "normal" PCI device, but i
- Original Message -
> From: "Przemyslaw Czesnowicz"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
>
> Hi
>
> > 1) If the device is a "normal" PCI device, but is a network card, am I
> > still able to
> > take advantage of the advanced syntax added circa Juno
Hi
> 1) If the device is a "normal" PCI device, but is a network card, am I still
> able to
> take advantage of the advanced syntax added circa Juno to define the
> relationship between that card and a given physical network so that the
> scheduler can place accordingly (and does this still use
Hi all,
In the current SR-IOV implementation there is a check in Nova (specifically
_get_device_type in nova/virt/libvirt/driver.py) that determines if a given PCI
device is:
- a normal PCI device,
- an SR-IOV physical function (PF); or
- an SR-IOV virtual function (VF).
If it's a normal PCI d
