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 me
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 ; openstack@lists.openstack.org
Subject: RE: [Openstack
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 ; openstack@lists.openstack.org
Subject: RE: [Openstack] Openstack SRIOV and PCI passthrough error while
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 lo
> -Original Message-
> From: pranab boruah [mailto:pranabjyotibor...@gmail.com]
> Sent: Friday, October 6, 2017 9:45 AM
> To: openstack@lists.openstack.org
> Cc: Moshe Levi ; sean.k.moo...@intel.com
> Subject: [openstack-dev] [networking-odl] [SRIOV] [OVS HW offloa
Hi Eddie,
Looking on the your nova database after the delete looks correct to me.
| created_at | updated_at | deleted_at | deleted | id
| 2017-06-21 00:56:06 | 2017-07-07 02:27:16 | NULL| 0 | 2
| 2017-07-07 01:42:48 | 2017-07-07 02:13:14 | 2017
Hi all,
A recent change [1] in tempest broke all Mellanox CIs.
This is the second time it happened.
After the first time it happened we decided that Mellanox CI will comment on
tempest.
On this time I saw that Mellanox CI was commenting on that patch with a
failure but was still got approv
From: Chinmaya Dwibedy [mailto:ckdwib...@gmail.com]
Sent: Wednesday, June 08, 2016 8:39 AM
To: Moshe Levi
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] Issue with dev_type: type-PCI using openstack-mitaka
release on host (Cent OS 7.2)
Hi Moshe,
Thank you for the clarification. I
From: Chinmaya Dwibedy [mailto:ckdwib...@gmail.com]
Sent: Wednesday, June 08, 2016 7:43 AM
To: openstack@lists.openstack.org
Subject: [Openstack] Issue with dev_type: type-PCI using openstack-mitaka
release on host (Cent OS 7.2)
Hi All,
I want the Ethernet Card to be used for PCI Passthrough d
From: Chinmaya Dwibedy [mailto:ckdwib...@gmail.com]
Sent: Tuesday, June 07, 2016 9:22 AM
To: Moshe Levi
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] Issue with assignment of Intel’s QAT Card to VM
(PCI-passthrough) using openstack-mitaka release on Cent OS 7.2 host
Hi Moshe
Can you look if you have errors in the nova-computes log?
Also check if you passed the PciPassthroughFilter in the nova-scheduler log
From: Chinmaya Dwibedy [mailto:ckdwib...@gmail.com]
Sent: Tuesday, June 07, 2016 8:29 AM
To: openstack@lists.openstack.org
Subject: [Openstack] Issue with assignm
with I use Mellanox NIC), but I will try to help
Thank,
Moshe Levi.
From: OpenStack Mailing List Archive [mailto:cor...@gmail.com]
Sent: Tuesday, November 17, 2015 6:29 PM
To: openstack@lists.openstack.org
Subject: [Openstack] how to allow vlan tagged traffic to be sent from SR-IOV
> -Original Message-
> From: Mikyung Kang [mailto:mkk...@isi.edu]
> Sent: Tuesday, September 22, 2015 7:20 PM
> To: openstack@lists.openstack.org
> Subject: [Openstack] Is it possible to setup both SR-IOV-IB and Non-SR-IOV-
> Ethernet within 1 VM?
>
> Hello,
>
> I'm working for Icehouse
-
http://eavesdrop.openstack.org/meetings/pci_passthrough/2015/pci_passthrough.2015-06-23-13.09.log.txt
[2] - sriov: update port state even if ip link fails -
https://review.openstack.org/#/c/195060/
[3] - SR-IOV: deprecate agent_required option -
https://review.openstack.org/#/c/214324/
Thanks,
Mo
Hi,
The driver name should be kvm and not qemu.
I think you need to set the virt_type to kvm as describe below in the nova.conf
[libvirt]
virt_type = kvm
From: Kamsali, RaghavendraChari (Artesyn)
[mailto:raghavendrachari.kam
Hi,
I have update the SR-IOV wiki
https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking
Let me know if it clearer now.
Thanks,
Moshe Levi.
> -Original Message-
> From: Andreas Scheuring [mailto:scheu...@linux.vnet.ibm.com]
> Sent: Monday, July 20, 2015 12:3
> -Original Message-
> From: Andreas Scheuring [mailto:scheu...@linux.vnet.ibm.com]
> Sent: Monday, July 20, 2015 10:04 AM
> To: Moshe Levi
> Cc: Sam Stoelinga; openstack@lists.openstack.org
> Subject: Re: [Openstack] [Neutron][SRIOV][docs] Enabling SRIOV on
> OpenSt
See my comments inline
From: Sam Stoelinga [mailto:sammiest...@gmail.com]
Sent: Sunday, July 19, 2015 10:37 AM
To: Moshe Levi
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] [Neutron][SRIOV][docs] Enabling SRIOV on OpenStack
Juno step-by-step guide
I think it was not fair to say it&#
Hi Sam,
Can you explain why you think that the
https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking is out of
date?
Moreover you blog explain how to configure SR-IOV on Intel NIC, but keep in
mind Neutron SRIOV is generic and can support any other vendors such as
Mellanox.
Mayb
pci'
could not be initialized
You are using intel card therefore I think you should contact them and ask if
this card is supported.
From: Kamsali, RaghavendraChari (Artesyn)
[mailto:raghavendrachari.kams...@artesyn.com]
Sent: Tuesday, May 26, 2015 4:49 PM
To: Kamsali, RaghavendraChari (
Hi Kamsali,
This is the error:
Refusing to bind due to unsupported vnic_type: direct
Please add the following to you ml2_conf.ini
supported_pci_vendor_devs = 8086:154c
Thanks,
Moshe Levi
From: Kamsali, RaghavendraChari (Artesyn)
[mailto:raghavendrachari.kams...@artesyn.com
Hi Kamsali,
According to the logs you got binding failed error, which mean neutron failed
to bind the port.
Can you send the neutron server log and the your neutron ml2 conf file?
Thank,
Moshe Levi
From: Kamsali, RaghavendraChari
(Artesyn)<mailto:raghavendrachari.kams...@artesyn.
...@gmail.com]
Sent: Thursday, April 23, 2015 7:12 PM
To: Moshe Levi
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] DHCP issues with SR-IOV networking
I followed the wiki for the setup and did the following to configure the nw and
subnet.
neutron net-create --provider:physical_network
that do tcpdump on br-int and see broadcast messages arrived form
ovs-physical bridge.
-Original Message-
From: jacob jacob [mailto:opstk...@gmail.com]
Sent: Thursday, April 23, 2015 5:11 PM
To: Moshe Levi
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] DHCP issues with SR
The openvswitch agent should be able to bind the port.
Can you check that you have in ml2 conf
mechaniscm_drivers = openvswitch,sriovnicswitch
also check that the openvswitch agent is running on your network node.
-Original Message-
From: jacob jacob [mailto:opstk...@gmail.com]
Sent:
25 matches
Mail list logo
