Hi Lucian,
For now I have disabled it by setting the compute offerings to bandwidth
limit to 0. This removes the bandwidth section from KVM XML.
When my compute offering is set to 1000, the following XML is created (via
virsh dumpxml i-2-xx-VM)
<bandwidth>
<inbound average='128000' peak='128000'/>
<outbound average='128000' peak='128000'/>
</bandwidth>
This seems to give the bandwidth of around 2.5Mbit/s (using iperf to check
against a physical server).
Setting the compute offering to something else (I can't remember sorry!) it
gave:
<bandwidth>
<inbound average='640000' peak='640000'/>
<outbound average='640000' peak='640000'/>
</bandwidth>
But it gave a bandwidth of 1.32Mbit/s
This is a tad odd, surely a higher value should result in more bandwidth
being allowed through?
Thanks,
Marty
On Mon, Oct 28, 2013 at 11:56 AM, Nux! <[email protected]> wrote:
> On 28.10.2013 11:18, Marty Sweet wrote:
>
>> Hi Guys,
>>
>> Following my upgrade from 4.1.1 -> 4.2.0, I have noticed that VM traffic
>> is
>> now limited to 2Mbits.
>> My compute offerings were already 1000 for network limit and I have
>> created
>> new offerings to ensure this wasn't the issue (this fixed it for someone
>> in
>> the mailing list).
>>
>> Is there anything that I am missing? I can't remember reading this as a
>> bug
>> fix or new feature.
>> If there is a way to resolve or disable it, it would be most appreciated -
>> have been going round in circles for hours.
>>
>> Thanks,
>> Marty
>>
>
> Hi Marty,
>
> I think on Linux "tc" is the tool used to limit traffic. Have a look at
> this for a crashcourse and see if it helps you find the culprit:
> http://www.cyberciti.biz/faq/**linux-traffic-shaping-using-**
> tc-to-control-http-traffic/<http://www.cyberciti.biz/faq/linux-traffic-shaping-using-tc-to-control-http-traffic/>
>
> HTH
> Lucian
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
