diff options
Diffstat (limited to '')
| -rw-r--r-- | results/classifier/118/none/200 | 31 | ||||
| -rw-r--r-- | results/classifier/118/none/2003 | 45 | ||||
| -rw-r--r-- | results/classifier/118/none/2005 | 59 | ||||
| -rw-r--r-- | results/classifier/118/none/2009 | 31 |
4 files changed, 166 insertions, 0 deletions
diff --git a/results/classifier/118/none/200 b/results/classifier/118/none/200 new file mode 100644 index 00000000..e1d07156 --- /dev/null +++ b/results/classifier/118/none/200 @@ -0,0 +1,31 @@ +device: 0.552 +performance: 0.491 +arm: 0.479 +network: 0.463 +architecture: 0.426 +ppc: 0.426 +PID: 0.425 +semantic: 0.340 +TCG: 0.333 +boot: 0.308 +debug: 0.287 +socket: 0.280 +risc-v: 0.279 +graphic: 0.265 +vnc: 0.248 +register: 0.237 +peripherals: 0.225 +files: 0.214 +permissions: 0.200 +VMM: 0.178 +virtual: 0.150 +i386: 0.135 +kernel: 0.116 +x86: 0.107 +hypervisor: 0.099 +mistranslation: 0.079 +KVM: 0.053 +user-level: 0.038 +assembly: 0.022 + +Add Python linters (mypy, pylint, isort, flake8) to Gitlab CI diff --git a/results/classifier/118/none/2003 b/results/classifier/118/none/2003 new file mode 100644 index 00000000..2ef50936 --- /dev/null +++ b/results/classifier/118/none/2003 @@ -0,0 +1,45 @@ +graphic: 0.636 +device: 0.408 +boot: 0.391 +user-level: 0.303 +debug: 0.278 +performance: 0.248 +x86: 0.229 +PID: 0.192 +permissions: 0.192 +semantic: 0.188 +ppc: 0.179 +vnc: 0.164 +register: 0.135 +risc-v: 0.106 +mistranslation: 0.101 +architecture: 0.101 +socket: 0.098 +VMM: 0.089 +files: 0.086 +network: 0.072 +hypervisor: 0.065 +i386: 0.064 +TCG: 0.052 +peripherals: 0.051 +virtual: 0.051 +assembly: 0.047 +arm: 0.041 +KVM: 0.029 +kernel: 0.020 + +Windows guest boot happens blue screen and crash by using "-cpu Skylake-Server,+la57,phys-bits=52" +Description of problem: +We are verifying 5-level paging enabling on Windows guest. After creating Windows guest, the system boot caused blue screen and no screen interface response. + +Same QEMU parameter without **+la57,phys-bits=52** (i.e., `./qemu-system-x86_64 -accel kvm -smp 4 -m 4096 -machine q35 -drive file=Winvm5l_host5l_ept5_1698034398,if=none,id=virtio-disk0 -device virtio-blk-pci,drive=virtio-disk0,bootindex=0 -cpu Skylake-Server -monitor pty -daemonize -vnc :40541 -device virtio-net-pci,netdev=nic0,mac=00:5b:0b:59:0d:26 -netdev tap,id=nic0,br=virbr0,helper=/usr/local/libexec/qemu-bridge-helper,vhost=on`), the same Windows image can be booted successfully. Initially suspected this new QEMU release does not support 5-level paging related features. +Steps to reproduce: +1. Create guest by using the command + +``` +./qemu-system-x86_64 -accel kvm -smp 4 -m 4096 -machine q35 -drive file=Winvm5l_host5l_ept5_1698034398,if=none,id=virtio-disk0 -device virtio-blk-pci,drive=virtio-disk0,bootindex=0 -cpu Skylake-Server,+la57,phys-bits=52 -monitor pty -daemonize -vnc :40541 -device virtio-net-pci,netdev=nic0,mac=00:5b:0b:59:0d:26 -netdev tap,id=nic0,br=virbr0,helper=/usr/local/libexec/qemu-bridge-helper,vhost=on +``` +Additional information: +Suspected to be a QEMU regression issue, the first bad commit id: 14f5a7bae4cb5ca45a03e16b5bb0c5d766fd51b7. + +Latest successful version commit id: cea3ea670fe265421131aad90c36fbb87bc4d206 diff --git a/results/classifier/118/none/2005 b/results/classifier/118/none/2005 new file mode 100644 index 00000000..37872fcf --- /dev/null +++ b/results/classifier/118/none/2005 @@ -0,0 +1,59 @@ +user-level: 0.742 +mistranslation: 0.736 +ppc: 0.704 +vnc: 0.658 +TCG: 0.655 +performance: 0.653 +KVM: 0.650 +arm: 0.624 +architecture: 0.613 +permissions: 0.613 +register: 0.613 +device: 0.611 +peripherals: 0.610 +risc-v: 0.607 +x86: 0.600 +graphic: 0.596 +debug: 0.587 +virtual: 0.578 +VMM: 0.574 +semantic: 0.570 +PID: 0.548 +socket: 0.540 +assembly: 0.535 +hypervisor: 0.530 +files: 0.515 +kernel: 0.514 +network: 0.512 +boot: 0.500 +i386: 0.487 + +qemu-system-aarch64: ../target/arm/helper.c:6757: sve_vqm1_for_el_sm: Assertion `sm' failed. +Description of problem: +Qemu crashes when sve is completely disabled for CPU model "max" (`-cpu max,sve=off`). Using any CPU model which does not include SVE, or using only e.g. SVE128 (`-cpu max,sve128=on`) works fine.\ +\ +`#0 0x00007f94b8291dec in __pthread_kill_implementation () at /lib64/libc.so.6 `\ +`#1 0x00007f94b823f0c6 in raise () at /lib64/libc.so.6 `\ +`#2 0x00007f94b82268d7 in abort () at /lib64/libc.so.6 `\ +`#3 0x00007f94b82267eb in _nl_load_domain.cold () at /lib64/libc.so.6 `\ +`#4 0x00007f94b8237016 in () at /lib64/libc.so.6 `\ +`#5 0x000055d6794aa698 in sve_vqm1_for_el_sm (env=env@entry=0x55d67c6ff9b0, el=el@entry=1, sm=false) at ../target/arm/helper.c:6757 `\ +`#6 0x000055d6794afc29 in sve_vqm1_for_el (el=1, env=0x55d67c6ff9b0) at ../target/arm/helper.c:6763 `\ +`#7 smcr_write (env=0x55d67c6ff9b0, ri=0x55d67c78f600, value=<optimized out>) at ../target/arm/helper.c:6887 `\ +`#8 0x00007f9469bad101 in code_gen_buffer () `\ +`#9 0x000055d67977dc19 in cpu_tb_exec (cpu=cpu@entry=0x55d67c6fd1f0, itb=<optimized out>, tb_exit=tb_exit@entry=0x7f94acdcc4c4) at ../accel/tcg/cpu-exec.c:457 `\ +`#10 0x000055d67977e59f in cpu_loop_exec_tb (tb_exit=0x7f94acdcc4c4, last_tb=<synthetic pointer>, pc=<optimized out>, tb=<optimized out>, cpu=<optimized out>) at ../accel/tcg/cpu-exec.c:919 `\ +`#11 cpu_exec_loop (cpu=cpu@entry=0x55d67c6fd1f0, sc=sc@entry=0x7f94acdcc570) at ../accel/tcg/cpu-exec.c:1040 `\ +`#12 0x000055d67977ee7d in cpu_exec_setjmp (cpu=0x55d67c6fd1f0, sc=0x7f94acdcc570) at ../accel/tcg/cpu-exec.c:1057 `\ +`#13 0x000055d679787c3d in cpu_exec (cpu=0x55d67c6fd1f0) at ../accel/tcg/cpu-exec.c:1083 `\ +`#14 0x000055d6797a1d52 in tcg_cpus_exec (cpu=0x55d67c6fd1f0) at ../accel/tcg/tcg-accel-ops.c:75 `\ +`#15 mttcg_cpu_thread_fn (arg=arg@entry=0x55d67c6fd1f0) at ../accel/tcg/tcg-accel-ops-mttcg.c:95 `\ +`#16 0x000055d679938698 in qemu_thread_start (args=0x55d67c7a1500) at ../util/qemu-thread-posix.c:541 `\ +`#17 0x00007f94b828ff44 in start_thread () at /lib64/libc.so.6 `\ +`#18 0x00007f94b8318314 in clone () at /lib64/``libc.so``.6`\ + \ +This happens when the system is booting, i.e. grub has just finished, loaded kernel and initrd, and the kernel has just began to run, i.e. early in the kernel startup. +Steps to reproduce: +1. +2. +3. diff --git a/results/classifier/118/none/2009 b/results/classifier/118/none/2009 new file mode 100644 index 00000000..995bd825 --- /dev/null +++ b/results/classifier/118/none/2009 @@ -0,0 +1,31 @@ +kernel: 0.770 +network: 0.758 +device: 0.757 +arm: 0.684 +register: 0.673 +files: 0.657 +VMM: 0.616 +socket: 0.592 +architecture: 0.544 +mistranslation: 0.525 +debug: 0.516 +performance: 0.478 +boot: 0.461 +TCG: 0.436 +vnc: 0.400 +risc-v: 0.394 +PID: 0.389 +peripherals: 0.372 +assembly: 0.365 +hypervisor: 0.335 +semantic: 0.307 +graphic: 0.305 +KVM: 0.264 +user-level: 0.233 +permissions: 0.228 +x86: 0.223 +virtual: 0.213 +i386: 0.204 +ppc: 0.169 + +ld: warning: -undefined error is deprecated |