From: Paolo Bonzini <pbonzini@redhat.com>
To: kvm@vger.kernel.org
Subject: Re: Live migration locks up 3.2 guests in do_timer(ticks ~ 500000)
Date: Wed, 12 Nov 2014 09:59:59 +0100 [thread overview]
Message-ID: <5463218F.6020106@redhat.com> (raw)
In-Reply-To: <20141111195703.GF29098@hydra.tuxags.com>
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
prev parent reply other threads:[~2014-11-12 9:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 5:54 Live migration locks up 3.2 guests in do_timer(ticks ~ 500000) Matt Mullins
2014-09-08 8:18 ` Paolo Bonzini
2014-09-08 15:56 ` Matt Mullins
2014-09-08 16:18 ` Paolo Bonzini
2014-09-08 16:39 ` Matt Mullins
2014-09-10 6:53 ` Matt Mullins
2014-09-15 18:14 ` Matt Mullins
2014-09-16 8:42 ` Paolo Bonzini
2014-10-27 18:42 ` Matt Mullins
2014-10-28 9:04 ` Paolo Bonzini
2014-11-11 19:57 ` Matt Mullins
2014-11-12 8:59 ` Paolo Bonzini [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5463218F.6020106@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox