| 2008-08-23 19:28:02 |
robvarga |
description |
Binary package hint: ubuntu-vm-builder
When creating the partitions within the .raw files with parted, ubuntu-vm-builder leaves a 1MB gap between partitions:
E.g. When using 1000MB swap file and 2000 MB root, the partitions will be created as follows:
0-1000MB swap
1000MB-1001MB gap
1001MB-3001MB root
Also, the size of the created image file as passed to the qemu-img create command is one MB larger than the end of the last partition, so in this case it is 3002 MB, so there is an additional megabyte gap after the last image.
This means that if the image is converted to a raw_device, then there should be (in this case) at least 3002MB allocated for the device (e.g. by LVM) in order for it to safely be able to hold the entire image.
Are these gaps intentional, or are these bugs in the script (deficiencies due to calculating with megabytes instead of with sector numbers)?
Best regards,
Robert |
Binary package hint: ubuntu-vm-builder
When creating the partitions within the .raw files with parted, ubuntu-vm-builder leaves a 1MB gap between partitions:
E.g. When using 1000MB swap file and 2000 MB root, the partitions will be created as follows:
0-1000MB swap
1000MB-1001MB gap
1001MB-3001MB root
Also, the size of the created image file as passed to the qemu-img create command is one MB larger than the end of the last partition, so in this case it is 3002 MB, so there is an additional megabyte gap after the last partition in the image.
This means that if the image is converted to a raw_device, then there should be (in this case) at least 3002MB allocated for the device (e.g. by LVM) in order for it to safely be able to hold the entire image.
Are these gaps intentional, or are these bugs in the script (deficiencies due to calculating with megabytes instead of with sector numbers)?
Best regards,
Robert |
|
