** Changed in: neutron
       Status: Confirmed => Fix Released

** Tags added: doc

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

Title:
  SRIOV not working with OvS on same host on vlan network for intel NICs

Status in neutron:
  Fix Released

Bug description:
  Hi,

  Issue -
    On Liberty Openstack with FDB patch, SRIOV VM communication to OvS VM on 
same host is working good for openstack Flat network but not for openstack VLAN 
network.

  Pre condn -
          https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking

  Scenario
        . Create a VLAN network.
        . Create a normal instance VM A VM B, the OVS external bridge(br-ex) is 
connected to PF.
        . I am not able to get the IP from external DHCP and i am able to see 
the fdb entries for the VM.
        . Create SRIOV instance VM C on the same VLAN network on the same 
compute host.
        . I am able to get IP from external server and do ping gateway for VM C 
via VF.
        . VM A & VM B work if i clear the VFs in the same compute host or if i 
create OvS VM after booting SRIOV VMs(i.e, after assigning MAC and VLANs to VFs)
        . But still i am not able to ping each other between VM A/VM B and VM C

  Logs -
        . The TCP dump shows the reply going out of the DHCP server, but it is 
not hitting PF but the ARP is received at the VF and hit the SRIOV instance 
VM-SRIOV.

        . PF is not getting any incoming packets from external server or
  from SRIOV instance.

  Versions -
  Openstack - Liberty with fdb extension
  ixgbe - 4.3.13
  ixgbevf - 3.1.2

  Please help me if i am doing wrong

  Regards,
  MK

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to