| 16 | Hypervisor/Virtual Machine Support Driver |
Hypervisor/Virtual Machine Support Driver |
| 0x1 | Hypervisor successfully started. |
Hypervisor successfully started. |
| 0x2 | Hypervisor scheduler type is %1. |
Hypervisor scheduler type is %1. |
| 0x3 | Hypervisor Eventlog for global system events could not be created! |
Hypervisor Eventlog for global system events could not be created! |
| 0x5 | Hypervisor launch has been disabled through the hypervisorlaunchtype bcdedit setting. |
Hypervisor launch has been disabled through the hypervisorlaunchtype bcdedit setting. |
| 0xC | Hypervisor SPT Resizing policy failed to initialize. |
Hypervisor SPT Resizing policy failed to initialize. |
| 0xD | Hypervisor fails to start ETW tracing session. |
Hypervisor fails to start ETW tracing session. |
| 0x14 | Hypervisor launch failed; sleep and hibernate could not be disabled (status %1). |
Hypervisor launch failed; sleep and hibernate could not be disabled (status %1). |
| 0x1A | Hypervisor launch failed; the hypervisor boot loader's internal logic failed (BalStatus %1, sub-status %2). |
Hypervisor launch failed; the hypervisor boot loader's internal logic failed (BalStatus %1, sub-status %2). |
| 0x1B | Hypervisor launch failed; the hypervisor boot loader was unable to allocate sufficient resources to perform the launch. |
Hypervisor launch failed; the hypervisor boot loader was unable to allocate sufficient resources to perform the launch. |
| 0x1C | Hypervisor launch failed; the hypervisor boot loader does not support the vendor of at least one of the processors in the system. |
Hypervisor launch failed; the hypervisor boot loader does not support the vendor of at least one of the processors in the system. |
| 0x1D | Hypervisor launch failed; at least one of the processors in the system does not appear to support the features required by the hypervisor. (leaf: %1, required features: %2, features available: %3) |
Hypervisor launch failed; at least one of the processors in the system does not appear to support the features required by the hypervisor. (leaf: %1, required features: %2, features available: %3) |
| 0x1F | Hyper-V launch failed; the system does not appear to have a sufficient level of ACPI support to launch the hypervisor. |
Hyper-V launch failed; the system does not appear to have a sufficient level of ACPI support to launch the hypervisor. |
| 0x20 | Hypervisor launch failed; at least one of the processors in the system does not appear to provide a virtualization platform supported by the hypervisor. |
Hypervisor launch failed; at least one of the processors in the system does not appear to provide a virtualization platform supported by the hypervisor. |
| 0x21 | Hyper-V launch failed; the image %1 could not be accessed (status %2). |
Hyper-V launch failed; the image %1 could not be accessed (status %2). |
| 0x22 | Hyper-V launch failed; the image %1 could not be loaded (status %2). |
Hyper-V launch failed; the image %1 could not be loaded (status %2). |
| 0x23 | Hyper-V launch failed; the image %1 could not be read (status %2). |
Hyper-V launch failed; the image %1 could not be read (status %2). |
| 0x24 | Hypervisor launch failed; the image %1 failed code integrity checks, and cannot be used. |
Hypervisor launch failed; the image %1 failed code integrity checks, and cannot be used. |
| 0x25 | Hypervisor launch failed; the image %1 does not contain the image description datastructures, and cannot be used. |
Hypervisor launch failed; the image %1 does not contain the image description datastructures, and cannot be used. |
| 0x26 | Hyper-V launch failed; at least one of the processors in the system was unable to launch the hypervisor (status %1). |
Hyper-V launch failed; at least one of the processors in the system was unable to launch the hypervisor (status %1). |
| 0x28 | Hypervisor launch failed; the hypervisor image is revision %1, but the currently installed virtualization software only supports launching revision %2 hypervisor images. |
Hypervisor launch failed; the hypervisor image is revision %1, but the currently installed virtualization software only supports launching revision %2 hypervisor images. |
| 0x29 | Hypervisor launch failed; Either VMX not present or not enabled in BIOS. |
Hypervisor launch failed; Either VMX not present or not enabled in BIOS. |
| 0x2A | Hypervisor launch failed; Either SVM not present or not enabled in BIOS. |
Hypervisor launch failed; Either SVM not present or not enabled in BIOS. |
| 0x2C | Hypervisor launch failed; Either No Execute feature (NX) not present or not enabled in BIOS. |
Hypervisor launch failed; Either No Execute feature (NX) not present or not enabled in BIOS. |
| 0x2D | Hypervisor launch failed; at least one of the processors in the system is incompatible with the others. |
Hypervisor launch failed; at least one of the processors in the system is incompatible with the others. |
| 0x2E | Hypervisor launch failed; Processor does not support the minimum features required to run the hypervisor (MSR index %1, allowed bits %2, required bits %3). |
Hypervisor launch failed; Processor does not support the minimum features required to run the hypervisor (MSR index %1, allowed bits %2, required bits %3). |
| 0x2F | Hypervisor launch failed; Processor does not provide the features necessary to run the hypervisor (BalStatus %1, leaf1 EAX %2, VMCR MS EAX %3, SVM CPUID features %4, has working SMM %5). |
Hypervisor launch failed; Processor does not provide the features necessary to run the hypervisor (BalStatus %1, leaf1 EAX %2, VMCR MS EAX %3, SVM CPUID features %4, has working SMM %5). |
| 0x30 | Hypervisor launch failed; Processor does not provide the features necessary to run the hypervisor (leaf %1, register %2: features needed %3, features supported %4). |
Hypervisor launch failed; Processor does not provide the features necessary to run the hypervisor (leaf %1, register %2: features needed %3, features supported %4). |
| 0x36 | Hypervisor launch failed; Hypervisor image does not match the platform being run on. |
Hypervisor launch failed; Hypervisor image does not match the platform being run on. |
| 0x37 | Hypervisor launch failed; Required firmware table not found. |
Hypervisor launch failed; Required firmware table not found. |
| 0x38 | Hypervisor launch failed; Encountered invalid firmware information. |
Hypervisor launch failed; Encountered invalid firmware information. |
| 0x39 | Hypervisor launch failed; Incompatible SVM features present. |
Hypervisor launch failed; Incompatible SVM features present. |
| 0x3A | Hypervisor launch failed; Incompatible VMX features present. |
Hypervisor launch failed; Incompatible VMX features present. |
| 0x3B | Hypervisor launch failed; Second Level Address Translation is required to launch the hypervisor. |
Hypervisor launch failed; Second Level Address Translation is required to launch the hypervisor. |
| 0x3C | Hypervisor launch failed; Secure Mode Extensions have been enabled by the BIOS. Please disable Secure Mode Extensions in the BIOS to launch Hyper-V. |
Hypervisor launch failed; Secure Mode Extensions have been enabled by the BIOS. Please disable Secure Mode Extensions in the BIOS to launch Hyper-V. |
| 0x3D | Hypervisor launch failed; Minimum CPUID leaves required by the hypervisor are not supported on the system. |
Hypervisor launch failed; Minimum CPUID leaves required by the hypervisor are not supported on the system. |
| 0x3E | Hypervisor launch failed; The physical address limit supported has been exceeded. |
Hypervisor launch failed; The physical address limit supported has been exceeded. |
| 0x3F | Hypervisor launch failed; The hypervisor was unable to initialize successfully (phase %1), and was not started. This initialization failure may be the result of a platform configuration or firmware issue. Contact your system vendor for more information or updated firmware. |
Hypervisor launch failed; The hypervisor was unable to initialize successfully (phase %1), and was not started. This initialization failure may be the result of a platform configuration or firmware issue. Contact your system vendor for more information or updated firmware. |
| 0x40 | Hypervisor launch failed; Too many runtime services memory ranges described by firmware. |
Hypervisor launch failed; Too many runtime services memory ranges described by firmware. |
| 0x50 | Hypervisor launch failed; The operating systems boot loader failed with error %1. |
Hypervisor launch failed; The operating systems boot loader failed with error %1. |
| 0x51 | Hypervisor launch failed; The operating system boot loader was unable to locate a required resource. |
Hypervisor launch failed; The operating system boot loader was unable to locate a required resource. |
| 0x52 | Hypervisor launch failed; The operating system boot loader detected a persistent memory failure. |
Hypervisor launch failed; The operating system boot loader detected a persistent memory failure. |
| 0x53 | Hypervisor launch failed; The operating system boot loader was unable to allocate sufficient memory to complete the operation. |
Hypervisor launch failed; The operating system boot loader was unable to allocate sufficient memory to complete the operation. |
| 0x54 | Hypervisor launch failed; The operating system boot loader was unable to allocate sufficient resources to complete the operation. |
Hypervisor launch failed; The operating system boot loader was unable to allocate sufficient resources to complete the operation. |
| 0x55 | Hypervisor launch failed; The operating system boot loader detected a memory map conflict. |
Hypervisor launch failed; The operating system boot loader detected a memory map conflict. |
| 0x60 | Hypervisor processor startup failed (APIC ID %1, status %2). Further processors in the system were not started. |
Hypervisor processor startup failed (APIC ID %1, status %2). Further processors in the system were not started. |
| 0x61 | Hypervisor processor startup failed (APIC ID %1) due to CPUID feature validation error. Further processors in the system were not started. Leaf %2, register %3 feature mismatch: BSP has features %5; AP has features %4 |
Hypervisor processor startup failed (APIC ID %1) due to CPUID feature validation error. Further processors in the system were not started. Leaf %2, register %3 feature mismatch: BSP has features %5; AP has features %4 |
| 0x81 | Hypervisor initialized I/O remapping.%n%nHardware present: %1%nHardware enabled: %2%nPolicy: %3%nEnabled features: %4%nInternal information: %5%nProblems: %6%nAdditional information: %7 |
Hypervisor initialized I/O remapping.%n%nHardware present: %1%nHardware enabled: %2%nPolicy: %3%nEnabled features: %4%nInternal information: %5%nProblems: %6%nAdditional information: %7 |
| 0x82 | Hypervisor I/O remapping is forcibly enabled by policy (the hypervisoriommupolicy BCD option is set to enable). If the system exhibits instability or reduced performance, consider restoring the default policy. |
Hypervisor I/O remapping is forcibly enabled by policy (the hypervisoriommupolicy BCD option is set to enable). If the system exhibits instability or reduced performance, consider restoring the default policy. |
| 0x90 | A device is operating with reduced performance because of a problem with the system BIOS.%n%nThe device is not reported under the scope of a unique I/O remapping unit.%n%nDevice ID: %1%nPartition ID: %2 |
A device is operating with reduced performance because of a problem with the system BIOS.%n%nThe device is not reported under the scope of a unique I/O remapping unit.%n%nDevice ID: %1%nPartition ID: %2 |
| 0x91 | A device will not work correctly because of a problem with the system BIOS.%n%nThe Requester IDs reported for the device overlap with those reported for another device.%n%nDevice ID: %1%nPartition ID: %2 |
A device will not work correctly because of a problem with the system BIOS.%n%nThe Requester IDs reported for the device overlap with those reported for another device.%n%nDevice ID: %1%nPartition ID: %2 |
| 0x92 | A device will not work correctly because the hypervisor does not have enough resources.%n%nDevice ID: %1%nPartition ID: %2 |
A device will not work correctly because the hypervisor does not have enough resources.%n%nDevice ID: %1%nPartition ID: %2 |
| 0x93 | A device will not work correctly because of a problem with the system BIOS.%n%nAn IOAPIC is not correctly reported.%n%nIOAPIC ID: %1 |
A device will not work correctly because of a problem with the system BIOS.%n%nAn IOAPIC is not correctly reported.%n%nIOAPIC ID: %1 |
| 0x94 | A device could not be used by a child partition because of a limitation of the system hardware and BIOS.%n%nThe I/O remapping unit that controls the device does not have sufficient capabilities.%n%nDevice ID: %1%nI/O remapping unit base address: %2%nPartition ID: %3 |
A device could not be used by a child partition because of a limitation of the system hardware and BIOS.%n%nThe I/O remapping unit that controls the device does not have sufficient capabilities.%n%nDevice ID: %1%nI/O remapping unit base address: %2%nPartition ID: %3 |
| 0x95 | A device could not be used by a child partition because of a limitation of the system hardware and BIOS.%n%nThe device cannot be securely used by a child partition.%n%nDevice ID: %1%nPartition ID: %2 |
A device could not be used by a child partition because of a limitation of the system hardware and BIOS.%n%nThe device cannot be securely used by a child partition.%n%nDevice ID: %1%nPartition ID: %2 |
| 0x96 | The image %1 could not be accessed (status %2). |
The image %1 could not be accessed (status %2). |
| 0x97 | The image %1 could not be loaded (status %2). |
The image %1 could not be loaded (status %2). |
| 0x98 | The image %1 could not be read (status %2). |
The image %1 could not be read (status %2). |
| 0x99 | The image %1 failed code integrity checks, and cannot be used. |
The image %1 failed code integrity checks, and cannot be used. |
| 0x9A | Hypervisor failed to properly synchronize TSC across logical processors (Max delta: %1, Min delta: %2). |
Hypervisor failed to properly synchronize TSC across logical processors (Max delta: %1, Min delta: %2). |
| 0x50000002 | Error |
Error |
| 0x50000003 | Warning |
Warning |
| 0x50000004 | Information |
Information |
| 0x90000001 | Microsoft-Windows-Hyper-V-Hypervisor |
Microsoft-Windows-Hyper-V-Hypervisor |
| 0x90000002 | System |
System |
| 0xB000000A | Hypervisor Eventlog creation failed! |
Hypervisor Eventlog creation failed! |
| 0xB000000B | Hypervisor Eventlog deletion failed! |
Hypervisor Eventlog deletion failed! |
| 0xB0000027 | Hypervisor System Start Options! |
Hypervisor System Start Options! |
| 0xB0002103 | Hyper-V failed creating a new partition (status %1)! |
Hyper-V failed creating a new partition (status %1)! |
| 0xB0003106 | Hyper-V detected access to a restricted MSR (Msr: %1, IsWrite: %2, MsrValue: %3, AccessStatus: %4, Pc: %5, ImageBase: %6, ImageChecksum: %7, ImageTimestamp: %8, ImageName: %9). |
Hyper-V detected access to a restricted MSR (Msr: %1, IsWrite: %2, MsrValue: %3, AccessStatus: %4, Pc: %5, ImageBase: %6, ImageChecksum: %7, ImageTimestamp: %8, ImageName: %9). |
| 0xB0004101 | Hyper-V successfully created a new partition (partition %1). |
Hyper-V successfully created a new partition (partition %1). |
| 0xB0004102 | Hyper-V successfully deleted a partition (partition %1). |
Hyper-V successfully deleted a partition (partition %1). |