summary refs log tree commit diff stats
path: root/results/classifier/deepseek-2-tmp/output/files/1289898
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-06-30 12:34:26 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-06-30 12:35:44 +0000
commit25f8033d556aa17afaea4a5196ea7a69fe248320 (patch)
tree0f056db167683be54ea1e5e72d29d6069af55e7d /results/classifier/deepseek-2-tmp/output/files/1289898
parent8e6da29e4ee5fc14bc1cc816a24f21271f14090d (diff)
downloadqemu-analysis-25f8033d556aa17afaea4a5196ea7a69fe248320.tar.gz
qemu-analysis-25f8033d556aa17afaea4a5196ea7a69fe248320.zip
add new temporary deepseek-r1:14b results
Diffstat (limited to 'results/classifier/deepseek-2-tmp/output/files/1289898')
-rw-r--r--results/classifier/deepseek-2-tmp/output/files/12898988
1 files changed, 8 insertions, 0 deletions
diff --git a/results/classifier/deepseek-2-tmp/output/files/1289898 b/results/classifier/deepseek-2-tmp/output/files/1289898
new file mode 100644
index 000000000..b005995cc
--- /dev/null
+++ b/results/classifier/deepseek-2-tmp/output/files/1289898
@@ -0,0 +1,8 @@
+
+qemu-system-ppc64 easily cause file corruption
+
+the qemu-system-ppc64 is used to run Fedora-19 on RHEL 5.3.
+Previously I was using QEMU 1.5.x for several months with no problem. But after the RHEL 5.3 host damaged, and rebuilt, now I tried both QEMU 1.6.2 and QEMU 1.7.0, found both can easily cause file corruptions. Symptoms:
+
+* using scp to transfer a tar.bz file from the RHEL 5.3 host to the Fedora-19 PPC VM, found the size is correct, but the content is corrupted from the middle of the 80+ MB file.  re-transfer again, got a correct file. But after untar, found some extracted files corrupted.
+The extracted file corruption happened several times, and also the filesystem in the VM had corrupted several times, had to restore the boot image to recover.
\ No newline at end of file