Skip to main content

Tricks for Windows 8 in Virtual Box

It's a bit of a ball ache getting Windows 8 to run nicely in VirtualBox. Here is a couple of small tips to help you though...


Install Virtual Machine Additions

This can be done, but you will need to mount Virtual Machine Additions as a disk, then explore and right click on the exe and set to run in Windows 7 compatability mode. 

Getting the resolution right

The resolution is never right if your using a laptop. You can use VboxManager to inject the correct resolution in the virtual machine though. You essentially go to your Virtual Box installation on your parent computer and run the following command.... 

C:Program FilesOracleVirtualBox>VBoxManage setextradata “Windows 8 Preview” CustomVideoMode1 1366x768x32

The "Windows 8 Preview" will be whatever you have called your Windows 8 virtual machine. Thanks to this site for this tip...


Changing the Virtual Disk Size

I made the foolish mistake of allowing the default virtual disk size of 20gb for my virtual machine. Windows 8 takes up quite a lot of space (around 8gb not including swap file space) and when you install Visual Studio 11 Beta that wants a massive amount of space as well. You will soon need more. First this trick, you firstly need to use VBoxManage again, discovered from above and then consulting the Virtual Box documentation. 

C:Program FilesOracleVirtualBox>VBoxManage modifyhd <your vdi> --resize 40960. 

Your vdi file is most likely somewhere like C:UsersYouVirtualBox VMsWindows8Windows8.vdi but you can find out where it is from Virtual Box anyway. 

Once you have done this, your Windows 8 installation will need it's partition resizing. You can do this using DiskPart. Open a command prompt up in Windows 8 by just typing CMD on the metro side.  At the command prompt type


to get you into the Diskpart program. You will then need to select the correct disk and volume. You can see your disks and volumes by typing





Make sure you select the correct disk and volume from those listed on the list commands as the next instructions will be performed on whichever you have selected....

You will then need to extend the disk to the amount you have resized the vdi to. Remember if you initially set it to 20gb and have resized to 40gb you will need to extend it by 20gb (20 * 1024 = 20480)


It should confirm this has been done. And I believe that is all you need to do.



Popular posts from this blog

Creating star ratings in HTML and Javascript

I'd searched around a little for some shortcuts to help in doing this but I couldn't find anything satisfactory that included the ability to pull the rating off again for saving. I'd ended up coming up with this rather cheeky solution. Hopefully it helps you too! This is my first post in a while (I stopped blogging properly about 8 years ago!) It's strange coming back to it. Blogger feels very crusty and old by todays standards too.

Make your objects immutable by default

More about the Good Dojo In my post last week , I discussed creating objects that are instantiated safely. Please go back and read if you are interested. At the end of the post, I mentioned that I'd also written the class so it was immutable when instantiated. This is important!!! I feel like a broken record in repeating this but I am sure at the time of writing your code, you aren't modifying your object all over the place and so are safe in the belief that protecting against mutability is overkill. Please remember though, your code could be around for a hell of a long time. You aren't writing your code for now... you are writing for the next fool that comes along (including you) . Nothing is more upsetting that coming back to fix a bug on some wonderfully crafted code to say "Who has butchered my code?!", but often you were involved at the start of the process. You made the code easy to modify, allowing objects to be used / reused / modified without thi

An instantiated object should be "ok"

I've been QA'ing quite a bit of work recently and one common theme I've noticed across both Java and C# projects I have been looking at is that we occasionally open ourselves up unessacarily to Exceptions by the way objects are being created. My general rule of thumb (which I have seen mentioned in a Pluralsight video recently but also always re-iterate in various Robust Software talks I have done) is that you shouldn't be able to create an object and then call a method or access a property that then throws an exception. At worst, it should return null (I'm not going to moan about that now). I've created an example below. We have two Dojos, one is good and one is bad. The bad dojo looks very familiar though. It's a little class written in the style that seems often encouraged. In fact, many classes start life as something like this. Then as years go on, you and other colleagues add more features to the class and it's instantiation becomes a second