>
> So finally an important question probably is : how do I create tap0 and
> tap1 ? And what network-configuration should I give to them (probably
> dhcp-client) ?
These virtual interfaces (tab0 and tab1) are supposed to be created by the
hypervisor, not by you. Xen, for example, creates virtua
Yes, the ovs is running in the host-machine, not in the VMs. This way,
the ovs is running on the same level as the VirtualBox infrastructure.
The bridges and their ports must be created on the host level, and then
should be visible as available interfaces in the hypervisor, and then
should be av
We generally encourage users to try to use the native OVS commands to do
configuration and not run the bridge compatibility code. Obviously, there are
situations where this is not possible, and it's necessary due to pre-compiled
binaries or some such to use this mode. For example, we had to do
Ben Pfaff a écrit :
On Wed, Jan 19, 2011 at 09:51:31AM +0100, Xavier COUDIN wrote:
I installed ovs from sources. Compilation was OK, initialization was OK.
I chose to compile-install it without kernel module, so that means
as userspace. Maybe in the future I will compile kernel modules, but
I
Hi
Lazy as I'm this morning (bad sleeping you know) and before trying to
adapt the default ovs init script to create one for brcompatd, may I
ask if someone around already did this and would be kind enough to
share its script with us ?
Thank you in advance
Jérémie
___
