On Thu, 2010-04-22 at 19:18 -0500, Kevin Burge wrote: > It's been almost two months now since I've been able to boot my Linux > vms. I'm really surprised by this - usually with Debian problems are > fixed within a couple hours to at most a few days. Sorry about this. We now have a candidate fix for this, which should be released soon. Perhaps you would like to test it? Instructions for rebuilding an official kernel package with extra patches are at <http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official>. Ben. Date: Fri, 19 Mar 2010 15:47:39 +0100 Subject: KVM: x86: disable paravirt mmu reporting From: Marcelo Tosatti <email@example.com> commit a68a6a7282373bedba8a2ed751b6384edb983a64 upstream Disable paravirt MMU capability reporting, so that new (or rebooted) guests switch to native operation. Paravirt MMU is a burden to maintain and does not bring significant advantages compared to shadow anymore. Signed-off-by: Marcelo Tosatti <firstname.lastname@example.org> Signed-off-by: Avi Kivity <email@example.com> Signed-off-by: Stefan Bader <firstname.lastname@example.org> Signed-off-by: Greg Kroah-Hartman <email@example.com> [bwh: Adjust context for 2.6.26] --- arch/x86/kvm/x86.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) --- a/arch/x86/kvm/x86.c +++ b/arch/x86/kvm/x86.c @@ -1242,8 +1242,8 @@ int kvm_dev_ioctl_check_extension(long e case KVM_CAP_NR_MEMSLOTS: r = KVM_MEMORY_SLOTS; break; - case KVM_CAP_PV_MMU: - r = !tdp_enabled; + case KVM_CAP_PV_MMU: /* obsolete */ + r = 0; break; default: r = 0; --- END --- -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Description: This is a digitally signed message part