On Oct 11, 2016, at 06:12 PM, Oliver Grawert wrote: >on VMs the img file defines the "physical VM disk" while for an actual >install you write the img file to a pyhsical disk device ... the resize >code will find that the partition table does not cover all of the disk >before first boot and start the resize process so here the img size >wont be taken into account at all. > >on a VM, all the resize code will see is the img file that pretends to >be a harddisk and it will find there is nothing to resize to.
Thanks, that helps a lot. >> Also, if you specify a fudge factor via cli/envar, should that be applied >> in addition to, or instead of, any built-in compensation for file system >> overhead? > >i dont mind either, whatever is easier to implement (as long as the >help documents the right behaviour) ;) Okay, I think I can put together something rather quickly to get it into Yakkety. I am going to go with a command line option. Cheers, -Barry
pgpWKU2HP0AhO.pgp
Description: OpenPGP digital signature
-- Devices mailing list [email protected] Modify settings or unsubscribe at: https://lists.snapcraft.io/mailman/listinfo/devices
