[lkml]   [2009]   [Jan]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [Bug #12465] KVM guests stalling on 2.6.28 (bisected)
Kevin Shanahan wrote:
>>> --- ping statistics ---
>>> 900 packets transmitted, 900 received, 0% packet loss, time 899326ms
>>> rtt min/avg/max/mdev = 0.093/0.157/3.611/0.117 ms
>>> So, a _huge_ difference. But what does it mean?
>> It means, a scheduling problem. Can you run the latency tracer (which
>> only works with realtime priority), so we can tell if it is (a) kvm
>> failing to wake up the vcpu properly or (b) the scheduler delaying the
>> vcpu from running.
> Sorry, but are you sure that's going to be useful?
> If it only works on realtime threads and I'm not seeing the problem when
> running kvm with realtime priority, is this going to tell you what you
> want to know?
> Not trying to be difficult, but that just didn't make sense to me.

You're right, wasn't thinking properly.

This is a tough one. I'll see if I can think of something. Ingo, any

error compiling committee.c: too many arguments to function

 \ /
  Last update: 2009-01-21 16:03    [W:0.385 / U:6.560 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site