The networking-ovn project was shut down and all code moved to neutron,
will try and re-target this bug.
** Also affects: neutron
Importance: Undecided
Status: New
** Changed in: networking-ovn
Status: New => Invalid
** Tags added: ovn sriov-pci-pt
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2115768
Title:
Mellanox Technologies MT2892 Family [ConnectX-6 Dx] SRIOV using
Openstack - No IP inside the VM
Status in networking-ovn:
Invalid
Status in neutron:
New
Bug description:
Hello,
Im using SRIOV using Openstack(version: Antelope) which is deployed using
kolla-ansible deployment (single node setup).
Ethernet card details:
root@poc-dev-3:/home/user# lspci -nnv -s a2:00.0
a2:00.0 Ethernet controller [0200]: Mellanox Technologies MT2892 Family
[ConnectX-6 Dx] [15b3:101d]
Subsystem: Mellanox Technologies MT2892 Family [ConnectX-6 Dx]
[15b3:0040]
Physical Slot: 5
Flags: bus master, fast devsel, latency 0, IRQ 18, NUMA node 2, IOMMU
group 161
Memory at e0000000 (64-bit, prefetchable) [size=32M]
Capabilities: [60] Express Endpoint, MSI 00
Capabilities: [48] Vital Product Data
Capabilities: [9c] MSI-X: Enable+ Count=64 Masked-
Capabilities: [c0] Vendor Specific Information: Len=18 <?>
Capabilities: [40] Power Management version 3
Capabilities: [100] Advanced Error Reporting
Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
Capabilities: [180] Single Root I/O Virtualization (SR-IOV)
Capabilities: [1c0] Secondary PCI Express
Capabilities: [320] Lane Margining at the Receiver <?>
Capabilities: [370] Physical Layer 16.0 GT/s <?>
Capabilities: [420] Data Link Feature <?>
Kernel driver in use: mlx5_core
Kernel modules: mlx5_core
OS Version: Ubuntu 22.04.5 LTS
Grub changes:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX="vfio_iommu_type1.allow_unsafe_interrupts=1 iommu=pt
intel_iommu=on"
SDN used: OVN(enabled with DHCP)
Number of VF’s created using the following command:
echo '7' > /sys/class/net/ens3np0/device/sriov_numvfs
root@poc-dev-3:/home/user# cat /sys/class/net/ens3np0/device/sriov_totalvfs
8
Other Info:
Enabled SRIOV & VT-d in the BIOS configuration
Enabled iommu=pt intel_iommu=on on the grub changes and rebooted the server
Enabled neutron_sriov in the globals.yml file(which is used in
kolla-ansible’s deployment)
Created a physical_network_function(physnet) called sriovtenant1 which is
mapped to ens3np0 port where SRIOV is enabled
Made all the necessary changes in nova-compute(pci devices are listed
passthrough_whitelist = [{“physical_network”: “sriovtenant1”, “devname”:
“ens3np0”}]
Similarlly for ml2_conf.ini
[ml2]
type_drivers = flat,vlan,vxlan,geneve
tenant_network_types = geneve
mechanism_drivers = ovn,sriovnicswitch
extension_drivers = port_security
[ml2_type_vlan]
network_vlan_ranges = sriovtenant1
[ml2_type_flat]
flat_networks = physnet1, sriovtenant1
Enabled PCI passthrough filter in nova-scheduler
ip link show ens3np0
root@poc-dev-3:/home/user# ip link show ens3np0
6: ens3np0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether 88:e9:a4:1f:2f:62 brd ff:ff:ff:ff:ff:ff
vf 0 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof
checking off, link-state auto, trust off, query_rss off
vf 1 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof
checking off, link-state auto, trust off, query_rss off
vf 2 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof
checking off, link-state auto, trust off, query_rss off
vf 3 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof
checking off, link-state auto, trust off, query_rss off
vf 4 link/ether fa:16:3e:e0:03:16 brd ff:ff:ff:ff:ff:ff, vlan 805,
spoof checking on, link-state enable, trust off, query_rss off
vf 5 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof
checking off, link-state auto, trust off, query_rss off
vf 6 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof
checking off, link-state auto, trust off, query_rss off
vf 7 link/ether 22:56:d7:64:61:89 brd ff:ff:ff:ff:ff:ff, spoof
checking on, link-state enable, trust off, query_rss off
altname enp15s0np0
Created sriov-net and used the VLAN network type (provided the same VLAN ID
where the port ens3np0 was connected to switch) and created the subnets & port
with vnic type as direct
Launched an instance using the port created from sriov-net, But there is no
IP address allocated in the VM
No IP Inside the VM
Even Static IP allocation is also not happening
Help me resolve this issue
To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-ovn/+bug/2115768/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
