restructure results

1 files changed, 0 insertions, 65 deletions

diff --git a/results/classifier/118/none/1137 b/results/classifier/118/none/1137
deleted file mode 100644
index c3b22c8b..00000000
--- a/results/classifier/118/none/1137
+++ /dev/null
@@ -1,65 +0,0 @@
-performance: 0.783
-architecture: 0.764
-user-level: 0.754
-x86: 0.738
-kernel: 0.727
-device: 0.694
-socket: 0.691
-boot: 0.679
-peripherals: 0.656
-graphic: 0.642
-KVM: 0.640
-hypervisor: 0.635
-ppc: 0.630
-vnc: 0.628
-register: 0.622
-TCG: 0.615
-VMM: 0.612
-PID: 0.608
-permissions: 0.608
-semantic: 0.608
-risc-v: 0.607
-i386: 0.586
-files: 0.579
-arm: 0.548
-network: 0.545
-debug: 0.534
-virtual: 0.522
-assembly: 0.463
-mistranslation: 0.417
-
-When using qemu-system-x86_64 whpx acceleration, cpu information is set strangely.
-Description of problem:
-When using the guest with whpx acceleration in qemu-system-x86_64, the CPU information of the guest seems to be set strangely.
-
-When the guest is Linux, it seems that individual CPUs are allocated as many as the number of cores when using the -accel whpx option and the -smp option.
-* -smp 4, -smp cores=4, -smp sockes=1, cores=4, threads=1 are all set to have 4 single-core CPUs plugged in
-
-If the guest is Windows, check the information with CPU-Z
- It is recognized as a Pentium 4 and is displayed as a CPU with 1 core and n threads.
-
-Physically, it seems to be set to have n individual CPUs with 1 core plugged in.
-In Windows 11 Home (which seems to be the case for all versions of Windows Home), you cannot give the -smp value more than 5.
-* When booting with the -smp option value of 5 or more, a BSOD saying multiprocessor configuration not supported appears. -smp n, -smp cores=n, -smp sockes=1,cores=n,threads=1 All same symptoms occur
-Steps to reproduce:
-1. Boot Windows or Linux with -accel whpx -smp 4 option (or with the -accel whpx -smp sockets=1,cores=4,threads=1 option to make it deterministic)
-2. For Linux guest, use cat /proc/cpuinfo to check cpu information, for Windows guest, use cpu-z, device manager, task manager, etc. to check cpu information
-3. In the information of the Linux guest, it is displayed as fixed as core id : 0, cpu cores : 1, 
-   In Windows guest, information is displayed as written in "Description of problem" respectively.
-Additional information:
-**Windows 11 Home Guest set to 4 cores :**
-
-qemu-system-x86_64 -M q35 -smp sockets=1,cores=4,threads=1 -m 8g -device qxl-vga,vgamem_mb=256 -display sdl -drive file="Windows 11.vmdk",id=disk,if=none -device ahci,id=ahci -device ide-hd,drive=disk,bus=ahci.0 -rtc base=localtime -usbdevice tablet -accel whpx
-![Windows_Guest](/uploads/7b38889ff4ef20c935f724b0307766c9/Windows_Guest.jpg)
-
-
-**Windows 11 Home Guest set to 5 cores :**
-
-qemu-system-x86_64 -M q35 -smp sockets=1,cores=5,threads=1 -m 8g -device qxl-vga,vgamem_mb=256 -display sdl -drive file="Windows 11.vmdk",id=disk,if=none -device ahci,id=ahci -device ide-hd,drive=disk,bus=ahci.0 -rtc base=localtime -usbdevice tablet -accel whpx
-![BSOD](/uploads/910378cc73140831d9db5c58cb575bb8/BSOD.jpg)
-
-
-**Linux (Debian 11) guest set to 4 cores :**
-
-qemu-system-x86_64 -M q35 -smp sockets=1,cores=4,threads=1 -m 4g -device qxl-vga,vgamem_mb=256 -display sdl -drive file="debian.vdi",id=disk,if=none -device ahci,id=ahci -device ide-hd,drive=disk,bus=ahci.0 -rtc base=localtime -usbdevice tablet -accel whpx
-![Linux_Guest](/uploads/d1dbb2e38fcba57741c43f0f348297a2/Linux_Guest.jpg)