Did you install the host side VIF driver?
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109
Tel : +972 (9) 7692306
IRC : ydary
On Wed, Dec 28, 2016 at 1:39 AM, Sverker Abrahamsson <
For long time I've been looking for proper support in ovirt for Open
vSwitch so I'm happy that it is moving in the right direction. However,
there seems to still be a dependency on a ovirtmgmt bridge and I'm unable
to move that to the OVN provider.
The hosting center where I rent hw instances has a bit special network
setup, so I have one physical network port with a /32 netmask and
point-to-point config to router. The physical port I connect to a ovs
bridge which has the public ip. Since ovirt always messes up the network
config when I've tried to let it have access to the network config for the
physical port, I've set eht0 and ovsbridge0 as hidden in vdsm.conf.
I then create a bridge for use with ovirt, with a private address. With
the OVN provider I am now able to import these into the engine and it looks
good. When creating a VM I can select that it will have a vNic on my OVS
However, I can't start the VM as an exception is thrown in the log:
2016-12-28 00:13:33,350 ERROR [org.ovirt.engine.core.bll.RunVmCommand]
(default task-5) [3c882d53] Error during ValidateFailure.:
Looking at that section of code where the exception is thrown, I see that
it iterates over host networks to find required networks, which I assume is
ovirtmgmt. In the host network setup dialog I don't see any networks at all
but it lists ovirtmgmt as required. It also list the OVN networks but these
can't be statically assigned as they are added dynamically when needed,
which is fine.
I believe that I either need to remove ovirtmgmt network or configure that
it is provided by the OVN provider, but neither is possible. Preferably it
shouldn't be hardcoded which network is management and mandatory but be
possible to configure.
Den 2016-12-27 kl. 17:10, skrev Marcin Mirecki:
The following is a new meeting request:
Subject: OVN Deep Dive for oVirt 4.1
Organizer: "Marcin Mirecki" <mmirecki(a)redhat.com>
Time: Wednesday, January 11, 2017, 4:00:00 PM - 5:00:00 PM GMT +01:00 Amsterdam, Berlin,
Bern, Rome, Stockholm, Vienna
OVN (Open Virtual Networking) is a new network virtualization project that
brings virtual networking to Open vSwitch.
OVN is now availble to use as a tech preview in oVirt. It is made available
using the oVirt external network providers API, which allows using external
network management software inside environments managed by oVirt.
The integration with OVN will allow users to take advantage of native OVS
support for software defined networks.
The advantages of using OVN:
- ability to use large number of networks with no need for multiple host NICs
or VLAN use
- ability to set up new network without any changes to the physical infrastructure
- easier to maintain due to centralized management
- good traffic isolation due to Openflow rules
- improved performance over neutron OVS plugin
- OVN overview
- oVirt external network provider API overview
- oVirt provider for OVN overview
Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
Users mailing list