diff options
| -rw-r--r-- | blog/2020/03/31/vmdb2_can_t_build_an_image_without_partitions.mdwn | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/blog/2020/03/31/vmdb2_can_t_build_an_image_without_partitions.mdwn b/blog/2020/03/31/vmdb2_can_t_build_an_image_without_partitions.mdwn new file mode 100644 index 0000000..7b574a1 --- /dev/null +++ b/blog/2020/03/31/vmdb2_can_t_build_an_image_without_partitions.mdwn @@ -0,0 +1,13 @@ +[[!meta title="vmdb2 can't build an image without partitions"]] +[[!tag ]] +[[!meta date="2020-03-31 08:39"]] + +vmdb2 cannot currently build an image without partitions. Such an +image would sometimes be nice, and it'd be easier to resize. The +reason partitions are required is that vmdb2 specification files refer +to devices by symbolic names, or tags, and there's no way to refer to +the whole image with a tag. + +This will eventually be rectified. +See <https://gitlab.com/larswirzenius/vmdb2/-/issues/21> if you want +to comment. |