On Wed, Jul 25, 2012 at 10:29 PM, Gianluca Cecchi wrote:
> On Wed, Jul 25, 2012 at 8:01 PM, Jesse Gross wrote:
>> I don't see an actual question or description of a problem in here.
>> I'm guessing that you expect the tap device to be a vlan access port
>> but I don't see that you've actually configured that anywhere.
>>
>
> The first question is about "brctl show" command error in its
> output... is it expected?
>
> The second question is about what to put inside vm.xml to automatically get
> ovs-vsctl add-port brvlan65 vnet0 tag=65
> when I power on the vm.
>
> But I just see in git that there is also an INSTALL.Libvirt file I
> didn't find in 1.6.1 tar.gz
> I'm going to read it too..
>
> Gianluca
To add content:
after starting the vm I get
Bridge "brvlan65"
Port "eth2"
trunks: [65, 66]
Interface "eth2"
Port "brvlan65"
Interface "brvlan65"
type: internal
Port "vnet0"
Interface "vnet0"
And as you say, the port appears not configured as an access port on vlan 65.
Then with vm still running I manually type
# ovs-vsctl del-port brvlan65 vnet0 -- add-port brvlan65 vnet0 tag=65
and now
Bridge "brvlan65"
Port "eth2"
trunks: [65, 66]
Interface "eth2"
Port "brvlan65"
Interface "brvlan65"
type: internal
Port "vnet0"
tag: 65
Interface "vnet0"
And from an outside physical server, connected in access mode to
another vlan (66 in my case) with routing configured to reach vlan
65, I can successfully connect to the vm via ssh.
So the openvswitch functionality seems in place.
I miss the link to get this automatically when I power on the vm, but
it could be that I need to read more docs.
BTW: INSTALL.Libvirt speaks abotu libvirt 0.9.11, while in CentOS 6.3
there is 0.9.10 and I don't see anything in libvirt rpm changelog
regarding openvswitch integration backported....
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
