When saving a VM or VM Template settings form, the disk size for all disks are reset to the value specified in the form. Luckily, this has no direct effect yet.
But when cloning a VM from a VM Template, those values are used for the new disks, therefore leading to one of the following problems:
larger disk sizes for all volumes other than vda than the respective original
smaller disk sizes for all volumes other than vda than the respective original, leading to disk corruption since partitions/filesystems get truncated
When saving a VM or VM Template settings form, the disk size for all disks are reset to the value specified in the form. Luckily, this has no direct effect yet.
But when cloning a VM from a VM Template, those values are used for the new disks, therefore leading to one of the following problems: