sriov binding:vif_type binding_failed [closed]

asked 2015-06-01 17:24:28 -0500

DaveJ gravatar image

Hi,

I'm having issues getting SR-IOV running. I have a fresh mutli-node install using packstack and Kilo running on RedHat 7.

My hardware is the Intel 82599 10G cards. Following instructions here: https://wiki.openstack.org/wiki/SR-IO...

I configured SR-IOV.

I create the port neutron port-create 9e504846-4a4c-48b3-bcf4-783b3f0f448a --binding:vnic-type direct

And then boot a VM nova boot --flavor m1.large --image 'RedHat 7' --nic port-id=b3fd96a7-937e-4b5c-a39d-4f54d5590e2b TestVM

On some occasions the VM boots, but doesn't appear to have a NIC. On others the VM doesn't boot, and when I do a port show I can see that it failed to bind.

+-----------------------+----------------------------------------------------------------------------------------------+
| Field                 | Value                                                                                        |
+-----------------------+----------------------------------------------------------------------------------------------+
| admin_state_up        | True                                                                                         |
| allowed_address_pairs |                                                                                              |
| binding:host_id       | compute-01.mydomain.com                                                              |
| binding:profile       | {"pci_slot": "0000:07:10.7", "physical_network": "physnet1", "pci_vendor_info": "8086:10ed"} |
| binding:vif_details   | {}                                                                                           |
| binding:vif_type      | binding_failed                                                                               |
| binding:vnic_type     | direct                                                                                       |
| device_id             | 6e60d7f0-ef6a-4676-a249-3b4110f8e09e                                                         |
| device_owner          | compute:None                                                                                 |
| extra_dhcp_opts       |                                                                                              |
| fixed_ips             | {"subnet_id": "6470b175-2659-48b0-9db5-200fdda926a9", "ip_address": "192.168.200.33"}        |
| id                    | b3fd96a7-937e-4b5c-a39d-4f54d5590e2b                                                         |
| mac_address           | fa:16:3e:f3:35:25                                                                            |
| name                  |                                                                                              |
| network_id            | 9e504846-4a4c-48b3-bcf4-783b3f0f448a                                                         |
| security_groups       | 31b0e195-b96e-41f2-9ec6-795019fbcca1                                                         |
| status                | DOWN                                                                                         |
| tenant_id             | 129752a47ddd46e1a76c3ebe473a5ee0                                                             |

+-----------------------+----------------------------------------------------------------------------------------------+

The binding profile looks correct, in that the when I do lspci on the host I see the following

| binding:profile       | {"pci_slot": "0000:07:10.7", "physical_network": "physnet1", "pci_vendor_info": "8086:10ed"} |

lspci -nn | grep 82599
07:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)
07:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)
07:10.0 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
07:10.1 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
07:10.2 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
07:10.3 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
07:10.4 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
07:10.5 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
07:10.6 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
07:10.7 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
07:11.0 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
07:11.1 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
07:11.2 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
07:11.3 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
07:11.4 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
07:11.5 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
07:11.6 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
07:11.7 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)

Can anyone advise me how to debug this further

edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by DaveJ
close date 2015-06-04 07:20:40.759008

Comments

I never got to the bottom of this. I performed a fresh install and went through the install steps again, this time the vif binding works - although it is binding to the wrong interfaces!

DaveJ gravatar imageDaveJ ( 2015-06-04 07:20:30 -0500 )edit