From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Marcelo Tosatti <mtosatti@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: soft lockup after live migration
Date: Sun, 08 Nov 2009 12:20:24 +0100 [thread overview]
Message-ID: <4AF6A978.5020006@wpkg.org> (raw)
In-Reply-To: <20091024203553.GA6891@amt.cnet>
Marcelo Tosatti wrote:
> Tomasz,
>
> The screenshots seem to indicate a paravirt mmu problem.
>
> Try to patch the x86.c file from kvm kernel module with:
>
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> - case KVM_CAP_PV_MMU:
> - r = !tdp_enabled;
> + case KVM_CAP_PV_MMU: /* obsolete */
> + r = 0;
>
> You'll probaby have to do it manually (this disables pvmmu).
With this, some guests fail to start with kernel panic; some have soft
lockups all the time. Some don't start at all.
And generally, everything is "dead slow".
--
Tomasz Chmielewski
http://wpkg.org
prev parent reply other threads:[~2009-11-08 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-24 0:40 soft lockup after live migration Tomasz Chmielewski
[not found] ` <20091024203553.GA6891@amt.cnet>
2009-11-08 11:20 ` Tomasz Chmielewski [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=4AF6A978.5020006@wpkg.org \
--to=mangoo@wpkg.org \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@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