From: Chris Webb <chris.webb@elastichosts.com>
To: kvm@vger.kernel.org
Subject: Unsupported delivery mode 7
Date: Wed, 19 Nov 2008 12:54:29 +0000 [thread overview]
Message-ID: <20081119125429.GH923@arachsys.com> (raw)
We're running kvm-78 in production on Linux 2.6.27 x86_64 on dual quad-core
Opteron 'Barcelona' machines. Our kvm modules are built from the kvm-78
sources rather than the older version bundled with the kernel, and we're
using the NPT features of the processors.
For the most part, everything is performing very well and running reliably.
However, occasionally a guest will hang as it starts (or is reset) with a
large number of messages of the form
Unsupported delivery mode 7
in the dmesg. Following this, killing and relaunching the qemu process is
usually sufficient to get a working guest.
I'm aware that our versions of the kvm kernel modules and userspace are not
the latest release, but because we're running long-lived guests on behalf of
clients, it's quite a major operation to upgrade. Does this look like a
known bug which has already been fixed or should I try to reproduce it
properly on a test machine with an ability to debug, use magic sysrq, etc?
(It seems impossible to reproduce on my lower spec desktop machine, for what
it's worth. Normally I'd reproduce kernel problems in a KVM virtual
machine---but that's obviously not an option here!)
Am I right in suspecting it might be connected to interrupt delivery
following page migration when a guest moves from one processor to another,
and that a workaround might be to taskset guests to one or other physical
CPU until we're able to upgrade to a more recent version of KVM?
Many thanks in advance for any advice anyone can offer.
Cheers,
Chris.
next reply other threads:[~2008-11-19 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 12:54 Chris Webb [this message]
2008-11-19 14:28 ` Unsupported delivery mode 7 Jan Kiszka
2008-11-21 15:02 ` Chris Webb
2008-11-21 17:15 ` Marcelo Tosatti
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=20081119125429.GH923@arachsys.com \
--to=chris.webb@elastichosts.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