diff options
Diffstat (limited to 'results/scraper/launchpad-without-comments/907063')
| -rw-r--r-- | results/scraper/launchpad-without-comments/907063 | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/results/scraper/launchpad-without-comments/907063 b/results/scraper/launchpad-without-comments/907063 new file mode 100644 index 00000000..8de84843 --- /dev/null +++ b/results/scraper/launchpad-without-comments/907063 @@ -0,0 +1,10 @@ +Error reading VMDK4 with footer instead of header + +VMDK4 files can have a footer in the last block, which is the same datastructure as the header but must be used instead if present. In this case, the gd_offset in the usual header at the beginning of the file is the special flag -1 (VMDK 1.1 spec, page 17, "GD_AT_END +"). qemu-img doesn't know about this flag so it goes on to try to read extents with a bogus l1_table from the wrong location in the file. + +I have regression-tested this with various OVAs exported from VSphere/ESXi 3 and 4. Current master and all previous QEMU versions were unable to import any compressed VMDKs with a footer. It now works on all the ones I have. + +bb45ded93115ad4303471c9a492579dc36716547 changed the order of gd_offset and rgd_offset in the VMDK4Header struct. Page 8 of the VMDK 1.1 spec from VMWare shows the structure as rgd_ then gd_, while QEMU now has gd_ *before* rgd_offset. I was only able to get VMDK conversion to work by switching the order back to that specified by VMWare and previously used by QEMU. I don't know what VMDK this commit is referring to, so I can't test to see if I've broken it. :( + +I will submit this patch to the mailing list if I get a chance, but I'm also uploading it here so I don't lose it. \ No newline at end of file |