[ovs-discuss] Connecting a VM to an emulated VTEP

[Mark Maglana]

Answering my own (inane) question. The kvm command I specified below works
except that i just needed to point the tap scripts it to br0 directly and
let it create the tap devices on the bridge. two VMs on that bridge can
ping each other. up next is how to create a logical switch between VMs on
different host machines.


On Tue, Aug 19, 2014 at 5:26 PM, Mark Maglana <mmaglana at gmail.com> wrote:

> Hi,
>
> I've set-up the VTEP emulator as indicated in
> https://github.com/openvswitch/ovs/blob/master/vtep/README.ovs-vtep
>
> Up next, I plan on launching a VM and then connect it to the "physical"
> switch br0. Before I proceed, I wanted to check if my plan of action makes
> sense:
>
> 1. Create another bridge, br1
>
>
> 2. Launch a VM via `kvm -m 512 -net nic,macaddr=00:00:00:00:cc:10 -net
> tap,script=/etc/ovs-ifup,downscript=/etc/ovs-ifdown -drive
> file=img/cirros-0.3.2-x86_64-disk.img -vnc :0`
>
>     /etc/ovs-ifup would look like:
>
>         #!/bin/sh
>         switch='br1'
>         /sbin/ifconfig $1 0.0.0.0 up
>         ovs-vsctl add-port ${switch} $1
>
>
> 3. Create a veth pair that connects br1 to br0. I'm thinking the
> connection is from br1's br1 internal port to br0's p0 port but I'm unsure
> if this is correct (still need to read up on creating veth pairs)
>
> After this, should I expect my VM to be able to ping to the outside world
> or am I seriously missing one or two things?
>
> Regards,
>
> Mark
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20140820/acfe168c/attachment-0002.html>