Avi Kivity schrieb:
Tomasz Chmielewski wrote:
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).
# dmesg | grep kvm
(...)
loaded kvm module (kvm-84)
# modinfo kvm
filename: /lib/modules/2.6.24-2-pve/kernel/arch/x86/kvm/kvm.ko
version: kvm-84
# kvm -h
QEMU PC emulator version 0.9.1 (kvm-84), Copyright (c) 2003-2008 Fabrice
Bellard
Does the problem occur if you pin a guest to a cpu with taskset?
Like this?
# taskset -p 01 22906
I meant 'taskset 01 qemu ...' but it wouldn't have helped if it's kvmclock.
It can be done on a running process as well (22906 is the PID of the
affected guest).
And the issue is hard to reproduce (shows up after 1-7 days on a random
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
