Recent autotest/virt-test testing on f20 discovered an anomaly in how
the bandwidth options are documented and used. This was discovered due
to a bug fix in the /sbin/tc utility found in iproute-3.11.0.1 (on f20)
in which overflow was actually caught and returned as an error. The fix
was first
I meant to add something under the -- in my email, but the fingers were
too quick... Although the commit message is quite lengthy - it does
hopefully give enough context to decisions made.
There was some consideration to perform kibibyte range checking in
libvirt; however, if the underlying
