blob: f4d3420c4fcee1c553b68dfee055fcb15f912a17 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
|
KVM: 0.869
device: 0.743
graphic: 0.734
performance: 0.486
semantic: 0.456
virtual: 0.433
mistranslation: 0.431
boot: 0.374
files: 0.367
vnc: 0.362
socket: 0.347
ppc: 0.346
user-level: 0.341
architecture: 0.301
network: 0.245
PID: 0.239
permissions: 0.233
debug: 0.233
register: 0.181
assembly: 0.180
kernel: 0.157
hypervisor: 0.152
x86: 0.134
risc-v: 0.130
VMM: 0.117
i386: 0.106
peripherals: 0.096
arm: 0.089
TCG: 0.056
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.]
|