From 89cfc99177c9270c5c6d429f6c5177ab3428ad57 Mon Sep 17 00:00:00 2001 From: Rusty Russell Date: Thu, 27 Oct 2011 10:56:17 +1030 Subject: lguest: don't allow KVM-detection cpuid. Host might be running under KVM, but we shouldn't allow Guest to think it can use KVM hypercalls (it can't, and it will embarrass itself if it tries). Signed-off-by: Rusty Russell --- arch/x86/lguest/boot.c | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'arch/x86/lguest') diff --git a/arch/x86/lguest/boot.c b/arch/x86/lguest/boot.c index 13ee258442a..f63da5ef217 100644 --- a/arch/x86/lguest/boot.c +++ b/arch/x86/lguest/boot.c @@ -70,6 +70,7 @@ #include #include #include /* for struct machine_ops */ +#include /*G:010 * Welcome to the Guest! @@ -455,6 +456,15 @@ static void lguest_cpuid(unsigned int *ax, unsigned int *bx, *ax &= 0xFFFFF0FF; *ax |= 0x00000500; break; + + /* + * This is used to detect if we're running under KVM. We might be, + * but that's a Host matter, not us. So say we're not. + */ + case KVM_CPUID_SIGNATURE: + *bx = *cx = *dx = 0; + break; + /* * 0x80000000 returns the highest Extended Function, so we futureproof * like we do above by limiting it to known fields. -- cgit v1.2.3-18-g5258