Nerijus Baliunas <nerijus <at> users.sourceforge.net> writes: > Paolo Bonzini <pbonzini <at> redhat.com> writes: > > > In the case of Windows it's probably some timing loop that is executed > > at startup, and the result depends on frequency scaling in the host. > > Try adding this to the XML in the meanwhile, and see if the control > > panel shows the same value: > > > > Inside <features>: > > > > <hyperv> > > <relaxed state='on'/> > > </hyperv> > > > > Inside <clock offset='localtime'>: > > > > <timer name='hypervclock' present='yes'/> > > So far Control Panel -> System shows CPU as 2.2 GHz, I rebooted once. So it > seems OK. Unfortunately after the host reboot the problem reappeared once. It helped to reboot the VM. Any ideas what else to try? Regards, Nerijus -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html