Ok, thanks for your confirmation!
** Changed in: qemu
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/950692
Title:
High CPU usage in Host (revisited)
Stat
>From our point of view, this ticket can be closed. KVM is running
without issues on all our servers for more than 5 years now.
The problem described above, was due to a weird combination of "timer"
kernel parameters in the early 3.x kernels. IIRC, enabling a high-
frequency timer and/or "tickless
Triaging old bug tickets ... can you somehow still reproduce this
problem with the latest version of QEMU (currently v2.9), or could we
close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-m
I see similar problem when few I/Os are pumped and the VM goes non-responsive.
The host sees nearly 100% CPU utilization.
top - 08:58:57 up 18:42, 2 users, load average: 0.99, 0.98, 0.95
Tasks: 355 total, 1 running, 354 sleeping, 0 stopped, 0 zombie
%Cpu(s): 1.5 us, 2.7 sy, 0.0 ni, 95.8
On Sun, Mar 11, 2012 at 05:30, PetaMem wrote:
> *Newsflash*
>
> We do have a "well-behaving" KVM Host with 3.2.9 kernel on machine C
Note: I am not Qemu developer :)
OK, I read your bug report many times. I think you need deeper
profiling here. Perhaps "perf top" is the best bet. Just make sure
*Newsflash*
We do have a "well-behaving" KVM Host with 3.2.9 kernel on machine C
After again numerous attempts to find the culprit, I decided to copy the
kernel 2.6.35 and modules from machine A to machine C, where it
exhibited also the desired "well-behaving".
I then simply copied its config to
