[ovs-discuss] Naive doubts regarding openvswitch
blp at nicira.com
Mon Sep 26 07:28:31 PDT 2011
There's nothing surprising about a particular module not being loaded by
default. It just means that it is not used by default. If you want to
use it, you just load it.
But the main issue with running OVS in a guest, as you describe, is that
it isn't likely to be useful for controlling traffic in a virtual
environment. That's because it won't be the primary switch. Instead,
traffic has to be switched by the actual hypervisor to and from the
virtual machine. You might be able to get it to work, but it will
perform poorly because there are two levels of switching going on.
To get good integration in your environment, you'd have to run OVS in
Windows 7. That's a nontrivial porting task.
On Mon, Sep 26, 2011 at 08:49:13AM +0530, Ajith Adapa wrote:
> Thanks for the reply. Sorry for my naive questions.
> As per my understanding ...
> OVS provides a L2 edge switching option within the hypervisor for
> controlling the traffic between VMs running on top of that hypervisor.
> Instead of using hypervisor's bridge like mechanism we place a openvswitch
> controlling the traffic flows and other options.
> What I meant in my second question is .. I am running linux as guest on my
> WIN7 host using virtualbox. When I search for default bridge module using
> lsmod command it is
> not loaded by default. Quite strange might be virtualbox has a different
> working. So now can I test ovs module in linux guest os ?
> As per the white papers I understand OVS main advantage seems only when the
> administrator wanted the control over packets being flown between VMs. In
> all others cases
> VESPA or next hop switch can do all the policing and other stuff at wire
> Sorry if I am wrong with my findings.
> On Sun, Sep 25, 2011 at 9:22 PM, Ben Pfaff <blp at nicira.com> wrote:
> > On Sun, Sep 25, 2011 at 02:48:57PM +0530, Ajith Adapa wrote:
> > > - Is OVS a kernel module with more integration into hypervisor level
> > > providing switching option for multiple VMs running on top of the
> > hypervisor
> > > ?
> > More integration than what?
> > > - Regarding test-setup I guess I cant test it directly on linux
> > running
> > > on a VM .. As per the doc available for replacing the linux default
> > bridge
> > > with OVS will not be supported if the linux is running on a VM ?
> > OVS works in a VM. What documentation are you looking at?
> > > - I see OVS supports virtual box but I havent found any doc regarding
> > it
> > > ?
> > I haven't used virtualbox so I can't help here.
More information about the discuss