On Mon, 2008-12-22 at 11:57 +0100, Max Kellermann wrote: > On 2008/12/21 12:55, Jan Niehusmann <[email protected]> wrote: > > As I observed such behaviour only when the host has frequency > > scaling activated: Could it be that in this case, > > clocksource_read(clock) on the guest is misbehaving? > > Indeed, the host had governor=ondemand. After the switch to > "performance", the guest seems to run stable. > > So this is a bug in the guest kernel, by making wrong assumptions on > the clock values retrieved from the host, right?
FWIW, several Fedora users are also seeing guest lockups with kvm-clock in the guest and frequency scaling enabled in the host. See: https://bugzilla.redhat.com/475598 Cheers, Mark. -- 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
