public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: pbonzini@redhat.com
Cc: kvm@vger.kernel.org
Subject: Guest OS migration and lost IPIs
Date: Tue, 4 Aug 2020 17:07:20 -0700	[thread overview]
Message-ID: <20200805000720.GA7516@paulmck-ThinkPad-P72> (raw)

Hello, Paolo!

We are seeing occasional odd hangs, but only in cases where guest OSes
are being migrated.  Migrating more often makes the hangs happen more
frequently.

Added debug showed that the hung CPU is stuck trying to send an IPI (e.g.,
smp_call_function_single()).  The hung CPU thinks that it has sent the
IPI, but the destination CPU has interrupts enabled (-not- disabled,
enabled, as in ready, willing, and able to take interrupts).  In fact,
the destination CPU usually is going about its business as if nothing
was wrong, which makes me suspect that the IPI got lost somewhere along
the way.

I bumbled a bit through the qemu and KVM source, and didn't find anything
synchronizing IPIs and migrations, though given that I know pretty much
nothing about either qemu or KVM, this doesn't count for much.

The guest OS is running v5.2, so reasonably recent.  It is using
QEMU Guest Agent 2.12.0.  The host is also running v5.2 and providing
qemu-system-x86_64 version 2.11.0.

Is this a known problem?  Is there some debugging options I should enable?
Any other patch I should apply?

							Thanx, Paul

             reply	other threads:[~2020-08-05  0:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-05  0:07 Paul E. McKenney [this message]
2020-08-07 12:36 ` Guest OS migration and lost IPIs Paolo Bonzini
2020-08-08  2:02   ` Paul E. McKenney

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=20200805000720.GA7516@paulmck-ThinkPad-P72 \
    --to=paulmck@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    /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