[openstack-dev] [sriov] Could create sriov vm on one host successfully but failed on another host

2016-01-07 Thread yujie 

Hi all,
  I have two hosts. Host1 run services of controller/compute/network, 
and host2 run services of compute. The network type is vlan.
  When creating port with direct type and booting a vm using this port 
on host2, the vm works well. But when create the vm on host1 using same 
way, the vm state is error. And the nova-compute log says:


ERROR nova.pci.stats [req-4af9b36d-8a0c-43d5-8535-fbf9e8d1b857 
06172a48a7254dda934a729f4a58d2ec 894880b2f31046d7b8a83bc3783df070 - - -] 
Failed to allocate PCI devices for instance. Unassigning devices back to 
pools. This should not happen, since the scheduler should have accurate 
information, and allocation during claims is controlled via a hold on 
the compute node semaphore


  Any suggestion 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

Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed

2015-12-01 Thread yujie 

Hi Sean,
 I noticed that above talking using openstack with dpdk only in devstack.
 I already have kilo environment and want it to support dpdk. Could 
reinstalling ovs with dpdk will be work?

Thanks.
Yu


在 2015/11/27 20:38, Mooney, Sean K 写道:

For kilo we provided a single node all in one example config here
https://github.com/openstack/networking-ovs-dpdk/blob/stable/kilo/doc/source/_downloads/local.conf_example

I have modified that to be a controller with the interfaces and ips form your 
controller local.conf.
I do not have any kilo compute local.conf to hand but I modified an old compute 
local.conf to so that it should work
Using the ip and interface settings from your compute local.conf.


Regards
Sean.

From: Praveen MANKARA RADHAKRISHNAN [mailto:praveen.mank...@6wind.com]
Sent: Friday, November 27, 2015 9:21 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with 
Unexpected vif_type=binding_failed

Hi Sean,

I have changed the hostname in both machines.
and tried again still i have the same error.

I am trying to configure ovs-dpdk with vlan now.
For the kilo version the getting started guide was missing in the repository.
But i have changed the repositories everywhere to kilo.

Please find the attached loal.conf for compute and controller.

one change i have made is i have added ml2 plusgin as vlan for compute config 
also.
because if i exactly use the local.confs as in example the controller was vlan 
and compute is taking as vxlan for the ml2 config.

And please find all the errors present in the compute and controller.

Thanks
Praveen

On Thu, Nov 26, 2015 at 5:58 PM, Mooney, Sean K 
> wrote:
Openstack uses the hostname as a primary key in many of the project.
Nova and neutron both do this.
If you had two nodes with the same host name then it would cause undefined 
behavior.

Based on the error Andreas highlighted  are you currently trying to configure 
ovs-dpdk with vxlan/gre?

I also noticed that the getting started guide you linked to earlier was for the 
master branch(mitaka) but
You mentioned you were deploying kilo.
The local.conf settings will be different in both case.





-Original Message-
From: Andreas Scheuring 
[mailto:scheu...@linux.vnet.ibm.com]
Sent: Thursday, November 26, 2015 1:43 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with 
Unexpected vif_type=binding_failed

Praveen,
there are many error in your q-svc log.
It says:

InvalidInput: Invalid input for operation: (u'Tunnel IP %(ip)s in use with host 
%(host)s', {'ip': u'10.81.1.150', 'host':
u'localhost.localdomain'}).\n"]


Did you maybe specify duplicated ips in your controllers and compute nodes 
neutron tunnel config?

Or did you change the hostname after installation

Or maybe the code has trouble with duplicated host names?

--
Andreas
(IRC: scheuran)



On Di, 2015-11-24 at 15:28 +0100, Praveen MANKARA RADHAKRISHNAN wrote:
> Hi Sean,
>
>
> Thanks for the reply.
>
>
> Please find the logs attached.
> ovs-dpdk is correctly running in compute.
>
>
> Thanks
> Praveen
>
> On Tue, Nov 24, 2015 at 3:04 PM, Mooney, Sean K
> > wrote:
>  Hi would you be able to attach the
>
>  n-cpu log form the computenode  and  the
>
>  n-sch and q-svc logs for the controller so we can see if there
>  is a stack trace relating to the
>
>  vm boot.
>
>
>
>  Also can you confirm ovs-dpdk is running correctly on the
>  compute node by running
>
>  sudo service ovs-dpdk status
>
>
>
>  the neutron and networking-ovs-dpdk commits are from their
>  respective stable/kilo branches so they should be compatible
>
>  provided no breaking changes have been merged to either
>  branch.
>
>
>
>  regards
>
>  sean.
>
>
>
>  From: Praveen MANKARA RADHAKRISHNAN
>  [mailto:praveen.mank...@6wind.com]
>  Sent: Tuesday, November 24, 2015 1:39 PM
>  To: OpenStack Development Mailing List (not for usage
>  questions)
>  Subject: Re: [openstack-dev] [networking-ovs-dpdk] VM creation
>  fails with Unexpected vif_type=binding_failed
>
>
>
>  Hi Przemek,
>
>
>
>
>  Thanks For the response,
>
>
>
>
>
>  Here are the commit ids for Neutron and networking-ovs-dpdk
>
>
>
>
>
>  [stack@localhost neutron]$ git log --format="%H" -n 1
>
>
>  026bfc6421da796075f71a9ad4378674f619193d
>
>
>  [stack@localhost neutron]$ cd ..
>
>
>  [stack@localhost ~]$ cd networking-ovs-dpdk/
>
>
>  [stack@localhost networking-ovs-dpdk]$  git log --format="%H"
>  -n 1
>
>
>

Re: [openstack-dev] [neutron][sriov] SRIOV-VM could not work well with normal VM

2015-10-22 Thread yujie 

I used ixgbe and vlan, passthrough a VF to vm.
After the VM created, it could not connect to VM on the same compute 
node without use sriov.


在 2015/10/22 10:58, Alexander Duyck 写道:

I assume by Intel cards you mean something that is running ixgbe?  If so
and you are trying to use SR-IOV with OVS and VLANs running on top of
the PF it will fail. The issue is that OVS requires the ability to place
the PF in promiscuous mode to support VLAN trunking, and ixgbe driver
prevents that when SR-IOV is enabled.

The "bridge fdb add" approach mentioned should work as long as ixgbe PF
is used on a flat network.

- Alex

On 10/19/2015 07:33 PM, yujie wrote:

Hi Moshe Levi,
   Sorry for replying to this message after so long time. The testing
environment was unavailable before.
   I use Intel cards, but could only tested base kilo and vlan. Could
it work?

在 2015/9/22 13:24, Moshe Levi 写道:

Hi Yujie,

There is a patch https://review.openstack.org/#/c/198736/ which I
wrote to add the mac of the normal instance to
the SR-IOV embedded switch so that the packet will go to the PF
instead of going to the wire.
This is done by using bridge tool with the command "bridge fdb add
 dev "

I was able to test it on Mellanox ConnectX3  card with both vlan and
flat network and it worked fine.
I wasn't able to test it on any of the Intel cards, but I was told
the it only working on flat network, in vlan network the Intel card
is dropping the tagged packets and they are not go up to the VF.

What NIC are you using? Can you try using "bridge fdb add  dev
" where  is the mac of the normal vm and 
is the PF
and see if  that resolve the issue.
Also can you check it with  flat and vlan networks.


-----Original Message-
From: yujie [mailto:judy_yu...@126.com]
Sent: Tuesday, September 22, 2015 6:28 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [neutron][sriov] SRIOV-VM could not work
well with normal VM

Hi all,
I am using neutron kilo without dvr to create sriov instance VM-A,it
works well and could connect to its gateway fine.
But when I let the normal instance VM-B which in the same
compute-node with VM-A ping its gateway, it failed. I capture the
packet on the network-node, find the gateway already reply the
ARP-reply message to VM-B. But compute-node which VM-B lives could
not send the package to VM-B.
If delete VM-A and set : echo 0 >
/sys/class/enp5s0f0/device/sriov_numvfs, the problem solved.

Is it a same question with the bug: SR-IOV port doesn't reach OVS
port on same compute node ?
https://bugs.launchpad.net/neutron/+bug/1492228
Any suggestions will be grateful.

Thanks,
Yujie


__

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

__

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




__

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



__
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



__
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

Re: [openstack-dev] [neutron][sriov] SRIOV-VM could not work well with normal VM

2015-10-19 Thread yujie 

Hi Moshe Levi,
   Sorry for replying to this message after so long time. The testing 
environment was unavailable before.
   I use Intel cards, but could only tested base kilo and vlan. Could 
it work?


在 2015/9/22 13:24, Moshe Levi 写道:

Hi Yujie,

There is a patch https://review.openstack.org/#/c/198736/ which I wrote to add 
the mac of the normal instance to
the SR-IOV embedded switch so that the packet will go to the PF instead of 
going to the wire.
This is done by using bridge tool with the command "bridge fdb add  dev 
"

I was able to test it on Mellanox ConnectX3  card with both  vlan and flat 
network and it worked fine.
I wasn't able to test it on any of the Intel cards, but I was told the it only 
working on flat network, in vlan network the Intel card is dropping the tagged 
packets and they are not go up to the VF.

What NIC are you using? Can you try using "bridge fdb add  dev " where 
 is the mac of the normal vm and  is the PF
and see if  that resolve the issue.
Also can you check it with  flat and vlan networks.


-Original Message-
From: yujie [mailto:judy_yu...@126.com]
Sent: Tuesday, September 22, 2015 6:28 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [neutron][sriov] SRIOV-VM could not work well with 
normal VM

Hi all,
I am using neutron kilo without dvr to create sriov instance VM-A,it works well 
and could connect to its gateway fine.
But when I let the normal instance VM-B which in the same compute-node with 
VM-A ping its gateway, it failed. I capture the packet on the network-node, 
find the gateway already reply the ARP-reply message to VM-B. But compute-node 
which VM-B lives could not send the package to VM-B.
If delete VM-A and set : echo 0 >
/sys/class/enp5s0f0/device/sriov_numvfs, the problem solved.

Is it a same question with the bug: SR-IOV port doesn't reach OVS port on same 
compute node ?
https://bugs.launchpad.net/neutron/+bug/1492228
Any suggestions will be grateful.

Thanks,
Yujie


__
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

__
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




__
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

[openstack-dev] [neutron][sriov] SRIOV-VM could not work well with normal VM

2015-09-21 Thread yujie 

Hi all,
I am using neutron kilo without dvr to create sriov instance VM-A,it 
works well and could connect to its gateway fine.
But when I let the normal instance VM-B which in the same compute-node 
with VM-A ping its gateway, it failed. I capture the packet on the 
network-node, find the gateway already reply the ARP-reply message to 
VM-B. But compute-node which VM-B lives could not send the package to VM-B.
If delete VM-A and set : echo 0 > 
/sys/class/enp5s0f0/device/sriov_numvfs, the problem solved.


Is it a same question with the bug: SR-IOV port doesn't reach OVS port 
on same compute node ?

https://bugs.launchpad.net/neutron/+bug/1492228
Any suggestions will be grateful.

Thanks,
Yujie


__
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