7 files changed, 564 insertions, 0 deletions
diff --git a/results/classifier/108/other/120 b/results/classifier/108/other/120
new file mode 100644
index 00000000..d7bebe09
--- /dev/null
+++ b/results/classifier/108/other/120
@@ -0,0 +1,16 @@
+device: 0.710
+other: 0.559
+performance: 0.480
+graphic: 0.417
+debug: 0.413
+PID: 0.409
+socket: 0.361
+vnc: 0.348
+permissions: 0.338
+network: 0.338
+boot: 0.336
+KVM: 0.305
+semantic: 0.203
+files: 0.187
+
+Please provide an option to print the default hardware configuration as command-line options, to make -nodefaults easier to use
diff --git a/results/classifier/108/other/1203 b/results/classifier/108/other/1203
new file mode 100644
index 00000000..d021acc1
--- /dev/null
+++ b/results/classifier/108/other/1203
@@ -0,0 +1,60 @@
+performance: 0.821
+KVM: 0.819
+permissions: 0.815
+other: 0.808
+graphic: 0.797
+device: 0.769
+semantic: 0.767
+debug: 0.760
+boot: 0.746
+files: 0.737
+network: 0.722
+socket: 0.712
+vnc: 0.698
+PID: 0.691
+
+migrate with block-dirty-bitmap (disk size is big enough) can't be finished
+Description of problem:
+when disk size is big enough(this case using the 4T,related to the bandwith of migration), migrate the VM with block-dirty-bitmap , 
+the migration will not be finished!
+Steps to reproduce:
+1. **Start up the source VM,using the commands**: 
+
+/usr/libexec/qemu-kvm -name guest=i-00001C,debug-threads=on  -machine pc,accel=kvm,usb=off,dump-guest-core=off -cpu qemu64,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff -m 4096 -smp 4,sockets=1,cores=4,threads=1   -uuid 991c2994-e1c9-48c0-9554-6b23e43900eb -smbios type=1,manufacturer=data,serial=7C1A9ABA-02DD-4E7D-993C-E1CDAB47A19B,family="Virtual Machine" -no-user-config -nodefaults -device sga  -rtc base=2022-09-09T02:54:38,clock=host,driftfix=slew -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot menu=on,splash-time=0,strict=on -device pci-bridge,chassis_nr=1,id=pci.1,bus=pci.0,addr=0x6 -device pci-bridge,chassis_nr=2,id=pci.2,bus=pci.0,addr=0xa -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0xb -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0xc -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0xd -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0xe -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x5 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive if=none,id=drive-ide0-1-1,readonly=on -device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1,bootindex=2 -drive if=none,id=drive-fdc0-0-0,readonly=on  -drive file=/datastore/e88e2b29-cd39-4b21-9629-5ef2458f7ddd/c08fee8e-caf4-4217-ab4d-351a021c2c3d,format=qcow2,if=none,id=drive-virtio-disk0,cache=none -device virtio-blk-pci,scsi=off,num-queues=1,bus=pci.1,addr=0x1,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1,write-cache=on -device usb-tablet,id=input0,bus=usb.0,port=1     -device intel-hda,id=sound0,bus=pci.0,addr=0x3 -device hda-micro,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -sandbox off -device pvpanic,ioport=1285 -msg timestamp=on -qmp tcp:127.0.0.1:4444,server,nowait 
+
+**Start the dst VM using commands as:**
+
+/usr/libexec/qemu-kvm -name guest=i-00001C,debug-threads=on  -machine pc,accel=kvm,usb=off,dump-guest-core=off -cpu qemu64,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff -m 4096 -smp 4,sockets=1,cores=4,threads=1   -uuid 991c2994-e1c9-48c0-9554-6b23e43900eb -smbios type=1,manufacturer=data,serial=7C1A9ABA-02DD-4E7D-993C-E1CDAB47A19B,family="Virtual Machine" -no-user-config -nodefaults -device sga  -rtc base=2022-09-09T02:54:38,clock=host,driftfix=slew -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot menu=on,splash-time=0,strict=on -device pci-bridge,chassis_nr=1,id=pci.1,bus=pci.0,addr=0x6 -device pci-bridge,chassis_nr=2,id=pci.2,bus=pci.0,addr=0xa -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0xb -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0xc -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0xd -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0xe -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x5 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive if=none,id=drive-ide0-1-1,readonly=on -device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1,bootindex=2 -drive if=none,id=drive-fdc0-0-0,readonly=on  -drive file=/datastore/e88e2b29-cd39-4b21-9629-5ef2458f7ddd/c08fee8e-caf4-4217-ab4d-351a021c2c3d,format=qcow2,if=none,id=drive-virtio-disk0,cache=none -device virtio-blk-pci,scsi=off,num-queues=1,bus=pci.1,addr=0x1,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1,write-cache=on -device usb-tablet,id=input0,bus=usb.0,port=1     -device intel-hda,id=sound0,bus=pci.0,addr=0x3 -device hda-micro,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -sandbox off -device pvpanic,ioport=1285 -msg timestamp=on -qmp tcp:127.0.0.1:4444,server,nowait -incoming tcp:0:3333
+
+2. **image info as:**
+
+image: /datastore/e88e2b29-cd39-4b21-9629-5ef2458f7ddd/c08fee8e-caf4-4217-ab4d-351a021c2c3d
+
+file format: qcow2
+virtual size: 4.0T (4380866641920 bytes)
+disk size: 1.0M
+cluster_size: 65536
+
+Format specific information:
+    compat: 1.1
+    lazy refcounts: false
+    refcount bits: 16
+    corrupt: false
+
+3. **Add the bitmap :** {"execute":"block-dirty-bitmap-add","arguments":{"node":"drive-virtio-disk0", "name":"bitmap-2022-09-09-16-10-23"}}
+4. **set the dirty-bitmaps capability** :{ "execute": "migrate-set-capabilities" , "arguments":{"capabilities":[ {"capability":"dirty-bitmaps","state": true }]}}
+5. **start migrate ** { "execute": "migrate", "arguments": { "uri": "tcp:10.49.35.23:3333" } }
+6. **quert migrate parameters** {"execute":"query-migrate-parameters"} the retrun message :
+{"return": {"cpu-throttle-tailslow": false, "xbzrle-cache-size": 67108864, "cpu-throttle-initial": 20, "announce-max": 550, "decompress-threads": 2, "compress-threads": 8, "compress-level": 1, "multifd-channels": 2, "multifd-zstd-level": 1, "announce-initial": 50, "block-incremental": false, "compress-wait-thread": true, "downtime-limit": 300, "tls-authz": "", "multifd-compression": "none", "announce-rounds": 5, "announce-step": 100, "tls-creds": "", "multifd-zlib-level": 1, "max-cpu-throttle": 99, "max-postcopy-bandwidth": 0, "tls-hostname": "", "throttle-trigger-threshold": 50, "max-bandwidth": 134217728, "x-checkpoint-delay": 20000, "cpu-throttle-increment": 10}}
+
+7. **query-migrate-capabilities** ：
+{"execute":"query-migrate-capabilities"} the retrun message :
+{"return": [{"state": false, "capability": "xbzrle"}, {"state": false, "capability": "rdma-pin-all"}, {"state": false, "capability": "auto-converge"}, {"state": false, "capability": "zero-blocks"}, {"state": false, "capability": "compress"}, {"state": false, "capability": "events"}, {"state": false, "capability": "postcopy-ram"}, {"state": false, "capability": "x-colo"}, {"state": false, "capability": "release-ram"}, {"state": false, "capability": "return-path"}, {"state": false, "capability": "pause-before-switchover"}, {"state": false, "capability": "multifd"}, {"state": true, "capability": "dirty-bitmaps"}, {"state": false, "capability": "postcopy-blocktime"}, {"state": false, "capability": "late-block-activate"}, {"state": false, "capability": "x-ignore-shared"}, {"state": false, "capability": "validate-uuid"}, {"state": false, "capability": "background-snapshot"}]}
+
+8. **query the info of migrate** using the command {"execute":"query-migrate"}
+{"return": {"expected-downtime": 0, "status": "active", "setup-time": 64, "total-time": 1320361, "ram": {"total": 4295499776, "postcopy-requests": 0, "dirty-sync-count": 7909410, "multifd-bytes": 0, "pages-per-second": 80, "page-size": 4096, "remaining": 0, "mbps": 3.5006399999999998, "transferred": 430971236, "duplicate": 1048569, "dirty-pages-rate": 66, "skipped": 0, "normal-bytes": 357560320, "normal": 87295}}}
+
+**the state of migrate is always active ,no matter how long it takes.**
+The bug is : migration with big block dirty bitmap  can not be finished
+Additional information:
+
diff --git a/results/classifier/108/other/1204697 b/results/classifier/108/other/1204697
new file mode 100644
index 00000000..44146e26
--- /dev/null
+++ b/results/classifier/108/other/1204697
@@ -0,0 +1,146 @@
+graphic: 0.861
+PID: 0.859
+permissions: 0.844
+semantic: 0.824
+KVM: 0.804
+device: 0.800
+performance: 0.795
+files: 0.759
+other: 0.735
+vnc: 0.733
+debug: 0.726
+boot: 0.673
+socket: 0.539
+network: 0.491
+
+guest disk accesses lead to ATA errors + host vcpu0 unhandled wrmsr/rdmsr
+
+Hi.
+
+This is from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717724.
+
+Using Debian sid with 1.5.0-5 my Linux VMs (also Debian sid) are broken. When they boot I get gazillions of ATA errors inside the guest, as well as:
+[  242.479951] kvm [7790]: vcpu0 unhandled rdmsr: 0x345
+[  242.483683] kvm [7790]: vcpu0 unhandled wrmsr: 0x680 data 0
+[  242.483687] kvm [7790]: vcpu0 unhandled wrmsr: 0x6c0 data 0
+[  242.483689] kvm [7790]: vcpu0 unhandled wrmsr: 0x681 data 0
+[  242.483691] kvm [7790]: vcpu0 unhandled wrmsr: 0x6c1 data 0
+[  242.483693] kvm [7790]: vcpu0 unhandled wrmsr: 0x682 data 0
+[  242.483696] kvm [7790]: vcpu0 unhandled wrmsr: 0x6c2 data 0
+[  242.483698] kvm [7790]: vcpu0 unhandled wrmsr: 0x683 data 0
+[  242.483700] kvm [7790]: vcpu0 unhandled wrmsr: 0x6c3 data 0
+[  242.483702] kvm [7790]: vcpu0 unhandled wrmsr: 0x684 data 0
+[  242.483704] kvm [7790]: vcpu0 unhandled wrmsr: 0x6c4 data 0
+[  242.988307] kvm [7790]: vcpu0 unhandled rdmsr: 0xe8
+[  242.988312] kvm [7790]: vcpu0 unhandled rdmsr: 0xe7
+[  242.988314] kvm [7790]: vcpu0 unhandled rdmsr: 0xce
+[  242.988316] kvm [7790]: vcpu0 unhandled rdmsr: 0xce
+[  242.988318] kvm [7790]: vcpu0 unhandled rdmsr: 0x1ad
+[  242.988320] kvm [7790]: vcpu0 unhandled rdmsr: 0xce
+[  242.988322] kvm [7790]: vcpu0 unhandled rdmsr: 0xe8
+[  242.988324] kvm [7790]: vcpu0 unhandled rdmsr: 0xe7
+[  242.988598] kvm [7790]: vcpu0 unhandled rdmsr: 0xce
+
+in the host.
+
+Please have a look at the Debian bug, for screenshots and more info.
+The problem didn't occur in 1.5.0-4 and there were basically no changes inside the VM (i.e. no kernel upgrade or so).
+
+Thanks,
+Chris.
+
+For the record, the difference between debian qemu 1.5.0-4 and 1.5.0-5 is the 1.5.1 patch - I applied it without actually changing the "upstream" version number.
+
+
+Hi.
+
+Finally I was able to get it running with IDE instead of SATA.
+That works,... fine... no ATA errors.
+
+As you already expected,.. I still get the:
+[20424.793207] kvm [20947]: vcpu0 unhandled wrmsr: 0x6c1 data 0
+[20424.793211] kvm [20947]: vcpu0 unhandled wrmsr: 0x682 data 0
+[20424.793215] kvm [20947]: vcpu0 unhandled wrmsr: 0x6c2 data 0
+[20424.793218] kvm [20947]: vcpu0 unhandled wrmsr: 0x683 data 0
+[20424.793222] kvm [20947]: vcpu0 unhandled wrmsr: 0x6c3 data 0
+[20424.793226] kvm [20947]: vcpu0 unhandled wrmsr: 0x684 data 0
+[20424.793229] kvm [20947]: vcpu0 unhandled wrmsr: 0x6c4 data 0
+[20425.946617] kvm [20947]: vcpu0 unhandled rdmsr: 0xe8
+[20425.946623] kvm [20947]: vcpu0 unhandled rdmsr: 0xe7
+[20425.946625] kvm [20947]: vcpu0 unhandled rdmsr: 0xce
+[20425.946628] kvm [20947]: vcpu0 unhandled rdmsr: 0xce
+
+So that seems to be unrelated... nevertheless.. I haven't seen these before with 1.5.0.
+
+
+Anyway...I will try to get it running with virtio as well, as you suggested... but I have troubles to convince libvirt of using it.
+
+
+btw: Might be unrealted... but with 1.5.1 and IDE now... when I do an update-initramfs -u inside the guest I gues these:
+[  276.130974] traps: ld-linux-x32.so[5642] general protection ip:f7788e8d sp:ffe12528 error:0 in ld-2.17.so[f7772000+21000]
+[  276.141129] traps: ld-linux-x32.so[5656] general protection ip:f77b8e8d sp:ff978458 error:0 in ld-2.17.so[f77a2000+21000]
+[  276.151444] traps: ld-linux-x32.so[5670] general protection ip:f7721e8d sp:ffd44cc8 error:0 in ld-2.17.so[f770b000+21000]
+[  276.207037] traps: ld-linux-x32.so[5714] general protection ip:f7770e8d sp:ff92cce8 error:0 in ld-2.17.so[f775a000+21000]
+[  276.278651] traps: ld-linux-x32.so[5775] general protection ip:f76fbe8d sp:ffe73048 error:0 in ld-2.17.so[f76e5000+21000]
+[  276.319277] traps: ld-linux-x32.so[5805] general protection ip:f76fee8d sp:fff486f8 error:0 in ld-2.17.so[f76e8000+21000]
+[  276.329552] traps: ld-linux-x32.so[5819] general protection ip:f77a8e8d sp:ffc9b448 error:0 in ld-2.17.so[f7792000+21000]
+[  276.338671] traps: ld-linux-x32.so[5833] general protection ip:f77bfe8d sp:ffe597b8 error:0 in ld-2.17.so[f77a9000+21000]
+[  276.347835] traps: ld-linux-x32.so[5847] general protection ip:f77b9e8d sp:ffcb1f08 error:0 in ld-2.17.so[f77a3000+21000]
+[  276.356548] traps: ld-linux-x32.so[5861] general protection ip:f77d1e8d sp:ffee16d8 error:0 in ld-2.17.so[f77bb000+21000]
+[  313.662052] do_general_protection: 24 callbacks suppressed
+[  313.662371] traps: ld-linux-x32.so[8926] general protection ip:f77e9e8d sp:ffa443a8 error:0 in ld-2.17.so[f77d3000+21000]
+[  313.670615] traps: ld-linux-x32.so[8940] general protection ip:f7796e8d sp:ff879cf8 error:0 in ld-2.17.so[f7780000+21000]
+[  313.677952] traps: ld-linux-x32.so[8954] general protection ip:f7791e8d sp:ffa25948 error:0 in ld-2.17.so[f777b000+21000]
+[  313.708061] traps: ld-linux-x32.so[8998] general protection ip:f7724e8d sp:ffe6b858 error:0 in ld-2.17.so[f770e000+21000]
+[  313.750866] traps: ld-linux-x32.so[9059] general protection ip:f77c7e8d sp:ff8a32a8 error:0 in ld-2.17.so[f77b1000+21000]
+[  313.771839] traps: ld-linux-x32.so[9089] general protection ip:f77b0e8d sp:ffdfa038 error:0 in ld-2.17.so[f779a000+21000]
+[  313.780747] traps: ld-linux-x32.so[9103] general protection ip:f777ae8d sp:ffc699a8 error:0 in ld-2.17.so[f7764000+21000]
+[  313.789250] traps: ld-linux-x32.so[9117] general protection ip:f778de8d sp:ffce6358 error:0 in ld-2.17.so[f7777000+21000]
+[  313.797782] traps: ld-linux-x32.so[9131] general protection ip:f7794e8d sp:ffcc8a38 error:0 in ld-2.17.so[f777e000+21000]
+[  313.806169] traps: ld-linux-x32.so[9145] general protection ip:f7703e8d sp:ff9e61a8 error:0 in ld-2.17.so[f76ed000+21000]
+
+Seems also kinda weird.... never seen that before in that context.
+
+
+Cheers,
+Chris.
+
+Also, when using SATA for the virtual disk,... it seems that it takes much longer till it get's to the point where it (the initrd) tries to mount root.
+
+Till that point I see no errors... but then, after some time hanging at the root mount... it starts with the ATA errors.
+
+
+So, what changed so you were able to boot from IDE without errors?  As far as I understand, your initial prob was I/O errors on IDE (virtual) drive, but now you can boot it without errors.  Or was it always SATA not IDE?
+
+The rdmsr/wrmsr are unrelated, I already told you that, it is accessing optional CPU features which has nothing to do with disk access.
+
+The segfaults during mkinitrd are unrelated too _unless_ you're running it from "failing" virtual drive.  If you run it from failing virtual drive, it is remotely possible to have errors due to some file not read properly due to errors, but even this is a very remote possibility.
+
+The time it takes to start mounting root is most likely also unrelated, it depends on the guest.
+
+It _looks_ like the whole prob is due to FLUSH CASHE command not working correctly with SATA and IDE, but you confused me here - I don't understand where you were and are getting errors and where you don't.
+
+Besides, you never answered to this: do you have enough free space in the host filesystem where your disk image(s) are located?
+
+Sorry for the confusion.
+The initial problem was _always_ with SATA... I couldn't try IDE at first, as the guest  initrd haven't had and the IDE drivers.
+
+Yesterday then, I tried IDE and it worked with that.
+
+
+Sure, I just wanted to confirm that you were really right ;-)
+
+
+Sorry I have missed the question about enough space before.. there is plenty of free host space left (133 GB).
+
+Having tried now with virtio as well: works
+
+So:
+virtio, ide = OK
+sata = broken
+
+The fix is in a62eaa26c1d6d48fbdc3ac1d32bd1314f5fdc8c9 "ahci: Fix FLUSH command", should be in 1.6 and 1.5.3.
+
+From a first test of the Debian package in experimental, I'd say that the issue has been fixed :)
+Thanks a lot for all your help!
+
diff --git a/results/classifier/108/other/1205156 b/results/classifier/108/other/1205156
new file mode 100644
index 00000000..c40b6063
--- /dev/null
+++ b/results/classifier/108/other/1205156
@@ -0,0 +1,265 @@
+other: 0.876
+semantic: 0.859
+debug: 0.847
+performance: 0.844
+PID: 0.831
+graphic: 0.812
+socket: 0.774
+permissions: 0.766
+device: 0.763
+network: 0.754
+KVM: 0.750
+vnc: 0.735
+files: 0.701
+boot: 0.692
+
+Errors while compiling version 1.5.2
+
+Environment: Ubuntu 13.04
+
+"hw/ide/macio.c: In function ‘pmac_ide_atapi_transfer_cb’:
+hw/ide/macio.c:134:9: error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘hwaddr’ [-Werror=format]
+hw/ide/macio.c: In function ‘pmac_ide_transfer_cb’:
+hw/ide/macio.c:215:5: error: format ‘%ld’ expects argument of type ‘long int’, but argument 5 has type ‘int64_t’ [-Werror=format]
+hw/ide/macio.c:222:9: error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘hwaddr’ [-Werror=format]
+hw/ide/macio.c:264:9: error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘hwaddr’ [-Werror=format]
+cc1: all warnings being treated as errors
+make: *** [hw/ide/macio.o] Error 1"
+
+I got the source files with a "git clone git://git.qemu-project.org/qemu.git" + a recent "git fetch"
+
+I was able to compile and link latest 1.5.2 release with the tar.bz2 source files.
+
+I'm glad that ASAs do not crash anymore within GNS3 with this latest qemu release: nice work guys! :)
+
+Quoting Stefan Weil (2013-07-26 00:12:59)
+> Am 26.07.2013 04:03, schrieb jean-christophe manciot:
+> > Public bug reported:
+> >
+> > Environment: Ubuntu 13.04
+> >
+> > "hw/ide/macio.c: In function ‘pmac_ide_atapi_transfer_cb’:
+> > hw/ide/macio.c:134:9: error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘hwaddr’ [-Werror=format]
+> > hw/ide/macio.c: In function ‘pmac_ide_transfer_cb’:
+> > hw/ide/macio.c:215:5: error: format ‘%ld’ expects argument of type ‘long int’, but argument 5 has type ‘int64_t’ [-Werror=format]
+> > hw/ide/macio.c:222:9: error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘hwaddr’ [-Werror=format]
+> > hw/ide/macio.c:264:9: error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘hwaddr’ [-Werror=format]
+> > cc1: all warnings being treated as errors
+> > make: *** [hw/ide/macio.o] Error 1"
+> >
+> > I got the source files with a "git clone git://git.qemu-
+> > project.org/qemu.git" + a recent "git fetch"
+> >
+> > ** Affects: qemu
+> >      Importance: Undecided
+> >          Status: New
+> >
+> 
+> 
+> 
+> This patch should fix it: http://patchwork.ozlabs.org/patch/258774/.
+> 
+> It's also still missing in git master, but was already applied to
+> qemu-trivial.
+
+This doesn't seem to be vanilla 1.5.2, where 04dd1259 isn't applicable
+(no MACIO_DPRINTF statements), but rather a newer release or past
+version with this patch on top:
+
+  commit 80fc95d8bdaf3392106b131a97ca701fd374489a
+  Author: Alexander Graf <email address hidden>
+  Date:   Fri Jun 28 13:30:01 2013 +0200
+  
+      PPC: dbdma: Support unaligned DMA access
+
+I'd pull them both in if Alex wants to send a backported version for
+1.5.2, but otherwise this doesn't seem to be an issue with stable.
+
+> 
+> Stefan
+
+
+Quoting Michael Roth (2013-08-12 20:05:32)
+> Quoting Stefan Weil (2013-07-26 00:12:59)
+> > Am 26.07.2013 04:03, schrieb jean-christophe manciot:
+> > > Public bug reported:
+> > >
+> > > Environment: Ubuntu 13.04
+> > >
+> > > "hw/ide/macio.c: In function ‘pmac_ide_atapi_transfer_cb’:
+> > > hw/ide/macio.c:134:9: error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘hwaddr’ [-Werror=format]
+> > > hw/ide/macio.c: In function ‘pmac_ide_transfer_cb’:
+> > > hw/ide/macio.c:215:5: error: format ‘%ld’ expects argument of type ‘long int’, but argument 5 has type ‘int64_t’ [-Werror=format]
+> > > hw/ide/macio.c:222:9: error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘hwaddr’ [-Werror=format]
+> > > hw/ide/macio.c:264:9: error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘hwaddr’ [-Werror=format]
+> > > cc1: all warnings being treated as errors
+> > > make: *** [hw/ide/macio.o] Error 1"
+> > >
+> > > I got the source files with a "git clone git://git.qemu-
+> > > project.org/qemu.git" + a recent "git fetch"
+> > >
+> > > ** Affects: qemu
+> > >      Importance: Undecided
+> > >          Status: New
+> > >
+> > 
+> > 
+> > 
+> > This patch should fix it: http://patchwork.ozlabs.org/patch/258774/.
+> > 
+> > It's also still missing in git master, but was already applied to
+> > qemu-trivial.
+> 
+> This doesn't seem to be vanilla 1.5.2, where 04dd1259 isn't applicable
+> (no MACIO_DPRINTF statements), but rather a newer release or past
+> version with this patch on top:
+> 
+>   commit 80fc95d8bdaf3392106b131a97ca701fd374489a
+>   Author: Alexander Graf <email address hidden>
+>   Date:   Fri Jun 28 13:30:01 2013 +0200
+>   
+>       PPC: dbdma: Support unaligned DMA access
+> 
+> I'd pull them both in if Alex wants to send a backported version for
+> 1.5.2, but otherwise this doesn't seem to be an issue with stable.
+
+Forgot to cc Alex.
+
+> 
+> > 
+> > Stefan
+
+
+
+
+Am 13.08.2013 um 03:07 schrieb Michael Roth <email address hidden>:
+
+> Quoting Michael Roth (2013-08-12 20:05:32)
+>> Quoting Stefan Weil (2013-07-26 00:12:59)
+>>> Am 26.07.2013 04:03, schrieb jean-christophe manciot:
+>>>> Public bug reported:
+>>>> 
+>>>> Environment: Ubuntu 13.04
+>>>> 
+>>>> "hw/ide/macio.c: In function ‘pmac_ide_atapi_transfer_cb’:
+>>>> hw/ide/macio.c:134:9: error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘hwaddr’ [-Werror=format]
+>>>> hw/ide/macio.c: In function ‘pmac_ide_transfer_cb’:
+>>>> hw/ide/macio.c:215:5: error: format ‘%ld’ expects argument of type ‘long int’, but argument 5 has type ‘int64_t’ [-Werror=format]
+>>>> hw/ide/macio.c:222:9: error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘hwaddr’ [-Werror=format]
+>>>> hw/ide/macio.c:264:9: error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘hwaddr’ [-Werror=format]
+>>>> cc1: all warnings being treated as errors
+>>>> make: *** [hw/ide/macio.o] Error 1"
+>>>> 
+>>>> I got the source files with a "git clone git://git.qemu-
+>>>> project.org/qemu.git" + a recent "git fetch"
+>>>> 
+>>>> ** Affects: qemu
+>>>>     Importance: Undecided
+>>>>         Status: New
+>>> 
+>>> 
+>>> 
+>>> This patch should fix it: http://patchwork.ozlabs.org/patch/258774/.
+>>> 
+>>> It's also still missing in git master, but was already applied to
+>>> qemu-trivial.
+>> 
+>> This doesn't seem to be vanilla 1.5.2, where 04dd1259 isn't applicable
+>> (no MACIO_DPRINTF statements), but rather a newer release or past
+>> version with this patch on top:
+>> 
+>>  commit 80fc95d8bdaf3392106b131a97ca701fd374489a
+>>  Author: Alexander Graf <email address hidden>
+>>  Date:   Fri Jun 28 13:30:01 2013 +0200
+>> 
+>>      PPC: dbdma: Support unaligned DMA access
+>> 
+>> I'd pull them both in if Alex wants to send a backported version for
+>> 1.5.2, but otherwise this doesn't seem to be an issue with stable.
+> 
+> Forgot to cc Alex.
+
+I'd rather not backport these to 1.5, as the patches only make sense as a whole with an OpenBIOS update.
+
+IIUC the compile error has been fixed for 1.6, correct?
+
+
+Alex
+
+> 
+>> 
+>>> 
+>>> Stefan
+
+
+Quoting Alexander Graf (2013-08-12 23:06:19)
+> Am 13.08.2013 um 03:07 schrieb Michael Roth <email address hidden>:
+> 
+> > Quoting Michael Roth (2013-08-12 20:05:32)
+> >> Quoting Stefan Weil (2013-07-26 00:12:59)
+> >>> Am 26.07.2013 04:03, schrieb jean-christophe manciot:
+> >>>> Public bug reported:
+> >>>> 
+> >>>> Environment: Ubuntu 13.04
+> >>>> 
+> >>>> "hw/ide/macio.c: In function ‘pmac_ide_atapi_transfer_cb’:
+> >>>> hw/ide/macio.c:134:9: error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘hwaddr’ [-Werror=format]
+> >>>> hw/ide/macio.c: In function ‘pmac_ide_transfer_cb’:
+> >>>> hw/ide/macio.c:215:5: error: format ‘%ld’ expects argument of type ‘long int’, but argument 5 has type ‘int64_t’ [-Werror=format]
+> >>>> hw/ide/macio.c:222:9: error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘hwaddr’ [-Werror=format]
+> >>>> hw/ide/macio.c:264:9: error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘hwaddr’ [-Werror=format]
+> >>>> cc1: all warnings being treated as errors
+> >>>> make: *** [hw/ide/macio.o] Error 1"
+> >>>> 
+> >>>> I got the source files with a "git clone git://git.qemu-
+> >>>> project.org/qemu.git" + a recent "git fetch"
+> >>>> 
+> >>>> ** Affects: qemu
+> >>>>     Importance: Undecided
+> >>>>         Status: New
+> >>> 
+> >>> 
+> >>> 
+> >>> This patch should fix it: http://patchwork.ozlabs.org/patch/258774/.
+> >>> 
+> >>> It's also still missing in git master, but was already applied to
+> >>> qemu-trivial.
+> >> 
+> >> This doesn't seem to be vanilla 1.5.2, where 04dd1259 isn't applicable
+> >> (no MACIO_DPRINTF statements), but rather a newer release or past
+> >> version with this patch on top:
+> >> 
+> >>  commit 80fc95d8bdaf3392106b131a97ca701fd374489a
+> >>  Author: Alexander Graf <email address hidden>
+> >>  Date:   Fri Jun 28 13:30:01 2013 +0200
+> >> 
+> >>      PPC: dbdma: Support unaligned DMA access
+> >> 
+> >> I'd pull them both in if Alex wants to send a backported version for
+> >> 1.5.2, but otherwise this doesn't seem to be an issue with stable.
+> > 
+> > Forgot to cc Alex.
+> 
+> I'd rather not backport these to 1.5, as the patches only make sense as a whole with an OpenBIOS update.
+
+Ok, makes sense, just thought I'd double-check. Got the impression from the bug
+report that maybe some downstreams were carrying your patch on top of 1.5.2 for
+OSX support, but I'm not really sure what's going on here.
+
+> 
+> IIUC the compile error has been fixed for 1.6, correct?
+
+Yup, should be fixed upstream with 04dd1259
+
+> 
+> 
+> Alex
+> 
+> > 
+> >> 
+> >>> 
+> >>> Stefan
+
+
+Marking this ticket as "Fix released" according to comment #6.
+
diff --git a/results/classifier/108/other/1207228 b/results/classifier/108/other/1207228
new file mode 100644
index 00000000..de6a6cd9
--- /dev/null
+++ b/results/classifier/108/other/1207228
@@ -0,0 +1,33 @@
+device: 0.733
+performance: 0.714
+graphic: 0.672
+network: 0.614
+socket: 0.604
+PID: 0.563
+permissions: 0.545
+semantic: 0.533
+vnc: 0.378
+files: 0.365
+boot: 0.361
+debug: 0.352
+other: 0.158
+KVM: 0.077
+
+Qemu (trunk code) crashes when using --soundhw all option in ioport.c
+
+After not building qemu (git version) for about 3 weeks, I've done it again this morning.
+
+With up-to-date trunk code, I got this error on start, when using --soundhw all option
+
+$ qemu-system-i386 -soundhw all
+qemu-system-i386: /home/fred/Téléchargements/logs/qemu-git/src/qemu/ioport.c:240: portio_list_add: Assertion `pio->offset >= off_last' failed.
+Abandon (core dumped)
+
+And if I use only soundhw with one or more options, it doesn't crash.
+
+Tell me what you'll need to fix this bug.
+
+Please always specify the exact version (git commit ID) that you are using... can you still reproduce this issue with the latest version of QEMU?
+
+[Expired for QEMU because there has been no activity for 60 days.]
+
diff --git a/results/classifier/108/other/1207896 b/results/classifier/108/other/1207896
new file mode 100644
index 00000000..fdbf2cf1
--- /dev/null
+++ b/results/classifier/108/other/1207896
@@ -0,0 +1,24 @@
+graphic: 0.718
+other: 0.626
+device: 0.555
+vnc: 0.458
+semantic: 0.432
+network: 0.416
+debug: 0.408
+performance: 0.360
+files: 0.357
+permissions: 0.349
+socket: 0.346
+boot: 0.242
+PID: 0.208
+KVM: 0.136
+
+binfmt wrapper for argv[0] handling
+
+Please, add patch https://lists.gnu.org/archive/html/qemu-devel/2011-09/msg03841.html to upstream. 2 years have passed and this patch is not jet applied. Why? 99% GNU/Linux distribution uses qemu with this patch. It is 100% needed.
+
+The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now.
+If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Or mark it as "Fix Released" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience.
+
+[Expired for QEMU because there has been no activity for 60 days.]
+
diff --git a/results/classifier/108/other/1209 b/results/classifier/108/other/1209
new file mode 100644
index 00000000..90108148
--- /dev/null
+++ b/results/classifier/108/other/1209
@@ -0,0 +1,20 @@
+device: 0.778
+vnc: 0.552
+graphic: 0.526
+boot: 0.507
+network: 0.484
+socket: 0.448
+semantic: 0.447
+performance: 0.343
+PID: 0.327
+files: 0.277
+debug: 0.246
+permissions: 0.242
+other: 0.195
+KVM: 0.102
+
+Optionally do not clear the screen when starting a VM
+Additional information:
+```
+QEMU emulator version 6.2.0 (qemu-6.2.0-14.fc36)
+```