Enable notify VM exit
v6 cover Enable notify VM exit
Notify VM exit is introduced to mitigate the potential DOS attach from malicious VM. This series is the userspace part to enable this feature through a new KVM capability KVM_CAP_X86_NOTIFY_VMEXIT. The detailed info can be seen in Patch 3.
The corresponding KVM support can be found in linux 6.0-rc1:
(2f4073e08f4c KVM: VMX: Enable Notify VM exit)
This patch set depends on some definition which can be updated from scripts/update-linux-headers.sh. A separate patch set is sent out at
https://lists.gnu.org/archive/html/qemu-devel/2022-09/msg02102.html
---
Change logs:
v5 -> v6
- Add some info related to the valid range of notify_window in patch 2. (Peter Xu)
- Add the doc in qemu-options.hx. (Peter Xu)
- v5: https://lore.kernel.org/qemu-devel/[email protected]/
v4 -> v5
- Remove the assert check to avoid the nop in NDEBUG case. (Yuan)
- v4: https://lore.kernel.org/qemu-devel/[email protected]/
v3 -> v4
- Add a new KVM cap KVM_CAP_TRIPLE_FAULT_EVENT to guard the extension of triple fault event save&restore.
- v3: https://lore.kernel.org/qemu-devel/[email protected]/
v2 -> v3
- Extend the argument to include both the notify window and some flags when enabling KVM_CAP_X86_BUS_LOCK_EXIT CAP.
- Change to use KVM_VCPUEVENTS_VALID_TRIPLE_FAULT in flags field and add pending_triple_fault field in struct kvm_vcpu_events.
- v2: https://lore.kernel.org/qemu-devel/[email protected]/
v1 -> v2
- Add some commit message to explain why we disable Notify VM exit by default.
- Rename KVM_VCPUEVENT_SHUTDOWN to KVM_VCPUEVENT_TRIPLE_FAULT.
- Do the corresponding change to use the KVM_VCPUEVENTS_TRIPLE_FAULT
to save/restore the triple fault event to avoid lose some synthesized triple fault from KVM.
- v1: https://lore.kernel.org/qemu-devel/[email protected]/
---
Chenyi Qiang (2):
i386: kvm: extend kvm_{get, put}_vcpu_events to support pending triple
fault
i386: Add notify VM exit support
hw/i386/x86.c | 45 ++++++++++++++++++++++++++++++++++++++++ include/hw/i386/x86.h | 5 +++++ qemu-options.hx | 10 ++++++++- target/i386/cpu.c | 1 + target/i386/cpu.h | 1 + target/i386/kvm/kvm.c | 48 +++++++++++++++++++++++++++++++++++++++++++ 6 files changed, 109 insertions(+), 1 deletion(-)
Signature · 1 line
2.17.1
PATCH v6 1/2 i386: kvm: extend kvm_{get, put}_vcpu_events to support pending triple fault
For the direct triple faults, i.e. hardware detected and KVM morphed to VM-Exit, KVM will never lose them. But for triple faults sythesized by KVM, e.g. the RSM path, if KVM exits to userspace before the request is serviced, userspace could migrate the VM and lose the triple fault.
A new flag KVM_VCPUEVENT_VALID_TRIPLE_FAULT is defined to signal that the event.triple_fault_pending field contains a valid state if the KVM_CAP_X86_TRIPLE_FAULT_EVENT capability is enabled.
--- target/i386/cpu.c | 1 + target/i386/cpu.h | 1 + target/i386/kvm/kvm.c | 20 ++++++++++++++++++++ 3 files changed, 22 insertions(+)
target/i386/cpu.c +1 -0
@@ -6017,6 +6017,7 @@ static void x86_cpu_reset(DeviceState *dev) env->exception_has_payload = false; env->exception_payload =0 ; env->nmi_injected = false; + env->triple_fault_pending = false;#if !defined(CONFIG_USER_ONLY )/* We hard-wire the BSP to the first CPU. */ apic_designate_bsp (cpu->apic_state, s->cpu_index ==0 );
target/i386/cpu.h +1 -0
@@ -1739,6 +1739,7 @@ typedef struct CPUArchState {uint8_t has_error_code;uint8_t exception_has_payload;uint64_t exception_payload; +bool triple_fault_pending;uint32_t ins_len;uint32_t sipi_vector;bool tsc_valid;
target/i386/kvm/kvm.c +20 -0
@@ -132,6 +132,7 @@ static int has_xcrs;static int has_pit_state2;static int has_sregs2;static int has_exception_payload; +static int has_triple_fault_event;static bool has_msr_mcg_ext_ctl;
@@ -2483,6 +2484,16 @@ int kvm_arch_init(MachineState *ms, KVMState *s) } } + has_triple_fault_event =kvm_check_extension (s,KVM_CAP_X86_TRIPLE_FAULT_EVENT ); +if (has_triple_fault_event) { + ret =kvm_vm_enable_cap (s,KVM_CAP_X86_TRIPLE_FAULT_EVENT ,0 , true); +if (ret <0 ) { +error_report ("kvm: Failed to enable triple fault event cap: %s" , +strerror (-ret)); +return ret; + } + } + ret =kvm_get_supported_msrs (s);if (ret <0 ) {return ret;
@@ -4299,6 +4310,11 @@ static int kvm_put_vcpu_events(X86CPU *cpu, int level) } } +if (has_triple_fault_event) { + events.flags |=KVM_VCPUEVENT_VALID_TRIPLE_FAULT ; + events.triple_fault.pending = env->triple_fault_pending; + } +return kvm_vcpu_ioctl (CPU (cpu),KVM_SET_VCPU_EVENTS , &events); }
@@ -4368,6 +4384,10 @@ static int kvm_get_vcpu_events(X86CPU *cpu) } } +if (events.flags &KVM_VCPUEVENT_VALID_TRIPLE_FAULT ) { + env->triple_fault_pending = events.triple_fault.pending; + } + env->sipi_vector = events.sipi_vector;return 0 ;
Signature · 1 line
2.17.1
PATCH v6 2/2 i386: Add notify VM exit support
In reply to Chenyi QiangThere are cases that malicious virtual machine can cause CPU stuck (due to event windows don't open up), e.g., infinite loop in microcode when nested #AC (CVE-2015-5307). No event window means no event (NMI, SMI and IRQ) can be delivered. It leads the CPU to be unavailable to host or other VMs. Notify VM exit is introduced to mitigate such kind of attacks, which will generate a VM exit if no event window occurs in VM non-root mode for a specified amount of time (notify window).
A new KVM capability KVM_CAP_X86_NOTIFY_VMEXIT is exposed to user space so that the user can query the capability and set the expected notify window when creating VMs. The format of the argument when enabling this capability is as follows:
Bit 63:32 - notify window specified in qemu command
Bit 31:0 - some flags (e.g. KVM_X86_NOTIFY_VMEXIT_ENABLED is set to
enable the feature.)
Because there are some concerns, e.g. a notify VM exit may happen with VM_CONTEXT_INVALID set in exit qualification (no cases are anticipated that would set this bit), which means VM context is corrupted. To avoid the false positive and a well-behaved guest gets killed, make this feature disabled by default. Users can enable the feature by a new machine property:
qemu -machine notify_vmexit=on,notify_window=0 ...
Note that notify_window is only valid when notify_vmexit is on. The valid range of notify_window is non-negative. It is even safe to set it to zero since there's an internal hardware threshold to be added to ensure no false positive.
A new KVM exit reason KVM_EXIT_NOTIFY is defined for notify VM exit. If it happens with VM_INVALID_CONTEXT, hypervisor exits to user space to inform the fatal case. Then user space can inject a SHUTDOWN event to the target vcpu. This is implemented by injecting a sythesized triple fault event.
--- hw/i386/x86.c | 45 +++++++++++++++++++++++++++++++++++++++++++ include/hw/i386/x86.h | 5 +++++ qemu-options.hx | 10 +++++++++- target/i386/kvm/kvm.c | 28 +++++++++++++++++++++++++++ 4 files changed, 87 insertions(+), 1 deletion(-)
hw/i386/x86.c +45 -0
@@ -1379,6 +1379,37 @@ static void machine_set_sgx_epc(Object *obj, Visitor *v, const char *name,qapi_free_SgxEPCList (list); } +static bool x86_machine_get_notify_vmexit (Object *obj,Error **errp) +{ +X86MachineState *x86ms =X86_MACHINE (obj); + +return x86ms->notify_vmexit; +} + +static void x86_machine_set_notify_vmexit (Object *obj,bool value,Error **errp) +{ +X86MachineState *x86ms =X86_MACHINE (obj); + + x86ms->notify_vmexit = value; +} + +static void x86_machine_get_notify_window (Object *obj,Visitor *v, +const char *name,void *opaque,Error **errp) +{ +X86MachineState *x86ms =X86_MACHINE (obj); +uint32_t notify_window = x86ms->notify_window; + +visit_type_uint32 (v, name, ¬ify_window, errp); +} + +static void x86_machine_set_notify_window (Object *obj,Visitor *v, +const char *name,void *opaque,Error **errp) +{ +X86MachineState *x86ms =X86_MACHINE (obj); + +visit_type_uint32 (v, name, &x86ms->notify_window, errp); +} +static void x86_machine_initfn (Object *obj) {X86MachineState *x86ms =X86_MACHINE (obj);
@@ -1392,6 +1423,8 @@ static void x86_machine_initfn(Object *obj) x86ms->oem_table_id =g_strndup (ACPI_BUILD_APPNAME8 ,8 ); x86ms->bus_lock_ratelimit =0 ; x86ms->above_4g_mem_start =4 * GiB; + x86ms->notify_vmexit = false; + x86ms->notify_window =0 ; }static void x86_machine_class_init (ObjectClass *oc,void *data)
@@ -1461,6 +1494,18 @@ static void x86_machine_class_init(ObjectClass *oc, void *data) NULL, NULL);object_class_property_set_description (oc,"sgx-epc" ,"SGX EPC device" ); + +object_class_property_add (oc,X86_MACHINE_NOTIFY_WINDOW ,"uint32_t" , + x86_machine_get_notify_window, + x86_machine_set_notify_window,NULL ,NULL ); +object_class_property_set_description (oc,X86_MACHINE_NOTIFY_WINDOW , +"Set the notify window required by notify VM exit" ); + +object_class_property_add_bool (oc,X86_MACHINE_NOTIFY_VMEXIT , + x86_machine_get_notify_vmexit, + x86_machine_set_notify_vmexit); +object_class_property_set_description (oc,X86_MACHINE_NOTIFY_VMEXIT , +"Enable notify VM exit" ); }static const TypeInfo x86_machine_info = {
include/hw/i386/x86.h +5 -0
@@ -85,6 +85,9 @@ struct X86MachineState {* which means no limitation on the guest's bus locks. */ uint64_t bus_lock_ratelimit; + +bool notify_vmexit; +uint32_t notify_window; };#define X86_MACHINE_SMM "smm"
@@ -94,6 +97,8 @@ struct X86MachineState {#define X86_MACHINE_OEM_ID "x-oem-id"#define X86_MACHINE_OEM_TABLE_ID "x-oem-table-id"#define X86_MACHINE_BUS_LOCK_RATELIMIT "bus-lock-ratelimit" +#define X86_MACHINE_NOTIFY_VMEXIT "notify-vmexit" +#define X86_MACHINE_NOTIFY_WINDOW "notify-window"#define TYPE_X86_MACHINE MACHINE_TYPE_NAME("x86")OBJECT_DECLARE_TYPE (X86MachineState, X86MachineClass,X86_MACHINE )
qemu-options.hx +9 -1
@@ -37,7 +37,8 @@ DEF("machine", HAS_ARG, QEMU_OPTION_machine, \ " memory-encryption=@var{} memory encryption object to use (default=none)\n" " hmat=on|off controls ACPI HMAT support (default=off)\n" " memory-backend='backend-id' specifies explicitly provided backend for main RAM (default=none)\n" - " cxl-fmw.0.targets.0=firsttarget,cxl-fmw.0.targets.1=secondtarget,cxl-fmw.0.size=size[,cxl-fmw.0.interleave-granularity=granularity]\n", + " cxl-fmw.0.targets.0=firsttarget,cxl-fmw.0.targets.1=secondtarget,cxl-fmw.0.size=size[,cxl-fmw.0.interleave-granularity=granularity]\n" + " notify_vmexit=on|off,notify_window=n controls notify VM exit support (default=off) and specifies the notify window size (default=0)\n", QEMU_ARCH_ALL) SRST ``-machine [type=]name[,prop=value[,...]]``
@@ -157,6 +158,13 @@ SRST :: -machine cxl-fmw.0.targets.0=cxl.0,cxl-fmw.0.targets.1=cxl.1,cxl-fmw.0.size=128G,cxl-fmw.0.interleave-granularity=512k + + ``notify_vmexit=on|off,notify_window=n`` + Enables or disables Notify VM exit support on x86 host and specify + the corresponding notify window to trigger the VM exit if enabled. + This feature can mitigate the CPU stuck issue due to event windows + don't open up for a specified of time (notify window). + The default is off. ERST DEF("M", HAS_ARG, QEMU_OPTION_M,
target/i386/kvm/kvm.c +28 -0
@@ -2597,6 +2597,20 @@ int kvm_arch_init(MachineState *ms, KVMState *s)ratelimit_set_speed (&bus_lock_ratelimit_ctrl, x86ms->bus_lock_ratelimit,BUS_LOCK_SLICE_TIME ); } + +if (x86ms->notify_vmexit && +kvm_check_extension (s,KVM_CAP_X86_NOTIFY_VMEXIT )) { +uint64_t notify_window_flags = ((uint64_t )x86ms->notify_window <<32 ) | +KVM_X86_NOTIFY_VMEXIT_ENABLED | +KVM_X86_NOTIFY_VMEXIT_USER ; + ret =kvm_vm_enable_cap (s,KVM_CAP_X86_NOTIFY_VMEXIT ,0 , + notify_window_flags); +if (ret <0 ) { +error_report ("kvm: Failed to enable notify vmexit cap: %s" , +strerror (-ret)); +return ret; + } + } }return 0 ;
@@ -5141,6 +5155,7 @@ int kvm_arch_handle_exit(CPUState *cs, struct kvm_run *run)X86CPU *cpu =X86_CPU (cs);uint64_t code;int ret; +struct kvm_vcpu_events events = {};switch (run->exit_reason) {case KVM_EXIT_HLT :
@@ -5196,6 +5211,19 @@ int kvm_arch_handle_exit(CPUState *cs, struct kvm_run *run)/* already handled in kvm_arch_post_run */ ret =0 ;break ; +case KVM_EXIT_NOTIFY : + ret =0 ; +if (run->notify.flags &KVM_NOTIFY_CONTEXT_INVALID ) { +warn_report ("KVM: invalid context due to notify vmexit" ); +if (has_triple_fault_event) { + events.flags |=KVM_VCPUEVENT_VALID_TRIPLE_FAULT ; + events.triple_fault.pending = true; + ret =kvm_vcpu_ioctl (cs,KVM_SET_VCPU_EVENTS , &events); + }else { + ret =-1 ; + } + } +break ;default :fprintf (stderr,"KVM: unknown exit reason %d\n" , run->exit_reason); ret =-1 ;
Signature · 1 line
2.17.1
Re: [PATCH v6 2/2] i386: Add notify VM exit support
Quoted 169 lines · Chenyi Qiang
There are cases that malicious virtual machine can cause CPU stuck (due to event windows don't open up), e.g., infinite loop in microcode when nested #AC (CVE-2015-5307). No event window means no event (NMI, SMI and IRQ) can be delivered. It leads the CPU to be unavailable to host or other VMs. Notify VM exit is introduced to mitigate such kind of attacks, which will generate a VM exit if no event window occurs in VM non-root mode for a specified amount of time (notify window).
A new KVM capability
KVM_CAP_X86_NOTIFY_VMEXITis exposed to user space so that the user can query the capability and set the expected notify window when creating VMs. The format of the argument when enabling this capability is as follows:
Bit 63:32 - notify window specified in qemu command
Bit 31:0 - some flags (e.g.KVM_X86_NOTIFY_VMEXIT_ENABLEDis set to
enable the feature.)Because there are some concerns, e.g. a notify VM exit may happen with
VM_CONTEXT_INVALIDset in exit qualification (no cases are anticipated that would set this bit), which means VM context is corrupted. To avoid the false positive and a well-behaved guest gets killed, make this feature disabled by default. Users can enable the feature by a new machine property:
qemu -machine notify_vmexit=on,notify_window=0 ...Note that
notify_windowis only valid whennotify_vmexitis on. The valid range ofnotify_windowis non-negative. It is even safe to set it to zero since there's an internal hardware threshold to be added to ensure no false positive.A new KVM exit reason
KVM_EXIT_NOTIFYis defined for notify VM exit. If it happens withVM_INVALID_CONTEXT, hypervisor exits to user space to inform the fatal case. Then user space can inject a SHUTDOWN event to the target vcpu. This is implemented by injecting a sythesized triple fault event.Signed-off-by Chenyi Qiang <[email protected]>--- hw/i386/x86.c | 45 +++++++++++++++++++++++++++++++++++++++++++ include/hw/i386/x86.h | 5 +++++ qemu-options.hx | 10 +++++++++- target/i386/kvm/kvm.c | 28 +++++++++++++++++++++++++++ 4 files changed, 87 insertions(+), 1 deletion(-)hw/i386/x86.c +45
-0@@ -1379,6 +1379,37 @@ static void machine_set_sgx_epc(Object *obj, Visitor *v, const char *name,qapi_free_SgxEPCList (list); } +static bool x86_machine_get_notify_vmexit (Object *obj,Error **errp) +{ +X86MachineState *x86ms =X86_MACHINE (obj); + +return x86ms->notify_vmexit; +} + +static void x86_machine_set_notify_vmexit (Object *obj,bool value,Error **errp) +{ +X86MachineState *x86ms =X86_MACHINE (obj); + + x86ms->notify_vmexit = value; +} + +static void x86_machine_get_notify_window (Object *obj,Visitor *v, +const char *name,void *opaque,Error **errp) +{ +X86MachineState *x86ms =X86_MACHINE (obj); +uint32_t notify_window = x86ms->notify_window; + +visit_type_uint32 (v, name, ¬ify_window, errp); +} + +static void x86_machine_set_notify_window (Object *obj,Visitor *v, +const char *name,void *opaque,Error **errp) +{ +X86MachineState *x86ms =X86_MACHINE (obj); + +visit_type_uint32 (v, name, &x86ms->notify_window, errp); +} +static void x86_machine_initfn (Object *obj) {X86MachineState *x86ms =X86_MACHINE (obj);@@ -1392,6 +1423,8 @@ static void x86_machine_initfn(Object *obj) x86ms->oem_table_id =g_strndup (ACPI_BUILD_APPNAME8 ,8 ); x86ms->bus_lock_ratelimit =0 ; x86ms->above_4g_mem_start =4 * GiB; + x86ms->notify_vmexit = false; + x86ms->notify_window =0 ; }static void x86_machine_class_init (ObjectClass *oc,void *data)@@ -1461,6 +1494,18 @@ static void x86_machine_class_init(ObjectClass *oc, void *data) NULL, NULL);object_class_property_set_description (oc,"sgx-epc" ,"SGX EPC device" ); + +object_class_property_add (oc,X86_MACHINE_NOTIFY_WINDOW ,"uint32_t" , + x86_machine_get_notify_window, + x86_machine_set_notify_window,NULL ,NULL ); +object_class_property_set_description (oc,X86_MACHINE_NOTIFY_WINDOW , +"Set the notify window required by notify VM exit" ); + +object_class_property_add_bool (oc,X86_MACHINE_NOTIFY_VMEXIT , + x86_machine_get_notify_vmexit, + x86_machine_set_notify_vmexit); +object_class_property_set_description (oc,X86_MACHINE_NOTIFY_VMEXIT , +"Enable notify VM exit" ); }static const TypeInfo x86_machine_info = {include/hw/i386/x86.h +5
-0@@ -85,6 +85,9 @@ struct X86MachineState {* which means no limitation on the guest's bus locks. */ uint64_t bus_lock_ratelimit; + +bool notify_vmexit; +uint32_t notify_window; };#define X86_MACHINE_SMM "smm"@@ -94,6 +97,8 @@ struct X86MachineState {#define X86_MACHINE_OEM_ID "x-oem-id"#define X86_MACHINE_OEM_TABLE_ID "x-oem-table-id"#define X86_MACHINE_BUS_LOCK_RATELIMIT "bus-lock-ratelimit" +#define X86_MACHINE_NOTIFY_VMEXIT "notify-vmexit" +#define X86_MACHINE_NOTIFY_WINDOW "notify-window"#define TYPE_X86_MACHINE MACHINE_TYPE_NAME("x86")OBJECT_DECLARE_TYPE (X86MachineState, X86MachineClass,X86_MACHINE )qemu-options.hx +9
-1@@ -37,7 +37,8 @@ DEF("machine", HAS_ARG, QEMU_OPTION_machine, \ " memory-encryption=@var{} memory encryption object to use (default=none)\n" " hmat=on|off controls ACPI HMAT support (default=off)\n" " memory-backend='backend-id' specifies explicitly provided backend for main RAM (default=none)\n" - " cxl-fmw.0.targets.0=firsttarget,cxl-fmw.0.targets.1=secondtarget,cxl-fmw.0.size=size[,cxl-fmw.0.interleave-granularity=granularity]\n", + " cxl-fmw.0.targets.0=firsttarget,cxl-fmw.0.targets.1=secondtarget,cxl-fmw.0.size=size[,cxl-fmw.0.interleave-granularity=granularity]\n" + " notify_vmexit=on|off,notify_window=n controls notify VM exit support (default=off) and specifies the notify window size (default=0)\n", QEMU_ARCH_ALL) SRST ``-machine [type=]name[,prop=value[,...]]``@@ -157,6 +158,13 @@ SRST :: -machine cxl-fmw.0.targets.0=cxl.0,cxl-fmw.0.targets.1=cxl.1,cxl-fmw.0.size=128G,cxl-fmw.0.interleave-granularity=512k + + ``notify_vmexit=on|off,notify_window=n`` + Enables or disables Notify VM exit support on x86 host and specify + the corresponding notify window to trigger the VM exit if enabled. + This feature can mitigate the CPU stuck issue due to event windows + don't open up for a specified of time (notify window). + The default is off. ERST DEF("M", HAS_ARG, QEMU_OPTION_M,target/i386/kvm/kvm.c +0
-0
target/i386/kvm/kvm.c int kvm_arch_init(MachineState *ms, KVMState *s) · line 2605
Quoted 9 lines
target/i386/kvm/kvm.c +6
-0@@ -2597,6 +2597,20 @@ int kvm_arch_init(MachineState *ms, KVMState *s)ratelimit_set_speed (&bus_lock_ratelimit_ctrl, x86ms->bus_lock_ratelimit,BUS_LOCK_SLICE_TIME ); } + +if (x86ms->notify_vmexit && +kvm_check_extension (s,KVM_CAP_X86_NOTIFY_VMEXIT )) { +uint64_t notify_window_flags = ((uint64_t )x86ms->notify_window <<32 ) | +KVM_X86_NOTIFY_VMEXIT_ENABLED | +KVM_X86_NOTIFY_VMEXIT_USER ;
It'll always request a user exit here as long as enabled, then...
Quoted 25 lines
target/i386/kvm/kvm.c +11
-0+ ret =kvm_vm_enable_cap (s,KVM_CAP_X86_NOTIFY_VMEXIT ,0 , + notify_window_flags); +if (ret <0 ) { +error_report ("kvm: Failed to enable notify vmexit cap: %s" , +strerror (-ret)); +return ret; + } + } }return 0 ;@@ -5141,6 +5155,7 @@ int kvm_arch_handle_exit(CPUState *cs, struct kvm_run *run)X86CPU *cpu =X86_CPU (cs);uint64_t code;int ret; +struct kvm_vcpu_events events = {};switch (run->exit_reason) {case KVM_EXIT_HLT :@@ -5196,6 +5211,19 @@ int kvm_arch_handle_exit(CPUState *cs, struct kvm_run *run)/* already handled in kvm_arch_post_run */ ret =0 ;break ; +case KVM_EXIT_NOTIFY : + ret =0 ;
target/i386/kvm/kvm.c int kvm_arch_handle_exit(CPUState *cs, struct kvm_run *run) · line 5225
Quoted 10 lines
target/i386/kvm/kvm.c +10
-0+if (run->notify.flags &KVM_NOTIFY_CONTEXT_INVALID ) { +warn_report ("KVM: invalid context due to notify vmexit" ); +if (has_triple_fault_event) { + events.flags |=KVM_VCPUEVENT_VALID_TRIPLE_FAULT ; + events.triple_fault.pending = true; + ret =kvm_vcpu_ioctl (cs,KVM_SET_VCPU_EVENTS , &events); + }else { + ret =-1 ; + } + }
... should we do something even if the context is valid? Or I'm a bit confused why KVM_X86_NOTIFY_VMEXIT_USER was set (IIUC we can just enable it without setting VMEXIT_USER then).
Not sure some warning would be also useful here, but I really don't know the whole context so I can't tell whether there can easily be false positives to pollute qemu log.
Quoted 7 lines
target/i386/kvm/kvm.c +1
-0+break ;default :fprintf (stderr,"KVM: unknown exit reason %d\n" , run->exit_reason); ret =-1 ;Signature · 1 line
2.17.1
Signature · 1 line
Peter Xu
Re: [PATCH v6 2/2] i386: Add notify VM exit support
Quoted 211 lines · Peter Xu
Quoted 169 lines · Chenyi Qiang
There are cases that malicious virtual machine can cause CPU stuck (due to event windows don't open up), e.g., infinite loop in microcode when nested #AC (CVE-2015-5307). No event window means no event (NMI, SMI and IRQ) can be delivered. It leads the CPU to be unavailable to host or other VMs. Notify VM exit is introduced to mitigate such kind of attacks, which will generate a VM exit if no event window occurs in VM non-root mode for a specified amount of time (notify window).
A new KVM capability
KVM_CAP_X86_NOTIFY_VMEXITis exposed to user space so that the user can query the capability and set the expected notify window when creating VMs. The format of the argument when enabling this capability is as follows:
Bit 63:32 - notify window specified in qemu command
Bit 31:0 - some flags (e.g.KVM_X86_NOTIFY_VMEXIT_ENABLEDis set to
enable the feature.)Because there are some concerns, e.g. a notify VM exit may happen with
VM_CONTEXT_INVALIDset in exit qualification (no cases are anticipated that would set this bit), which means VM context is corrupted. To avoid the false positive and a well-behaved guest gets killed, make this feature disabled by default. Users can enable the feature by a new machine property:
qemu -machine notify_vmexit=on,notify_window=0 ...Note that
notify_windowis only valid whennotify_vmexitis on. The valid range ofnotify_windowis non-negative. It is even safe to set it to zero since there's an internal hardware threshold to be added to ensure no false positive.A new KVM exit reason
KVM_EXIT_NOTIFYis defined for notify VM exit. If it happens withVM_INVALID_CONTEXT, hypervisor exits to user space to inform the fatal case. Then user space can inject a SHUTDOWN event to the target vcpu. This is implemented by injecting a sythesized triple fault event.Signed-off-by Chenyi Qiang <[email protected]>--- hw/i386/x86.c | 45 +++++++++++++++++++++++++++++++++++++++++++ include/hw/i386/x86.h | 5 +++++ qemu-options.hx | 10 +++++++++- target/i386/kvm/kvm.c | 28 +++++++++++++++++++++++++++ 4 files changed, 87 insertions(+), 1 deletion(-)hw/i386/x86.c +45
-0@@ -1379,6 +1379,37 @@ static void machine_set_sgx_epc(Object *obj, Visitor *v, const char *name,qapi_free_SgxEPCList (list); } +static bool x86_machine_get_notify_vmexit (Object *obj,Error **errp) +{ +X86MachineState *x86ms =X86_MACHINE (obj); + +return x86ms->notify_vmexit; +} + +static void x86_machine_set_notify_vmexit (Object *obj,bool value,Error **errp) +{ +X86MachineState *x86ms =X86_MACHINE (obj); + + x86ms->notify_vmexit = value; +} + +static void x86_machine_get_notify_window (Object *obj,Visitor *v, +const char *name,void *opaque,Error **errp) +{ +X86MachineState *x86ms =X86_MACHINE (obj); +uint32_t notify_window = x86ms->notify_window; + +visit_type_uint32 (v, name, ¬ify_window, errp); +} + +static void x86_machine_set_notify_window (Object *obj,Visitor *v, +const char *name,void *opaque,Error **errp) +{ +X86MachineState *x86ms =X86_MACHINE (obj); + +visit_type_uint32 (v, name, &x86ms->notify_window, errp); +} +static void x86_machine_initfn (Object *obj) {X86MachineState *x86ms =X86_MACHINE (obj);@@ -1392,6 +1423,8 @@ static void x86_machine_initfn(Object *obj) x86ms->oem_table_id =g_strndup (ACPI_BUILD_APPNAME8 ,8 ); x86ms->bus_lock_ratelimit =0 ; x86ms->above_4g_mem_start =4 * GiB; + x86ms->notify_vmexit = false; + x86ms->notify_window =0 ; }static void x86_machine_class_init (ObjectClass *oc,void *data)@@ -1461,6 +1494,18 @@ static void x86_machine_class_init(ObjectClass *oc, void *data) NULL, NULL);object_class_property_set_description (oc,"sgx-epc" ,"SGX EPC device" ); + +object_class_property_add (oc,X86_MACHINE_NOTIFY_WINDOW ,"uint32_t" , + x86_machine_get_notify_window, + x86_machine_set_notify_window,NULL ,NULL ); +object_class_property_set_description (oc,X86_MACHINE_NOTIFY_WINDOW , +"Set the notify window required by notify VM exit" ); + +object_class_property_add_bool (oc,X86_MACHINE_NOTIFY_VMEXIT , + x86_machine_get_notify_vmexit, + x86_machine_set_notify_vmexit); +object_class_property_set_description (oc,X86_MACHINE_NOTIFY_VMEXIT , +"Enable notify VM exit" ); }static const TypeInfo x86_machine_info = {include/hw/i386/x86.h +5
-0@@ -85,6 +85,9 @@ struct X86MachineState {* which means no limitation on the guest's bus locks. */ uint64_t bus_lock_ratelimit; + +bool notify_vmexit; +uint32_t notify_window; };#define X86_MACHINE_SMM "smm"@@ -94,6 +97,8 @@ struct X86MachineState {#define X86_MACHINE_OEM_ID "x-oem-id"#define X86_MACHINE_OEM_TABLE_ID "x-oem-table-id"#define X86_MACHINE_BUS_LOCK_RATELIMIT "bus-lock-ratelimit" +#define X86_MACHINE_NOTIFY_VMEXIT "notify-vmexit" +#define X86_MACHINE_NOTIFY_WINDOW "notify-window"#define TYPE_X86_MACHINE MACHINE_TYPE_NAME("x86")OBJECT_DECLARE_TYPE (X86MachineState, X86MachineClass,X86_MACHINE )qemu-options.hx +9
-1@@ -37,7 +37,8 @@ DEF("machine", HAS_ARG, QEMU_OPTION_machine, \ " memory-encryption=@var{} memory encryption object to use (default=none)\n" " hmat=on|off controls ACPI HMAT support (default=off)\n" " memory-backend='backend-id' specifies explicitly provided backend for main RAM (default=none)\n" - " cxl-fmw.0.targets.0=firsttarget,cxl-fmw.0.targets.1=secondtarget,cxl-fmw.0.size=size[,cxl-fmw.0.interleave-granularity=granularity]\n", + " cxl-fmw.0.targets.0=firsttarget,cxl-fmw.0.targets.1=secondtarget,cxl-fmw.0.size=size[,cxl-fmw.0.interleave-granularity=granularity]\n" + " notify_vmexit=on|off,notify_window=n controls notify VM exit support (default=off) and specifies the notify window size (default=0)\n", QEMU_ARCH_ALL) SRST ``-machine [type=]name[,prop=value[,...]]``@@ -157,6 +158,13 @@ SRST :: -machine cxl-fmw.0.targets.0=cxl.0,cxl-fmw.0.targets.1=cxl.1,cxl-fmw.0.size=128G,cxl-fmw.0.interleave-granularity=512k + + ``notify_vmexit=on|off,notify_window=n`` + Enables or disables Notify VM exit support on x86 host and specify + the corresponding notify window to trigger the VM exit if enabled. + This feature can mitigate the CPU stuck issue due to event windows + don't open up for a specified of time (notify window). + The default is off. ERST DEF("M", HAS_ARG, QEMU_OPTION_M,target/i386/kvm/kvm.c +0
-0target/i386/kvm/kvm.c int kvm_arch_init(MachineState *ms, KVMState *s) · line 2605
Quoted 9 lines
target/i386/kvm/kvm.c +6
-0@@ -2597,6 +2597,20 @@ int kvm_arch_init(MachineState *ms, KVMState *s)ratelimit_set_speed (&bus_lock_ratelimit_ctrl, x86ms->bus_lock_ratelimit,BUS_LOCK_SLICE_TIME ); } + +if (x86ms->notify_vmexit && +kvm_check_extension (s,KVM_CAP_X86_NOTIFY_VMEXIT )) { +uint64_t notify_window_flags = ((uint64_t )x86ms->notify_window <<32 ) | +KVM_X86_NOTIFY_VMEXIT_ENABLED | +KVM_X86_NOTIFY_VMEXIT_USER ;It'll always request a user exit here as long as enabled, then...
Quoted 29 lines
target/i386/kvm/kvm.c +15
-0+ ret =kvm_vm_enable_cap (s,KVM_CAP_X86_NOTIFY_VMEXIT ,0 , + notify_window_flags); +if (ret <0 ) { +error_report ("kvm: Failed to enable notify vmexit cap: %s" , +strerror (-ret)); +return ret; + } + } }return 0 ;@@ -5141,6 +5155,7 @@ int kvm_arch_handle_exit(CPUState *cs, struct kvm_run *run)X86CPU *cpu =X86_CPU (cs);uint64_t code;int ret; +struct kvm_vcpu_events events = {};switch (run->exit_reason) {case KVM_EXIT_HLT :@@ -5196,6 +5211,19 @@ int kvm_arch_handle_exit(CPUState *cs, struct kvm_run *run)/* already handled in kvm_arch_post_run */ ret =0 ;break ; +case KVM_EXIT_NOTIFY : + ret =0 ; +if (run->notify.flags &KVM_NOTIFY_CONTEXT_INVALID ) { +warn_report ("KVM: invalid context due to notify vmexit" ); +if (has_triple_fault_event) { + events.flags |=KVM_VCPUEVENT_VALID_TRIPLE_FAULT ;
Quoted 8 lines
target/i386/kvm/kvm.c int kvm_arch_handle_exit(CPUState *cs, struct kvm_run *run) · line 5225
Quoted 6 lines
target/i386/kvm/kvm.c +6
-0+ events.triple_fault.pending = true; + ret =kvm_vcpu_ioctl (cs,KVM_SET_VCPU_EVENTS , &events); + }else { + ret =-1 ; + } + }... should we do something even if the context is valid? Or I'm a bit
Yes, make sense. A warning log is necessary if the context is valid.
Quoted 3 lines
confused why
KVM_X86_NOTIFY_VMEXIT_USERwas set (IIUC we can just enable it without settingVMEXIT_USERthen).
VMEXIT_USR was set because KVM community prefers userspace can get notified and help to do some analysis or mitigation if notify window was exceeded.
Quoted 4 lines
Not sure some warning would be also useful here, but I really don't know the whole context so I can't tell whether there can easily be false positives to pollute qemu log.
The false positive case is not easy to happen unless some potential issues in silicon. But in case of it, to avoid polluting qemu log, how about:
target/i386/kvm/kvm.c +1 -0
@@ -5213,6 +5213,7 @@ int kvm_arch_handle_exit(CPUState *cs, struct kvm_run *run)break ;case KVM_EXIT_NOTIFY : ret =0 ; +warn_report_once ("KVM: notify window was exceeded in guest" );if (run->notify.flags &KVM_NOTIFY_CONTEXT_INVALID ) {warn_report ("KVM: invalid context due to notify vmexit" );if (has_triple_fault_event) {
Quoted 8 lines
Quoted 7 lines
target/i386/kvm/kvm.c +1
-0+break ;default :fprintf (stderr,"KVM: unknown exit reason %d\n" , run->exit_reason); ret =-1 ;Signature · 1 line
2.17.1
Re: [PATCH v6 2/2] i386: Add notify VM exit support
Quoted 19 lines · Chenyi Qiang
Quoted 4 lines
Not sure some warning would be also useful here, but I really don't know the whole context so I can't tell whether there can easily be false positives to pollute qemu log.
The false positive case is not easy to happen unless some potential issues in silicon. But in case of it, to avoid polluting qemu log, how about:
target/i386/kvm/kvm.c +1
-0@@ -5213,6 +5213,7 @@ int kvm_arch_handle_exit(CPUState *cs, struct kvm_run *run) break; case KVM_EXIT_NOTIFY: ret = 0; + warn_report_once("KVM: notify window was exceeded in guest"); if (run->notify.flags & KVM_NOTIFY_CONTEXT_INVALID) { warn_report("KVM: invalid context due to notify vmexit");
Quoted 1 line
if (
has_triple_fault_event) {
how about this
case KVM_EXIT_NOTIFY:
bool ctx_invalid = run->notify.flags & KVM_NOTIFY_CONTEXT_INVALID;
ret = 0;
warn_report_once("KVM: Encounter notify exit with %svalid context",
ctx_invalid ? "in" : "");
if (ctx_invalid) {
...
}Peter Xu
Acked-byRe: [PATCH v6 2/2] i386: Add notify VM exit support
In reply to Chenyi QiangQuoted 237 lines · Chenyi Qiang
Quoted 202 lines · Peter Xu
Quoted 162 lines · Chenyi Qiang
There are cases that malicious virtual machine can cause CPU stuck (due to event windows don't open up), e.g., infinite loop in microcode when nested #AC (CVE-2015-5307). No event window means no event (NMI, SMI and IRQ) can be delivered. It leads the CPU to be unavailable to host or other VMs. Notify VM exit is introduced to mitigate such kind of attacks, which will generate a VM exit if no event window occurs in VM non-root mode for a specified amount of time (notify window).
A new KVM capability
KVM_CAP_X86_NOTIFY_VMEXITis exposed to user space so that the user can query the capability and set the expected notify window when creating VMs. The format of the argument when enabling this capability is as follows:
Bit 63:32 - notify window specified in qemu command
Bit 31:0 - some flags (e.g.KVM_X86_NOTIFY_VMEXIT_ENABLEDis set to
enable the feature.)Because there are some concerns, e.g. a notify VM exit may happen with
VM_CONTEXT_INVALIDset in exit qualification (no cases are anticipated that would set this bit), which means VM context is corrupted. To avoid the false positive and a well-behaved guest gets killed, make this feature disabled by default. Users can enable the feature by a new machine property:
qemu -machine notify_vmexit=on,notify_window=0 ...Note that
notify_windowis only valid whennotify_vmexitis on. The valid range ofnotify_windowis non-negative. It is even safe to set it to zero since there's an internal hardware threshold to be added to ensure no false positive.A new KVM exit reason
KVM_EXIT_NOTIFYis defined for notify VM exit. If it happens withVM_INVALID_CONTEXT, hypervisor exits to user space to inform the fatal case. Then user space can inject a SHUTDOWN event to the target vcpu. This is implemented by injecting a sythesized triple fault event.Signed-off-by Chenyi Qiang <[email protected]>--- hw/i386/x86.c | 45 +++++++++++++++++++++++++++++++++++++++++++ include/hw/i386/x86.h | 5 +++++ qemu-options.hx | 10 +++++++++- target/i386/kvm/kvm.c | 28 +++++++++++++++++++++++++++ 4 files changed, 87 insertions(+), 1 deletion(-)hw/i386/x86.c +45
-0@@ -1379,6 +1379,37 @@ static void machine_set_sgx_epc(Object *obj, Visitor *v, const char *name,qapi_free_SgxEPCList (list); } +static bool x86_machine_get_notify_vmexit (Object *obj,Error **errp) +{ +X86MachineState *x86ms =X86_MACHINE (obj); + +return x86ms->notify_vmexit; +} + +static void x86_machine_set_notify_vmexit (Object *obj,bool value,Error **errp) +{ +X86MachineState *x86ms =X86_MACHINE (obj); + + x86ms->notify_vmexit = value; +} + +static void x86_machine_get_notify_window (Object *obj,Visitor *v, +const char *name,void *opaque,Error **errp) +{ +X86MachineState *x86ms =X86_MACHINE (obj); +uint32_t notify_window = x86ms->notify_window; + +visit_type_uint32 (v, name, ¬ify_window, errp); +} + +static void x86_machine_set_notify_window (Object *obj,Visitor *v, +const char *name,void *opaque,Error **errp) +{ +X86MachineState *x86ms =X86_MACHINE (obj); + +visit_type_uint32 (v, name, &x86ms->notify_window, errp); +} +static void x86_machine_initfn (Object *obj) {X86MachineState *x86ms =X86_MACHINE (obj);@@ -1392,6 +1423,8 @@ static void x86_machine_initfn(Object *obj) x86ms->oem_table_id =g_strndup (ACPI_BUILD_APPNAME8 ,8 ); x86ms->bus_lock_ratelimit =0 ; x86ms->above_4g_mem_start =4 * GiB; + x86ms->notify_vmexit = false; + x86ms->notify_window =0 ; }static void x86_machine_class_init (ObjectClass *oc,void *data)@@ -1461,6 +1494,18 @@ static void x86_machine_class_init(ObjectClass *oc, void *data) NULL, NULL);object_class_property_set_description (oc,"sgx-epc" ,"SGX EPC device" ); + +object_class_property_add (oc,X86_MACHINE_NOTIFY_WINDOW ,"uint32_t" , + x86_machine_get_notify_window, + x86_machine_set_notify_window,NULL ,NULL ); +object_class_property_set_description (oc,X86_MACHINE_NOTIFY_WINDOW , +"Set the notify window required by notify VM exit" ); + +object_class_property_add_bool (oc,X86_MACHINE_NOTIFY_VMEXIT , + x86_machine_get_notify_vmexit, + x86_machine_set_notify_vmexit); +object_class_property_set_description (oc,X86_MACHINE_NOTIFY_VMEXIT , +"Enable notify VM exit" ); }static const TypeInfo x86_machine_info = {include/hw/i386/x86.h +5
-0@@ -85,6 +85,9 @@ struct X86MachineState {* which means no limitation on the guest's bus locks. */ uint64_t bus_lock_ratelimit; + +bool notify_vmexit; +uint32_t notify_window; };#define X86_MACHINE_SMM "smm"@@ -94,6 +97,8 @@ struct X86MachineState {#define X86_MACHINE_OEM_ID "x-oem-id"#define X86_MACHINE_OEM_TABLE_ID "x-oem-table-id"#define X86_MACHINE_BUS_LOCK_RATELIMIT "bus-lock-ratelimit" +#define X86_MACHINE_NOTIFY_VMEXIT "notify-vmexit" +#define X86_MACHINE_NOTIFY_WINDOW "notify-window"#define TYPE_X86_MACHINE MACHINE_TYPE_NAME("x86")OBJECT_DECLARE_TYPE (X86MachineState, X86MachineClass,X86_MACHINE )qemu-options.hx +9
-1@@ -37,7 +37,8 @@ DEF("machine", HAS_ARG, QEMU_OPTION_machine, \ " memory-encryption=@var{} memory encryption object to use (default=none)\n" " hmat=on|off controls ACPI HMAT support (default=off)\n" " memory-backend='backend-id' specifies explicitly provided backend for main RAM (default=none)\n" - " cxl-fmw.0.targets.0=firsttarget,cxl-fmw.0.targets.1=secondtarget,cxl-fmw.0.size=size[,cxl-fmw.0.interleave-granularity=granularity]\n", + " cxl-fmw.0.targets.0=firsttarget,cxl-fmw.0.targets.1=secondtarget,cxl-fmw.0.size=size[,cxl-fmw.0.interleave-granularity=granularity]\n" + " notify_vmexit=on|off,notify_window=n controls notify VM exit support (default=off) and specifies the notify window size (default=0)\n", QEMU_ARCH_ALL) SRST ``-machine [type=]name[,prop=value[,...]]``@@ -157,6 +158,13 @@ SRST :: -machine cxl-fmw.0.targets.0=cxl.0,cxl-fmw.0.targets.1=cxl.1,cxl-fmw.0.size=128G,cxl-fmw.0.interleave-granularity=512k + + ``notify_vmexit=on|off,notify_window=n`` + Enables or disables Notify VM exit support on x86 host and specify + the corresponding notify window to trigger the VM exit if enabled. + This feature can mitigate the CPU stuck issue due to event windows + don't open up for a specified of time (notify window). + The default is off. ERST DEF("M", HAS_ARG, QEMU_OPTION_M,target/i386/kvm/kvm.c +0
-0target/i386/kvm/kvm.c int kvm_arch_init(MachineState *ms, KVMState *s) · line 2605
Quoted 9 lines
target/i386/kvm/kvm.c +6
-0@@ -2597,6 +2597,20 @@ int kvm_arch_init(MachineState *ms, KVMState *s)ratelimit_set_speed (&bus_lock_ratelimit_ctrl, x86ms->bus_lock_ratelimit,BUS_LOCK_SLICE_TIME ); } + +if (x86ms->notify_vmexit && +kvm_check_extension (s,KVM_CAP_X86_NOTIFY_VMEXIT )) { +uint64_t notify_window_flags = ((uint64_t )x86ms->notify_window <<32 ) | +KVM_X86_NOTIFY_VMEXIT_ENABLED | +KVM_X86_NOTIFY_VMEXIT_USER ;It'll always request a user exit here as long as enabled, then...
Quoted 27 lines
target/i386/kvm/kvm.c +15
-0+ ret =kvm_vm_enable_cap (s,KVM_CAP_X86_NOTIFY_VMEXIT ,0 , + notify_window_flags); +if (ret <0 ) { +error_report ("kvm: Failed to enable notify vmexit cap: %s" , +strerror (-ret)); +return ret; + } + } }return 0 ;@@ -5141,6 +5155,7 @@ int kvm_arch_handle_exit(CPUState *cs, struct kvm_run *run)X86CPU *cpu =X86_CPU (cs);uint64_t code;int ret; +struct kvm_vcpu_events events = {};switch (run->exit_reason) {case KVM_EXIT_HLT :@@ -5196,6 +5211,19 @@ int kvm_arch_handle_exit(CPUState *cs, struct kvm_run *run)/* already handled in kvm_arch_post_run */ ret =0 ;break ; +case KVM_EXIT_NOTIFY : + ret =0 ; +if (run->notify.flags &KVM_NOTIFY_CONTEXT_INVALID ) { +warn_report ("KVM: invalid context due to notify vmexit" ); +if (has_triple_fault_event) { + events.flags |=KVM_VCPUEVENT_VALID_TRIPLE_FAULT ;Quoted 8 lines
target/i386/kvm/kvm.c int kvm_arch_handle_exit(CPUState *cs, struct kvm_run *run) · line 5225
Quoted 6 lines
target/i386/kvm/kvm.c +6
-0+ events.triple_fault.pending = true; + ret =kvm_vcpu_ioctl (cs,KVM_SET_VCPU_EVENTS , &events); + }else { + ret =-1 ; + } + }... should we do something even if the context is valid? Or I'm a bit
Yes, make sense. A warning log is necessary if the context is valid.
Quoted 3 lines
confused why
KVM_X86_NOTIFY_VMEXIT_USERwas set (IIUC we can just enable it without settingVMEXIT_USERthen).
VMEXIT_USRwas set because KVM community prefers userspace can get notified and help to do some analysis or mitigation if notify window was exceeded.Quoted 4 lines
Not sure some warning would be also useful here, but I really don't know the whole context so I can't tell whether there can easily be false positives to pollute qemu log.
The false positive case is not easy to happen unless some potential issues in silicon. But in case of it, to avoid polluting qemu log, how about:
target/i386/kvm/kvm.c +0
-0
target/i386/kvm/kvm.c int kvm_arch_handle_exit(CPUState *cs, struct kvm_run · line 5217
Quoted 5 lines
target/i386/kvm/kvm.c +1
-0@@ -5213,6 +5213,7 @@ int kvm_arch_handle_exit(CPUState *cs, struct kvm_run *run)break ;case KVM_EXIT_NOTIFY : ret =0 ; +warn_report_once ("KVM: notify window was exceeded in guest" );
Is there more informative way to dump this? If it's 99% that the guest was doing something weird and needs attention, maybe worthwhile to point that out directly to the admin?
Quoted 3 lines
target/i386/kvm/kvm.c +0
-0if (run->notify.flags &KVM_NOTIFY_CONTEXT_INVALID ) {warn_report ("KVM: invalid context due to notify vmexit" );if (has_triple_fault_event) {
Adding a warning looks good to me, with that (or in any better form of wording):
Thanks,
Signature · 1 line
Peter Xu
Re: [PATCH v6 2/2] i386: Add notify VM exit support
Quoted 233 lines · Peter Xu
Quoted 232 lines · Chenyi Qiang
Quoted 202 lines · Peter Xu
Quoted 162 lines · Chenyi Qiang
There are cases that malicious virtual machine can cause CPU stuck (due to event windows don't open up), e.g., infinite loop in microcode when nested #AC (CVE-2015-5307). No event window means no event (NMI, SMI and IRQ) can be delivered. It leads the CPU to be unavailable to host or other VMs. Notify VM exit is introduced to mitigate such kind of attacks, which will generate a VM exit if no event window occurs in VM non-root mode for a specified amount of time (notify window).
A new KVM capability
KVM_CAP_X86_NOTIFY_VMEXITis exposed to user space so that the user can query the capability and set the expected notify window when creating VMs. The format of the argument when enabling this capability is as follows:
Bit 63:32 - notify window specified in qemu command
Bit 31:0 - some flags (e.g.KVM_X86_NOTIFY_VMEXIT_ENABLEDis set to
enable the feature.)Because there are some concerns, e.g. a notify VM exit may happen with
VM_CONTEXT_INVALIDset in exit qualification (no cases are anticipated that would set this bit), which means VM context is corrupted. To avoid the false positive and a well-behaved guest gets killed, make this feature disabled by default. Users can enable the feature by a new machine property:
qemu -machine notify_vmexit=on,notify_window=0 ...Note that
notify_windowis only valid whennotify_vmexitis on. The valid range ofnotify_windowis non-negative. It is even safe to set it to zero since there's an internal hardware threshold to be added to ensure no false positive.A new KVM exit reason
KVM_EXIT_NOTIFYis defined for notify VM exit. If it happens withVM_INVALID_CONTEXT, hypervisor exits to user space to inform the fatal case. Then user space can inject a SHUTDOWN event to the target vcpu. This is implemented by injecting a sythesized triple fault event.Signed-off-by Chenyi Qiang <[email protected]>--- hw/i386/x86.c | 45 +++++++++++++++++++++++++++++++++++++++++++ include/hw/i386/x86.h | 5 +++++ qemu-options.hx | 10 +++++++++- target/i386/kvm/kvm.c | 28 +++++++++++++++++++++++++++ 4 files changed, 87 insertions(+), 1 deletion(-)hw/i386/x86.c +45
-0@@ -1379,6 +1379,37 @@ static void machine_set_sgx_epc(Object *obj, Visitor *v, const char *name,qapi_free_SgxEPCList (list); } +static bool x86_machine_get_notify_vmexit (Object *obj,Error **errp) +{ +X86MachineState *x86ms =X86_MACHINE (obj); + +return x86ms->notify_vmexit; +} + +static void x86_machine_set_notify_vmexit (Object *obj,bool value,Error **errp) +{ +X86MachineState *x86ms =X86_MACHINE (obj); + + x86ms->notify_vmexit = value; +} + +static void x86_machine_get_notify_window (Object *obj,Visitor *v, +const char *name,void *opaque,Error **errp) +{ +X86MachineState *x86ms =X86_MACHINE (obj); +uint32_t notify_window = x86ms->notify_window; + +visit_type_uint32 (v, name, ¬ify_window, errp); +} + +static void x86_machine_set_notify_window (Object *obj,Visitor *v, +const char *name,void *opaque,Error **errp) +{ +X86MachineState *x86ms =X86_MACHINE (obj); + +visit_type_uint32 (v, name, &x86ms->notify_window, errp); +} +static void x86_machine_initfn (Object *obj) {X86MachineState *x86ms =X86_MACHINE (obj);@@ -1392,6 +1423,8 @@ static void x86_machine_initfn(Object *obj) x86ms->oem_table_id =g_strndup (ACPI_BUILD_APPNAME8 ,8 ); x86ms->bus_lock_ratelimit =0 ; x86ms->above_4g_mem_start =4 * GiB; + x86ms->notify_vmexit = false; + x86ms->notify_window =0 ; }static void x86_machine_class_init (ObjectClass *oc,void *data)@@ -1461,6 +1494,18 @@ static void x86_machine_class_init(ObjectClass *oc, void *data) NULL, NULL);object_class_property_set_description (oc,"sgx-epc" ,"SGX EPC device" ); + +object_class_property_add (oc,X86_MACHINE_NOTIFY_WINDOW ,"uint32_t" , + x86_machine_get_notify_window, + x86_machine_set_notify_window,NULL ,NULL ); +object_class_property_set_description (oc,X86_MACHINE_NOTIFY_WINDOW , +"Set the notify window required by notify VM exit" ); + +object_class_property_add_bool (oc,X86_MACHINE_NOTIFY_VMEXIT , + x86_machine_get_notify_vmexit, + x86_machine_set_notify_vmexit); +object_class_property_set_description (oc,X86_MACHINE_NOTIFY_VMEXIT , +"Enable notify VM exit" ); }static const TypeInfo x86_machine_info = {include/hw/i386/x86.h +5
-0@@ -85,6 +85,9 @@ struct X86MachineState {* which means no limitation on the guest's bus locks. */ uint64_t bus_lock_ratelimit; + +bool notify_vmexit; +uint32_t notify_window; };#define X86_MACHINE_SMM "smm"@@ -94,6 +97,8 @@ struct X86MachineState {#define X86_MACHINE_OEM_ID "x-oem-id"#define X86_MACHINE_OEM_TABLE_ID "x-oem-table-id"#define X86_MACHINE_BUS_LOCK_RATELIMIT "bus-lock-ratelimit" +#define X86_MACHINE_NOTIFY_VMEXIT "notify-vmexit" +#define X86_MACHINE_NOTIFY_WINDOW "notify-window"#define TYPE_X86_MACHINE MACHINE_TYPE_NAME("x86")OBJECT_DECLARE_TYPE (X86MachineState, X86MachineClass,X86_MACHINE )qemu-options.hx +9
-1@@ -37,7 +37,8 @@ DEF("machine", HAS_ARG, QEMU_OPTION_machine, \ " memory-encryption=@var{} memory encryption object to use (default=none)\n" " hmat=on|off controls ACPI HMAT support (default=off)\n" " memory-backend='backend-id' specifies explicitly provided backend for main RAM (default=none)\n" - " cxl-fmw.0.targets.0=firsttarget,cxl-fmw.0.targets.1=secondtarget,cxl-fmw.0.size=size[,cxl-fmw.0.interleave-granularity=granularity]\n", + " cxl-fmw.0.targets.0=firsttarget,cxl-fmw.0.targets.1=secondtarget,cxl-fmw.0.size=size[,cxl-fmw.0.interleave-granularity=granularity]\n" + " notify_vmexit=on|off,notify_window=n controls notify VM exit support (default=off) and specifies the notify window size (default=0)\n", QEMU_ARCH_ALL) SRST ``-machine [type=]name[,prop=value[,...]]``@@ -157,6 +158,13 @@ SRST :: -machine cxl-fmw.0.targets.0=cxl.0,cxl-fmw.0.targets.1=cxl.1,cxl-fmw.0.size=128G,cxl-fmw.0.interleave-granularity=512k + + ``notify_vmexit=on|off,notify_window=n`` + Enables or disables Notify VM exit support on x86 host and specify + the corresponding notify window to trigger the VM exit if enabled. + This feature can mitigate the CPU stuck issue due to event windows + don't open up for a specified of time (notify window). + The default is off. ERST DEF("M", HAS_ARG, QEMU_OPTION_M,target/i386/kvm/kvm.c +0
-0target/i386/kvm/kvm.c int kvm_arch_init(MachineState *ms, KVMState *s) · line 2605
Quoted 9 lines
target/i386/kvm/kvm.c +6
-0@@ -2597,6 +2597,20 @@ int kvm_arch_init(MachineState *ms, KVMState *s)ratelimit_set_speed (&bus_lock_ratelimit_ctrl, x86ms->bus_lock_ratelimit,BUS_LOCK_SLICE_TIME ); } + +if (x86ms->notify_vmexit && +kvm_check_extension (s,KVM_CAP_X86_NOTIFY_VMEXIT )) { +uint64_t notify_window_flags = ((uint64_t )x86ms->notify_window <<32 ) | +KVM_X86_NOTIFY_VMEXIT_ENABLED | +KVM_X86_NOTIFY_VMEXIT_USER ;It'll always request a user exit here as long as enabled, then...
Quoted 27 lines
target/i386/kvm/kvm.c +15
-0+ ret =kvm_vm_enable_cap (s,KVM_CAP_X86_NOTIFY_VMEXIT ,0 , + notify_window_flags); +if (ret <0 ) { +error_report ("kvm: Failed to enable notify vmexit cap: %s" , +strerror (-ret)); +return ret; + } + } }return 0 ;@@ -5141,6 +5155,7 @@ int kvm_arch_handle_exit(CPUState *cs, struct kvm_run *run)X86CPU *cpu =X86_CPU (cs);uint64_t code;int ret; +struct kvm_vcpu_events events = {};switch (run->exit_reason) {case KVM_EXIT_HLT :@@ -5196,6 +5211,19 @@ int kvm_arch_handle_exit(CPUState *cs, struct kvm_run *run)/* already handled in kvm_arch_post_run */ ret =0 ;break ; +case KVM_EXIT_NOTIFY : + ret =0 ; +if (run->notify.flags &KVM_NOTIFY_CONTEXT_INVALID ) { +warn_report ("KVM: invalid context due to notify vmexit" ); +if (has_triple_fault_event) { + events.flags |=KVM_VCPUEVENT_VALID_TRIPLE_FAULT ;Quoted 8 lines
target/i386/kvm/kvm.c int kvm_arch_handle_exit(CPUState *cs, struct kvm_run *run) · line 5225
Quoted 6 lines
target/i386/kvm/kvm.c +6
-0+ events.triple_fault.pending = true; + ret =kvm_vcpu_ioctl (cs,KVM_SET_VCPU_EVENTS , &events); + }else { + ret =-1 ; + } + }... should we do something even if the context is valid? Or I'm a bit
Yes, make sense. A warning log is necessary if the context is valid.
Quoted 3 lines
confused why
KVM_X86_NOTIFY_VMEXIT_USERwas set (IIUC we can just enable it without settingVMEXIT_USERthen).
VMEXIT_USRwas set because KVM community prefers userspace can get notified and help to do some analysis or mitigation if notify window was exceeded.Quoted 4 lines
Not sure some warning would be also useful here, but I really don't know the whole context so I can't tell whether there can easily be false positives to pollute qemu log.
The false positive case is not easy to happen unless some potential issues in silicon. But in case of it, to avoid polluting qemu log, how about:
Quoted 15 lines
target/i386/kvm/kvm.c int kvm_arch_handle_exit(CPUState *cs, struct kvm_run · line 5217
Quoted 10 lines
target/i386/kvm/kvm.c +1
-0@@ -5213,6 +5213,7 @@ int kvm_arch_handle_exit(CPUState *cs, struct kvm_run *run)break ;case KVM_EXIT_NOTIFY : ret =0 ; +warn_report_once ("KVM: notify window was exceeded in guest" );Is there more informative way to dump this? If it's 99% that the guest was doing something weird and needs attention, maybe worthwhile to point that out directly to the admin?
Do you mean to use other method to dump the info? i.e. printing a message is not so clear. Or the output message ("KVM: notify window was exceeded in guest") is not obvious and we need other wording.
Quoted 7 lines
Quoted 3 lines
target/i386/kvm/kvm.c +0
-0if (run->notify.flags &KVM_NOTIFY_CONTEXT_INVALID ) {warn_report ("KVM: invalid context due to notify vmexit" );if (has_triple_fault_event) {Adding a warning looks good to me, with that (or in any better form of wording):
If no objection, I'll follow Xiaoyao's suggestion to form the wording like:
case KVM_EXIT_NOTIFY:
ctx_invalid = !!(run->notify.flags & KVM_NOTIFY_CONTEXT_INVALID);
ret = 0;
warn_report_once("KVM: Encounter notify exit with %svalid context
in guest", ctx_invalid ? "in" : "");
if (ctx_invalid) {
if (has_triple_fault_event) {}
}Quoted 4 lines
Acked-by Peter Xu <[email protected]>Thanks,
Re: [PATCH v6 2/2] i386: Add notify VM exit support
Quoted 12 lines · Chenyi Qiang
Quoted 11 lines
target/i386/kvm/kvm.c int kvm_arch_handle_exit(CPUState *cs, struct kvm_run · line 5217
Quoted 6 lines
target/i386/kvm/kvm.c +1
-0@@ -5213,6 +5213,7 @@ int kvm_arch_handle_exit(CPUState *cs, struct kvm_run *run)break ;case KVM_EXIT_NOTIFY : ret =0 ; +warn_report_once ("KVM: notify window was exceeded in guest" );Is there more informative way to dump this? If it's 99% that the guest was doing something weird and needs attention, maybe worthwhile to point that out directly to the admin?
Quoted 3 lines
Do you mean to use other method to dump the info? i.e. printing a message is not so clear. Or the output message ("KVM: notify window was exceeded in guest") is not obvious and we need other wording.
I meant something like:
KVM received notify exit. It means there can be possible misbehaves in the guest, please have a look.
Or something similar. What I'm worried is the admin may not understand what's "notify window" and that message got simply ignored.
Though I am not even sure whether that's accurate in the wordings.
Quoted 9 lines
Quoted 8 lines
Quoted 4 lines
target/i386/kvm/kvm.c +0
-0if (run->notify.flags &KVM_NOTIFY_CONTEXT_INVALID ) {warn_report ("KVM: invalid context due to notify vmexit" );if (has_triple_fault_event) {Adding a warning looks good to me, with that (or in any better form of wording):
If no objection, I'll follow Xiaoyao's suggestion to form the wording like:
No objection here. Thanks.
Signature · 1 line
Peter Xu
Re: [PATCH v6 2/2] i386: Add notify VM exit support
Quoted 13 lines · Peter Xu
Quoted 12 lines · Chenyi Qiang
Quoted 11 lines
target/i386/kvm/kvm.c int kvm_arch_handle_exit(CPUState *cs, struct kvm_run · line 5217
Quoted 6 lines
target/i386/kvm/kvm.c +1
-0@@ -5213,6 +5213,7 @@ int kvm_arch_handle_exit(CPUState *cs, struct kvm_run *run)break ;case KVM_EXIT_NOTIFY : ret =0 ; +warn_report_once ("KVM: notify window was exceeded in guest" );Is there more informative way to dump this? If it's 99% that the guest was doing something weird and needs attention, maybe worthwhile to point that out directly to the admin?
Quoted 8 lines
Quoted 3 lines
Do you mean to use other method to dump the info? i.e. printing a message is not so clear. Or the output message ("KVM: notify window was exceeded in guest") is not obvious and we need other wording.
I meant something like:
KVM received notify exit. It means there can be possible misbehaves in the guest, please have a look.
Get your point. Then I can print this message behind as well.
Thanks.
Quoted 18 lines
Or something similar. What I'm worried is the admin may not understand what's "notify window" and that message got simply ignored.
Though I am not even sure whether that's accurate in the wordings.
Quoted 9 lines
Quoted 8 lines
Quoted 4 lines
target/i386/kvm/kvm.c +0
-0if (run->notify.flags &KVM_NOTIFY_CONTEXT_INVALID ) {warn_report ("KVM: invalid context due to notify vmexit" );if (has_triple_fault_event) {Adding a warning looks good to me, with that (or in any better form of wording):
If no objection, I'll follow Xiaoyao's suggestion to form the wording like:
No objection here. Thanks.