summaryrefslogtreecommitdiffstats
path: root/results/classifier/111/review/567380
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/111/review/567380')
-rw-r--r--results/classifier/111/review/56738051
1 files changed, 51 insertions, 0 deletions
diff --git a/results/classifier/111/review/567380 b/results/classifier/111/review/567380
new file mode 100644
index 00000000..810bcf97
--- /dev/null
+++ b/results/classifier/111/review/567380
@@ -0,0 +1,51 @@
+semantic: 0.189
+other: 0.147
+graphic: 0.141
+files: 0.089
+device: 0.071
+performance: 0.061
+PID: 0.056
+socket: 0.048
+network: 0.040
+permissions: 0.038
+debug: 0.036
+boot: 0.035
+vnc: 0.027
+KVM: 0.022
+other: 0.149
+debug: 0.148
+files: 0.138
+network: 0.091
+socket: 0.079
+PID: 0.069
+performance: 0.068
+device: 0.065
+semantic: 0.059
+vnc: 0.043
+boot: 0.029
+graphic: 0.025
+permissions: 0.021
+KVM: 0.015
+
+qemu-img fails to create images >= 4G
+
+On a Windows XP system and an NTFS drive, using QEMU on Windows Ver 0.12.2 from http://homepage3.nifty.com/takeda-toshiya/qemu/ or QEMU 0.12.3 or d3538b45ea88e82d1b01959b4ca55d3696b71cb2 built locally, when I run the following command, a zero-length file is created.
+
+ qemu-img create foo.img 4G
+
+Confirmed under Win 7 64-bit.
+Also does same thing on v10.6, v11.1, v12.1
+
+what a zero-length file means? Run the following command to see
+qemu-img info foo.img
+
+The file size was zero bytes (i.e., it contained no data).
+
+I've tried again with QEMU 2.6.50 on a Windows 7 Professional system and it appears to have created the s
+
+Sorry, I accidentally submitted comment #3 without finishing it.
+
+I was going to say that when I tried QEMU 2.6.50 on a Windows 7 Professional system, it appears to have created the image file successfully.
+
+Thanks for the update ... since it is working with the current version of QEMU, I assume this problem has been fixed sometimes during the past years, thus we can close this ticket now.
+