This is a limitation of cloud images, not uvtool. It comes from the filesystem size used at cloud image build time. On first boot cloud-init will grow the filesystem to available space, but, AIUI, cannot shrink it since it cannot be booted with a smaller size than the backing image. I don't understand your use case though. uvtool uses copy-on-write, so what you're really specifying is the maximum space you want the VM to be able to grow to.
I don't think the cloud image maintainers will consider this a bug, so I'm marking this as Invalid for uvtool rather than reassigning it. Feel free to start a discussion about minimum sizes somewhere though (eg. https://community.ubuntu.com/c/server or https://lists.ubuntu.com/mailman/listinfo/ubuntu-server). I suppose it might be possible to add a feature to uvtool to create a VM specific image that is shrunk further (and therefore necessarily not copy-on-write) but I'm not sure would be appropriate to consider with the scope of uvtool. You could script this yourself though, and then use --backing-image-file. ** Changed in: uvtool (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819463 Title: disk size limit with uvt-kvm create To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/1819463/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
