On Thu, Jul 24, 2014 at 03:31:53PM +0200, Ján Tomko wrote:
On 07/24/2014 02:03 PM, Martin Kletzander wrote:This reflects the same change made in kernel commit df457f845e (before v2.6.38-rc7). On the rare occasion when the user would try setting the weight to value in range <10, 100) on older kernel, we will error out with EINVAL properly. Modifying the error message (adding a hint for example) would cause weird logs, especially without stacked error messages (I couldn't resist mentioning it again).There is no (easy) way of getting the limits from kernel, since it's not exposed.I think removing the limit checks from libvirt, as was done for ranges specified via XML, would be a nicer fix: https://www.redhat.com/archives/libvir-list/2013-October/msg00525.html Jan
Oh, so we just failed to remove some of the checks in that series. OK, I'll repost that as a v2.
signature.asc
Description: Digital signature
-- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
