>What is your guest KVM traffic label set to?
It is set to cloudbrguest.
>And tell it to use cloudbrguest-10 as the traffic label, it will go up one
from vlan10 and settle on vlan211 as the physical device.
Yes, that should work(I don't have possibility to test it right now),
thanks for suggestio
I created that document, as a suggestion. I never got feedback. The
way it worked previously was sort of a happy accident, which was
'fixed' when the code changed to accept overlapping vlan numbers on
multiple physical devices (hence the bridge name change).
However... I believe there is still a
Hi all.
I was able to change vlan creation behaviour by source code modification
(plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtComputingResource.java),
had to comment several lines of code:
private String getPif(String bridge) {
String pif = matchPifFileInDirector
So, nobody uses q in q and cloudstack 4.1 ?
On Mon, Jul 8, 2013 at 3:13 PM, Valery Ciareszka
wrote:
> Hi all,
>
> I use the following environment: CS 4.1, KVM, Centos 6.4
> (management+node1+node2), OpenIndiana NFS server as primary and secondary
> storage
> I have advanced networking in zone. I
Hi all,
I use the following environment: CS 4.1, KVM, Centos 6.4
(management+node1+node2), OpenIndiana NFS server as primary and secondary
storage
I have advanced networking in zone. I split management/public/guest traffic
into different vlans, and use kvm network labels (bridge names):
# cat /etc
