[PATCH] Don't try to mess with CPUID when running nested SVM

When using nested SVM we usually want the guest to see the exact CPUID values we gave it and not some mangled ones. Hyper-V for example doesn't even start when the hypervisor present bit is set. Signed-off-by: Alexander Graf ag...@suse.de --- target-i386/helper.c |4 ++-- 1 files changed, 2

Re: [PATCH] Don't try to mess with CPUID when running nested SVM

Alexander Graf wrote: When using nested SVM we usually want the guest to see the exact CPUID values we gave it and not some mangled ones. That would triggered by -cpu host, not nesting. @@ -1506,7 +1506,7 @@ void cpu_x86_cpuid(CPUX86State *env, uint32_t index, uint32_t count,

Re: [PATCH] Don't try to mess with CPUID when running nested SVM

On 15.05.2009, at 13:09, Avi Kivity wrote: Alexander Graf wrote: When using nested SVM we usually want the guest to see the exact CPUID values we gave it and not some mangled ones. That would triggered by -cpu host, not nesting. Oh we have -cpu host already? If so, we don't need that

Re: [PATCH] Don't try to mess with CPUID when running nested SVM

Alexander Graf wrote: When using nested SVM we usually want the guest to see the exact CPUID values we gave it and not some mangled ones. That would triggered by -cpu host, not nesting. Oh we have -cpu host already? No, we don't :) hm - treating the hypervisor bit like any other cpuid