* [Qemu-devel] [PATCH] kvm: do not force hypervisor flag in guest`s CPUID
[not found] <1429788803-7964-1-git-send-email-yarmak.vladislav@gmail.com>
@ 2015-04-23 11:33 ` Vladislav Yarmak
0 siblings, 0 replies; only message in thread
From: Vladislav Yarmak @ 2015-04-23 11:33 UTC (permalink / raw)
To: qemu-devel; +Cc: Vladislav Yarmak
Do not force hypervisor flag in guests` CPUID - let invoker decide this. It is needed for hidding hypervisor from guest and aimed to run Hyper-V nested in KVM.
Signed-off-by: Vladislav A Yarmak <yarmak.vladislav@gmail.com>
---
target-i386/kvm.c | 4 ----
1 file changed, 4 deletions(-)
diff --git a/target-i386/kvm.c b/target-i386/kvm.c
index 41d09e5..63026cc 100644
--- a/target-i386/kvm.c
+++ b/target-i386/kvm.c
@@ -213,10 +213,6 @@ uint32_t kvm_arch_get_supported_cpuid(KVMState *s, uint32_t function,
/* KVM before 2.6.30 misreports the following features */
ret |= CPUID_MTRR | CPUID_PAT | CPUID_MCE | CPUID_MCA;
} else if (function == 1 && reg == R_ECX) {
- /* We can set the hypervisor flag, even if KVM does not return it on
- * GET_SUPPORTED_CPUID
- */
- ret |= CPUID_EXT_HYPERVISOR;
/* tsc-deadline flag is not returned by GET_SUPPORTED_CPUID, but it
* can be enabled if the kernel has KVM_CAP_TSC_DEADLINE_TIMER,
* and the irqchip is in the kernel.
--
2.1.4
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2015-04-23 11:33 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1429788803-7964-1-git-send-email-yarmak.vladislav@gmail.com>
2015-04-23 11:33 ` [Qemu-devel] [PATCH] kvm: do not force hypervisor flag in guest`s CPUID Vladislav Yarmak
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).