11 files changed, 324 insertions, 0 deletions
diff --git a/results/classifier/108/other/253 b/results/classifier/108/other/253
new file mode 100644
index 000000000..c6775f171
--- /dev/null
+++ b/results/classifier/108/other/253
@@ -0,0 +1,16 @@
+device: 0.902
+KVM: 0.895
+performance: 0.684
+other: 0.330
+graphic: 0.292
+semantic: 0.226
+debug: 0.178
+PID: 0.176
+permissions: 0.160
+vnc: 0.121
+boot: 0.098
+socket: 0.079
+network: 0.019
+files: 0.016
+
+Qemu Win98 VM with KVM videocard passthrough DOS mode video is not working for most of games..
diff --git a/results/classifier/108/other/2530 b/results/classifier/108/other/2530
new file mode 100644
index 000000000..73f304325
--- /dev/null
+++ b/results/classifier/108/other/2530
@@ -0,0 +1,32 @@
+device: 0.873
+graphic: 0.844
+vnc: 0.827
+files: 0.727
+PID: 0.610
+semantic: 0.568
+socket: 0.566
+network: 0.537
+permissions: 0.442
+debug: 0.431
+boot: 0.402
+other: 0.370
+performance: 0.317
+KVM: 0.192
+
+Duplicate ACPI _SUN
+Description of problem:
+ACPI _SUN is `the slot-unique ID number for a slot`, but qemu uses `PCI_SLOT()` which is definitely not unique
+https://gitlab.com/qemu-project/qemu/-/blob/407f9a4b121eb65166375c410e14d7b704bc1106/hw/i386/acpi-build.c#L524
+Steps to reproduce:
+1. Create a linux VM with 2 virtio NICs
+2. Look at the ACPI _SUN of the virtio-pci devices (firmware_node/sun)
+
+Both virtio-pci devices have _SUN == 0
+```
+#
+Additional information:
+In systemd we recently introduced code to use firmware_node/sun information for NIC naming
+https://github.com/systemd/systemd/commit/0a4ecc54cb9f2d3418b970c51bfadb69c34ae9eb
+
+but having duplicate _SUN is of course problematic
+https://github.com/systemd/systemd/issues/34082
diff --git a/results/classifier/108/other/2531 b/results/classifier/108/other/2531
new file mode 100644
index 000000000..60c5e2a56
--- /dev/null
+++ b/results/classifier/108/other/2531
@@ -0,0 +1,75 @@
+device: 0.898
+files: 0.879
+PID: 0.751
+debug: 0.747
+graphic: 0.729
+performance: 0.727
+boot: 0.699
+vnc: 0.681
+socket: 0.656
+semantic: 0.625
+other: 0.534
+network: 0.501
+permissions: 0.495
+KVM: 0.353
+
+QEMU internal SIGSEGV when creating an x86_64 Debian chroot from an aarch64 host.
+Description of problem:
+When I try to create a x86_64 Debian chroot using debootstrap from an aarch64 host system, QEMU segfaults causing the process to fail.
+Steps to reproduce:
+1. Run `sudo apt install debootstrap qemu-user-static binfmt-support`
+2. Run `sudo debootstrap --arch amd64 bookworm debian_chroot http://deb.debian.org/debian/`
+Additional information:
+End of deboostrap output:
+```
+I: Configuring dash...
+I: Configuring libpam-modules:amd64...
+I: Configuring grep...
+I: Configuring perl-base...
+I: Configuring gzip...
+I: Configuring passwd...
+I: Configuring login...
+I: Configuring apt...
+I: Configuring adduser...
+I: Configuring libc-bin...
+W: Failure while configuring required packages.
+W: See /home/allen/debian_chroot/debootstrap/debootstrap.log for details (possibly the package passwd is at fault)
+```
+
+End of debootstrap log:
+```
+$ tail /home/allen/debian_chroot/debootstrap/debootstrap.log -n30
+Setting up grep (3.8-5) ...
+Setting up perl-base (5.36.0-7+deb12u1) ...
+Setting up gzip (1.12-1) ...
+Setting up passwd (1:4.13+dfsg1-1+b1) ...
+x86_64-binfmt-P: QEMU internal SIGSEGV {code=MAPERR, addr=0x20}
+Segmentation fault
+groupadd: group 'shadow' already exists
+Group ID 42 has been allocated for the shadow group.  You have either
+used 42 yourself or created a shadow group with a different ID.
+Please correct this problem and reconfigure with dpkg --configure passwd''.
+
+Note that both user and group IDs in the range 0-99 are globally
+allocated by the Debian project and must be the same on every Debian
+system.
+dpkg: error processing package passwd (--configure):
+ installed passwd package post-installation script subprocess returned error exit status 1
+Setting up libpam-runtime (1.5.2-6+deb12u1) ...
+Setting up login (1:4.13+dfsg1-1+b1) ...
+dpkg: apt: dependency problems, but configuring anyway as you requested:
+ apt depends on adduser.
+
+Setting up apt (2.6.1) ...
+dpkg: adduser: dependency problems, but configuring anyway as you requested:
+ adduser depends on passwd; however:
+  Package passwd is not configured yet.
+
+Setting up adduser (3.134) ...
+Processing triggers for libc-bin (2.36-9+deb12u7) ...
+Errors were encountered while processing:
+ passwd
+```
+
+Full debootstrap log:
+[debootstrap.log](/uploads/4eb24abd98a647e08bd03deea897b9dd/debootstrap.log)
diff --git a/results/classifier/108/other/2532 b/results/classifier/108/other/2532
new file mode 100644
index 000000000..84daf7589
--- /dev/null
+++ b/results/classifier/108/other/2532
@@ -0,0 +1,55 @@
+graphic: 0.735
+other: 0.633
+semantic: 0.628
+PID: 0.587
+permissions: 0.586
+debug: 0.586
+performance: 0.574
+files: 0.529
+network: 0.515
+KVM: 0.513
+device: 0.511
+vnc: 0.485
+socket: 0.479
+boot: 0.458
+
+empty vmdk disk created by qemu-img cann't import to vmware ESXi or Workstation
+Description of problem:
+qemu-img create empty vmdk file, and can't import to vmware workstation or ESXi. the ovftool
+ fail.  the log:
+
+> ```
+> 2024-08-23T11:19:32.335+08:00 verbose OVFTool[4088548] [Originator@6876 sub=Default] Opening disk target empty-disk2.vmdk
+> 2024-08-23T11:19:32.335+08:00 error OVFTool[4088548] [Originator@6876 sub=Default] Error on read, error: -1
+> 2024-08-23T11:19:32.336+08:00 verbose OVFTool[4088187] [Originator@6876 sub=Default] Exception thrown: N5boost16exception_detail10clone_implINS_17unknown_exceptionEEE(std::exception)
+> 2024-08-23T11:19:32.337+08:00 verbose OVFTool[4088187] [Originator@6876 sub=Default] Backtrace: 
+> --> [backtrace begin] product: VMware Workstation, version: e.x.p, build: build-15722219, tag: OVFTool, cpu: x86_64, os: linux, buildType: release
+> --> backtrace[00] libvmacore.so[0x003DD716]
+> --> backtrace[01] libvmacore.so[0x001CF8DF]: Vmacore::System::Stacktrace::CaptureWork(unsigned int)
+> --> backtrace[02] libvmacore.so[0x001B6EA9]: Vmacore::System::SystemFactory::CreateQuickBacktrace(Vmacore::Ref<Vmacore::System::Backtrace>&)
+> --> backtrace[03] libvmacore.so[0x0016CF2E]: Vmacore::Throwable::Throwable(std::string&&)
+> --> backtrace[04] ovftool.bin[0x001C1F38]
+> --> backtrace[05] ovftool.bin[0x002008D5]
+> --> backtrace[06] ovftool.bin[0x00129EF0]
+> --> backtrace[07] libc.so.6[0x00044E50]
+> --> backtrace[08] libc.so.6[0x00044EFC]
+> --> backtrace[09] ovftool.bin[0x00132D21]
+> --> [backtrace end]
+> ```
+
+the log file:
+[test.log](/uploads/174db2ace468bd9f0ec3ab14de524217/test.log)
+Steps to reproduce:
+1. create empty vmdk file
+
+./qemu-img create -f vmdk -o adapter_type=lsilogic,subformat=streamOptimized empty.vmdk 1G
+
+2. add empty file info  to  ovf file
+<File ovf:href="empty.vmdk" ovf:id="file2"/>
+
+3. import it to vmware workstation
+Additional information:
+If i write some data to empty vmdk file, it can import successfully.  The reson: qemu only write metadata for empty vmdk file, but the ovftool need read more data and it cann't read more.
+we can write one sector zero data after the metadata, ovftool work well. 
+I submitted the patch:
+https://patchew.org/QEMU/20240822105237.777-1-luzhipeng@cestc.cn/
diff --git a/results/classifier/108/other/2533 b/results/classifier/108/other/2533
new file mode 100644
index 000000000..317acee34
--- /dev/null
+++ b/results/classifier/108/other/2533
@@ -0,0 +1,16 @@
+device: 0.886
+performance: 0.776
+graphic: 0.640
+debug: 0.435
+other: 0.304
+semantic: 0.178
+boot: 0.142
+permissions: 0.102
+socket: 0.052
+PID: 0.045
+network: 0.042
+files: 0.016
+vnc: 0.012
+KVM: 0.002
+
+Black screen while I'm trying to emulate Android using "-machine raspi4b"
diff --git a/results/classifier/108/other/2534 b/results/classifier/108/other/2534
new file mode 100644
index 000000000..2e00986b6
--- /dev/null
+++ b/results/classifier/108/other/2534
@@ -0,0 +1,25 @@
+graphic: 0.919
+device: 0.915
+debug: 0.863
+PID: 0.855
+files: 0.845
+performance: 0.800
+boot: 0.769
+socket: 0.726
+permissions: 0.713
+vnc: 0.688
+other: 0.674
+semantic: 0.655
+network: 0.426
+KVM: 0.076
+
+Solaris cannot be power offed with system_powerdown on qemu-system-sparc
+Description of problem:
+When a `system_powerdown` is done in the QEMU Monitor, nothing happens. Also happens with `qemu-system-sparc.exe` version 9.1.0-rc3, that is, it's not fixed in newer versions. Looking at [sun4m.c](https://gitlab.com/qemu-project/qemu/-/blob/master/hw/sparc/sun4m.c#L451) code, it registers a system_powerdown handler, but it's not working.
+Steps to reproduce:
+1. Start the machine with the command line above and wait for the complete OS initialization
+2. Open the machine monitor
+3. Do a `system_powerdown` command
+4. Nothing will happen
+Additional information:
+
diff --git a/results/classifier/108/other/2535 b/results/classifier/108/other/2535
new file mode 100644
index 000000000..c30b0b7cd
--- /dev/null
+++ b/results/classifier/108/other/2535
@@ -0,0 +1,16 @@
+device: 0.820
+network: 0.717
+socket: 0.497
+KVM: 0.407
+vnc: 0.339
+boot: 0.326
+PID: 0.308
+files: 0.208
+semantic: 0.191
+graphic: 0.148
+other: 0.135
+debug: 0.126
+permissions: 0.043
+performance: 0.008
+
+Security patch of CVE-2024-4693 backport request
diff --git a/results/classifier/108/other/2536 b/results/classifier/108/other/2536
new file mode 100644
index 000000000..493c5d350
--- /dev/null
+++ b/results/classifier/108/other/2536
@@ -0,0 +1,16 @@
+device: 0.869
+performance: 0.675
+debug: 0.576
+graphic: 0.483
+boot: 0.076
+semantic: 0.062
+other: 0.024
+permissions: 0.021
+vnc: 0.011
+network: 0.010
+socket: 0.004
+files: 0.004
+PID: 0.002
+KVM: 0.002
+
+Dynamic translation issue of arm instruction VFNMA and VFNMS
diff --git a/results/classifier/108/other/2537 b/results/classifier/108/other/2537
new file mode 100644
index 000000000..1a9f9c51d
--- /dev/null
+++ b/results/classifier/108/other/2537
@@ -0,0 +1,16 @@
+device: 0.755
+performance: 0.533
+vnc: 0.492
+network: 0.476
+semantic: 0.458
+graphic: 0.438
+PID: 0.395
+debug: 0.307
+boot: 0.301
+socket: 0.206
+other: 0.165
+KVM: 0.138
+files: 0.083
+permissions: 0.012
+
+Hang in Cocoa_SetWindowSize()
diff --git a/results/classifier/108/other/2538 b/results/classifier/108/other/2538
new file mode 100644
index 000000000..b0d39bd1e
--- /dev/null
+++ b/results/classifier/108/other/2538
@@ -0,0 +1,41 @@
+PID: 0.779
+graphic: 0.777
+vnc: 0.745
+device: 0.683
+semantic: 0.530
+network: 0.526
+files: 0.520
+performance: 0.515
+debug: 0.464
+socket: 0.414
+permissions: 0.370
+KVM: 0.361
+boot: 0.191
+other: 0.090
+
+qemu-system-loongarch64: ../hw/loongarch/virt.c:118: virt_flash_map1: Assertion `QEMU_IS_ALIGNED(real_size, VIRT_FLASH_SECTOR_SIZE)' failed.
+Description of problem:
+Cannot enter the loongarch64 UEFI shell due to the error below:
+qemu-system-loongarch64: ../hw/loongarch/virt.c:118: virt_flash_map1: Assertion `QEMU_IS_ALIGNED(real_size, VIRT_FLASH_SECTOR_SIZE)' failed.
+Steps to reproduce:
+1.follow the steps to create an empty loongarch64 uefi bare metal.
+2.Click start the installation
+3.Then the error occurs.
+Additional information:
+```
+qemu-system-loongarch64: ../hw/loongarch/virt.c:118: virt_flash_map1: Assertion `QEMU_IS_ALIGNED(real_size, VIRT_FLASH_SECTOR_SIZE)' failed.'
+
+Traceback (most recent call last):
+  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 72, in cb_wrapper
+    callback(asyncjob, *args, **kwargs)
+  File "/usr/share/virt-manager/virtManager/createvm.py", line 2008, in _do_async_install
+    installer.start_install(guest, meter=meter)
+  File "/usr/share/virt-manager/virtinst/install/installer.py", line 695, in start_install
+    domain = self._create_guest(
+             ^^^^^^^^^^^^^^^^^^^
+  File "/usr/share/virt-manager/virtinst/install/installer.py", line 637, in _create_guest
+    domain = self.conn.createXML(initial_xml or final_xml, 0)
+             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+  File "/usr/lib64/python3.12/site-packages/libvirt.py", line 4545, in createXML
+    raise libvirtError('virDomainCreateXML() failed')
+```
diff --git a/results/classifier/108/other/2539 b/results/classifier/108/other/2539
new file mode 100644
index 000000000..e6d0ab6ba
--- /dev/null
+++ b/results/classifier/108/other/2539
@@ -0,0 +1,16 @@
+device: 0.895
+performance: 0.854
+graphic: 0.725
+debug: 0.621
+network: 0.558
+socket: 0.434
+PID: 0.403
+files: 0.391
+boot: 0.385
+other: 0.228
+semantic: 0.210
+vnc: 0.208
+permissions: 0.158
+KVM: 0.056
+
+Crash in early_gtk_display_init() on macOS 14.6.1