As far as I know, Xen and kvm will not actually downgrade the clock speed to the guest, they will just attempt to make sure the guest does not get scheduled for more than it's share of the core's total power.
Someone correct me if I am wrong please. > On Sep 16, 2014, at 7:47 PM, Vibranze Teh <vibranze...@gmail.com> wrote: > > Hi Lists, > > I found out that the guest OS CPU clock is not conforming to the one > defined in compute offering. > > In Compute Offerings, I defined 1GHz, 2 Cores and the CPU Cap is ticked, > but when I did a 'cat /proc/cpuinfo' from guest OS, it shown my hypervisor > physical CPU clock. > > Is this behavior by design? How to really limit the guest OS to the one set > in Compute Offering? > > Thanks.
