Re: Ubuntu 16.04, Openvswitch networking issue

Hi, looks like I was wrong. The typo did not fix our issue. We are still not sure whats going on but we are not able to deploy virtual router on xenserver if system.vm.default.hyper is empty. All the best, Florian From: Engelmann Florian Sent: Wedne

vm.network.throttling.rate changed from 200 to 1000 but VMs are still limited to 200

Hi, I changed vm.network.throttling.rate from 200 to 1000 but when I run iperf between 2 VMs the maximum speed I get is still 200. Can you please advise why this didn't take effect. Thanks & Regards, Nezar.

Re: vm.network.throttling.rate changed from 200 to 1000 but VMs are still limited to 200

from 200 mega bits to 1000 mega bits? How is your underlying networking configuration? Are the VMs on the same host? on different host, but same pod? On different hosts from different pods? On Mon, Mar 6, 2017 at 4:46 PM, Nezar Madbouh wrote: > Hi, > > I changed vm.network.throttling.rate from 2

Re: vm.network.throttling.rate changed from 200 to 1000 but VMs are still limited to 200

Take a look at https://cwiki.apache.org/confluence/display/CLOUDSTACK/Network+throttling+in+CloudStack You might have to change more than the setting. -- Erik On Mon, Mar 6, 2017 at 10:46 PM, Nezar Madbouh wrote: > Hi, > > I changed vm.network.throttling.rate from 200 to 1000 but when I run ip

Re: vm.network.throttling.rate changed from 200 to 1000 but VMs are still limited to 200

Hi Rafael, Thank you very much for your assistance. Please see answers to your questions below: from 200 mega bits to 1000 mega bits? yes megabits. How is your underlying networking configuration? Adanced network setup. Please let me know how much information you need here. Are the VMs on the s

Re: vm.network.throttling.rate changed from 200 to 1000 but VMs are still limited to 200

Thanks for your answers. Did you check Erik's link? Can I assume that your switch has GB ports as well as your hosts? On Mon, Mar 6, 2017 at 7:04 PM, Nezar Madbouh wrote: > Hi Rafael, > > Thank you very much for your assistance. Please see answers to your > questions below: > > from 200 mega bi

Re: vm.network.throttling.rate changed from 200 to 1000 but VMs are still limited to 200

After this change, you need to stop and start your VM from GUI or via api calls. On 3/6/17, 1:46 PM, "Nezar Madbouh" wrote: Hi, I changed vm.network.throttling.rate from 200 to 1000 but when I run iperf between 2 VMs the maximum speed I get is still 200. Can you please

Re: vm.network.throttling.rate changed from 200 to 1000 but VMs are still limited to 200

Thank you Yiping. After stopping / starting the VMs I can see I can go beyond 200M. Your help is much appreciated. Nezar. On 7 March 2017 at 12:49, Yiping Zhang wrote: > After this change, you need to stop and start your VM from GUI or via api > calls. > > > On 3/6/17, 1:46 PM, "Nezar Madbouh

Hosts going down

All, This is little bit off-topic. More of hardware issue. For our cloudstack, compute nodes (XENserver 6.2) are running on Supermicro SuperServer 5017R-MTF . Sometimes in a pool, some server goes down on its own (host appears a