On (Thu) Aug 26 2010 [10:05:44], Paolo Bonzini wrote:
> On 08/26/2010 08:05 AM, Amit Shah wrote:
> >This is what I have currently. It would need some timer handling in
> >the save/load case as well, right?
>
> When loading you won't have any pending "info balloon" command, so I
> think the timer need not be preserved across migration.
>
> Also, 5 seconds for a stopped guest is actually a lot,
That's the problem; it's policy. Where and how to specify it?
> so maybe
> Amit's original patch or a variant thereof would make sense anyway.
This seems to be needed though -- as Anthony mentioned, a guest which
has oopsed or similar, incapable of servicing the stats request, is
going to block the monitor command from returning forever.
So it's better to have a timeout, just that we need to decide how much
it should be.
Amit
