setting the link as non VM networks let me configure the interface as needed.
On 07/04/2016 04:16 PM, Yevgeny Zaspitsky wrote:
> Infiniband should not be bridged.
> Ovirt tries to build a bridge over a NIC if the network is a VM one. Please
> verify that it isn't.
> On Mon,
Infiniband should not be bridged.
Ovirt tries to build a bridge over a NIC if the network is a VM one. Please
verify that it isn't.
On Mon, Jul 4, 2016 at 5:10 PM, Giorgio Biacchi wrote:
> As I said, Infiniband is not ethernet so it cannot be L2 bridged. This is
As I said, Infiniband is not ethernet so it cannot be L2 bridged. This is normal
and I understand why it can't be done. I'd like to know if there's a way to
configure host networking for infiniband link without bridging because is not
necessary to have a bridge there. In addition to this, 3.6
As I remember the IBoIP is not fully implemented Ethernet protocol, it does
not support bridging.
Dr. Arman Khalatyan eScience -SuperComputing
Leibniz-Institut für Astrophysik Potsdam (AIP)
An der Sternwarte 16, 14482 Potsdam,
hooks are only needed to set connected mode and the correct MTU on the
infiniband link. The problem is bound to the host networking setup procedure.
Here's the hooks:
echo Setting IB connected mode
What's "couple of vdsm hooks"? Could you provide the source code of those?
On Mon, Jul 4, 2016 at 1:43 PM, Giorgio Biacchi wrote:
> Hi list,
> I'm trying a test installation of the new Ovirt Node Image and engine
> upgrading my 3.6
I'm trying a test installation of the new Ovirt Node Image and engine before
upgrading my 3.6 installation.
In my current environment every hypervisor access the NFS shared data domain via
infiniband. With a couple of vdsm hooks I was able to set the infiniband link in
connected mode and
Mail list logo