blob: ac4a4223a188480c28f77713ce3e9233d8a0ab8c (
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
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
|
device: 0.211
semantic: 0.179
graphic: 0.081
debug: 0.056
other: 0.035
socket: 0.029
performance: 0.021
PID: 0.019
vnc: 0.013
boot: 0.009
network: 0.007
permissions: 0.006
files: 0.005
KVM: 0.002
qemu-img will fail to convert images in 2.3.0
Hello guys,
There seems to be a bug in qemu-img with 2.3.0 that wasn't there in 2.2.1 .... qemu convert will always fail converting. See the output below:
Started by upstream project "Create windows image" build number 73
originally caused by:
Started by user anonymous
Building remotely on builder (builder lab) in workspace /var/lib/jenkins/remote/workspace/Prepare windows Image
[Prepare WS2008R2 Image] $ /bin/sh -xe /tmp/hudson4138890034689910617.sh
+ sudo bash -x /var/images/prepare_windows.sh WS2008R2
+ set +x
Preparing: windows
Virtio CD: virtio-win-0.1.96.iso
Sparsifying...
qemu-img: error while compressing sector 11131648: Input/output error
virt-sparsify: error: external command failed: qemu-img convert -f
qcow2 -O 'qcow2' -c -o 'compat=0.10' '/tmp/sparsifyb459a0.qcow2'
'/var/images/generated/WS2008R2.qcow2'
virt-sparsify: If reporting bugs, run virt-sparsify with debugging
enabled (-v) and include the complete output.
Build step 'Execute shell' marked build as failure
Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
Finished: FAILURE
Thanks,
Dave
I can't reproduce this. qemu-img convert works just fine here.
qemu-img convert -f qcow2 -O qcow2 -c -o compat=0.10 x.img y.img
(from a random winXP guest image).
The only possibly relevant change I can see in 2.3 is that the qcow2 driver added an additional error check to a truncate operation. Can you please run qemu-img under strace -f and either provide the output as an attachment or paste the relevant failing call(s) if you can recognise them?
I rolled back QEMU to 2.2.1 and it succeeded converting the image ... I'll try to see if I can re-upgrade QEMU without breaking again the CI we have here.
This problem is fixed with commit 3e5feb62 ("qcow2: Handle EAGAIN returned from update_refcount"), which will be included in qemu 2.4.0.
|