diff options
Diffstat (limited to '')
| -rw-r--r-- | results/classifier/108/other/289 | 16 | ||||
| -rw-r--r-- | results/classifier/108/other/2890 | 16 | ||||
| -rw-r--r-- | results/classifier/108/other/2891 | 16 | ||||
| -rw-r--r-- | results/classifier/108/other/2892 | 16 | ||||
| -rw-r--r-- | results/classifier/108/other/2894 | 40 | ||||
| -rw-r--r-- | results/classifier/108/other/2895 | 45 | ||||
| -rw-r--r-- | results/classifier/108/other/2896 | 16 | ||||
| -rw-r--r-- | results/classifier/108/other/2898 | 130 | ||||
| -rw-r--r-- | results/classifier/108/other/2899 | 51 |
9 files changed, 346 insertions, 0 deletions
diff --git a/results/classifier/108/other/289 b/results/classifier/108/other/289 new file mode 100644 index 000000000..e070b3c00 --- /dev/null +++ b/results/classifier/108/other/289 @@ -0,0 +1,16 @@ +device: 0.912 +performance: 0.882 +graphic: 0.540 +semantic: 0.513 +PID: 0.462 +other: 0.432 +permissions: 0.420 +debug: 0.348 +network: 0.300 +boot: 0.268 +files: 0.237 +vnc: 0.125 +KVM: 0.040 +socket: 0.018 + +Guest freezes until there is a keyboard input on Windows version diff --git a/results/classifier/108/other/2890 b/results/classifier/108/other/2890 new file mode 100644 index 000000000..f66c38375 --- /dev/null +++ b/results/classifier/108/other/2890 @@ -0,0 +1,16 @@ +device: 0.772 +semantic: 0.596 +other: 0.481 +performance: 0.377 +graphic: 0.358 +vnc: 0.350 +boot: 0.318 +files: 0.295 +debug: 0.241 +permissions: 0.222 +KVM: 0.201 +socket: 0.145 +PID: 0.134 +network: 0.014 + +RFE: Individual ON_SHUTDOWN diff --git a/results/classifier/108/other/2891 b/results/classifier/108/other/2891 new file mode 100644 index 000000000..02d28fc0e --- /dev/null +++ b/results/classifier/108/other/2891 @@ -0,0 +1,16 @@ +device: 0.872 +performance: 0.736 +network: 0.736 +graphic: 0.483 +permissions: 0.433 +socket: 0.390 +files: 0.379 +debug: 0.351 +semantic: 0.346 +boot: 0.232 +other: 0.118 +PID: 0.114 +vnc: 0.057 +KVM: 0.005 + +qemu-system-x86_64 segfaults when executing ipxe selftests diff --git a/results/classifier/108/other/2892 b/results/classifier/108/other/2892 new file mode 100644 index 000000000..2e6b272b3 --- /dev/null +++ b/results/classifier/108/other/2892 @@ -0,0 +1,16 @@ +device: 0.791 +other: 0.362 +boot: 0.321 +permissions: 0.232 +semantic: 0.213 +debug: 0.193 +performance: 0.161 +PID: 0.145 +vnc: 0.134 +graphic: 0.126 +socket: 0.077 +network: 0.048 +files: 0.040 +KVM: 0.008 + +Outdated documentation about MicroVMs diff --git a/results/classifier/108/other/2894 b/results/classifier/108/other/2894 new file mode 100644 index 000000000..4fb09b81f --- /dev/null +++ b/results/classifier/108/other/2894 @@ -0,0 +1,40 @@ +permissions: 0.906 +device: 0.895 +other: 0.883 +network: 0.870 +files: 0.865 +graphic: 0.856 +semantic: 0.851 +boot: 0.850 +performance: 0.839 +KVM: 0.814 +socket: 0.809 +debug: 0.808 +PID: 0.796 +vnc: 0.737 + +There is a bug in versions 2025-02-10 and later that causes virtual machines to be created with incorrect SMP settings with warnings about TCG features when setting more than 2 cores with the smp option in the default TCG acceleration (see main text). +Description of problem: +When using qemu-system-x86_64 in versions 9.2.50 and later, if you create a virtual machine with 2 or more cores using the smp option, + +``` +qemu-system-x86_64: warning: TCG doesn't support requested feature: CPUID.01H:EDX.ht [bit 28] +qemu-system-x86_64: warning: TCG doesn't support requested feature: CPUID.80000001H:ECX.cmp-legacy [bit 1] +``` +The log will be displayed as many as the number of cores you have enabled, and the created virtual machine will be displayed as having a 1-core CPU with the number of cores you have enabled. +* I have not tested whether the same symptom occurs on versions 9.2.50 and later for other environments (Linux and the WoA version released on March 26th). +Steps to reproduce: +1. Create a virtual machine with more than two cores using TCG acceleration, which is the default acceleration, by using options such as 'qemu-system-x86_64 -smp 2' or 'qemu-system-x86_64 -smp sockets=1,cores=2,threads=1'. +2. 'qemu-system-x86_64: warning: TCG doesn't support requested feature: CPUID.01H:EDX.ht [bit 28]' and +'qemu-system-x86_64: warning: TCG doesn't support requested feature: CPUID.80000001H:ECX.cmp-legacy [bit 1]' +The log is generated as many as the number of cores set and the virtual machine is created. +3. When checking the CPU information of the booted virtual machine, it does not show that there is one CPU with the specified number of cores, but rather that there is a single core CPU with the specified number of cores. +Additional information: +``` +>qemu-system-x86_64 -M q35 -smp 2 -m 4g -display sdl -usb -device usb-tablet -drive file=MasterOS.vdi,id=disk,if=none -drive file="C:\Program Files\qemu\share\edk2-x86_64-code.fd",id=efi,readonly=on,format=raw,if=pflash -device ahci,id=ahci -device ide-hd,drive=disk,bus=ahci.1 -rtc base=localtime +``` + +``` +>qemu-system-x86_64 -M q35 -smp 4 -m 4g -display sdl -usb -device usb-tablet -drive file=MasterOS.vdi,id=disk,if=none -drive file="C:\Program Files\qemu\share\edk2-x86_64-code.fd",id=efi,readonly=on,format=raw,if=pflash -device ahci,id=ahci -device ide-hd,drive=disk,bus=ahci.1 -rtc base=localtime +``` + diff --git a/results/classifier/108/other/2895 b/results/classifier/108/other/2895 new file mode 100644 index 000000000..e90c297c6 --- /dev/null +++ b/results/classifier/108/other/2895 @@ -0,0 +1,45 @@ +graphic: 0.729 +performance: 0.646 +debug: 0.521 +device: 0.435 +files: 0.274 +semantic: 0.240 +vnc: 0.199 +PID: 0.187 +socket: 0.158 +boot: 0.157 +network: 0.135 +permissions: 0.064 +other: 0.030 +KVM: 0.023 + +qemu-system-aarch64: Error: r = HV_BAD_ARGUMENT (0xfae94003, at ../target/arm/hvf/hvf.c:2259) +Description of problem: +When I launch a Linux guest in QEMU with `-accel hvf` + `-gdb "tcp::1234"`, and I try to debug the kernel with `lldb`, QEMU crashes with the following report: + +``` +qemu-system-aarch64: Error: r = HV_BAD_ARGUMENT (0xfae94003, at ../target/arm/hvf/hvf.c:2259) +``` +Steps to reproduce: +1. Run QEMU with `-accel hvf` + `-gdb "tcp::1234"` and a custom kernel (`-kernel Image`) +2. Try to attach using `lldb vmlinux` + `(lldb) gdb-remote 1234` +Additional information: +Debugging QEMU I see the crash is due to the `cpu->accel->fd` file descriptor being `0`: + +``` +warning: qemu-system-aarch64 was compiled with optimization - stepping may behave oddly; variables may not be available. +frame #4: 0x00000001003dd24c qemu-system-aarch64`hvf_arch_update_guest_debug [inlined] hvf_put_guest_debug_registers(cpu=0x0000000158118000) at hvf.c:2259:9 [opt] + 2256 for (i = 0; i < max_hw_bps; i++) { + 2257 r = hv_vcpu_set_sys_reg(cpu->accel->fd, dbgbcr_regs[i], + 2258 env->cp15.dbgbcr[i]); +-> 2259 assert_hvf_ok(r); + 2260 r = hv_vcpu_set_sys_reg(cpu->accel->fd, dbgbvr_regs[i], + 2261 env->cp15.dbgbvr[i]); + 2262 assert_hvf_ok(r); +(lldb) print cpu->accel->fd +(hvf_vcpuid) 0 +(lldb) print dbgbcr_regs[i] +(const uint16_t) 32773 +(lldb) print env->cp15.dbgbcr[i] +(uint64_t) 480 +``` diff --git a/results/classifier/108/other/2896 b/results/classifier/108/other/2896 new file mode 100644 index 000000000..9be5cb90a --- /dev/null +++ b/results/classifier/108/other/2896 @@ -0,0 +1,16 @@ +device: 0.771 +network: 0.541 +performance: 0.490 +debug: 0.259 +boot: 0.249 +graphic: 0.215 +permissions: 0.208 +socket: 0.136 +semantic: 0.133 +vnc: 0.126 +other: 0.100 +files: 0.089 +KVM: 0.045 +PID: 0.037 + +How to enable MPU support on Cortex-R5F? diff --git a/results/classifier/108/other/2898 b/results/classifier/108/other/2898 new file mode 100644 index 000000000..e792f0233 --- /dev/null +++ b/results/classifier/108/other/2898 @@ -0,0 +1,130 @@ +other: 0.945 +device: 0.935 +performance: 0.928 +boot: 0.920 +permissions: 0.920 +debug: 0.909 +socket: 0.908 +semantic: 0.905 +vnc: 0.903 +graphic: 0.901 +PID: 0.899 +KVM: 0.897 +files: 0.895 +network: 0.887 + +-M virt,dumpdtb is missing information from the device tree +Description of problem: +dumpdtb no longer produces a device tree with the full system described. + + +``` +$ dtc -I dtb -O dts test.dtb +<stdout>: Warning (unit_address_vs_reg): /soc/pci@30000000: node has a unit name, but no reg or ranges property +<stdout>: Warning (simple_bus_reg): /soc/pci@30000000: missing or empty reg/ranges property +/dts-v1/; + +/ { + #address-cells = <0x02>; + #size-cells = <0x02>; + compatible = "riscv-virtio"; + model = "riscv-virtio,qemu"; + + pmu { + riscv,event-to-mhpmcounters = <0x01 0x01 0x7fff9 0x02 0x02 0x7fffc 0x10019 0x10019 0x7fff8 0x1001b 0x1001b 0x7fff8 0x10021 0x10021 0x7fff8>; + compatible = "riscv,pmu"; + }; + + fw-cfg@10100000 { + dma-coherent; + reg = <0x00 0x10100000 0x00 0x18>; + compatible = "qemu,fw-cfg-mmio"; + }; + + flash@20000000 { + bank-width = <0x04>; + reg = <0x00 0x20000000 0x00 0x2000000 0x00 0x22000000 0x00 0x2000000>; + compatible = "cfi-flash"; + }; + + aliases { + }; + + chosen { + rng-seed = <0xd4266784 0xc7a7c66f 0xd5b7347d 0x862188f3 0x78065a8e 0xebdedae5 0xd77c47b0 0x34d31eff>; + }; + + soc { + #address-cells = <0x02>; + #size-cells = <0x02>; + compatible = "simple-bus"; + ranges; + + pci@30000000 { + }; + }; +}; +``` +Steps to reproduce: +1. qemu-system-riscv64 -machine virt,dumpdtb=test.dtb +2. dtc -I dtb -O dts test.dtb +Additional information: +The regression was introduced in https://gitlab.com/qemu-project/qemu/-/commit/8fd2518ef2f8d. If this commit is reverted, the expected behavior returns. + +``` +dtc -I dtb -O dts test.dtb | grep "@" + platform-bus@4000000 { + memory@80000000 { + cpu@0 { + fw-cfg@10100000 { + flash@20000000 { + serial0 = "/soc/serial@10000000"; + stdout-path = "/soc/serial@10000000"; + rtc@101000 { + serial@10000000 { + clock-frequency = "", "8@"; + test@100000 { + virtio_mmio@10008000 { + virtio_mmio@10007000 { + virtio_mmio@10006000 { + virtio_mmio@10005000 { + virtio_mmio@10004000 { + virtio_mmio@10003000 { + virtio_mmio@10002000 { + virtio_mmio@10001000 { + plic@c000000 { + clint@2000000 { + pci@30000000 { +``` + +Other machines are affected to a lesser degree. The arm virt machine: + +qemu-system-arm -machine virt,dumpdtb=test.dtb +``` +@@ -8,28 +8,6 @@ + #address-cells = <0x02>; + compatible = "linux,dummy-virt"; + +- psci { +- migrate = <0x84000005>; +- cpu_on = <0x84000003>; +- cpu_off = <0x84000002>; +- cpu_suspend = <0x84000001>; +- method = "hvc"; +- compatible = "arm,psci-1.0", "arm,psci-0.2", "arm,psci"; +- }; +- +- memory@40000000 { +- reg = <0x00 0x40000000 0x00 0x8000000>; +- device_type = "memory"; +- }; +- +- platform-bus@c000000 { +- interrupt-parent = <0x8002>; +- ranges = <0x00 0x00 0xc000000 0x2000000>; +- #address-cells = <0x01>; +- #size-cells = <0x01>; +- compatible = "qemu,platform", "simple-bus"; +- }; +- +``` diff --git a/results/classifier/108/other/2899 b/results/classifier/108/other/2899 new file mode 100644 index 000000000..c62f8aed7 --- /dev/null +++ b/results/classifier/108/other/2899 @@ -0,0 +1,51 @@ +performance: 0.865 +graphic: 0.792 +device: 0.661 +files: 0.653 +semantic: 0.590 +debug: 0.582 +socket: 0.443 +vnc: 0.425 +PID: 0.410 +network: 0.381 +other: 0.241 +boot: 0.229 +permissions: 0.207 +KVM: 0.070 + +Regression 10.0.0rc1: Segmentation fault on executing QEMU advent calendar 2014, day 4 +Description of problem: +On executing QEMU, a segmentation fault occurs +Steps to reproduce: +1. Download https://www.qemu-advent-calendar.org/2014/download/stxmas.tar.xz +2. Execute with QEMU command line +Additional information: +git bisect finishes with: + +``` +456709db50f424d112bc5f07260fdc51555f3a24 is the first bad commit +commit 456709db50f424d112bc5f07260fdc51555f3a24 +Author: Paolo Bonzini <pbonzini@redhat.com> +Date: Sun Dec 15 10:06:10 2024 +0100 + + target/i386: execute multiple REP/REPZ iterations without leaving TB + + Use a TCG loop so that it is not necessary to go through the setup steps + of REP and through the I/O check on every iteration. Interestingly, this + is not a particularly effective optimization on its own, though it avoids + the cost of correct RF emulation that was added in the previous patch. + The main benefit lies in allowing the hoisting of loop invariants outside + the loop, which will happen separately. + + The loop exits when the low 16 bits of CX/ECX/RCX are zero (so generally + speaking the string operation runs in 65536 iteration batches) to give + the main loop an opportunity to pick up interrupts. + + Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> + Reviewed-by: Richard Henderson <richard.henderson@linaro.org> + Link: https://lore.kernel.org/r/20241215090613.89588-12-pbonzini@redhat.com + Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> + + target/i386/tcg/translate.c | 55 ++++++++++++++++++++++++++++++++++++++++----- + 1 file changed, 49 insertions(+), 6 deletions(-) +``` |