1 files changed, 51 insertions, 0 deletions
diff --git a/results/classifier/118/graphic/1003 b/results/classifier/118/graphic/1003
new file mode 100644
index 000000000..c91c9a59a
--- /dev/null
+++ b/results/classifier/118/graphic/1003
@@ -0,0 +1,51 @@
+graphic: 0.881
+boot: 0.856
+device: 0.786
+performance: 0.680
+register: 0.679
+architecture: 0.673
+x86: 0.594
+semantic: 0.575
+PID: 0.551
+vnc: 0.520
+hypervisor: 0.513
+mistranslation: 0.491
+debug: 0.447
+i386: 0.411
+KVM: 0.388
+permissions: 0.357
+user-level: 0.297
+ppc: 0.245
+peripherals: 0.203
+VMM: 0.194
+network: 0.135
+risc-v: 0.123
+kernel: 0.122
+TCG: 0.107
+arm: 0.094
+socket: 0.075
+assembly: 0.026
+files: 0.016
+virtual: 0.012
+
+"Cannot allocate memory" when boots a VM > 1026GB memory with -accel kvm
+Description of problem:
+I can boot an empty VM using command `qemu-system-x86_64 -m 1026G -accel kvm -vnc :1` or `qemu-system-x86_64 -m 8T -vnc :1`
+
+But when I use `qemu-system-x86_64 -m 1027G -accel kvm -vnc :1`, it will not boot:
+
+```
+root@debian11:~# qemu-system-x86_64 -m 1027G -accel kvm -vnc :1
+qemu-system-x86_64: kvm_set_user_memory_region: KVM_SET_USER_MEMORY_REGION failed, slot=1, start=0x100000000, size=0x10000000000: Cannot allocate memory
+kvm_set_phys_mem: error registering slot: Cannot allocate memory
+Aborted
+```
+
+Which means, with `-accel kvm`, it only can boot a VM which memory <= 1026G, but without these args, it can boot whatever you want.
+Steps to reproduce:
+1. sysctl vm.overcommit_memory=1  # enable overcommit first
+2. qemu-system-x86_64 -m 1027G -accel kvm -vnc :1
+Additional information:
+The qemu I use is compiled from the latest source, not the package provided by debian.
+
+Hardware is `PowerEdge R630` with `E5-2630 v4` * 2, 128G physical RAM.