Vxlan is not supported in SR-IOV and flat network should work from Kilo see commit[1]
Like I said you need to check your physical_device_mappings is correct can you post your Did you put your agent config in /etc/neutron/conf.d/neutron-sriov-nic-agent? So on the compute node you should do the following: Create - /etc/neutron/conf.d/neutron-sriov-nic-agent/ml2_sriov.conf And put the content [securitygroup] firewall_driver = neutron.agent.firewall.NoopFirewallDriver [sriov_nic] physical_device_mappings = physnet1:eth1 This will make only the agent to use firewall_driver = neutron.agent.firewall.NoopFirewallDriver Also make sure physical_device_mappings is configure correctly Please Note that the physnet1 in physical_device_mappings should be also appears in the nova.conf pci_passthrough_whitelist = {"address":"*:0a:00.*","physical_network":"physnet1"} [1] - https://review.openstack.org/#/c/142699/ From: 于洁 [mailto:16189...@qq.com] Sent: Saturday, August 22, 2015 5:47 AM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: [openstack-dev] 回复: [Neutron][SR-IOV]How to assign VF to a VM? Thanks Moshe, Referring to https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking, it has the note: Note:SR-IOV agent only work with NoopFirewallDriver when Security Groups are enabled, but you can still use other firewall_driver for other Agents by updating their conf with the requested firewall driver. So I think linux.iptables_firewall.OVSHybridIptabl maybe not the issue. [root@compute ~]# ps -ef|grep neutron-sriov root 28672 26639 0 22:45 pts/0 00:00:00 grep --color=auto neutron-sriov neutron 30891 1 0 05:21 ? 00:01:41 /usr/bin/python2 /usr/bin/neutron-sriov-nic-agent --config-file /usr/share/neutron/neutron-dist.conf --config-file /etc/neutron/neutron.conf --config-dir /etc/neutron/conf.d/neutron-sriov-nic-agent --config-file /etc/neutron/plugins/ml2/ml2_conf_sriov.ini --log-file /var/log/neutron/sriov-nic-agent.log I will have a try of vlan and vxlan. Thank you, Yu ------------------ 原始邮件 ------------------ 发件人: "Moshe Levi";<mosh...@mellanox.com<mailto:mosh...@mellanox.com>>; 发送时间: 2015年8月21日(星期五) 下午5:15 收件人: "OpenStack Development Mailing List (not for usage questions)"<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>; "openstack-operators"<openstack-operat...@lists.openstack.org<mailto:openstack-operat...@lists.openstack.org>>; 主题: Re: [openstack-dev] [Neutron][SR-IOV]How to assign VF to a VM? The problem is the sriov mechanism drive failed to bind the port. For the log I see that you are working with agent_required=True, but the device mapping is empty {u'devices': 0, u'device_mappings': {} Please check the agent configuration file see that you have the following [securitygroup] firewall_driver = neutron.agent.firewall.NoopFirewallDriver [sriov_nic] physical_device_mappings = physnet1:eth1 exclude_devices = also can you send the output of “ps �Cef | grep neutron-sriov-nic-agent” command? From: 于洁 [mailto:16189...@qq.com] Sent: Friday, August 21, 2015 12:01 PM To: openstack-operators <openstack-operat...@lists.openstack.org<mailto:openstack-operat...@lists.openstack.org>>; openstack-dev <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: [openstack-dev] [Neutron][SR-IOV]How to assign VF to a VM? Hi all, I try to configure SRIOV on OpenStack Kilo referring the information below. http://www.qlogic.com/solutions/Documents/UsersGuide_OpenStack_SR-IOV.pdf https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking Until creating port it works well. But after creating VM using the port created before, it was in the state of ERROR. Below is the port information: neutron port-show 620187c5-b4ac-4aca-bdeb-96205503344d +-----------------------+----------------------------------------------------------------------------------------------+ | Field | Value | +-----------------------+----------------------------------------------------------------------------------------------+ | admin_state_up | True | | allowed_address_pairs | | | binding:host_id | compute | | binding:profile | {"pci_slot": "0000:09:11.5", "physical_network": "external", "pci_vendor_info": "8086:1520"} | | binding:vif_details | {} | | binding:vif_type | binding_failed | | binding:vnic_type | direct | | device_id | baab9ba5-80e8-45f7-b86a-8ac3ce8ba944 | | device_owner | compute:None | | extra_dhcp_opts | | | fixed_ips | {"subnet_id": "86849224-a0a7-4059-a6b0-689a2b35c995", "ip_address": "10.254.4.64"} | | id | 620187c5-b4ac-4aca-bdeb-96205503344d | | mac_address | fa:16:3e:8a:92:9b | | name | | | network_id | db078c2d-63f1-40c0-b6c3-b49de487362b | | security_groups | 8e12a661-09b5-41ac-ade8-fddf6d997262 | | status | DOWN | | tenant_id | 85aa4ef08044470dab1608395e5cac26 | +-----------------------+----------------------------------------------------------------------------------------------+ The logs of /var/log/neutron/server.log and /var/log/nova/nova-conductor.log are in attachment. Any suggestions will be grateful. Thanks. Yu
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev