From: Jan Kiszka <jan.kiszka@siemens.com>
To: Henrik Holst <henrik@witsbits.com>
Cc: kvm@vger.kernel.org
Subject: Re: kvm-kmod-2.6.33 (or 2.6.32) messes up pages on guest exit
Date: Mon, 08 Mar 2010 09:01:32 +0100 [thread overview]
Message-ID: <4B94AEDC.10305@siemens.com> (raw)
In-Reply-To: <4e9085271003071304l73708cbek1d5e54cefedcddf7@mail.gmail.com>
Henrik Holst wrote:
> Hi,
>
> I'm running a few Debian Lenny host machines with kernel 2.6.26, in
> production we use kvm-kmod-2.6.31.5 without any problems. Today I
> tested to change to kvm-kmod-2.6.33 and everything went just fine up
> to the moment when a guest exited and when it did the kernel started
> to log thousands of rows about page errors on the host.
>
> modprobe -r kvm-intel (and kvm) and modprobe of the 2.6.31.5 version
> made the problems go away again. Could it be that 2.6.26 is a little
> too old kernel to run as host for the newer kvm?
Maybe. I'm only testing against 2.6.27 as oldest host, down to 2.6.24 is
solely build-tested. Maybe the missing MMU notfiers in <= 2.6.26 cause
troubles, though this used to work before.
Can't promise that I find the time to look into this (such old kernels
are out of official scope). If I managed to, I would try to bisect over
kvm-kmod-2.6.32 what import from kvm.git or what kvm-kmod wrapping
brought us the breakage. But maybe someone else finds the time, setup
support would be provided...
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2010-03-08 8:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-07 21:04 kvm-kmod-2.6.33 (or 2.6.32) messes up pages on guest exit Henrik Holst
2010-03-08 8:01 ` Jan Kiszka [this message]
2010-03-08 8:11 ` Henrik Holst
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=4B94AEDC.10305@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=henrik@witsbits.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