6093637b4d
Some Windows versions crash at boot or fail to enable the VMBus device if they don't see the expected set of Hyper-V features (enlightenments). Since this provides poor user experience let's warn user if the VMBus device is enabled without the recommended set of Hyper-V features. The recommended set is the minimum set of Hyper-V features required to make the VMBus device work properly in Windows Server versions 2016, 2019 and 2022. Acked-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Maciej S. Szmigiero <maciej.szmigiero@oracle.com>
59 lines
1.2 KiB
C
59 lines
1.2 KiB
C
/*
|
|
* Stubs for CONFIG_HYPERV=n
|
|
*
|
|
* Copyright (c) 2015-2018 Virtuozzo International GmbH.
|
|
*
|
|
* This work is licensed under the terms of the GNU GPL, version 2 or later.
|
|
* See the COPYING file in the top-level directory.
|
|
*/
|
|
|
|
#include "qemu/osdep.h"
|
|
#include "hyperv.h"
|
|
|
|
#ifdef CONFIG_KVM
|
|
int kvm_hv_handle_exit(X86CPU *cpu, struct kvm_hyperv_exit *exit)
|
|
{
|
|
switch (exit->type) {
|
|
case KVM_EXIT_HYPERV_SYNIC:
|
|
if (!hyperv_feat_enabled(cpu, HYPERV_FEAT_SYNIC)) {
|
|
return -1;
|
|
}
|
|
|
|
/*
|
|
* Tracking the changes in the MSRs is unnecessary as there are no
|
|
* users for them beside save/load, which is handled nicely by the
|
|
* generic MSR save/load code
|
|
*/
|
|
return 0;
|
|
case KVM_EXIT_HYPERV_HCALL:
|
|
exit->u.hcall.result = HV_STATUS_INVALID_HYPERCALL_CODE;
|
|
return 0;
|
|
case KVM_EXIT_HYPERV_SYNDBG:
|
|
if (!hyperv_feat_enabled(cpu, HYPERV_FEAT_SYNDBG)) {
|
|
return -1;
|
|
}
|
|
|
|
return 0;
|
|
default:
|
|
return -1;
|
|
}
|
|
}
|
|
#endif
|
|
|
|
int hyperv_x86_synic_add(X86CPU *cpu)
|
|
{
|
|
return -ENOSYS;
|
|
}
|
|
|
|
void hyperv_x86_synic_reset(X86CPU *cpu)
|
|
{
|
|
}
|
|
|
|
void hyperv_x86_synic_update(X86CPU *cpu)
|
|
{
|
|
}
|
|
|
|
void hyperv_x86_set_vmbus_recommended_features_enabled(void)
|
|
{
|
|
}
|