Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed
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
<sean.k.moo...@intel.com<mailto:sean.k.moo...@intel.com>> 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<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
> <sean.k.moo...@intel.com<mailto:sean.k.moo...@intel.com>> 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<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=
Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed
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
<sean.k.moo...@intel.com<mailto:sean.k.moo...@intel.com>> 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<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
> <sean.k.moo...@intel.com<mailto:sean.k.moo...@intel.com>> 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<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=
Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed
Hi, One thing i observed is there is no packets coming to the dpdk interface (data network). I have verified it with the tcpdump using mirror interface. and if i assign ip address and ping each other the data network bridges that is also not working. could this be a possible cause for the nova exception? (NovaException: Unexpected vif_type=binding_failed) Thanks Praveen On Tue, Nov 24, 2015 at 3:28 PM, Praveen MANKARA RADHAKRISHNAN < praveen.mank...@6wind.com> 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 <sean.k.moo...@intel.com> > 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 >> >> 90dd03a76a7e30cf76ecc657f23be8371b1181d2 >> >> >> >> The Neutron agents are up and running in compute node. >> >> >> >> Thanks >> >> Praveen >> >> >> >> >> >> On Tue, Nov 24, 2015 at 12:57 PM, Czesnowicz, Przemyslaw < >> przemyslaw.czesnow...@intel.com> wrote: >> >> Hi Praveen, >> >> >> >> There’s been some changes recently to networking-ovs-dpdk, it no longer >> host’s a mech driver as the openviswitch mech driver in Neutron supports >> vhost-user ports. >> >> I guess something went wrong and the version of Neutron is not matching >> networking-ovs-dpdk. Can you post commit ids of Neutron and >> networking-ovs-dpdk. >> >> >> >> The other possibility is that the Neutron agent is not running/died on >> the compute node. >> >> Check with: >> >> neutron agent-list >> >> >> >> Przemek >> >> >> >> *From:* Praveen MANKARA RADHAKRISHNAN [mailto:praveen.mank...@6wind.com] >> *Sent:* Tuesday, November 24, 2015 12:18 PM >> *To:* openstack-dev@lists.openstack.org >> *Subject:* [openstack-dev] [networking-ovs-dpdk] VM creation fails with >> Unexpected vif_type=binding_failed >> >> >> >> Hi, >> >> >> >> Am trying to set up an open stack (kilo) installation using ovs-dpdk >> through devstack installation. >> >> >> >> I have followed the " >> https://github.com/openstack/networking-ovs-dpdk/blob/master/doc/source/getstarted.rst >> " documentation. >> >> >> >> I used the same versions as in documentation (fedora21, with right >> kernel). >> >> >> >> My openstack installation is successful in both controller and compute. >> >> I have used example local.conf given in the documentation. >> >> But if i try to spawn the VM. I am having the following error. >> >> >> >> "NovaException: Unexpected vif_type=binding_failed" >> >> >> >> It would be really helpful if you can point out how to debug and fix this >> error. >> >> >> >> Thanks >> >> Praveen >> >> >> >> >> __ >> 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] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed
Am when you say dpdk interface do you mean dpdk physical interface is not reciving any packets or a vhost-user interface. Can you provide the output of ovs-vsctl show. And sudo /opt/stack/DPDK-v2.1.0/tools/dpdk_nic_bind.py –status You should see an output similar to this. Network devices using DPDK-compatible driver :02:00.0 'Ethernet Controller XL710 for 40GbE QSFP+' drv=igb_uio unused=i40e Network devices using kernel driver === :02:00.1 'Ethernet Controller XL710 for 40GbE QSFP+' if=ens785f1 drv=i40e unused=igb_uio :02:00.2 'Ethernet Controller XL710 for 40GbE QSFP+' if=ens785f2 drv=i40e unused=igb_uio :02:00.3 'Ethernet Controller XL710 for 40GbE QSFP+' if=ens785f3 drv=i40e unused=igb_uio :06:00.0 'I350 Gigabit Network Connection' if=enp6s0f0 drv=igb unused=igb_uio :06:00.1 'I350 Gigabit Network Connection' if=enp6s0f1 drv=igb unused=igb_uio Other network devices = From: Praveen MANKARA RADHAKRISHNAN [mailto:praveen.mank...@6wind.com] Sent: Thursday, November 26, 2015 9:46 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, One thing i observed is there is no packets coming to the dpdk interface (data network). I have verified it with the tcpdump using mirror interface. and if i assign ip address and ping each other the data network bridges that is also not working. could this be a possible cause for the nova exception? (NovaException: Unexpected vif_type=binding_failed) Thanks Praveen On Tue, Nov 24, 2015 at 3:28 PM, Praveen MANKARA RADHAKRISHNAN <praveen.mank...@6wind.com<mailto:praveen.mank...@6wind.com>> 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 <sean.k.moo...@intel.com<mailto:sean.k.moo...@intel.com>> 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<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 90dd03a76a7e30cf76ecc657f23be8371b1181d2 The Neutron agents are up and running in compute node. Thanks Praveen On Tue, Nov 24, 2015 at 12:57 PM, Czesnowicz, Przemyslaw <przemyslaw.czesnow...@intel.com<mailto:przemyslaw.czesnow...@intel.com>> wrote: Hi Praveen, There’s been some changes recently to networking-ovs-dpdk, it no longer host’s a mech driver as the openviswitch mech driver in Neutron supports vhost-user ports. I guess something went wrong and the version of Neutron is not matching networking-ovs-dpdk. Can you post commit ids of Neutron and networking-ovs-dpdk. The other possibility is that the Neutron agent is not running/died on the compute node. Check with: neutron agent-list Przemek From: Praveen MANKARA RADHAKRISHNAN [mailto:praveen.mank...@6wind.com<mailto:praveen.mank...@6wind.com>] Sent: Tuesday, November 24, 2015 12:18 PM To: openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org> Subject: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed Hi, Am trying to set up an open stack (kilo) installation using ovs-dpdk through devstack installation. I have followed the " https://github.com/openstack/networking-ovs-dpdk/blob/master/doc/source/getstarted.rst " documentation. I used the same versions as in documentation (fedora21, with right kernel). My openstack installation is successful in both controller and compute. I have used example local.conf given in the documentation. But if i try to spawn the VM. I am having the following error. "NovaException: Unexpected vif_type=binding_failed" It
Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed
compatible driver > > > > :02:00.0 'Ethernet Controller XL710 for 40GbE QSFP+' drv=igb_uio > unused=i40e > > > > Network devices using kernel driver > > === > > :02:00.1 'Ethernet Controller XL710 for 40GbE QSFP+' if=ens785f1 > drv=i40e unused=igb_uio > > :02:00.2 'Ethernet Controller XL710 for 40GbE QSFP+' if=ens785f2 > drv=i40e unused=igb_uio > > :02:00.3 'Ethernet Controller XL710 for 40GbE QSFP+' if=ens785f3 > drv=i40e unused=igb_uio > > :06:00.0 'I350 Gigabit Network Connection' if=enp6s0f0 drv=igb > unused=igb_uio > > 0000:06:00.1 'I350 Gigabit Network Connection' if=enp6s0f1 drv=igb > unused=igb_uio > > > > Other network devices > > = > > > > > > > > *From:* Praveen MANKARA RADHAKRISHNAN [mailto:praveen.mank...@6wind.com] > *Sent:* Thursday, November 26, 2015 9:46 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, > > > > One thing i observed is there is no packets coming to the dpdk interface > (data network). > > I have verified it with the tcpdump using mirror interface. > > and if i assign ip address and ping each other the data network bridges > that is also not working. > > could this be a possible cause for the nova exception? (NovaException: > Unexpected vif_type=binding_failed) > > > > Thanks > > Praveen > > > > On Tue, Nov 24, 2015 at 3:28 PM, Praveen MANKARA RADHAKRISHNAN < > praveen.mank...@6wind.com> 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 <sean.k.moo...@intel.com> > 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 > > 90dd03a76a7e30cf76ecc657f23be8371b1181d2 > > > > The Neutron agents are up and running in compute node. > > > > Thanks > > Praveen > > > > > > On Tue, Nov 24, 2015 at 12:57 PM, Czesnowicz, Przemyslaw < > przemyslaw.czesnow...@intel.com> wrote: > > Hi Praveen, > > > > There’s been some changes recently to networking-ovs-dpdk, it no longer > host’s a mech driver as the openviswitch mech driver in Neutron supports > vhost-user ports. > > I guess something went wrong and the version of Neutron is not matching > networking-ovs-dpdk. Can you post commit ids of Neutron and > networking-ovs-dpdk. > > > > The other possibility is that the Neutron agent is not running/died on the > compute node. > > Check with: > > neutron agent-list > > > > Przemek > > > > *From:* Praveen MANKARA RADHAKRISHNAN [mailto:praveen.mank...@6wind.com] > *Sent:* Tuesday, November 24, 2015 12:18 PM > *To:* openstack-dev@lists.openstack.org > *Subject:* [openstack-dev] [networking-ovs-dpdk] VM creation fails with > Unexpected vif_type=binding_failed > > > > Hi, > > > > Am trying to set up an open stack (kilo) installation using ovs-dpdk > through devstack installation. > > > > I have followed the "
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
> <sean.k.moo...@intel.com> 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
>
>
> 90dd03a76a7e30cf76ecc657f23be8371b1181d2
>
>
>
>
>
> The Neutron agents are up and running in compute node.
>
>
>
>
>
> Thanks
>
>
> Praveen
>
>
>
>
>
>
>
> On Tue, Nov 24, 2015 at 12:57 PM, Czesnowicz, Przemyslaw
> <przemyslaw.czesnow...@intel.com> wrote:
>
> Hi Praveen,
>
>
>
> There’s been some changes recently to
> networking-ovs-dpdk, it no longer host’s a mech driver
> as the openviswitch mech driver in Neutron supports
> vhost-user ports.
>
> I guess something went wrong and the version of
> Neutron is not matching networking-ovs-dpdk. Can you
> post commit ids of Neutron and networking-ovs-dpdk.
>
>
>
> The other possibility is that the Neutron agent is not
> running/died on the compute node.
>
> Check with:
>
> neutron agent-list
>
>
>
> Przemek
>
>
>
> From: Praveen MANKARA RADHAKRISHNAN
> [mailto:praveen.mank...@6wind.com]
> Sent: Tuesday, November 24, 2015 12:18 PM
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] [networking-ovs-dpdk] VM
> creation f
Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed
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
> <sean.k.moo...@intel.com> 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
>
>
> 90dd03a76a7e30cf76ecc657f23be8371b1181d2
>
>
>
>
>
> The Neutron agents are up and running in compute node.
>
>
>
>
>
> Thanks
>
>
> Praveen
>
>
>
>
>
>
>
> On Tue, Nov 24, 2015 at 12:57 PM, Czesnowicz, Przemyslaw
> <przemyslaw.czesnow...@intel.com> wrote:
>
> Hi Praveen,
>
>
>
> There’s been some changes recently to
> networking-ovs-dpdk, it no longer host’s a mech driver
> as the openviswitch mech driver in Neutron supports
> vhost-user ports.
>
> I guess something went wrong and the version of
> Neutron is not matching networking-ovs-dpdk. Can you
> post commit ids of Neutron and networking-ovs-dpdk.
>
>
Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed
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 90dd03a76a7e30cf76ecc657f23be8371b1181d2 The Neutron agents are up and running in compute node. Thanks Praveen On Tue, Nov 24, 2015 at 12:57 PM, Czesnowicz, Przemyslaw <przemyslaw.czesnow...@intel.com<mailto:przemyslaw.czesnow...@intel.com>> wrote: Hi Praveen, There’s been some changes recently to networking-ovs-dpdk, it no longer host’s a mech driver as the openviswitch mech driver in Neutron supports vhost-user ports. I guess something went wrong and the version of Neutron is not matching networking-ovs-dpdk. Can you post commit ids of Neutron and networking-ovs-dpdk. The other possibility is that the Neutron agent is not running/died on the compute node. Check with: neutron agent-list Przemek From: Praveen MANKARA RADHAKRISHNAN [mailto:praveen.mank...@6wind.com<mailto:praveen.mank...@6wind.com>] Sent: Tuesday, November 24, 2015 12:18 PM To: openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org> Subject: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed Hi, Am trying to set up an open stack (kilo) installation using ovs-dpdk through devstack installation. I have followed the " https://github.com/openstack/networking-ovs-dpdk/blob/master/doc/source/getstarted.rst " documentation. I used the same versions as in documentation (fedora21, with right kernel). My openstack installation is successful in both controller and compute. I have used example local.conf given in the documentation. But if i try to spawn the VM. I am having the following error. "NovaException: Unexpected vif_type=binding_failed" It would be really helpful if you can point out how to debug and fix this error. Thanks Praveen __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://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] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed
Please have a look at your neutron server log and neutron agent log and provide this information if you have troubles interpreting the messages. Probably you'll find the reason there! -- Andreas (IRC: scheuran) On Di, 2015-11-24 at 12:17 +0100, Praveen MANKARA RADHAKRISHNAN wrote: > Hi, > > > Am trying to set up an open stack (kilo) installation using ovs-dpdk > through devstack installation. > > > I have followed the " > https://github.com/openstack/networking-ovs-dpdk/blob/master/doc/source/getstarted.rst > " documentation. > > > I used the same versions as in documentation (fedora21, with right > kernel). > > > My openstack installation is successful in both controller and > compute. > I have used example local.conf given in the documentation. > But if i try to spawn the VM. I am having the following error. > > > "NovaException: Unexpected vif_type=binding_failed" > > > > It would be really helpful if you can point out how to debug and fix > this error. > > > Thanks > Praveen > > > __ > 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] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed
Hi Praveen, There’s been some changes recently to networking-ovs-dpdk, it no longer host’s a mech driver as the openviswitch mech driver in Neutron supports vhost-user ports. I guess something went wrong and the version of Neutron is not matching networking-ovs-dpdk. Can you post commit ids of Neutron and networking-ovs-dpdk. The other possibility is that the Neutron agent is not running/died on the compute node. Check with: neutron agent-list Przemek From: Praveen MANKARA RADHAKRISHNAN [mailto:praveen.mank...@6wind.com] Sent: Tuesday, November 24, 2015 12:18 PM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed Hi, Am trying to set up an open stack (kilo) installation using ovs-dpdk through devstack installation. I have followed the " https://github.com/openstack/networking-ovs-dpdk/blob/master/doc/source/getstarted.rst " documentation. I used the same versions as in documentation (fedora21, with right kernel). My openstack installation is successful in both controller and compute. I have used example local.conf given in the documentation. But if i try to spawn the VM. I am having the following error. "NovaException: Unexpected vif_type=binding_failed" It would be really helpful if you can point out how to debug and fix this error. Thanks Praveen __ 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
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 90dd03a76a7e30cf76ecc657f23be8371b1181d2 The Neutron agents are up and running in compute node. Thanks Praveen On Tue, Nov 24, 2015 at 12:57 PM, Czesnowicz, Przemyslaw < przemyslaw.czesnow...@intel.com> wrote: > Hi Praveen, > > > > There’s been some changes recently to networking-ovs-dpdk, it no longer > host’s a mech driver as the openviswitch mech driver in Neutron supports > vhost-user ports. > > I guess something went wrong and the version of Neutron is not matching > networking-ovs-dpdk. Can you post commit ids of Neutron and > networking-ovs-dpdk. > > > > The other possibility is that the Neutron agent is not running/died on the > compute node. > > Check with: > > neutron agent-list > > > > Przemek > > > > *From:* Praveen MANKARA RADHAKRISHNAN [mailto:praveen.mank...@6wind.com] > *Sent:* Tuesday, November 24, 2015 12:18 PM > *To:* openstack-dev@lists.openstack.org > *Subject:* [openstack-dev] [networking-ovs-dpdk] VM creation fails with > Unexpected vif_type=binding_failed > > > > Hi, > > > > Am trying to set up an open stack (kilo) installation using ovs-dpdk > through devstack installation. > > > > I have followed the " > https://github.com/openstack/networking-ovs-dpdk/blob/master/doc/source/getstarted.rst > " documentation. > > > > I used the same versions as in documentation (fedora21, with right > kernel). > > > > My openstack installation is successful in both controller and compute. > > I have used example local.conf given in the documentation. > > But if i try to spawn the VM. I am having the following error. > > > > "NovaException: Unexpected vif_type=binding_failed" > > > > It would be really helpful if you can point out how to debug and fix this > error. > > > > Thanks > > Praveen > > > > __ > 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
