3 files changed, 218 insertions, 0 deletions
diff --git a/results/classifier/118/files/1809 b/results/classifier/118/files/1809
new file mode 100644
index 000000000..32fd4b782
--- /dev/null
+++ b/results/classifier/118/files/1809
@@ -0,0 +1,83 @@
+architecture: 0.955
+files: 0.926
+performance: 0.922
+virtual: 0.901
+PID: 0.895
+device: 0.881
+socket: 0.875
+kernel: 0.828
+boot: 0.806
+register: 0.795
+peripherals: 0.774
+network: 0.762
+hypervisor: 0.759
+graphic: 0.755
+mistranslation: 0.742
+permissions: 0.708
+semantic: 0.696
+VMM: 0.689
+risc-v: 0.660
+arm: 0.657
+TCG: 0.626
+debug: 0.573
+user-level: 0.563
+ppc: 0.562
+vnc: 0.558
+assembly: 0.516
+x86: 0.496
+i386: 0.433
+KVM: 0.406
+
+config machine "virt-6.2" with qemu-system-aarch64,it report "mem is not supported by this machine type"
+Description of problem:
+When i config the machine with virt-6.2 and config the numa for cpu,it report "mem is not supported by this machine type",but with virt-5.0 it work well,the newer version virt not support it? It is bug or require hardware support?Or compile configure is not correctlly?
+
+when i create vm,get the error report as follow:
+ 
+virsh create test.xml
+```
+qemu unexpectedly closed the monitor: qemu-system-aarch64: -chardev socket,id=charmonitor,fd=34,server,nowait: warning: short-form boolean option 'server' deprecated
+Please use server=on instead
+qemu-system-aarch64: -chardev socket,id=charmonitor,fd=34,server,nowait: warning: short-form boolean option 'nowait' deprecated
+Please use wait=off instead
+configure accelerator virt-6.2 start
+machine init start
+2023-08-04T02:17:13.984797Z qemu-system-aarch64: -numa node,nodeid=0,cpus=0-3,mem=8192: Parameter -numa node,mem is not supported by this machine type
+Use -numa node,memdev instead
+
+```
+
+
+I use qmp command "query-machines" get the result as follow:
+```
+{
+      "hotpluggable-cpus": true,
+      "name": "virt-6.2",
+     ** "numa-mem-supported": false,**
+      "default-cpu-type": "cortex-a15-arm-cpu",
+      "cpu-max": 512,
+      "deprecated": false,
+      "default-ram-id": "mach-virt.ram",
+      "alias": "virt"
+    },
+```
+
+I add the code "mc->numa_mem_supported = true;" in the api "virt_machine_6_1_options",it can supoort numa,but i don't know whether it is affected.
+
+```
+DEFINE_VIRT_MACHINE_AS_LATEST(6, 2)
+
+static void virt_machine_6_1_options(MachineClass *mc)
+{
+    VirtMachineClass *vmc = VIRT_MACHINE_CLASS(OBJECT_CLASS(mc));
+
+    virt_machine_6_2_options(mc);
+    compat_props_add(mc->compat_props, hw_compat_6_1, hw_compat_6_1_len);
+    mc->smp_props.prefer_sockets = true;
+    vmc->no_cpu_topology = true;
+    **mc->numa_mem_supported = true;**
+
+    /* qemu ITS was introduced with 6.2 */
+    vmc->no_tcg_its = true;
+}
+```
diff --git a/results/classifier/118/files/1809304 b/results/classifier/118/files/1809304
new file mode 100644
index 000000000..2d4737f46
--- /dev/null
+++ b/results/classifier/118/files/1809304
@@ -0,0 +1,88 @@
+files: 0.957
+device: 0.938
+user-level: 0.909
+performance: 0.895
+graphic: 0.829
+semantic: 0.799
+VMM: 0.761
+PID: 0.750
+architecture: 0.745
+x86: 0.718
+risc-v: 0.715
+vnc: 0.708
+boot: 0.704
+ppc: 0.698
+virtual: 0.689
+register: 0.680
+network: 0.677
+i386: 0.667
+arm: 0.657
+socket: 0.650
+kernel: 0.648
+KVM: 0.641
+hypervisor: 0.627
+TCG: 0.590
+mistranslation: 0.572
+permissions: 0.564
+debug: 0.514
+peripherals: 0.467
+assembly: 0.432
+
+qemu-img convert is freezing for some DMG files.
+
+Recently, I created a file using hdiutil from MacOS (using Zlib compression):
+
+$ hdiutil create -volname MyVolName -srcfolder /path/to/my/vol/ -ov -format UDZO myvolname.dmg
+
+But, when I try to convert this volume using qemu-img convert, this command is freezing.
+
+I'm using the upstream version to test it.
+
+It is freezing inside the binary search method to retrieve the chunk.
+
+But, I still don't know why.
+
+I'm attaching the file as an example.
+
+It can be mounted using MacOS or other Linux apps like hfsleuth and darling-dmg.
+
+
+
+I have submitted a patch to prevent hanging in binary search.
+See: http://lists.nongnu.org/archive/html/qemu-devel/2018-12/msg05453.html?fbclid=IwAR0ObsaZ4kVMVv6MWIdq0ZCAN5tGhDsd9GmFv8_v7HBTl94Cu5EkRZ3z4n4
+
+Thanks,
+Yu-Chen Lin
+
+I'm almost sure that we need other improvements beyond fixing binary search deadlock.
+
+It is returning read errors when you apply your patch.
+
+Because of lacking zero chunk table, reading zero sector will return EIO.
+I have submitted a series to fix this problem.
+
+Please refer to this series: http://lists.nongnu.org/archive/html/qemu-devel/2018-12/msg05637.html
+
+Thanks,
+Yu-Chen Lin
+
+Hi Yu-Chen.
+
+The series looks good. It fixed the problems related to zero chunk. Nice work!
+
+I added a comment that I reviewed your patch considering my scenarios here. At least, It contributes to merge your changes.
+
+Additional info: tested with version 3.0.0. So, before pushing my commits. Conclusion: This is not a new bug.
+
+Since QEMU 4.0 has been released now, I assume we can close this ticket as "Fix released"? Or is there still anything left to do here?
+
+I re-test the dmg img with QEMU 4.0 again, and it works.
+
+In my opinion, the bug can be closed as "Fix released".
+
+Thanks.
+
+
+
+Thanks for testing. So I'm marking this now as "Fix released".
+
diff --git a/results/classifier/118/files/1809453 b/results/classifier/118/files/1809453
new file mode 100644
index 000000000..689d6f8b8
--- /dev/null
+++ b/results/classifier/118/files/1809453
@@ -0,0 +1,47 @@
+files: 0.873
+virtual: 0.804
+network: 0.762
+mistranslation: 0.662
+graphic: 0.594
+user-level: 0.573
+device: 0.543
+semantic: 0.528
+performance: 0.450
+socket: 0.318
+architecture: 0.286
+ppc: 0.248
+PID: 0.192
+x86: 0.190
+i386: 0.162
+register: 0.147
+boot: 0.123
+vnc: 0.123
+arm: 0.123
+risc-v: 0.107
+permissions: 0.089
+TCG: 0.078
+debug: 0.072
+VMM: 0.066
+peripherals: 0.059
+hypervisor: 0.009
+assembly: 0.005
+kernel: 0.005
+KVM: 0.004
+
+Windows  qemu download Big file bug in net user mode
+
+hi 
+
+Windows qemu with -net user downloading big files has a bug, -net tap is good!
+
+I suspect that the Slirp protocol has a bug on the Windows pc, which is normal on ubuntu.
+
+What is your version of qemu? I understand you are running qemu on ubuntu.
+
+The VM is windows? which version? Which URL are you downloading? What is the program being used?
+
+thanks
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+