Alexander Graf <agraf@xxxxxxx> wrote: Hi, > Do you have ntpd running inside the guest? I have a bug report lying > around about 2.6.33 with kvm-clock jumping in time when ntpd is used: > https://bugzilla.novell.com/show_bug.cgi?id=582260 I want to chime in here, I have a very similar problem, but not with ntpd in the guest. The host was a HP ProLiant DL320 G5p with a Dualcore Xeon3075. System was a Debian Lenny with a custom 2.6.33 host kernel and a custom qemu-kvm 0.11.0 .deb ported from Ubuntu. The host is synced with ntpd. The guests are various Debian Lenny/Squeeze VMs, with a custom kernel (2.6.33 at the moment) with kvm-clock. Exclusively amd64 guest kernels, but one system has i386 userland. With this setup once in a while (maybe every other week) one VM would have a sudden clock jump, 6-12 hours into the future. No kernel messages or other log entries than applications complaining about the clock jump after the fact. Other VMs were unaffected. Yesterday I did an upgrade to Debian Squeeze. This involved a new qemu-kvm (0.12.4), but not a new host kernel. I also upgraded the guest kernels from 2.6.33 to 2.6.33.4. First of all, after the reboot the host clock was totally unreliable. I had a constant skew of up to five seconds per minute in the host clock, which of course affected the VMs as well. This problem went away when I changed from tsc into hpet on the host. The host does CPU frequency scaling which is, as far as I know, known to affect TSC stability. I think I remember messages about tsc being unstable in earlier boots, maybe the detection did just not work this time. Worse, the clock jump issues in the guest appeared much more often than before. The higher loaded VMs did not survive ten minutes without jumping several hours ahead. Situation has stabilized after setting clocksource hpet in the guest immediately after boot. So it seems kvm-clock has some issues here. I've seen a preliminary patch floating around on the ML by Zachary Amsden, but I haven't tried it yet. It talks of backward warps, but so far I've only seen forward warps (the VM time suddenly jumps into the future), so it might be unrelated. Bernhard -- 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
