1 files changed, 39 insertions, 0 deletions
diff --git a/results/classifier/118/none/1357 b/results/classifier/118/none/1357
new file mode 100644
index 000000000..a781a8069
--- /dev/null
+++ b/results/classifier/118/none/1357
@@ -0,0 +1,39 @@
+device: 0.793
+performance: 0.770
+graphic: 0.686
+mistranslation: 0.583
+semantic: 0.490
+network: 0.434
+virtual: 0.388
+vnc: 0.381
+architecture: 0.352
+debug: 0.306
+i386: 0.288
+boot: 0.278
+risc-v: 0.278
+VMM: 0.256
+ppc: 0.252
+kernel: 0.237
+socket: 0.223
+PID: 0.217
+x86: 0.212
+register: 0.206
+permissions: 0.205
+hypervisor: 0.200
+arm: 0.191
+user-level: 0.162
+TCG: 0.152
+KVM: 0.140
+files: 0.140
+peripherals: 0.117
+assembly: 0.091
+
+qemu-img should generate VMDK with an EOS marker when `has_marker` flag enabled
+Additional information:
+I generate a empty volume with capacity 1G and try to deploy it as a part of OVF. This would fail. 
+
+But when I append an EOS marker to that VMDK, which is actually a zeroed sector, the deployed procedure succeeded.
+
+This case merely happened if VMDK has data, since `qemu-img` always write at least one grain(64 KB). So the padding part will be recognized as  EOS marker.
+
+I have written a temporary patch for this and it works fine for me. I'm glad to send it for review.