1 files changed, 57 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/118/x86/492 b/results/classifier/zero-shot/118/x86/492
new file mode 100644
index 00000000..9be3f534
--- /dev/null
+++ b/results/classifier/zero-shot/118/x86/492
@@ -0,0 +1,57 @@
+x86: 0.820
+virtual: 0.805
+graphic: 0.771
+semantic: 0.708
+device: 0.673
+hypervisor: 0.671
+performance: 0.631
+PID: 0.619
+debug: 0.602
+files: 0.569
+ppc: 0.565
+VMM: 0.550
+vnc: 0.548
+socket: 0.546
+kernel: 0.534
+network: 0.519
+architecture: 0.505
+arm: 0.471
+peripherals: 0.470
+i386: 0.436
+permissions: 0.422
+mistranslation: 0.419
+risc-v: 0.417
+register: 0.409
+TCG: 0.382
+KVM: 0.380
+boot: 0.367
+user-level: 0.256
+assembly: 0.230
+
+[git] "qemu-system-x86_64: Parameter 'drive' is missing" when I tried to launch an existing VM in Virt-Manager.
+Description of problem:
+This bug is related in some way to bug #488.
+
+I cannot start an existing virtual machine using qemu-git.
+Additional information:
+```
+internal error: process exited while connecting to monitor: 2021-07-19T19:24:27.044654Z qemu-system-x86_64: Parameter 'drive' is missing
+
+Traceback (most recent call last):
+  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in cb_wrapper
+    callback(asyncjob, *args, **kwargs)
+  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 101, in tmpcb
+    callback(*args, **kwargs)
+  File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn
+    ret = fn(self, *args, **kwargs)
+  File "/usr/share/virt-manager/virtManager/object/domain.py", line 1329, in startup
+    self._backend.create()
+  File "/usr/lib/python3.9/site-packages/libvirt.py", line 1353, in create
+    raise libvirtError('virDomainCreate() failed')
+libvirt.libvirtError: internal error: process exited while connecting to monitor: 2021-07-19T19:24:27.044654Z qemu-system-x86_64: Parameter 'drive' is missing
+
+```
+
+My last working build was made using commit 9bef7ea9. Using Peter Maydell commits as milestone, I noticed commit 9aef0954 was the first showing the bug.
+
+I'll try to do bisect between these two commits and report asap. There is about 40 commits to verify.