Re: 2.6.32 guest with paravirt clock enabled hangs on 2.6.37.6 host (w qemu-kvm-0.13.0)

[Zachary Amsden <zamsden@redhat.com>]

On 05/09/2011 11:25 AM, Nikola Ciprich wrote:
> The guest, because latest kernels do not suffer this problem, so I'd like to
> find fix so it can be pushed to -stable (we're using 2.6.32.x)
> host is currently 2.6.37 (and i'm currently testing 2.6.38 as well)
> n.

That's a pretty wide range to be bisecting, and I think we know for a 
fact there were some kvmclock related bugs in that range.

If you are looking for something causing problems with tcpdump, I'd 
suggest getting rid of kvmclock in your testing and using TSC instead; 
if you're looking to verify that kvmclock related changed have been 
backported to -stable, rather than bisect and run into bugs, it would 
probably be faster to check the commit logs for arch/x86/kvm/x86.c and 
make sure you're not missing anything from me or Glauber that has been 
applied to the most recent branch.

Zach