#120: Fedora 22 Cloud vagrant image does not extend filesystem to disk size
------------------------------+---------------------
Reporter: pwnall | Owner:
Type: defect | Status: new
Priority: normal | Milestone: Future
Component: Cloud Base Image | Resolution:
Keywords: |
------------------------------+---------------------
Comment (by jpeeler):
Cloud-init usage allows automatic dynamic resizing and might be the best
option to allow vagrant to nicely mirror what happens with most cloud
images. The F22 vagrant image wasn't technically broken, it was just small
at 3G. I would say that the situation with a static 40G image is only
slightly better now, because if somebody wants a smaller image they'll
have to umount the filesystem since (I think) online resizing only works
for growing the size. And again, if somebody wants something larger than
40GB they'll have to resize the filesystems/partitions themselves as well.
Hope that's clear - the whole point is to properly utilize the newly
available "machine_virtual_size" option in vagrant-libvirt.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/120#comment:9>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
