restructure results

1 files changed, 56 insertions, 0 deletions

diff --git a/results/classifier/zero-shot/105/boot/2400 b/results/classifier/zero-shot/105/boot/2400
new file mode 100644
index 00000000..8f846688
--- /dev/null
+++ b/results/classifier/zero-shot/105/boot/2400
@@ -0,0 +1,56 @@
+boot: 0.916
+device: 0.871
+instruction: 0.849
+graphic: 0.840
+semantic: 0.832
+mistranslation: 0.829
+socket: 0.657
+network: 0.653
+KVM: 0.555
+other: 0.506
+vnc: 0.436
+assembly: 0.282
+
+Qemu fails to boot snapshot image if its header is qcow2 but its payload and backing image extension are luks
+Description of problem:
+Qemu fails to recognize snapshot image E:\\test_snapshot.qcow2 saying Volume is not in LUKS format
+
+You need three commands to reproduce:
+
+`qemu-img create -f luks --object secret,id=sec0,data=123 -o key-secret=sec0 E:\test.luks 1G`
+
+`qemu-img create --object secret,id=sec0,data=123 -f qcow2 -o encrypt.format=luks,encrypt.key-secret=sec0 -b E:\test.luks -F luks E:\test_snapshot.qcow2`
+
+`qemu-system-x86_64 -drive file=E:\test_snapshot.qcow2,format=luks,key-secret=sec0 -object secret,id=sec0,data=123`
+
+This error is printed:
+
+`qemu-system-x86_64: -drive file=E:\test_snapshot.qcow2,format=luks,key-secret=sec0: Volume is not in LUKS format`
+
+But fourth command shows that payload of `E:\test_snapshot.qcow2` has LUKS format:
+
+`qemu-img info E:\test_snapshot.qcow2`
+
+\[output\]
+
+```bash
+virtual size: 1 GiB (1073741824 bytes)
+disk size: 2.25 MiB
+encrypted: yes
+cluster_size: 65536
+backing file: E:\test.luks
+backing file format: luks
+Format specific information:
+    compat: 1.1
+    compression type: zlib
+    lazy refcounts: false
+    refcount bits: 16
+    encrypt:
+        ivgen alg: plain64
+        detached header: false
+        hash alg: sha256
+        cipher alg: aes-256
+        uuid: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
+        format: luks
+        cipher mode: xts ...
+```