I got the impression that installing a new system on a dynamically growing disk image is pretty slow due to the continuous need to grow the file system for every new packet.
How about adding an option for specifying a minimum initial size that will be immediately allocated?
Initial size of dynamically growing disk images
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Initial size of dynamically growing disk images
"I got the impression" doesn't sound like very strong evidence, and being the first +1 to a post from 2008 probably indicates that this suggestion may not be a runner...
In any case the observation is b******t. The guest filesystem is not grown at any time. All that happens is that an additional 1MB block may be appended to the VDI file. That takes very little time unless your host drive is incredibly slow and congested - in which case no amount of fiddling in the VBox code will improve matters much.
In any case the observation is b******t. The guest filesystem is not grown at any time. All that happens is that an additional 1MB block may be appended to the VDI file. That takes very little time unless your host drive is incredibly slow and congested - in which case no amount of fiddling in the VBox code will improve matters much.