blob: 47bb87b232bca4d0b1d71df914ae11f36b0c7d34 (
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
|
graphic: 0.781
device: 0.773
semantic: 0.732
files: 0.709
vnc: 0.704
user-level: 0.688
performance: 0.679
register: 0.639
network: 0.637
socket: 0.634
permissions: 0.634
architecture: 0.622
ppc: 0.563
mistranslation: 0.561
VMM: 0.542
hypervisor: 0.534
virtual: 0.512
PID: 0.500
debug: 0.423
peripherals: 0.414
risc-v: 0.414
kernel: 0.392
TCG: 0.392
boot: 0.359
arm: 0.358
KVM: 0.306
i386: 0.244
x86: 0.241
assembly: 0.094
qemu-img convert file.vmdk: Invalid footer
Steps to reproduce
- Open ESXi 6.5 Web UI
- Export OVF
- qemu-img convert disk.vmdk disk.qcow2
Error:
qemu-img: Could not open './disk-1.vmdk': Invalid footer
I found another person having this problem here:
https://forum.proxmox.com/threads/error-converting-vmdk-file-to-qcow2-file.38264/
As I guess from the answer, the guy went over to manually copy the flat file from the datastore instead of using the ovf-exported file.
Nevertheless, I think this bug should be investigated further and closed. Probably it is just some metadata issue and should not be too hard to fix once the root of the problem is found.
I just compiled the version in the master branch and the same error occurred.
Probably my image was corrupt since it works with another image. So this bug can be closed.
|