summary refs log tree commit diff stats
path: root/results/classifier/deepseek-2-tmp/output/hypervisor/1818
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/deepseek-2-tmp/output/hypervisor/1818')
-rw-r--r--results/classifier/deepseek-2-tmp/output/hypervisor/181821
1 files changed, 0 insertions, 21 deletions
diff --git a/results/classifier/deepseek-2-tmp/output/hypervisor/1818 b/results/classifier/deepseek-2-tmp/output/hypervisor/1818
deleted file mode 100644
index 739992ca1..000000000
--- a/results/classifier/deepseek-2-tmp/output/hypervisor/1818
+++ /dev/null
@@ -1,21 +0,0 @@
-
-whpx does not work with hyper-v enabled
-Description of problem:
-I am experiencing issues with the WHPX (Windows Hypervisor Platform Accelerator) hardware acceleration in QEMU on my Windows 10 22h2 system. When I run QEMU with the `-accel whpx` option, I encounter the following problems:
-
-2. I receive the error message "WHPX: No accelerator found, hr=00000000" followed by "failed to initialize whpx: No space left on device."
-Steps to reproduce:
-1. Enable the Hyper-V feature on Windows.
-2. Install the latest QEMU version
-3. Run the QEMU command with the `-accel whpx` option.
-Additional information:
-- my cpu : intel i7 6500U
-- ram : 8 gigabytes
-- gpu : intel hd 520
-- drive : C: -> 200 gigabytes, D: -> 1to (c: 109 used, d: 732 used)
-- emulated drive -> 50 gigabytes (500mb used)
-
-![image](/uploads/bbc4648b36f7a0430da39460d8f6c4de/image.png)
-![image](/uploads/cb0a59ddf0a1e7ed62253ea7abe21046/image.png)
-![image](/uploads/cd1c1116f6b3fa2c043d638f3983cc83/image.png)
-(in french sorry)