100% means potentially complete usage of the number of cores allocated/reserved. So, if the vcpu value is 1, hyper-v allocates 1 virtual cpu, and reserves 1 core on the system for that vcpu, the 100% limit allows it to use that entire reserved amount. (it is kind of a duplicate cap, I don't know why one would reserve CPU cycles and then limit anything below that since you have already taken the resource)
I am not sure how that works on libvirt / what the settings are right now, we might want to adjust the reservation amount to mirror that, since right now it is an entire core per vcpu with hyper-v...
100% means potentially complete usage of the number of cores allocated/reserved. So, if the vcpu value is 1, hyper-v allocates 1 virtual cpu, and reserves 1 core on the system for that vcpu, the 100% limit allows it to use that entire reserved amount. (it is kind of a duplicate cap, I don't know why one would reserve CPU cycles and then limit anything below that since you have already taken the resource)
I am not sure how that works on libvirt / what the settings are right now, we might want to adjust the reservation amount to mirror that, since right now it is an entire core per vcpu with hyper-v...