summary refs log tree commit diff stats
path: root/results/classifier/deepseek-2/output/files/1357
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-07-03 07:27:52 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-07-03 07:27:52 +0000
commitd0c85e36e4de67af628d54e9ab577cc3fad7796a (patch)
treef8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/deepseek-2/output/files/1357
parent7f4364274750eb8cb39a3e7493132fca1c01232e (diff)
downloadqemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz
qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip
add deepseek and gemma results
Diffstat (limited to 'results/classifier/deepseek-2/output/files/1357')
-rw-r--r--results/classifier/deepseek-2/output/files/135710
1 files changed, 10 insertions, 0 deletions
diff --git a/results/classifier/deepseek-2/output/files/1357 b/results/classifier/deepseek-2/output/files/1357
new file mode 100644
index 000000000..c90b5cc88
--- /dev/null
+++ b/results/classifier/deepseek-2/output/files/1357
@@ -0,0 +1,10 @@
+
+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.