Please don't drop the list. KVM creates the interfaces, then you add them to a bridge. Creating internal interfaces isn't going to do what you want, because those interfaces won't be used by the VM.
Did you read INSTALL.Libvirt.md? On Wed, Feb 18, 2015 at 10:18:09PM +0530, jayakeerthi k wrote: > Hi, > then how to create the openvswitch interfaces to connect to the VM's. But > it works fine with above method. > i'm creating the vm with virt-manager(kvm-qemu) and when i give the > specified shared name i could not able to create the vm. it says that > unable to add vneto port on the bridge. > > ovs-vsctl add-port br3 vport1-- port created this way is not shown in the > available interfaces. > please suggest any resources regarding this. > > Thanking you, > Jayakeerthi k > > > > On Wed, Feb 18, 2015 at 9:38 PM, Ben Pfaff <[email protected]> wrote: > > > On Wed, Feb 18, 2015 at 03:25:33PM +0530, jayakeerthi k wrote: > > > I installed openvswitch and i could able to add port and connect it to vm > > > on KVM only when the port created in the following way. > > > ovs-vsctl add-port br3 vport1 -- set interface vport1 type=internal. > > > > > > is the correct way of creating port and connecting it the vm. > > > > No. VM interfaces aren't "internal". > > > > > Also when i connect it the controller (ODL) . It shows many hosts which > > are > > > not really connected particular port i created. > > > > It's hard to tell what you mean. > > _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
