Tomasz Chmielewski wrote:
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).
And the problem continues?
What's your current clocksource (in the guest)? Does changing it help?
See /sys/devices/system/clocksource/clocksource0/*.
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 gue
Right, but if the guest is poisoned somehow, this won't help.
--
error compiling committee.c: too many arguments to function
--
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
