them right away.
>
> ** **
>
> Cheers,
>
> ** **
>
> Hugo
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> *From:* Sheng Yang [mailto:sh...@yasker.org]
> *Sent:* Friday, May 03, 2013 12:39 AM
> *To:* Hugo Trippaers
> *Cc:*
> *Subj
er.org]
Sent: Friday, May 03, 2013 12:39 AM
To: Hugo Trippaers
Cc:
Subject: Re: OVS on KVM
After upgrade to Ubuntu 13.04(libvirt 1.0.2), vlan tag works well.
--Sheng
On Thu, May 2, 2013 at 11:18 AM, Sheng Yang
mailto:sh...@yasker.org>> wrote:
After searching I found this:
http:/
After upgrade to Ubuntu 13.04(libvirt 1.0.2), vlan tag works well.
--Sheng
On Thu, May 2, 2013 at 11:18 AM, Sheng Yang wrote:
> After searching I found this:
>
> http://libvirt.org/formatnetwork.html
>
>
> Setting VLAN tag (on supported network types only)
> ...
>
>
>
>
After searching I found this:
http://libvirt.org/formatnetwork.html
Setting VLAN tag (on supported network types only)
...
...
If (and only if) the network type supports vlan tagging transparent to the
guest, an op
I DO SEE the tag on VM profile when agent start, but I didn't see them on
OVS ports.
2013-05-01 18:04:44,702{GMT} DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-5:) starting v-2-VM:
v-2-VM
1422832d-be18-352a-a08a-9bbff40e0d14
Debian GNU/Linux 5.0 (32-bit)
/usr/bin/kvm
Hey Sheng,
The tagging is done by libvirt. Can you check your agent.log?
I would have expected an entry in the log file looking like this
's_logger.debug("creating a vlan dev and bridge for public traffic per traffic
label " + trafficLabel);'
Also the XML document for the vif sent to libvirt s