Unfortunately, it's the only hypervisor that vagrant supports decently and it works on Mac OS X, Windows and Linux (as opposed to using KVM on Linux, xhyve on OSX and Hyper-V on Windows. It's on life support and will stay like that for a little while.
MAC OS X ISO FOR VIRTUALBOX 5.1 HOW TO
The reality is, they don't know how to steer open source projects and have no desire to do that anyway (separate private bug tracker? write access to repository only to Oracle employees? harsh email replies and comments on bug reports?). One day, enough customers will stop paying Oracle for it, they will look at community contributions (rare to nonexistent?) and will close the project down rationalizing it as they did all the work. It's a dead project just like OpenOffice, OpenSolaris, etc.
![mac os x iso for virtualbox 5.1 mac os x iso for virtualbox 5.1](https://www.sysprobs.com/wp-content/uploads/2010/05/workingmac-1024x832.png)
The community has no interest in maintaining VirtualBox, mostly because of Oracle.
![mac os x iso for virtualbox 5.1 mac os x iso for virtualbox 5.1](https://techspite.com/wp-content/uploads/2019/06/macos.jpg)
They are completely broken and/or missing important features. Having said that, if 10-20 GB of space are taken so quickly on boot, it may be worth investigating (you could even vim the diff disk), but I find your claim somewhat misleading, as you're likely experiencing this on the first absolute boot after taking then snapshot, but not on the subsequent ones therefore, if your system steadily takes 20+20 GB of space, that's a perfectly reasonable requirement.īetter shared folders and 3D acceleration would be a good start. It's inappropriate to target space saving when it comes virtualization, as it's not what hypervisors are designed for - if so, a hypervisor would have to interpret the underlying FS calls, and optimize them space-wise.īesides, I think pretty much all the formats behave the same qcow2 for example, does not optimize on the fly the writing of zeros.Īll in all though, if you ultimately moved to a native Windows 10, therefore allocated X space of native disk, the space requirement is not different from having only a virtualized one with X space of virtualized disk (heck, you could even pass a partition).