[Yahoo-eng-team] [Bug 1628301] Re: SR-IOV not working in Mitaka and Intel X series NIC
Closing this out, after updating the ixgbe and ixgbevf driver I was able
"attach" VF ports on nova instances.
** Changed in: neutron
Status: Incomplete => Invalid
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1628301
Title:
SR-IOV not working in Mitaka and Intel X series NIC
Status in neutron:
Invalid
Status in OpenStack Compute (nova):
Invalid
Bug description:
The SRIO functionality in Mitaka seems broken, all configuration
options we evaluated lead to
NovaException: Unexpected vif_type=binding_failed
errors, stack following.
We are currently using this code base, along with SRIOV configuration posted
here
Nova SHA 611efbe77c712d9ac35904f659d28dd0f0c1b3ff # HEAD of "stable/mitaka"
as of 08.09.2016
Neutron SHA c73269fa480a8a955f440570fc2fa6c347e3bb3c # HEAD of
"stable/mitaka" as of 08.09.2016
Stack :
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa] Traceback (most recent call last):
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa] File
"/openstack/venvs/nova-13.3.4/lib/python2.7/site-packages/nova/compute/manager.py",
line 2218, in _build_resources
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa] yield resources
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa] File
"/openstack/venvs/nova-13.3.4/lib/python2.7/site-packages/nova/compute/manager.py",
line 2064, in _build_and_run_instance
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa] block_device_info=block_device_info)
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa] File
"/openstack/venvs/nova-13.3.4/lib/python2.7/site-packages/nova/virt/libvirt/driver.py",
line 2776, in spawn
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa] write_to_disk=True)
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa] File
"/openstack/venvs/nova-13.3.4/lib/python2.7/site-packages/nova/virt/libvirt/driver.py",
line 4729, in _get_guest_xml
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa] context)
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa] File
"/openstack/venvs/nova-13.3.4/lib/python2.7/site-packages/nova/virt/libvirt/driver.py",
line 4595, in _get_guest_config
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa] flavor, virt_type, self._host)
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa] File
"/openstack/venvs/nova-13.3.4/lib/python2.7/site-packages/nova/virt/libvirt/vif.py",
line 447, in get_config
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa] _("Unexpected vif_type=%s") %
vif_type)
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa] NovaException: Unexpected
vif_type=binding_failed
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa]
Interestingly the nova resource tracker seem to be able to create a
list of all available sriov devices and they show up correctly inside
the database as pci_device table entries
2016-09-27 16:13:52.175 10248 INFO nova.compute.resource_tracker
[req-284a7832-3794-4597-b939-273ea75d45f7 - - - - -] Total usable vcpus: 32,
total allocated vcpus: 0
2016-09-27 16:13:52.175 10248 INFO nova.compute.resource_tracker
[req-284a7832-3794-4597-b939-273ea75d45f7 - - - - -] Final resource view:
name=compute01 phys_ram=25
MB used_ram=2048MB phys_disk=1935GB used_disk=2GB total_vcpus=32 used_vcpus=0
pci_stats=[PciDevicePool(count=15,numa_node=None,product_id='10ed',tags={dev_type='type-VF',physical_network='physnet1'},vendor
_id='8086'),
PciDevicePool(count=2,numa_node=None,product_id='10fb',tags={dev_type='type-PF',physical_network='physnet1'},vendor_id='8086')]
Available ports inside DB:
+-+--++---+--+--+---+
| compute_node_id | address | product_id | vendor_id | dev_type | dev_id
| status|
+-+--++---+--+--+---+
| 5 | :88:10.1 | 10ed | 8086 | type-VF |
pci__88_10_1 | available |
|
[Yahoo-eng-team] [Bug 1628301] Re: SR-IOV not working in Mitaka and Intel X series NIC
Adding Neutron since I believe the issue is the neutron-sriov-nic-agent
not building the port so that nova can allocate it for the instance.
** Also affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1628301
Title:
SR-IOV not working in Mitaka and Intel X series NIC
Status in neutron:
New
Status in OpenStack Compute (nova):
New
Bug description:
The SRIO functionality in Mitaka seems broken, all configuration
options we evaluated lead to
NovaException: Unexpected vif_type=binding_failed
errors, stack following.
We are currently using this code base, along with SRIOV configuration posted
here
Nova SHA 611efbe77c712d9ac35904f659d28dd0f0c1b3ff # HEAD of "stable/mitaka"
as of 08.09.2016
Neutron SHA c73269fa480a8a955f440570fc2fa6c347e3bb3c # HEAD of
"stable/mitaka" as of 08.09.2016
Stack :
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa] Traceback (most recent call last):
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa] File
"/openstack/venvs/nova-13.3.4/lib/python2.7/site-packages/nova/compute/manager.py",
line 2218, in _build_resources
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa] yield resources
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa] File
"/openstack/venvs/nova-13.3.4/lib/python2.7/site-packages/nova/compute/manager.py",
line 2064, in _build_and_run_instance
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa] block_device_info=block_device_info)
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa] File
"/openstack/venvs/nova-13.3.4/lib/python2.7/site-packages/nova/virt/libvirt/driver.py",
line 2776, in spawn
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa] write_to_disk=True)
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa] File
"/openstack/venvs/nova-13.3.4/lib/python2.7/site-packages/nova/virt/libvirt/driver.py",
line 4729, in _get_guest_xml
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa] context)
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa] File
"/openstack/venvs/nova-13.3.4/lib/python2.7/site-packages/nova/virt/libvirt/driver.py",
line 4595, in _get_guest_config
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa] flavor, virt_type, self._host)
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa] File
"/openstack/venvs/nova-13.3.4/lib/python2.7/site-packages/nova/virt/libvirt/vif.py",
line 447, in get_config
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa] _("Unexpected vif_type=%s") %
vif_type)
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa] NovaException: Unexpected
vif_type=binding_failed
2016-09-27 16:09:09.156 10248 ERROR nova.compute.manager [instance:
00c620f0-1b5d-43c2-89f6-d5a5c4ce98fa]
Interestingly the nova resource tracker seem to be able to create a
list of all available sriov devices and they show up correctly inside
the database as pci_device table entries
2016-09-27 16:13:52.175 10248 INFO nova.compute.resource_tracker
[req-284a7832-3794-4597-b939-273ea75d45f7 - - - - -] Total usable vcpus: 32,
total allocated vcpus: 0
2016-09-27 16:13:52.175 10248 INFO nova.compute.resource_tracker
[req-284a7832-3794-4597-b939-273ea75d45f7 - - - - -] Final resource view:
name=compute01 phys_ram=25
MB used_ram=2048MB phys_disk=1935GB used_disk=2GB total_vcpus=32 used_vcpus=0
pci_stats=[PciDevicePool(count=15,numa_node=None,product_id='10ed',tags={dev_type='type-VF',physical_network='physnet1'},vendor
_id='8086'),
PciDevicePool(count=2,numa_node=None,product_id='10fb',tags={dev_type='type-PF',physical_network='physnet1'},vendor_id='8086')]
Available ports inside DB:
+-+--++---+--+--+---+
| compute_node_id | address | product_id | vendor_id | dev_type | dev_id
| status|
+-+--++---+--+--+---+
| 5 | :88:10.1 | 10ed | 8086 | type-VF |
pci__88_10_1 | available |
| 5 |
