Created attachment 1191078[details]
pf sriov
Description of problem:
PFs aren't showing up as available making it not possible to boot vms with PFs
When I am trying to boot VM with Neutron port with vnic type - direct - physical there is an error.
attached the error.
The ENV is SRIOV 1 compute & 1 controller
Version-Release number of selected component (if applicable):
python-nova-14.0.0-0.20160726054215.02421fc.el7ost.noarch
python-novaclient-5.0.1-0.20160724130722.6b11a1c.el7ost.noarch
openstack-nova-compute-14.0.0-0.20160726054215.02421fc.el7ost.noarch
openstack-nova-common-14.0.0-0.20160726054215.02421fc.el7ost.noarch
python-neutron-lib-0.2.1-0.20160726025313.405f896.el7ost.noarch
openstack-neutron-9.0.0-0.20160726001729.6a23add.el7ost.noarch
openstack-neutron-sriov-nic-agent-9.0.0-0.20160726001729.6a23add.el7ost.noarch
python-neutron-9.0.0-0.20160726001729.6a23add.el7ost.noarch
openstack-neutron-openvswitch-9.0.0-0.20160726001729.6a23add.el7ost.noarch
openstack-neutron-common-9.0.0-0.20160726001729.6a23add.el7ost.noarch
python-neutronclient-4.2.1-0.20160721230146.3b1c538.el7ost.noarch
How reproducible:
always
Steps to Reproduce:
1.Deploy SRIOV ENV
2.Config the ENV to work with PF (no VFS configured )
3.Create neutron port vnic type= direct physical
4.boot vm with neutrn port that created
Actual results:
VM is in ERROR state
Expected results:
VM should boot as active
Additional info:
Comment 2Vladik Romanovsky
2016-08-19 13:24:18 UTC
Eran,
Is it a bug that Brent and me helped debug recently?
If yes, It seemed to me that we were able to allocate PFs and boot a vm.
Is there anything else needed here besides the documentation or can this bug be closed?
Thanks,
Vladik
Yes this is the same issue. but after I tried to set again the ENV we could not allocate PF and boot vm. so we need explaination what sould we need to config so we can work with PF. Also there is RFE https://bugzilla.redhat.com/show_bug.cgi?id=1233921
so I need to verify that the ENV can handke with dynamic switch. One ime boot vm to VF and one time to PF .You can see mail that Brent sent you so we can document all the info .
After a conversation with Brent it seems like we need someone to verify that documentation wise we're not recommending folks to use the 'devname' configuration key when trying to use SRIOV-PF.
Created attachment 1191078 [details] pf sriov Description of problem: PFs aren't showing up as available making it not possible to boot vms with PFs When I am trying to boot VM with Neutron port with vnic type - direct - physical there is an error. attached the error. The ENV is SRIOV 1 compute & 1 controller Version-Release number of selected component (if applicable): python-nova-14.0.0-0.20160726054215.02421fc.el7ost.noarch python-novaclient-5.0.1-0.20160724130722.6b11a1c.el7ost.noarch openstack-nova-compute-14.0.0-0.20160726054215.02421fc.el7ost.noarch openstack-nova-common-14.0.0-0.20160726054215.02421fc.el7ost.noarch python-neutron-lib-0.2.1-0.20160726025313.405f896.el7ost.noarch openstack-neutron-9.0.0-0.20160726001729.6a23add.el7ost.noarch openstack-neutron-sriov-nic-agent-9.0.0-0.20160726001729.6a23add.el7ost.noarch python-neutron-9.0.0-0.20160726001729.6a23add.el7ost.noarch openstack-neutron-openvswitch-9.0.0-0.20160726001729.6a23add.el7ost.noarch openstack-neutron-common-9.0.0-0.20160726001729.6a23add.el7ost.noarch python-neutronclient-4.2.1-0.20160721230146.3b1c538.el7ost.noarch How reproducible: always Steps to Reproduce: 1.Deploy SRIOV ENV 2.Config the ENV to work with PF (no VFS configured ) 3.Create neutron port vnic type= direct physical 4.boot vm with neutrn port that created Actual results: VM is in ERROR state Expected results: VM should boot as active Additional info: