On Thu, May 17, 2012 at 11:19:04PM +0300, Gleb Natapov wrote: > On Thu, May 17, 2012 at 10:14:35PM +0200, Sasha Levin wrote: > > On Thu, May 17, 2012 at 10:05 PM, Gleb Natapov <gleb@xxxxxxxxxx> wrote: > > > On Thu, May 17, 2012 at 09:49:08PM +0200, Sasha Levin wrote: > > >> Hi all, > > >> > > >> I've observed a guest hang after putting a little stress testing on > > >> it. It basically hangs in ~10 secs after running several trinity > > >> instances inside a KVM tools guest. > > >> > > > And do you set hypervisor bit in KVM tool? > > > > We're basically forwarding the cpuid of the host, so I assume that no? > You really should, but hang shouldn't happen anyway. > > -- > Gleb. If kvmclock is not enabled a number of problems arise (miscalibrated loops per jiffy, sched_clock using tsc's out of sync on smp). Should set the hypervisor cpuid bit (see 49ab56ac6e1b907b7da). -- 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
