| 2012-04-18 14:37:39 |
Volker Grabsch |
description |
When using "qemu-img convert" to create a VDI image, the VDI image is valid, but may contain an altered disk image. When such an image is run under VirtualBox, subtle bugs such as spontaneous segmentation faults happen because of broken system libraries.
The following set of commands reproduces the bug (using the provided test disk image slice):
bunzip2 < test-2M-2.raw.bz2 > test.raw
qemu-img convert -O vdi test.raw test-2.vdi
qemu-img convert -O raw test-2.vdi test-2.raw
diff -qs test.raw test-2.raw
# Output: Files test.raw and test-2.raw differ
If the VDI image is created via "VBoxManage convertfromraw", everything is okay:
VBoxManage convertfromraw test.raw test-3.vdi --format VDI 2>/dev/null
qemu-img convert -O raw test-3.vdi test-3.raw
diff -qs test.raw test-3.raw
# Output: Files test.raw and test-3.raw are identical |
When using "qemu-img convert" to create a VDI image, the VDI image is valid, but may contain an altered disk image. When such an image is run under VirtualBox, subtle bugs such as spontaneous segmentation faults happen because of broken system libraries.
The following set of commands reproduces the bug (using the provided test disk image slice):
bunzip2 < test-2M-2.raw.bz2 > test.raw
qemu-img convert -O vdi test.raw test-2.vdi
qemu-img convert -O raw test-2.vdi test-2.raw
diff -qs test.raw test-2.raw
# Output: Files test.raw and test-2.raw differ
If the VDI image is created via "VBoxManage convertfromraw", everything is okay:
VBoxManage convertfromraw test.raw test-3.vdi --format VDI
qemu-img convert -O raw test-3.vdi test-3.raw
diff -qs test.raw test-3.raw
# Output: Files test.raw and test-3.raw are identical |
|
