On 09/10/2010 06:03 PM, Michael Tokarev wrote:
Strange. Can you also post a few lines of 'vmstat 1'?
Maybe we'll see a lot of context switches in there.
Not that many. Still running the same w7 guest, still
~25..27% CPU usage reported by top for the kvm process,
here's `vmstat 5' after a while (I tend to use larger
delay to mitigate large(ish) spikes):
procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu----
r b swpd free buff cache si so bi bo in cs us sy id wa
0 0 286764 1262976 20640 1618468 0 0 0 24 6206 4460 7 9 84 0
1 0 286764 1263040 20640 1618436 0 0 0 0 6080 4415 7 9 84 0
1 0 286764 1264380 20648 1618448 0 0 0 5 6332 4576 8 11 81 0
1 0 286760 1264700 20656 1618436 6 0 6 18 6464 4742 7 8 84 1
1 0 286760 1264864 20664 1618472 0 0 0 10 6266 4704 8 8 85 0
0
Stumped.
A shot in the dark: can you try running with vnc instead of sdl (and
disconnecting your vnc client while measuring)? Maybe the guest is
doing a lot of vga updates.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
--
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
