summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/108/other/492
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/zero-shot/108/other/492')
-rw-r--r--results/classifier/zero-shot/108/other/49242
1 files changed, 42 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/other/492 b/results/classifier/zero-shot/108/other/492
new file mode 100644
index 000000000..5c15b2269
--- /dev/null
+++ b/results/classifier/zero-shot/108/other/492
@@ -0,0 +1,42 @@
+graphic: 0.771
+semantic: 0.708
+device: 0.673
+performance: 0.631
+PID: 0.619
+debug: 0.602
+files: 0.569
+vnc: 0.548
+socket: 0.546
+network: 0.519
+permissions: 0.422
+KVM: 0.380
+boot: 0.367
+other: 0.329
+
+[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.