summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/108/other/1470481
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/zero-shot/108/other/1470481')
-rw-r--r--results/classifier/zero-shot/108/other/147048129
1 files changed, 29 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/other/1470481 b/results/classifier/zero-shot/108/other/1470481
new file mode 100644
index 000000000..45e135116
--- /dev/null
+++ b/results/classifier/zero-shot/108/other/1470481
@@ -0,0 +1,29 @@
+KVM: 0.869
+device: 0.743
+graphic: 0.734
+performance: 0.486
+semantic: 0.456
+boot: 0.374
+files: 0.367
+vnc: 0.362
+socket: 0.347
+network: 0.245
+PID: 0.239
+permissions: 0.233
+debug: 0.233
+other: 0.118
+
+qemu-img converts large vhd files into only approx. 127GB raw file causing the VM to crash
+
+I have a VHD file for Windows 2014 server OS. I use the following command to convert VHD file (20GB) to a RAW file for KVM.
+
+qemu-img convert -f vpc -O raw WIN-SNRGCQV6O3O.VHD disk.img
+
+The output file is about 127GB. When install the VM and boot it up, the OS crashes with STOP error after the intial screen. I found on the internet that the file limit of 127GB is an existing bug. Kindly fix the problem. The workaround to use a Hyper-V to convert to fixed disk is not a feasible solution.
+
+Which version of QEMU (or rather qemu-img) have you been using here? Can you still reproduce it with the latest version (currently v2.12)?
+
+I have qemu-img 1.4.1 included in Suse Linux Enterprise server version 11 SP3. I will see whether I can update it and then try the conversion and post the results. 
+
+[Expired for QEMU because there has been no activity for 60 days.]
+