Tomasz Chmielewski schrieb:
Avi Kivity schrieb:
I'm guessing there's a problem with timers or timer interrupts.
What is the host cpu?
4 entries like this in /proc/cpuinfo:
processor : 3
vendor_id : AuthenticAMD
cpu family : 15
model : 65
model name : Dual-Core AMD Opteron(tm) Processor 2212
That's probably the kvmclock issue that hit older AMDs. It was
fixed in kvm-84, please try that.
It is kvm-84, I have it running since Saturday (but I had this issue
with kvm-83 as well).
And the problem continues?
What's your current clocksource (in the guest)? Does changing it help?
See /sys/devices/system/clocksource/clocksource0/*.
It was kvm-clock.
I tried changing it to acpi_pm, jiffies, tsc, but it made no difference.
Actually, I don't think that I checked tsc, because when I changed to jiffies, the time has stopped:
# echo jiffies > /sys/devices/system/clocksource/clocksource0/current_clocksource
# date
Mon Mar 9 12:29:00 CET 2009
# date
Mon Mar 9 12:29:00 CET 2009
# date
Mon Mar 9 12:29:00 CET 2009
# date
Mon Mar 9 12:29:00 CET 2009
# date
Mon Mar 9 12:29:00 CET 2009
And I couldn't change to anything else any more:
# echo tsc > /sys/devices/system/clocksource/clocksource0/current_clocksource
# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
jiffies
# echo kvm-clock > /sys/devices/system/clocksource/clocksource0/current_clocksource
# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
jiffies
So I had to kill the guest and start it again (the above is reproduced on another,
"non-poisoned" guest).
--
Tomasz Chmielewski
http://wpkg.org
--
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
