![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(80, 3%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EF%3C/text%3E%3C/svg%3E)
Hyper-V
一种 Windows 技术，提供基于虚拟机监控程序的虚拟化解决方案，使客户能够将工作负载整合到单个服务器上。
49 个问题
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 57.99999999999999%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESP%3C/text%3E%3C/svg%3E)
Dear Team,
This error, "whpx: injection failed, MSI...lost (c0350005)" followed by "WHPX: Unexpected VP exit code 4" upon restart, points to a known issue with the Windows Hypervisor Platform (WHPX) accelerator in specific QEMU versions, particularly when dealing with interrupt handling (MSI) and virtual processor state.
The most common cause is a bug within the WHPX API or its interaction with your specific CPU and QEMU version. This often manifests during guest OS operations that heavily rely on interrupt requests, like restarting or shutting down.
Here are the most effective solutions, ranked from most likely to succeed:
- Update QEMU
This is the most frequent and successful solution. Newer versions of QEMU often contain patches and workarounds for bugs in WHPX.
- Recommendation: Download and install the latest stable version of QEMU for Windows. Bug fixes for WHPX are common in new releases.