Open FedericoRessi opened 8 years ago
Before stacking:
/opt/stack/dpdk/tools$ ./dpdk_nic_bind.py --status
Network devices using DPDK-compatible driver
============================================
<none>
Network devices using kernel driver
===================================
0000:00:03.0 '82540EM Gigabit Ethernet Controller' if=eth0 drv=e1000 unused= *Active*
0000:00:08.0 '82540EM Gigabit Ethernet Controller' if=eth1 drv=e1000 unused= *Active*
0000:00:09.0 '82540EM Gigabit Ethernet Controller' if=eth2 drv=e1000 unused= *Active*
0000:00:0a.0 '82540EM Gigabit Ethernet Controller' if=eth3 drv=e1000 unused=
Other network devices
=====================
<none>
After stacking:
/opt/stack/dpdk/tools$ ./dpdk_nic_bind.py --status
Network devices using DPDK-compatible driver
============================================
0000:00:0a.0 '82540EM Gigabit Ethernet Controller' drv=igb_uio unused=
Network devices using kernel driver
===================================
0000:00:03.0 '82540EM Gigabit Ethernet Controller' if=eth0 drv=e1000 unused=igb_uio *Active*
0000:00:08.0 '82540EM Gigabit Ethernet Controller' if=eth1 drv=e1000 unused=igb_uio *Active*
0000:00:09.0 '82540EM Gigabit Ethernet Controller' if=eth2 drv=e1000 unused=igb_uio *Active*
Other network devices
=====================
<none>
According last conversation I had on this issue this should not affect this workflow if devstack is used to launch openstack and ovs-dpdk.
This bug has to be probably workaround as it is expected to hurt compute node when using Ubuntu.
https://bugs.launchpad.net/ubuntu/+source/pciutils/+bug/1516095
Proposed workaround for it is running following just before stacking:
Where would be one of following: