Jul 142014

The main reason of almost every post on this blog is the same.

Need to do something, dig the Net, take a while to find stuff so I think to make a note on my… virtual hints book πŸ˜‰

This time the need was to move a Windows 8.1 virtual machine from VMware Fusion for OS X 10.9.4 to VirtualBox on Linux.

The best option is to export and import the VM in OVA (Open Virtual Appliance) format, but there is no GUI option to export in Fusion. It took me a while to understand that Fusion comes with OVF Tool included, as a command line, and located in the default path “/Applications/VMware Fusion.app/Contents/Library/VMware OVF Tool

A working example of a command line is:

./ovftool --acceptAllEulas /Users/marco/Documents/Virtual\ Machines.localized/Windows\ 8.1\ x64.vmwarevm/Windows\ 8.1\ x64.vmx /Users/marco/Desktop/Win81.ova

The green part of the command above refers to specific names I gave to the VM in Fusion and to the OVA file.

–acceptAllEulas is an option to make the command less interactive.


Oct 302013

I’ve been struggling with VirtualBox 3.0 since I’ve upgraded my MacBook Pro to Mavericks one week ago.

The problem was that launching the software and Virtual Machines led to kernel errors like “Kernel Driver not loaded” and “Failed to load VMMR0.r0”

Googling leads to VirtualBox Forums and Apple Support Community posts stating to reinstall VirtualBox on top of existing installation, but this fixes the issue only temporarily since at reboot the issue will be still there.

Likewise, dragdropping VirtualBox to the Trash Bin and reinstalling seems not to help.

Even using the uninstal tool provided with VirtualBox does not seem to help.



The final trick is to modify the Mavericks security settings (Security & Privacy – General tab) for the time needed for the reinstallation, configuring the parameter “Allow apps downloaded from:” toΒ Anywhere as shown below:


Then confirm, proceed to install VirtualBox 3.0 and change back the setting to previous safer configuration.

Once completed, you can enjoy a “reboot-safe, error-free” VirtualBox environment.


Jan 302013

Very handy and easy operation, performed successfully on a Windows 7 64 bit box without ANY issue.

First, you go in Settings of the VM in VirtualBox and in Storage Section, remove the VDI Virtual HDD from the storage controller of the VM as shown in the picture below.

Once VDI is selected, click on - sign to detach it.

Once VDI is selected, click on – sign to detach it.

Then, you open a Terminal session, position in the VM directory and type the command:

VBoxManage modifyhd <name_of_the_VDI_file>.vdi --resize <new_size_you_want_in_megabytes>

You can follow the progression with the command output, which should be similar to the example reported below:

VBoxManage modifyhd ObsoleteOS.vdi --resize 50000

Once the command completes, remember to reattach the VDI to the VM before powering up.

When Windows boots up again, right click on Computer and select Manage to see the new disk space active and shown as an Unallocated partition.

To extend the current partition to match the new space, you need to use external softwares such as the free (for Home use) Easeus Partition Manager.


Dec 032012

Being in love with wonderful VirtualBox since I’ve tried the first time few years ago, I noticed that the disk files are often incompatible with VMware.

Today I’ve found a good solution and I want to make sure I will not forget, hence writing on my… favourite notepad πŸ™‚

The conversion trick can be done on a command line, using the utility VBoxManage with the clonehd parameter as follows:

VBoxManage clonehd "name_of_original_disk_file.vmdk" name_of_the_converted_disk_file.vmdk --format vmdk --variant standard

This will create in no time (13 GB converted in few seconds) a VMware compatible disk image which can be used as a starting point to recreate the VMware VM.

Example of the output is:

Clone hard disk created in format ‘vmdk’. UUID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx