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.

Reply via email to