On 11/11/2014 20:57, Matt Mullins wrote: > That seems to work great, yes. > > Looking through the commit history, I see: > kvmclock: Ensure time in migration never goes backward > kvmclock: Ensure proper env->tsc value for kvmclock_current_nsec calculation > > Assuming those are the right fixes for this issue, are they suitable to request > backported to distros' qemu 2.0 branches? The merge commit for them seemed to > indicate they were problematic at first. > > On second thought - I found the qemu-devel threads about reverting them in the > 2.1 timeframe, so I'm going to do a little more research before I start trying > to suggest how to fix for existing install-base. The right commits are de9d61e83d43be9069e6646fa9d57a3f47779d28 317b0a6d8ba44e9bf8f9c3dbd776c4536843d82c 9a48bcd1b82494671c111109b0eefdb882581499 which are similar but not equivalent to the two commits you found. They should be in 2.1.3 if there will be one, and they are appropriate for backporting to 2.0. Thanks for confirming that they fix your problem! Paolo -- 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
