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 From: xen-api-boun...@lists.xen.org [mailto:xen-api-boun...@lists.xen.org] On Behalf Of George Shuklin Sent: 14 January 2013 13:33 To: xen-api@lists.xen.org Subject: Re: [Xen-API] qos_algorithm_type=ratelimit 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@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
