[Openstack] Openstack Pike SRIOV Enablement issue
Dear All,
I am facing some issues while trying to enable SRIOV interfaces with OpenStack
Pike.
I am using Solarflare NICs. In my case I have done all the required
configurations as stated in :
But on starting the sriov-nic-agent, I am getting following error:
neutron-sriov-nic-agent --config-file /etc/neutron/neutron.conf
--config-file /etc/neutron/plugins/ml2/sriov_agent.ini
Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward
compatibility. SIGUSR1 will no longer be registered in a future release, so
please use SIGUSR2 to generate reports.
2018-09-07 16:30:47.097 7503 INFO neutron.common.config [-] Logging enabled!
2018-09-07 16:30:47.097 7503 INFO neutron.common.config [-]
/usr/bin/neutron-sriov-nic-agent version 11.0.5
2018-09-07 16:30:47.097 7503 INFO
neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent [-] Physical
Devices mappings: {'sriovprovider': ['enp1s0f1']}
2018-09-07 16:30:47.097 7503 INFO
neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent [-] Exclude
Devices: {}
2018-09-07 16:30:47.098 7503 INFO
neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent
[req-a6d17b33-6256-46cb-9652-936d7d22c7a1 - - - - -] RPC agent_id:
nic-switch-agent.box
2018-09-07 16:30:47.100 7503 INFO neutron.agent.agent_extensions_manager
[req-a6d17b33-6256-46cb-9652-936d7d22c7a1 - - - - -] Loaded agent extensions: []
2018-09-07 16:30:47.130 7503 INFO
neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent
[req-a6d17b33-6256-46cb-9652-936d7d22c7a1 - - - - -] Agent initialized
successfully, now running...
2018-09-07 16:30:47.130 7503 INFO
neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent
[req-a6d17b33-6256-46cb-9652-936d7d22c7a1 - - - - -] SRIOV NIC Agent RPC Daemon
Started!
2018-09-07 16:30:47.130 7503 INFO
neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent
[req-a6d17b33-6256-46cb-9652-936d7d22c7a1 - - - - -] Agent out of sync with
plugin!
2018-09-07 16:30:47.229 7503 WARNING
neutron.plugins.ml2.drivers.mech_sriov.agent.pci_lib
[req-a6d17b33-6256-46cb-9652-936d7d22c7a1 - - - - -] failed to parse vf link
show line vf 6 MAC 9e:87:7b:bf:75:d2, link-state auto: for enp1s0f1
2018-09-07 16:30:47.229 7503 WARNING
neutron.plugins.ml2.drivers.mech_sriov.agent.pci_lib
[req-a6d17b33-6256-46cb-9652-936d7d22c7a1 - - - - -] failed to parse vf link
show line vf 7 MAC 1e:46:04:79:cd:6b, link-state auto: for enp1s0f1
2018-09-07 16:30:49.239 7503 WARNING
neutron.plugins.ml2.drivers.mech_sriov.agent.pci_lib
[req-a6d17b33-6256-46cb-9652-936d7d22c7a1 - - - - -] failed to parse vf link
show line vf 6 MAC 9e:87:7b:bf:75:d2, link-state auto: for enp1s0f1
2018-09-07 16:30:49.239 7503 WARNING
neutron.plugins.ml2.drivers.mech_sriov.agent.pci_lib
[req-a6d17b33-6256-46cb-9652-936d7d22c7a1 - - - - -] failed to parse vf link
show line vf 7 MAC 1e:46:04:79:cd:6b, link-state auto: for enp1s0f1
Please help on resolving this issue. Any pointers would be welcome.
Kind Regards,
Navdeep
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] SRIOV Enablement in openstack error
Hi Moshe,
Thank you very much for figuring it out. It works now, Just had to restart the
sriov-agent.
Kind Regards,
Navdeep
From: Moshe Levi
Sent: 02 May 2018 18:26
To: Navdeep Uniyal ; OpenStack Mailing List
Subject: RE: SRIOV Enablement in openstack error
Hi Navdeep,
The yellow lines that you outline are related to the ovs mechanism driver
which indicate that it can't bind direct port which as expected.
(/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/mech_agent.py is
port of the ovs mechanism driver)
The error with the sriov mechanism driver seem to be in
Checking agent: {'binary': u'neutron-sriov-nic-agent', 'description': None,
'admin_state_up': True, 'heartbeat_timestamp': datetime.datetime(2018, 5, 2,
16, 8, 9), 'availability_zone': Non
e, 'alive': True, 'topic': u'N/A', 'host': u'controller', 'agent_type': u'NIC
Switch agent', 'resource_versions': {u'Subnet': u'1.0', u'Network': u'1.0',
u'SubPort': u'1.0', u'SecurityGroup': u'1.0', u'Secur
ityGroupRule': u'1.0', u'Trunk': u'1.1', u'QosPolicy': u'1.6', u'Port': u'1.1',
u'Log': u'1.0'}, 'created_at': datetime.datetime(2018, 4, 10, 7, 40, 42),
'started_at': datetime.datetime(2018, 4, 10, 8, 36, 4
), 'id': u'f2f40c44-cc99-4371-93b9-4c21731122a4', 'configurations':
{u'extensions': [], u'devices': 0, u'device_mappings': {u'internetprovider':
[u'enp130s0f0']}}}
It seem the network has physical_network= 'sriovprovider' but in the sriov
agnet has outlined in yellow the physnet is 'internetprovider'.
If you change the in the sriov agent config to device_mappings= sriovprovider:
enp130s0f0 and restart the agnet is should work.
From: Navdeep Uniyal [mailto:navdeep.uni...@bristol.ac.uk]
Sent: Wednesday, May 2, 2018 7:33 PM
To: OpenStack Mailing List
mailto:openstack@lists.openstack.org>>
Subject: [Openstack] SRIOV Enablement in openstack error
Dear all,
I am trying to enable the SRIOV interfaces in my openstack Pike installation. I
am following the guide:
https://docs.openstack.org/neutron/pike/admin/config-sriov.html<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.openstack.org%2Fneutron%2Fpike%2Fadmin%2Fconfig-sriov.html&data=02%7C01%7Cmoshele%40mellanox.com%7Cb3186f9f8ed14eb4ca3208d5b04c4a2f%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636608764063059825&sdata=pJrQ2n89oy6Pb1p2t1IsbCxtBzG8YFt1XhdpWJnHXik%3D&reserved=0>
I am getting following error in neutron while doing so:
2018-05-02 17:08:19.492 75833 ERROR neutron.plugins.ml2.managers
[req-4e2f89f4-4d26-4e78-9b05-e997f398f2a1 2b4070ba7a5044cca6f42f594c37011c
65ac10ca3d2f407eab488c208348ace5 - default default] Failed to bind
port ef64559f-c047-47d6-b9eb-09c5a60d7549 on host controller for vnic_type
direct using segments [{'network_id': 'ba89924e-3134-4966-af56-b582d70f5f41',
'segmentation_id': 200, 'physical_network': u'sriovpro
vider', 'id': '19120c0a-0ec7-4b6b-ad07-f68effdb5bf3', 'network_type': u'vlan'}]
2018-05-02 17:08:19.492 75833 INFO neutron.plugins.ml2.plugin
[req-4e2f89f4-4d26-4e78-9b05-e997f398f2a1 2b4070ba7a5044cca6f42f594c37011c
65ac10ca3d2f407eab488c208348ace5 - default default] Attempt 10 to bind
port ef64559f-c047-47d6-b9eb-09c5a60d7549
2018-05-02 17:08:19.500 75833 DEBUG neutron.plugins.ml2.managers
[req-4e2f89f4-4d26-4e78-9b05-e997f398f2a1 2b4070ba7a5044cca6f42f594c37011c
65ac10ca3d2f407eab488c208348ace5 - default default] Attempting to b
ind port ef64559f-c047-47d6-b9eb-09c5a60d7549 on host controller for vnic_type
direct with profile {"pci_slot": ":82:08.5", "physical_network":
"sriovprovider", "pci_vendor_info": "1924:1a03"} bind_port
/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/managers.py:744
2018-05-02 17:08:19.500 75833 DEBUG neutron.plugins.ml2.managers
[req-4e2f89f4-4d26-4e78-9b05-e997f398f2a1 2b4070ba7a5044cca6f42f594c37011c
65ac10ca3d2f407eab488c208348ace5 - default default] Attempting to b
ind port ef64559f-c047-47d6-b9eb-09c5a60d7549 on host controller at level 0
using segments [{'network_id': 'ba89924e-3134-4966-af56-b582d70f5f41',
'segmentation_id': 200, 'physical_network': u'sriovprovider'
, 'id': '19120c0a-0ec7-4b6b-ad07-f68effdb5bf3', 'network_type': u'vlan'}]
_bind_port_level
/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/managers.py:765
2018-05-02 17:08:19.501 7
[Openstack] SRIOV Enablement in openstack error
Dear all,
I am trying to enable the SRIOV interfaces in my openstack Pike installation. I
am following the guide:
https://docs.openstack.org/neutron/pike/admin/config-sriov.html
I am getting following error in neutron while doing so:
2018-05-02 17:08:19.492 75833 ERROR neutron.plugins.ml2.managers
[req-4e2f89f4-4d26-4e78-9b05-e997f398f2a1 2b4070ba7a5044cca6f42f594c37011c
65ac10ca3d2f407eab488c208348ace5 - default default] Failed to bind
port ef64559f-c047-47d6-b9eb-09c5a60d7549 on host controller for vnic_type
direct using segments [{'network_id': 'ba89924e-3134-4966-af56-b582d70f5f41',
'segmentation_id': 200, 'physical_network': u'sriovpro
vider', 'id': '19120c0a-0ec7-4b6b-ad07-f68effdb5bf3', 'network_type': u'vlan'}]
2018-05-02 17:08:19.492 75833 INFO neutron.plugins.ml2.plugin
[req-4e2f89f4-4d26-4e78-9b05-e997f398f2a1 2b4070ba7a5044cca6f42f594c37011c
65ac10ca3d2f407eab488c208348ace5 - default default] Attempt 10 to bind
port ef64559f-c047-47d6-b9eb-09c5a60d7549
2018-05-02 17:08:19.500 75833 DEBUG neutron.plugins.ml2.managers
[req-4e2f89f4-4d26-4e78-9b05-e997f398f2a1 2b4070ba7a5044cca6f42f594c37011c
65ac10ca3d2f407eab488c208348ace5 - default default] Attempting to b
ind port ef64559f-c047-47d6-b9eb-09c5a60d7549 on host controller for vnic_type
direct with profile {"pci_slot": ":82:08.5", "physical_network":
"sriovprovider", "pci_vendor_info": "1924:1a03"} bind_port
/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/managers.py:744
2018-05-02 17:08:19.500 75833 DEBUG neutron.plugins.ml2.managers
[req-4e2f89f4-4d26-4e78-9b05-e997f398f2a1 2b4070ba7a5044cca6f42f594c37011c
65ac10ca3d2f407eab488c208348ace5 - default default] Attempting to b
ind port ef64559f-c047-47d6-b9eb-09c5a60d7549 on host controller at level 0
using segments [{'network_id': 'ba89924e-3134-4966-af56-b582d70f5f41',
'segmentation_id': 200, 'physical_network': u'sriovprovider'
, 'id': '19120c0a-0ec7-4b6b-ad07-f68effdb5bf3', 'network_type': u'vlan'}]
_bind_port_level
/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/managers.py:765
2018-05-02 17:08:19.501 75833 DEBUG neutron.plugins.ml2.drivers.mech_agent
[req-4e2f89f4-4d26-4e78-9b05-e997f398f2a1 2b4070ba7a5044cca6f42f594c37011c
65ac10ca3d2f407eab488c208348ace5 - default default] Attem
pting to bind port ef64559f-c047-47d6-b9eb-09c5a60d7549 on network
ba89924e-3134-4966-af56-b582d70f5f41 bind_port
/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/mech_agent.py:88
2018-05-02 17:08:19.501 75833 DEBUG neutron.plugins.ml2.drivers.mech_agent
[req-4e2f89f4-4d26-4e78-9b05-e997f398f2a1 2b4070ba7a5044cca6f42f594c37011c
65ac10ca3d2f407eab488c208348ace5 - default default] Refus
ing to bind due to unsupported vnic_type: direct bind_port
/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/mech_agent.py:93
2018-05-02 17:08:19.501 75833 DEBUG
neutron.plugins.ml2.drivers.mech_sriov.mech_driver.mech_driver
[req-4e2f89f4-4d26-4e78-9b05-e997f398f2a1 2b4070ba7a5044cca6f42f594c37011c
65ac10ca3d2f407eab488c208348ace5
- default default] Attempting to bind port ef64559f-c047-47d6-b9eb-09c5a60d7549
on network ba89924e-3134-4966-af56-b582d70f5f41 bind_port
/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/mech_sri
ov/mech_driver/mech_driver.py:78
2018-05-02 17:08:19.503 75833 DEBUG
neutron.plugins.ml2.drivers.mech_sriov.mech_driver.mech_driver
[req-4e2f89f4-4d26-4e78-9b05-e997f398f2a1 2b4070ba7a5044cca6f42f594c37011c
65ac10ca3d2f407eab488c208348ace5
- default default] Checking agent: {'binary': u'neutron-sriov-nic-agent',
'description': None, 'admin_state_up': True, 'heartbeat_timestamp':
datetime.datetime(2018, 5, 2, 16, 8, 9), 'availability_zone': Non
e, 'alive': True, 'topic': u'N/A', 'host': u'controller', 'agent_type': u'NIC
Switch agent', 'resource_versions': {u'Subnet': u'1.0', u'Network': u'1.0',
u'SubPort': u'1.0', u'SecurityGroup': u'1.0', u'Secur
ityGroupRule': u'1.0', u'Trunk': u'1.1', u'QosPolicy': u'1.6', u'Port': u'1.1',
u'Log': u'1.0'}, 'created_at': datetime.datetime(2018, 4, 10, 7, 40, 42),
'started_at': datetime.datetime(2018, 4, 10, 8, 36, 4
), 'id': u'f2f40c44-cc99-4371-93b9-4c21731122a4', 'configurations':
{u'extensions': [], u'devices': 0, u'device_mappings': {u'internetprovider':
[u'enp130s0f0']}}} bind_port /usr/lib/python2.7/dist-packages/
neutron/plugins/ml2/drivers/mech_sriov/mech_driver/mech_driver.py:110
2018-05-02 17:08:19.504 75833 DEBUG
neutron.plugins.ml2.drivers.mech_sriov.mech_driver.mech_driver
[req-4e2f89f4-4d26-4e78-9b05-e997f398f2a1 2b4070ba7a5044cca6f42f594c37011c
65ac10ca3d2f407eab488c208348ace5
- default default] Checking segment: {'network_id':
'ba89924e-3134-4966-af56-b582d70f5f41', 'segmentation_id': 200,
'physical_network': u'sriovprovider', 'id':
'19120c0a-0ec7-4b6b-ad07-f68effdb5bf3', 'networ
k_type': u'vlan'} for mappings: {u'internetprovider': [u'enp130s0f0']}
check_segment_for_agent
/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/mech_sriov/mech_driver/mech_driver.
Re: [Openstack] [Pike] [Nova] Error : ERROR : MissingRequiredOptions: Auth plugin requires parameters which were not given: auth_url
Hi Guru, It should be auth_url. Please see the highlighted error below. Regards, Navdeep From: Guru Desai Sent: 06 March 2018 16:41 To: OpenStack Mailing List Subject: [Openstack] [Pike] [Nova] Error : ERROR : MissingRequiredOptions: Auth plugin requires parameters which were not given: auth_url Hello, I am setting up pike version and facing an issue with nova on controller. I see below errors continouolsy in nova-api.log. But i have given the auth parameters in the /etc/nova/nova.conf. I am done installing keystone and glance, stuck here with nova. Modified the nova.conf as per the install guide. Please suggest as to what could be the issue.. [keystone_authtoken] auth_uri = http://test_controller:5000 auth_uri = http://test_controller:35357 memcached_servers = test_controller:11211 auth_type = password project_domain_name = default user_domain_name = default project_name = service username = nova password = NOVA_PASS Log ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Routing in connected VMs
Thanks James, I could figure out and resolved it by disabling port security. Regards, Navdeep From: James Denton Sent: Sunday, February 11, 2018 8:59:22 PM To: Navdeep Uniyal; OpenStack Mailing List Subject: Re: [Openstack] Routing in connected VMs Hi Navdeep, To get this to work, you will need to disable port security on the B device’s ports, or at a minimum, modify the allowed-address-pairs on the port to allow the traffic out towards C. Disabling port security is typically the way to go about satisfying this particular use case. James From: Navdeep Uniyal Date: Friday, February 9, 2018 at 12:40 PM To: OpenStack Mailing List Subject: [Openstack] Routing in connected VMs Dear all, I am trying to create a network chain manually of VMs in openstack by entering the routing table entries in the machines. However, it doesn’t seems to work. The network between the VMs is VLAN network on top of provider network. Scenario is like : A-->B-->C I have enabled the IP forwarding on the node B but I am not able to ping from A to C. ICMP echo requests are not reaching C. I am able to ping from B to A and B to C. Please if someone could help in this regard. Best Regards, Navdeep ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[Openstack] Routing in connected VMs
Dear all, I am trying to create a network chain manually of VMs in openstack by entering the routing table entries in the machines. However, it doesn't seems to work. The network between the VMs is VLAN network on top of provider network. Scenario is like : A-->B-->C I have enabled the IP forwarding on the node B but I am not able to ping from A to C. ICMP echo requests are not reaching C. I am able to ping from B to A and B to C. Please if someone could help in this regard. Best Regards, Navdeep ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Openstack manual setup
Hi Guru, Check this link: https://docs.openstack.org/pike/install/ Regards, Navdeep From: Guru Desai [mailto:guru...@gmail.com] Sent: 30 January 2018 14:58 To: OpenStack Mailing List Subject: [Openstack] Openstack manual setup Hello, I plan to setup openstack manually on single server ( preferably PIKE). Somehow i am not able to find any documentation for the same. Could some one help with any pointers. All the documentation that i find refers to either packstack or devstack which i dont want to use. I would like to setup all the openstack services on single server, either ubuntu or centOS. Any pointers would be very helpful.. Thanks, Guru ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Openstack SRIOV and PCI passthrough error while creating instance
Hi Moshe, Thank you. Dear All, Has anyone worked with intel NICs to enable SRIOV in Openstack. If yes, please if you could help me in configuring the NIC to be made suitable for Openstack to pick up. Currently, I am facing issues with Libvirt failing to list the node. With driver i40evf running, it lists the interfaces. However, if I disable the i40evf driver it does not list the interfaces in nodedev-list. Please if someone could verify this as right behaviour or not. Kind Regards, Navdeep From: Moshe Levi [mailto:mosh...@mellanox.com] Sent: 29 January 2018 12:00 To: Navdeep Uniyal ; openstack@lists.openstack.org Subject: RE: [Openstack] Openstack SRIOV and PCI passthrough error while creating instance Hi Nadepp, I am not familiar with Intel NIC (I work at Mellanox) Maybe the intel folks in the mailing list can help you. From: Navdeep Uniyal [mailto:navdeep.uni...@bristol.ac.uk] Sent: Monday, January 29, 2018 1:58 PM To: Moshe Levi mailto:mosh...@mellanox.com>>; openstack@lists.openstack.org<mailto:openstack@lists.openstack.org> Subject: RE: [Openstack] Openstack SRIOV and PCI passthrough error while creating instance Hi Moshe, Thank you for your response. I am creating VFs on intel X710 NIC. As per the documentation I need to disable 'i40evf driver' on the host machine to get the VMs running with the VFs however, on doing so I am not getting the VF list while doing 'virsh nodedev-list'. Could you please advise if this driver is required to be running or not. Best Regards, Navdeep From: Moshe Levi [mailto:mosh...@mellanox.com] Sent: 29 January 2018 09:30 To: Navdeep Uniyal mailto:navdeep.uni...@bristol.ac.uk>>; openstack@lists.openstack.org<mailto:openstack@lists.openstack.org> Subject: RE: [Openstack] Openstack SRIOV and PCI passthrough error while creating instance Can you try to restart libvirtd and query again "virsh nodedev-list" From: Navdeep Uniyal [mailto:navdeep.uni...@bristol.ac.uk] Sent: Monday, January 29, 2018 10:32 AM To: Moshe Levi mailto:mosh...@mellanox.com>>; openstack@lists.openstack.org<mailto:openstack@lists.openstack.org> Subject: RE: [Openstack] Openstack SRIOV and PCI passthrough error while creating instance Hi Moshe, Thank you very much for your response. I could see the list of nodes using virsh: net_enp129s0f0_3c_fd_fe_a9_37_c0 net_enp129s0f1_3c_fd_fe_a9_37_c1 net_enp129s2_36_a5_18_f7_41_c6 net_enp129s2f1_96_b0_b3_37_cf_c5 net_enp129s2f2_0e_0c_63_76_07_0f net_enp129s2f3_36_ca_41_10_7f_62 net_enp129s2f4_f2_79_ee_75_38_a9 net_enp129s2f5_2a_a1_c6_02_55_11 net_enp129s2f6_16_e3_c4_01_8c_6d net_enp129s2f7_66_56_63_d8_a8_ad these does not have the node 'net_enp129s2_b2_87_6e_13_a1_5e' listed. Could you please help me finding out what could be the reason behind this mismatch. Kind Regards, Navdeep Uniyal From: Moshe Levi [mailto:mosh...@mellanox.com] Sent: 29 January 2018 06:50 To: Navdeep Uniyal mailto:navdeep.uni...@bristol.ac.uk>>; openstack@lists.openstack.org<mailto:openstack@lists.openstack.org> Subject: RE: [Openstack] Openstack SRIOV and PCI passthrough error while creating instance Hi Navdeep, The errors you are pointing out shouldn't cause error while creating instance with SR-IOV/PCI passthrough. They are part of the SR-IOV nic capabilities feature which is not completed yet. Libvirt "virsh nodedev-list" command will show you the list of nic and this method [1] will look it in the hypervisor. For some reason you have a mismatch here. You need to compare them. Anyway if there is a mismatch it just won't report the capabilities of the nic. As I mentioned above I think this is not the issue for the error while creating instance [1] https://github.com/openstack/nova/blob/91f7a88b3f857d738d39984117e6c514cbec/nova/pci/utils.py#L196-L217<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fopenstack%2Fnova%2Fblob%2F91f7a88b3f857d738d39984117e6c514cbec%2Fnova%2Fpci%2Futils.py%23L196-L217&data=02%7C01%7Cmoshele%40mellanox.com%7C64da232237d54639b39208d566f2cc83%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636528115363097991&sdata=9warkJI5zs0l57YKgpBrXTUA5IO7lN1xWAAKxDo%2FSy0%3D&reserved=0> From: Navdeep Uniyal [mailto:navdeep.uni...@bristol.ac.uk] Sent: Sunday, January 28, 2018 10:58 PM To: openstack@lists.openstack.org<mailto:openstack@lists.openstack.org> Subject: [Openstack] Openstack SRIOV and PCI passthrough error while creating instance Dear All, I am getting an error while creating SRIOV enabled instances following the guide from Openstack pike https://docs.openstack.org/neutron/pike/admin/config-sriov.html<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.openstack.org%2Fneutron%2Fpike%2Fadmin%2Fconfig-sriov.html&data=02%7C01%7Cmoshele%40mellanox.com%7C7035d805a74d45ff0bbe08d56692fd3e%7Ca652971c7d2e4d9ba6a4d149256
Re: [Openstack] Openstack SRIOV and PCI passthrough error while creating instance
Hi Moshe, Thank you for your response. I am creating VFs on intel X710 NIC. As per the documentation I need to disable 'i40evf driver' on the host machine to get the VMs running with the VFs however, on doing so I am not getting the VF list while doing 'virsh nodedev-list'. Could you please advise if this driver is required to be running or not. Best Regards, Navdeep From: Moshe Levi [mailto:mosh...@mellanox.com] Sent: 29 January 2018 09:30 To: Navdeep Uniyal ; openstack@lists.openstack.org Subject: RE: [Openstack] Openstack SRIOV and PCI passthrough error while creating instance Can you try to restart libvirtd and query again "virsh nodedev-list" From: Navdeep Uniyal [mailto:navdeep.uni...@bristol.ac.uk] Sent: Monday, January 29, 2018 10:32 AM To: Moshe Levi mailto:mosh...@mellanox.com>>; openstack@lists.openstack.org<mailto:openstack@lists.openstack.org> Subject: RE: [Openstack] Openstack SRIOV and PCI passthrough error while creating instance Hi Moshe, Thank you very much for your response. I could see the list of nodes using virsh: net_enp129s0f0_3c_fd_fe_a9_37_c0 net_enp129s0f1_3c_fd_fe_a9_37_c1 net_enp129s2_36_a5_18_f7_41_c6 net_enp129s2f1_96_b0_b3_37_cf_c5 net_enp129s2f2_0e_0c_63_76_07_0f net_enp129s2f3_36_ca_41_10_7f_62 net_enp129s2f4_f2_79_ee_75_38_a9 net_enp129s2f5_2a_a1_c6_02_55_11 net_enp129s2f6_16_e3_c4_01_8c_6d net_enp129s2f7_66_56_63_d8_a8_ad these does not have the node 'net_enp129s2_b2_87_6e_13_a1_5e' listed. Could you please help me finding out what could be the reason behind this mismatch. Kind Regards, Navdeep Uniyal From: Moshe Levi [mailto:mosh...@mellanox.com] Sent: 29 January 2018 06:50 To: Navdeep Uniyal mailto:navdeep.uni...@bristol.ac.uk>>; openstack@lists.openstack.org<mailto:openstack@lists.openstack.org> Subject: RE: [Openstack] Openstack SRIOV and PCI passthrough error while creating instance Hi Navdeep, The errors you are pointing out shouldn't cause error while creating instance with SR-IOV/PCI passthrough. They are part of the SR-IOV nic capabilities feature which is not completed yet. Libvirt "virsh nodedev-list" command will show you the list of nic and this method [1] will look it in the hypervisor. For some reason you have a mismatch here. You need to compare them. Anyway if there is a mismatch it just won't report the capabilities of the nic. As I mentioned above I think this is not the issue for the error while creating instance [1] https://github.com/openstack/nova/blob/91f7a88b3f857d738d39984117e6c514cbec/nova/pci/utils.py#L196-L217<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fopenstack%2Fnova%2Fblob%2F91f7a88b3f857d738d39984117e6c514cbec%2Fnova%2Fpci%2Futils.py%23L196-L217&data=02%7C01%7Cmoshele%40mellanox.com%7C64da232237d54639b39208d566f2cc83%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636528115363097991&sdata=9warkJI5zs0l57YKgpBrXTUA5IO7lN1xWAAKxDo%2FSy0%3D&reserved=0> From: Navdeep Uniyal [mailto:navdeep.uni...@bristol.ac.uk] Sent: Sunday, January 28, 2018 10:58 PM To: openstack@lists.openstack.org<mailto:openstack@lists.openstack.org> Subject: [Openstack] Openstack SRIOV and PCI passthrough error while creating instance Dear All, I am getting an error while creating SRIOV enabled instances following the guide from Openstack pike https://docs.openstack.org/neutron/pike/admin/config-sriov.html<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.openstack.org%2Fneutron%2Fpike%2Fadmin%2Fconfig-sriov.html&data=02%7C01%7Cmoshele%40mellanox.com%7C7035d805a74d45ff0bbe08d56692fd3e%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636527703870300090&sdata=Oljh3%2Ff1B%2FLCsNxHIUkS%2FgLzTBkpOY3XaWBixYKWOaQ%3D&reserved=0> I want to start an instance on openstack pike with SRIOV enabled NICs. However, I am getting a Libvirt error regarding the node name. The error looks weird as the node name is not matching the interface name on the host machine or in the configuration files. 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager [req-caa92f1d-5ac1-402d-a8bc-b08ab350a21f - - - - -] Error updating resources for node jupiter.: libvirtError: Node device not found: no node device with matching name 'net_enp129s2_b2_87_6e_13_a1_5e' 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager Traceback (most recent call last): 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 6696, in update_available_resource_for_node 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager rt.update_available_resource(context, nodename) 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py", line 641, in update_available_resource 2018-01-28 20:40:11.416 2953 ERROR nova.comp
Re: [Openstack] Openstack SRIOV and PCI passthrough error while creating instance
Hi Moshe, Thank you very much for your response. I could see the list of nodes using virsh: net_enp129s0f0_3c_fd_fe_a9_37_c0 net_enp129s0f1_3c_fd_fe_a9_37_c1 net_enp129s2_36_a5_18_f7_41_c6 net_enp129s2f1_96_b0_b3_37_cf_c5 net_enp129s2f2_0e_0c_63_76_07_0f net_enp129s2f3_36_ca_41_10_7f_62 net_enp129s2f4_f2_79_ee_75_38_a9 net_enp129s2f5_2a_a1_c6_02_55_11 net_enp129s2f6_16_e3_c4_01_8c_6d net_enp129s2f7_66_56_63_d8_a8_ad these does not have the node 'net_enp129s2_b2_87_6e_13_a1_5e' listed. Could you please help me finding out what could be the reason behind this mismatch. Kind Regards, Navdeep Uniyal From: Moshe Levi [mailto:mosh...@mellanox.com] Sent: 29 January 2018 06:50 To: Navdeep Uniyal ; openstack@lists.openstack.org Subject: RE: [Openstack] Openstack SRIOV and PCI passthrough error while creating instance Hi Navdeep, The errors you are pointing out shouldn't cause error while creating instance with SR-IOV/PCI passthrough. They are part of the SR-IOV nic capabilities feature which is not completed yet. Libvirt "virsh nodedev-list" command will show you the list of nic and this method [1] will look it in the hypervisor. For some reason you have a mismatch here. You need to compare them. Anyway if there is a mismatch it just won't report the capabilities of the nic. As I mentioned above I think this is not the issue for the error while creating instance [1] https://github.com/openstack/nova/blob/91f7a88b3f857d738d39984117e6c514cbec/nova/pci/utils.py#L196-L217 From: Navdeep Uniyal [mailto:navdeep.uni...@bristol.ac.uk] Sent: Sunday, January 28, 2018 10:58 PM To: openstack@lists.openstack.org<mailto:openstack@lists.openstack.org> Subject: [Openstack] Openstack SRIOV and PCI passthrough error while creating instance Dear All, I am getting an error while creating SRIOV enabled instances following the guide from Openstack pike https://docs.openstack.org/neutron/pike/admin/config-sriov.html<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.openstack.org%2Fneutron%2Fpike%2Fadmin%2Fconfig-sriov.html&data=02%7C01%7Cmoshele%40mellanox.com%7C7035d805a74d45ff0bbe08d56692fd3e%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636527703870300090&sdata=Oljh3%2Ff1B%2FLCsNxHIUkS%2FgLzTBkpOY3XaWBixYKWOaQ%3D&reserved=0> I want to start an instance on openstack pike with SRIOV enabled NICs. However, I am getting a Libvirt error regarding the node name. The error looks weird as the node name is not matching the interface name on the host machine or in the configuration files. 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager [req-caa92f1d-5ac1-402d-a8bc-b08ab350a21f - - - - -] Error updating resources for node jupiter.: libvirtError: Node device not found: no node device with matching name 'net_enp129s2_b2_87_6e_13_a1_5e' 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager Traceback (most recent call last): 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 6696, in update_available_resource_for_node 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager rt.update_available_resource(context, nodename) 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py", line 641, in update_available_resource 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager resources = self.driver.get_available_resource(nodename) 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5857, in get_available_resource 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5621, in _get_pci_passthrough_devices 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager for name in dev_names: 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5582, in _get_pcidev_info 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager device['label'] = 'label_%(vendor_id)s_%(product_id)s' % device 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5553, in _get_device_capabilities 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager pcinet_info = self._get_pcinet_info(address) 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5496, in _get_pcinet_info 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager virtdev = self._host.device_lookup_by_name(devname) 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager File "/
[Openstack] Openstack SRIOV and PCI passthrough error while creating instance
Dear All,
I am getting an error while creating SRIOV enabled instances following the
guide from Openstack pike
https://docs.openstack.org/neutron/pike/admin/config-sriov.html
I want to start an instance on openstack pike with SRIOV enabled NICs. However,
I am getting a Libvirt error regarding the node name. The error looks weird as
the node name is not matching the interface name on the host machine or in the
configuration files.
2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager
[req-caa92f1d-5ac1-402d-a8bc-b08ab350a21f - - - - -] Error updating resources
for node jupiter.: libvirtError: Node device not found: no node device with
matching name 'net_enp129s2_b2_87_6e_13_a1_5e' 2018-01-28 20:40:11.416 2953
ERROR nova.compute.manager Traceback (most recent call last): 2018-01-28
20:40:11.416 2953 ERROR nova.compute.manager File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 6696, in
update_available_resource_for_node 2018-01-28 20:40:11.416 2953 ERROR
nova.compute.manager rt.update_available_resource(context, nodename) 2018-01-28
20:40:11.416 2953 ERROR nova.compute.manager File
"/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py", line 641,
in update_available_resource 2018-01-28 20:40:11.416 2953 ERROR
nova.compute.manager resources = self.driver.get_available_resource(nodename)
2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5857, in
get_available_resource 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager
2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5621, in
_get_pci_passthrough_devices 2018-01-28 20:40:11.416 2953 ERROR
nova.compute.manager for name in dev_names: 2018-01-28 20:40:11.416 2953 ERROR
nova.compute.manager File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5582, in
_get_pcidev_info 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager
device['label'] = 'label_%(vendor_id)s_%(product_id)s' % device 2018-01-28
20:40:11.416 2953 ERROR nova.compute.manager File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5553, in
_get_device_capabilities 2018-01-28 20:40:11.416 2953 ERROR
nova.compute.manager pcinet_info = self._get_pcinet_info(address) 2018-01-28
20:40:11.416 2953 ERROR nova.compute.manager File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5496, in
_get_pcinet_info 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager
virtdev = self._host.device_lookup_by_name(devname) 2018-01-28 20:40:11.416
2953 ERROR nova.compute.manager File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/host.py", line 845, in
device_lookup_by_name 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager
return self.get_connection().nodeDeviceLookupByName(name) 2018-01-28
20:40:11.416 2953 ERROR nova.compute.manager File
"/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 186, in doit
2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager result =
proxy_call(self._autowrap, f, *args, **kwargs) 2018-01-28 20:40:11.416 2953
ERROR nova.compute.manager File
"/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 144, in proxy_call
2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager rv = execute(f, *args,
**kwargs) 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager File
"/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 125, in execute
2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager six.reraise(c, e, tb)
2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager File
"/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 83, in tworker
2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager rv = meth(*args,
**kwargs) 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager File
"/usr/lib/python2.7/dist-packages/libvirt.py", line 4177, in
nodeDeviceLookupByName 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager
if ret is None:raise libvirtError('virNodeDeviceLookupByName() failed',
conn=self) 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager
libvirtError: Node device not found: no node device with matching name
'net_enp129s2_b2_87_6e_13_a1_5e' 2018-01-28 20:40:11.416 2953 ERROR
nova.compute.manager
The correct interface name is enp129s0f0. However, I am getting the node name
as net_enp129s2_b2_87_6e_13_a1_5e' which i believe is the reason behind the
failure of vm creation on openstack. Please if someone could help me understand
how the node name is passed on to the Libvirt from openstack or how can I
resolve this issue.
Regards,
Navdeep
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
