← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1400574] Re: Create VMs sometimes failure when use mellonax nic as SR-IOV

 

Since the bug reporter hasn't provided the necessary information,bug has
been closed. Feel free to reopen the bug by providing the requested
information and set the bug status back to ''New''.

** Changed in: nova
       Status: Incomplete => Invalid

-- 
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):
  Invalid

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


References