Unsolicited Intercept Types
Several conditions always cause the hypervisor to suspend a child partition's virtual processor and to send an intercept message to the parent partition. If certain events occur within the root partition, which has no parent, the hypervisor considers that the condition is fatal and restarts the operating system on the root partition.
The following table describes the intercepts that are defined on x64 implementations of the hypervisor.
| Unsolicited intercept type | Root partition behavior |
|---|---|
|
Invalid virtual processor state |
Fatal error. The system is restarted. |
|
Unrecoverable processor exception (for example, triple fault on x64) |
Fatal error. The system is restarted. |
|
Unsupported functionality error |
Fatal error. The system is restarted. |
|
FERR asserted (legacy floating point error) |
Ignored. No message is generated. |
|
APIC EOIs |
Ignored. No message is generated. |
Unsupported functionality errors are delivered to the parent if the guest uses a feature of the underlying processor architecture that is not virtualized by the hypervisor and cannot otherwise be reported as not implemented. For example, on the x64 architecture, some features can be reported as not implemented by using CPUID feature bits or by generating a #GP fault when accessing an MSR. If there is no architectural way for a guest to determine whether a feature is supported, the hypervisor can detect the use of the unsupported feature and deliver an unsupported functionality error to the parent.
Send comments about this topic to Microsoft
Build date: 11/16/2013