@samitouri / QOSamiQemu / commits / f0eb0ef4d8

whpx: i386: documentation update

Signed-off-by: Mohamed Mediouni <mohamed@unpredictable.fr> Link: https://lore.kernel.org/r/20260422214225.2242-38-mohamed@unpredictable.fr Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

Mohamed Mediouni committed Apr 22, 2026 at 23:42 UTC f0eb0ef4d83068fc3d909a0266832c7c5fbccb7a
1 file changed +11 -29
docs/system/whpx.rst
+11 -29
@@ -63,7 +63,7 @@ additional functionality compared to ``-device ramfb``, but is
63 incompatible with Windows's UEFI GOP implementation, which
64 expects a linear framebuffer to be available.
65
66 -Some tracing options
66 +Accelerator options
67 --------------------
68
69 x86_64
@@ -75,6 +75,11 @@ to undocumented MSRs.
75 ``-d invalid_mem`` allows to trace accesses to unmapped
76 GPAs.
77
78 +``-accel whpx,ssd=off`` disables the separate security domain feature,
79 +as in a BTB flush when entering/exiting the guest. This results in a
80 +significant MMIO performance increase at the detriment of security
81 +mitigations.
82 +
83 Known issues on x86_64
84 ----------------------
85
@@ -96,45 +101,22 @@ MMX, SSE or AVX instructions for access to MMIO memory ranges.
101 Attempts to run such guests will result in an ``Unimplemented handler``
102 warning for MMX and a failure to decode for newer instructions.
103
99 -``-M isapc``
100 -^^^^^^^^^^^^
101 -
102 -``-M isapc`` doesn't disable the Hyper-V LAPIC on its own yet. To
103 -be able to use that machine, use ``-accel whpx,hyperv=off,kernel-irqchip=off``.
104 -
105 -However, in QEMU 11.0, the guest will still be a 64-bit x86
106 -ISA machine with all the corresponding CPUID leaves exposed.
107 -
108 -gdbstub
109 -^^^^^^^
110 -
111 -As save/restore of xsave state is not currently present, state
112 -exposed through GDB will be incomplete.
113 -
114 -The same also applies to ``info registers``.
115 -
116 -``-cpu type`` ignored
117 -^^^^^^^^^^^^^^^^^^^^^
118 -
119 -In this release, -cpu is an ignored argument.
120 -
104 PIC interrupts on Windows 10
105 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
106
107 On Windows 10, a legacy PIC interrupt injected does not wake the guest
108 from an HLT when using the Hyper-V provided interrupt controller.
109
127 -This has been addressed in QEMU 11.0 on Windows 11 platforms but
128 -functionality to make it available on Windows 10 isn't present.
110 +As such, on Windows 10, using the Hyper-V interrupt controller is
111 +disabled by default. You can enable it via ``-M q35,pic=off`` which
112 +disables the PIC. In that configuration, using a UEFI is recommended.
113
130 -Workaround: for affected use cases, use ``-M kernel-irqchip=off``.
114 +On this release, ``-M kernel-irqchip=`` is not expected to be manually
115 +set during normal operation. It remains as a debugging option.
116
117 Known issues on Windows 11
118 ^^^^^^^^^^^^^^^^^^^^^^^^^^
119
135 -Nested virtualisation-specific Hyper-V enlightenments are not
136 -currently exposed.
137 -
120 arm64
121 -----
122