2 files changed, 101 insertions, 0 deletions
diff --git a/results/classifier/118/graphic/1356 b/results/classifier/118/graphic/1356
new file mode 100644
index 00000000..380fbc19
--- /dev/null
+++ b/results/classifier/118/graphic/1356
@@ -0,0 +1,47 @@
+graphic: 0.954
+device: 0.808
+x86: 0.733
+mistranslation: 0.729
+debug: 0.661
+architecture: 0.643
+KVM: 0.629
+network: 0.605
+performance: 0.522
+vnc: 0.478
+semantic: 0.453
+i386: 0.450
+ppc: 0.439
+hypervisor: 0.359
+PID: 0.342
+kernel: 0.332
+boot: 0.331
+socket: 0.325
+peripherals: 0.319
+register: 0.285
+arm: 0.196
+files: 0.180
+permissions: 0.151
+virtual: 0.144
+user-level: 0.144
+assembly: 0.131
+VMM: 0.129
+TCG: 0.105
+risc-v: 0.067
+
+"-set device" doesn't work with device specified in json
+Description of problem:
+The above QEMU command line results in:
+```
+qemu-system-x86_64: -set device.ua-igd.x-igd-gms=1: there is no device "ua-igd" defined
+```
+While the following command works:
+```
+qemu-system-x86_64 -accel kvm -m 8192 -nodefaults -display none -net none -device vfio-pci,host=0000:00:02.0,id=ua-igd -set device.ua-igd.x-igd-gms=1
+```
+libvirt has moved to the json device specification, therefore I can no longer associate use a <qemu:commandline> section to set driver options for a specific device with this broken id association.
+Steps to reproduce:
+1. Create a device with an ID and use -set device.$ID to set a driver option for the device
+2. Note failure when using json device format vs legacy device specification
+3. Profit
+Additional information:
+
diff --git a/results/classifier/118/graphic/1356969 b/results/classifier/118/graphic/1356969
new file mode 100644
index 00000000..27cfffa6
--- /dev/null
+++ b/results/classifier/118/graphic/1356969
@@ -0,0 +1,54 @@
+graphic: 0.900
+performance: 0.896
+semantic: 0.580
+device: 0.576
+network: 0.528
+ppc: 0.522
+vnc: 0.490
+mistranslation: 0.468
+i386: 0.461
+architecture: 0.446
+socket: 0.438
+risc-v: 0.438
+user-level: 0.423
+boot: 0.417
+VMM: 0.414
+PID: 0.408
+files: 0.381
+TCG: 0.379
+x86: 0.366
+kernel: 0.345
+register: 0.305
+arm: 0.300
+virtual: 0.297
+KVM: 0.291
+peripherals: 0.279
+permissions: 0.278
+hypervisor: 0.264
+debug: 0.247
+assembly: 0.110
+
+qemu-io: the 'map' command hangs on the fuzzed image
+
+Sequence:
+ 1. Unpack the attached archive, make a copy of test.img
+ 2. Put copy.img and backing_img.vdi in the same directory
+ 3. Execute
+
+qemu-io copy.img -c map
+
+Result: qemu-io processes part of the image and then hangs loading 100% of CPU time.
+
+
+qemu.git HEAD 2d591ce2aeebf
+
+
+
+Hi,
+
+well, the issue for this specific image is fixed because it is detected to be corrupt before the mapping can reach the point in question (unaligned L2 table entry). However, commit 4b25bbc4c22cf39350b75bd250d568a4d975f7c5 should have fixed the problem this bug report is really about. Thus, should be fixed.
+
+Thanks for reporting,
+
+Max
+