restructure results

1 files changed, 51 insertions, 0 deletions

diff --git a/results/classifier/zero-shot/118/files/1810343 b/results/classifier/zero-shot/118/files/1810343
new file mode 100644
index 000000000..2f9862afd
--- /dev/null
+++ b/results/classifier/zero-shot/118/files/1810343
@@ -0,0 +1,51 @@
+files: 0.903
+device: 0.699
+network: 0.512
+performance: 0.387
+ppc: 0.366
+kernel: 0.357
+socket: 0.319
+semantic: 0.306
+PID: 0.290
+i386: 0.264
+mistranslation: 0.261
+vnc: 0.243
+graphic: 0.242
+x86: 0.212
+hypervisor: 0.202
+boot: 0.184
+architecture: 0.180
+register: 0.157
+permissions: 0.153
+user-level: 0.153
+peripherals: 0.151
+VMM: 0.143
+risc-v: 0.137
+KVM: 0.136
+TCG: 0.130
+virtual: 0.107
+assembly: 0.100
+debug: 0.093
+arm: 0.076
+
+qemu-nbd -l and -s options don't work together
+
+When using qemu-nbd with -l to load a snapshot along with -s to create new active layer the tool fails to find the snapshot specified on the command line:
+
+For example the following does not work:
+  sudo qemu-nbd -s --load-snapshot=files  --connect /dev/nbd0 rootfs.qcow2                                   
+  Failed to load snapshot: Can't find snapshot
+
+However, the following option works
+  sudo qemu-nbd -s --connect /dev/nbd0 rootfs.qcow2
+and so does
+  sudo qemu-nbd --load-snapshot=files  --connect /dev/nbd0 rootfs.qcow2
+
+
+This is an automated cleanup. This bug report has been moved to QEMU's
+new bug tracker on gitlab.com and thus gets marked as 'expired' now.
+Please continue with the discussion here:
+
+ https://gitlab.com/qemu-project/qemu/-/issues/159
+
+