Project

General

Profile

Actions

Bug #14664

closed

bhyve missing triple-fault handling for VMX

Added by Patrick Mooney 4 months ago. Updated 4 months ago.

Status:
Closed
Priority:
Normal
Category:
bhyve
Start date:
Due date:
% Done:

100%

Estimated time:
Difficulty:
Medium
Tags:
Gerrit CR:

Description

When running the Windows kernel debugger under propolis, we tripped over an unhandled VMX exit on Intel hardware:

thread 'vcpu-0' panicked at 'VMX error: VmxDetail { status: 0, exit_reason: 2, exit_qualification: 0, inst_type: 0, inst_error: 0 }', propolis/src/lib.rs:133:17

That corresponds to the triple-fault exit reason, which after a trip to the relevant logic in vmx_exit_process, we're lacking a handler for. It should be translated into a vm-suspend of type triple-fault.

Actions

Also available in: Atom PDF