yahoo-eng-team team mailing list archive

[Preethi Dsilva <preethi.dsilva@xxxxxxx>]

Public bug reported:

dev name in the pci whitelist is not honored for SRIOV

steps to reproduce:
================
1.enable sriov in the bios in my case I have mellanox card with dual port nic which shows up in teh OS as eth4 and eth5
2.provide PCI whitelist in  nova.conf
pci_passthrough_whitelist = {"devname":"eth4","physical_network":"physnet1"}
3.the mlx4_core file is set as options mlx4_core port_type_array=2,2 num_vfs=6 probe_vf=6 enable_64b_cqe_eqe=0  log_num_mgm_entry_size=-1
However, the behavior seen is that irrespective of the devname specified the tenant VM gets booted into eth4 or eth5 .

Tested the issue with MItaka code I am attaching the nova logs and
local.conf for your reference.

** Affects: nova
     Importance: Undecided
         Status: New

** Project changed: neutron => nova

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1572826

Title:
  dev name in the pci whitelist is not honored for SRIOV

Status in OpenStack Compute (nova):
  New

Bug description:
  dev name in the pci whitelist is not honored for SRIOV

  steps to reproduce:
  ================
  1.enable sriov in the bios in my case I have mellanox card with dual port nic which shows up in teh OS as eth4 and eth5
  2.provide PCI whitelist in  nova.conf
  pci_passthrough_whitelist = {"devname":"eth4","physical_network":"physnet1"}
  3.the mlx4_core file is set as options mlx4_core port_type_array=2,2 num_vfs=6 probe_vf=6 enable_64b_cqe_eqe=0  log_num_mgm_entry_size=-1
  However, the behavior seen is that irrespective of the devname specified the tenant VM gets booted into eth4 or eth5 .

  Tested the issue with MItaka code I am attaching the nova logs and
  local.conf for your reference.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1572826/+subscriptions