Hi Rushikesh, Iâve made a mistake â this fix did get into XCP 1.6.10. It didnât make it into version 6.1 of commercial XenServer, which is what confused me.
The original problem could still be caused by kilobit/kilobyte confusion, as George suggests.
John
From: Rushikesh Jadhav [mailto:2rushikeshj@xxxxxxxxx]
Sent: 14 January 2013 14:39
To: John Else
Cc: xen-api@xxxxxxxxxxxxx
Subject: Re: [Xen-API] qos_algorithm_type=ratelimit
Hello John,
Since the commit is 4 months old can we consider that it is fixed in XCP1.6.10 or are you suggesting that the current stable XCP1.6.10 has this known bug ? ( I assumed 2nd but just want to confirm )
By looking at patch, it looks safe to locally integrate into XCP1.6.10 xapi.src.rpm. Any suggestions ?
On Mon, Jan 14, 2013 at 7:25 PM, John Else <john.else@xxxxxxxxxx> wrote:
Thereâs also a known bug in XCP 1.6, where the API QoS settings donât actually get passed down to Xen. The master branch patch is here: https://github.com/xen-org/xen-api/commit/4fb4b96b10c2d40cd5e166845659f27882c6dae5
John
14.01.2013 03:55, Matthew Spah ÐÐÑÐÑ:
Hey everyone,
I'm currently testing and documenting the qos parameters for VIF interfaces. I've set up two VMs with VIF interfaces attached to an internal network. I've set the following qos parameters on each VIF interface.
xe vif-param-set uuid=<VIF UUID> qos_algorithm_type=ratelimit
xe vif-param-set uuid=<VIF UUID> qos_algorithm_params:kbps=100
iperf is showing me bandwidth rates between the two VMS that aren't limited to 100 kbps. Am I missing something?
kbps is not kbps, but a KiloBYTESperSecond. Really strange, but it is. kbps=12 will make it 100kpbs.
_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
