On Mon, Mar 31, 2014 at 10:39:47AM +0200, Marcin Gibuła wrote: >>> I've seen very similar problem on our installation. Have you tried to >>> run with kvm-clock explicitly disabled (either via no-kvmclock in >>> guest kernel or with -kvm-clock in qemu) ? >> >> No, I haven't tried it yet (I've confirmed kvm-clock is currently >> being used). I'll have a look at it. >> >> Did it help your issue? > > My results were inconclusive, but there way a guy two months ago who > had the same problem and disabling kvm-clock resolved this for him. > > I wonder if it'll help you as well.
It's looking good so far, after a few migrations (it takes a while to test because I'm waiting at least 5 hours between migrations). I'll be happier once I've done a couple of weeks of this without any failures! Thanks for your suggestion. Chris
