yahoo-eng-team team mailing list archive

[KaiLin <linkai3@xxxxxxxxxx>]

Public bug reported:

SYMPTOM:
I used the mellonax nic as SR-IOV, then create  VMs has a problem (some can create success,some failed) ,and the traffic  is also affected (the VLAN of some VMs is error).

CAUSE:
Due to the particularity of mellonax nic, a PCI number corresponding to the two physical net ports, so lead to that nova side only scan to one net port from the PCI , and doesn't perceive another one.

In my environment, eth0 has three available VF resources, eth1 has four
available VF resources.

the comment of nova-compute.conf:
       pci_passthrough_whitelist={"devname":"eth1","physical_network":"sriov_net2","bandwidths":"0"}
       pci_passthrough_whitelist={"devname":"eth0","physical_network":"sriov_net","bandwidths":"10000"}

Even if the whitelist is correctly configured, Nova from whitelist is
still unable to get VF resources information network port, Nova side
only scan by PCI , when scanned a corresponding PCI net port, does not
scan a network the rest of the ports, causing direct plane in the net
export under the network not VF resources,so create a virtual machine
failed in the through plane.And the net port that has been scanned
occupies the VF resources of another net port,this will result in front
of a portion of the virtual machine settings VLAN error.

** Affects: nova
     Importance: Undecided
     Assignee: KaiLin (linkai3)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => KaiLin (linkai3)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1400574

Title:
  Create VMs sometimes failure when use mellonax nic as SR-IOV

Status in OpenStack Compute (Nova):
  New

Bug description:
  SYMPTOM:
  I used the mellonax nic as SR-IOV, then create  VMs has a problem (some can create success,some failed) ,and the traffic  is also affected (the VLAN of some VMs is error).

  CAUSE:
  Due to the particularity of mellonax nic, a PCI number corresponding to the two physical net ports, so lead to that nova side only scan to one net port from the PCI , and doesn't perceive another one.

  In my environment, eth0 has three available VF resources, eth1 has
  four available VF resources.

  the comment of nova-compute.conf:
         pci_passthrough_whitelist={"devname":"eth1","physical_network":"sriov_net2","bandwidths":"0"}
         pci_passthrough_whitelist={"devname":"eth0","physical_network":"sriov_net","bandwidths":"10000"}

  Even if the whitelist is correctly configured, Nova from whitelist is
  still unable to get VF resources information network port, Nova side
  only scan by PCI , when scanned a corresponding PCI net port, does not
  scan a network the rest of the ports, causing direct plane in the net
  export under the network not VF resources,so create a virtual machine
  failed in the through plane.And the net port that has been scanned
  occupies the VF resources of another net port,this will result in
  front of a portion of the virtual machine settings VLAN error.

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