Beth Kon wrote: > Clock drift on Linux is in the range of .017% - .019%, loaded and unloaded. I > haven't found a straightforward way to test on Windows and would appreciate > any pointers to existing approaches.
Is there any reason why there should be any clock drift, when the guest is using a non-PIT clock? I'm probably being naive, but with 32-bit or 64-bit HPET counters available to the guest, and accurate values from the CMOS clock emulation, I don't see why drift would accumulate over the long term relative to the host clock. -- Jamie -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
