6 files changed, 260 insertions, 0 deletions
diff --git a/results/classifier/108/other/255 b/results/classifier/108/other/255
new file mode 100644
index 00000000..f25a7c95
--- /dev/null
+++ b/results/classifier/108/other/255
@@ -0,0 +1,16 @@
+debug: 0.813
+performance: 0.751
+device: 0.591
+graphic: 0.552
+semantic: 0.501
+boot: 0.159
+other: 0.077
+permissions: 0.052
+network: 0.035
+PID: 0.031
+files: 0.018
+socket: 0.012
+vnc: 0.008
+KVM: 0.002
+
+Build on sparc64 fails with "undefined reference to `fdt_check_full'"
diff --git a/results/classifier/108/other/2552 b/results/classifier/108/other/2552
new file mode 100644
index 00000000..e09c5e1c
--- /dev/null
+++ b/results/classifier/108/other/2552
@@ -0,0 +1,87 @@
+network: 0.789
+KVM: 0.661
+graphic: 0.616
+semantic: 0.602
+device: 0.561
+socket: 0.532
+performance: 0.503
+permissions: 0.431
+PID: 0.385
+other: 0.385
+vnc: 0.351
+debug: 0.254
+boot: 0.232
+files: 0.198
+
+system libfdt said to be too old (1.5.1 min required) but 1.7.1 is installed.
+Description of problem:
+<--
+I am running an update build of the latest qemu version 9.0.2 to update it from 8.1.2 in the IPFire firewall distribution.
+The build command being run was
+
+`
+./configure \
+	--prefix=/usr \
+	--sysconfdir=/etc \
+	--localstatedir=/var \
+	--enable-kvm \
+	--disable-attr \
+	--target-list="$(TARGETS)" \
+	--extra-cflags="$(CFLAGS)" \
+	--enable-spice \
+	--enable-usb-redir \
+	--enable-seccomp \
+	--disable-docs \
+	--disable-sdl \
+	--enable-slirp 
+`
+
+and where $TARGETS is
+
+`	x86_64-linux-user \
+	aarch64-linux-user \
+	riscv64-linux-user \
+	x86_64-softmmu \
+	aarch64-softmmu \
+	riscv64-softmmu
+`
+
+and $CFLAGS is
+
+`	"-O2"
+	"-g0"
+	"-pipe"
+	"-Wall"
+	"-fexceptions"
+	"-fPIC"
+	"-Wp,-U_FORTIFY_SOURCE"
+	"-Wp,-D_FORTIFY_SOURCE=3"
+	"-Wp,-D_GLIBCXX_ASSERTIONS"
+	"-fstack-protector-strong"
+	"-fstack-clash-protection"
+` 
+
+This built qemu successfully with version 8.1.2 and earlier versions.
+
+From version 9.0.1 onwards the subproject dtc has been removed from the Source Tarball and the build came back with the error message
+
+Library fdt found: NO
+
+../meson.build:3190:18: ERROR: Git command failed: ['/usr/bin/git', 'fetch', '--depth', '1', 'origin', 'b6910bec11614980a21e46fbccc35934b671bd81']
+
+The git command failed as the distribution build is done with no network connection. All packages have to be available in the build and so the package cannot be downloaded during the build.
+
+Therefore I moved the dtc package in the IPFire build to before building qemu and added --disable-download to the ./configure options.
+
+The error message changed to
+
+Library fdt found: YES
+
+../meson.build:3182:7: ERROR: Problem encountered: system libfdt requested, but it is too old (1.5.1 or newer required)
+
+However the dtc libfdt version is 1.7.1 - definitely newer than 1.5.1
+
+Why is the version being seen as too old?
+How do I get this to detect the dtc libfdt version correctly (it has detected that libfdt is present in the IPFire build environment).
+
+-->
diff --git a/results/classifier/108/other/2554 b/results/classifier/108/other/2554
new file mode 100644
index 00000000..facba6e4
--- /dev/null
+++ b/results/classifier/108/other/2554
@@ -0,0 +1,26 @@
+debug: 0.914
+graphic: 0.801
+performance: 0.792
+device: 0.707
+vnc: 0.643
+network: 0.564
+semantic: 0.519
+PID: 0.396
+permissions: 0.385
+boot: 0.382
+socket: 0.368
+files: 0.242
+KVM: 0.182
+other: 0.170
+
+qemu-system-arm: thumb2: vector table branch instruction not followed
+Description of problem:
+When an undefined instruction is hit and causes an exception that causes a jump to the undef vector at 0x04; translation of the branch instruction found there appears to fail since instead of branching to the handler it steps to the next instruction - the next entry in the vector table, translates that, and on stepping once again moves to the next entry in the vector table. Eventually it steps out of the table and (re)enters the _start subroutine pointed to by vector 0x0.
+Steps to reproduce:
+This is related to issue #2542 in as much as I am hunting down failures in the picolibc 1.8.6 test suite on Debian. After fixing issues such as the failure to enable the MMU and some others via incorporating upstream commits I'm left with 10 tests, all for exception handling, that result in meson (build system) TIMEOUT instead of EXPECTEDFAIL. All of these tests should fail instantly and cause Qemu to exit but it continues - apparently spinning in an endless loop as described above until meson kills it.
+
+Creating a small reproducer has proved challenging and nigh impossible (for me) - even identifying the crux as described here has taken 4 days. However with the help of `qemu-system-arm -d in_asm,op,out_asm ...` and `gdb-multiarch` I believe I may have produced a focused report that will help figure this out.
+
+#
+Additional information:
+Since this is hard to debug I can give remote ssh access via `tmate` to directly control the debug session if necessary.
diff --git a/results/classifier/108/other/2555 b/results/classifier/108/other/2555
new file mode 100644
index 00000000..a1e35387
--- /dev/null
+++ b/results/classifier/108/other/2555
@@ -0,0 +1,35 @@
+graphic: 0.860
+device: 0.666
+performance: 0.642
+semantic: 0.596
+network: 0.432
+PID: 0.361
+permissions: 0.295
+vnc: 0.290
+socket: 0.285
+debug: 0.245
+boot: 0.175
+other: 0.129
+KVM: 0.095
+files: 0.033
+
+Can't start a guest with 2 IOAPICs
+Description of problem:
+For a host with multiple IOAPICs, I want to start a guest with 2 IOAPICs. I saw this commit about this function: **[x86: add support for second ioapic]**:
+     https://gitlab.com/qemu-project/qemu/-/commit/94c5a606379ddd04beecdb11fb34b51b4b28c7f2
+
+But after I started a guest in a host with multiple IOAPICs, there was still only one IOAPIC in guest. How should I enable this feature?
+Additional information:
+Host IOAPICs Info:
+   ```
+[    1.268280] IOAPIC[0]: apic_id 0, version 33, address 0xfec00000, GSI 0-23
+[    1.268286] IOAPIC[1]: apic_id 1, version 33, address 0xfec20000, GSI 24-55
+[    1.268291] IOAPIC[2]: apic_id 2, version 33, address 0xd9000000, GSI 56-87
+[    4.415313] ACPI: Using IOAPIC for interrupt routing
+   ```
+
+Guest IOAPIC Info:
+   ```
+[    0.000000] IOAPIC[0]: apic_id 0, version 17, address 0xfec00000, GSI 0-23
+[    0.255045] ACPI: Using IOAPIC for interrupt routing
+   ```
diff --git a/results/classifier/108/other/2557 b/results/classifier/108/other/2557
new file mode 100644
index 00000000..3fb987ae
--- /dev/null
+++ b/results/classifier/108/other/2557
@@ -0,0 +1,16 @@
+boot: 0.627
+graphic: 0.480
+performance: 0.424
+vnc: 0.293
+debug: 0.242
+KVM: 0.197
+PID: 0.159
+other: 0.130
+device: 0.122
+semantic: 0.081
+network: 0.037
+permissions: 0.008
+files: 0.005
+socket: 0.003
+
+balloon size startup parameter needed
diff --git a/results/classifier/108/other/2558 b/results/classifier/108/other/2558
new file mode 100644
index 00000000..8e3315c3
--- /dev/null
+++ b/results/classifier/108/other/2558
@@ -0,0 +1,80 @@
+other: 0.893
+permissions: 0.875
+device: 0.871
+graphic: 0.859
+files: 0.847
+boot: 0.829
+performance: 0.829
+PID: 0.824
+KVM: 0.819
+socket: 0.815
+vnc: 0.809
+debug: 0.798
+semantic: 0.794
+network: 0.756
+
+riscv64: Ubuntu doesn't boot with EDK2, although it boots with u-boot
+Description of problem:
+Ubuntu doesn't boot with `edk2-riscv-code.fd`:
+
+```bash
+wget https://cloud-images.ubuntu.com/noble/20240822/noble-server-cloudimg-riscv64.img
+
+qemu-system-riscv64 -M virt -m 2048 -nographic -hda noble-server-cloudimg-riscv64.img \
+  -drive if=pflash,format=raw,readonly=on,file=/usr/local/share/qemu/edk2-riscv-code.fd
+```
+
+
+```
+Loading Linux 6.8.0-41-generic ...
+Loading initial ramdisk ...
+InstallProtocolInterface: 4006C0C1-FCB3-403E-996D-4A6C8724E06D FDB3F3C8
+InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B FDB3F380
+[Security] 3rd party image[0] can be loaded after EndOfDxe: MemoryMapped(0x2,0xF9CC4000,0xFC194000).
+InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B FF29C2C0
+Loading driver at 0x000F732C000 EntryPoint=0x000F817FEA6 
+InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF FF29CC18
+ProtectUefiImageCommon - 0xFF29C2C0
+  - 0x00000000F732C000 - 0x0000000002598000
+SetUefiImageMemoryAttributes - 0x00000000F732C000 - 0x0000000000001000 (0x0000000000004000)
+SetUefiImageMemoryAttributes - 0x00000000F732D000 - 0x0000000000FFF000 (0x0000000000020000)
+SetUefiImageMemoryAttributes - 0x00000000F832C000 - 0x0000000001598000 (0x0000000000004000)
+TimerDriverSetTimerPeriod(0x0)
+SetUefiImageMemoryAttributes - 0x00000000FFEC7000 - 0x000000000000C000 (0x0000000000000000)
+SetUefiImageMemoryAttributes - 0x00000000FFEBC000 - 0x000000000000B000 (0x0000000000000000)
+SetUefiImageMemoryAttributes - 0x00000000FFEAC000 - 0x0000000000010000 (0x0000000000000000)
+SetUefiImageMemoryAttributes - 0x00000000FFEA1000 - 0x000000000000B000 (0x0000000000000000)
+SetUefiImageMemoryAttributes - 0x00000000FFE84000 - 0x000000000001D000 (0x0000000000000000)
+SetUefiImageMemoryAttributes - 0x00000000FFE79000 - 0x000000000000B000 (0x0000000000000000)
+SetUefiImageMemoryAttributes - 0x00000000FFE6E000 - 0x000000000000B000 (0x0000000000000000)
+SetUefiImageMemoryAttributes - 0x00000000FFE63000 - 0x000000000000B000 (0x0000000000000000)
+SetUefiImageMemoryAttributes - 0x00000000FFE59000 - 0x000000000000A000 (0x0000000000000000)
+(hangs here)
+```
+
+The same disk image still boots when `uboot.elf` is specified as the kernel image:
+
+```bash
+wget https://github.com/lima-vm/u-boot-qemu-mirror/releases/download/2023.07%2Bdfsg-1/qemu-riscv64_smode_uboot.elf
+
+qemu-system-riscv64 -M virt -m 2048 -nographic -hda noble-server-cloudimg-riscv64.img \
+  -kernel qemu-riscv64_smode_uboot.elf
+```
+
+```
+Loading Linux 6.8.0-41-generic ...
+Loading initial ramdisk ...
+syscon-poweroff poweroff: pm_power_off already claimed for sbi_srst_power_off
+-.mount
+etc-machine\x2did.mount
+systemd-journald.service
+dev-hugepages.mount
+...
+Ubuntu 24.04 LTS ubuntu ttyS0
+
+ubuntu login:
+```
+Steps to reproduce:
+See above
+Additional information:
+