> >
> > Its temporary and its regression bug caused due to other last min
> commit. due to this traffic labels are not considering.
> >
> > Regards
> > Sadhu
> >
> >
> >
> > -Original Message-
> > From: Serg Senko [mailto:kernc
ystem
> vm template? What happens if you destroy the router and let it
> recreate?
>
> On Sun, Apr 20, 2014 at 6:20 PM, Serg Senko wrote:
> > Hi
> >
> > After upgrade and restarting system-VM's
> > all VR started with some bad network configuration, egress r
Hi,
What does mean "In 4.3 traffic labels are not considering" ?
It's temporary or " traffic labels " is deprecated now ?
Does mean, anyone with KVM traffic labels environment can't upgrade to
4.3.0?
On Thu, Apr 10, 2014 at 5:05 PM, Suresh Sadhu wrote:
> Did you used traffic name labels?
>
Hi,
I have same issue after upgrade 4.1.1 to 4.3.0
Take a look, in CS4.2 VR you have NIC's eth0,eth1,eth2.
In CS 4.3 VR you have 4 NIC's where the eth2 and eth3 is the same.
How CS4.3 is passed the QA?
On Sat, Apr 12, 2014 at 12:16 AM, motty cruz wrote:
> I have a testing cloudstack cluster,
Hi
After upgrade and restarting system-VM's
all VR started with some bad network configuration, egress rules stopped
work.
also some staticNAT rules,
there is " ip addr show " from one of VR's
root@r-256-VM:~# ip addr show
1: lo: mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:
Hello all,
There is some bug after upgrade from 4.1.1 to 4.3.0
KVM Hypervizor
Agent settings labels :
guest.network.device=cloudbr1
private.network.device=cloudbr1
public.network.device=cloudbr0
After upgrade to 4.3 SSVM, all VR's started with multiple [public]
interfaces,
I have some VR's with
Hi,
It's can be some know bug?
Possible it's already solved in new releases of CS but i need the
work-around or fix before upgrade or reference to bug id.
Environment:
CS 4.1.1
libvirt-1.0.1
qemu-kvm-1.2
NFS Storage ( as primary for VR's )
Advanced VLAN isolation
After hypervisor host crashing,
Hi,
I have same error after computing node restaring ...
Did you find solution? fix ?
On Sat, Nov 16, 2013 at 3:17 PM, m2m isb wrote:
> Hello All
>
>
>
> We have a problem about Starting VMs.
>
> We have a ClousdStack 4.1.1 running with KVM,
> Unable to start VMs with Following error.
>
>
> Cl
