Skip to main content

Increasing Virtualbox disk size (Increasing VHD size without cloning)



Lets just face it, I like VirtualBox. I have used it in numerous occasions, back from the days when it was offered by Innotek, to Sun and now Oracle. Yeah it always was a less powerful than Vmware in some areas, but when i don't need them this was as good (or maybe sometimes better) than Vmware for my basic sandboxing needs!

But sometimes I find myself in a problem which the GUI isn't always helpful for me. One of them is when in an active Virtual Machine I run out of diskspace.

There are a number of ways to increase harddisk size without destroying your data, but most of them involve cloning or copying your data to a new vdi. Though they are also relatively painless I found a much more easier solution. Or rather a one liner

The following command will operate on the VirtualBox virtual disk located at “C:\Users\rk\VirtualBox VMs\Windows 7\Windows 7.vdi”. It will resize the virtual disk to 21920 MB (20 GB).

VBoxManage modifyhd “C:\Users\rk\VirtualBox VMs\Windows 7\Windows 7.vdi” –-resize 21920

Which actually will look like the following



Then boot up the Virtual Machine. You have assigned the space but you won't be able to access it right now. So we have to make it accessible within the guest os.

Open up Disk Management tool and it will look like the following


Just select the active drive and click Extend Volume. It will automatically extend it and you will have all the space you need


Comments

Popular posts from this blog

FirefoxOS, A keyboard and prediction: Story of my first contribution

Returning to my cubical holding a hot cup of coffee and with a head loaded with frustration and panic over a system codebase that I managed to break with no sufficient time to fix it before the next morning.  This was at IBM, New York where I was interning and working on the TJ Watson project. I returned back to my desk, turned on my dual monitors, started reading some blogs and engaging on Mozilla IRC (a new found and pretty short lived hobby). Just a few days before that, FirefoxOS was launched in India in the form of an Intex phone with a $35 price tag. It was making waves all around, because of its hefty price and poor performance . The OS struggle was showing up in the super low cost hardware. I was personally furious about some of the shortcomings, primarily the keyboard which at that time didn’t support prediction in any language other than English and also did not learn new words. Coincidentally, I came upon Dietrich Ayala in the FirefoxOS IRC channel, who...

April Fool and Google Part 2: A Round Up of ALL of Google’s April Fools Jokes

Ok....this post I think will contain all of the pranks I could find  for today. After my last post here http://rkrants.blogspot.com/2012/04/april-fool-and-google-my-favorite.html Last Time I reported Only a handful of the pranks.. Understandable, as it was only the morning. After that I stumbled upon more of them Which I am gonna round up here. Now staring with the list. The very first one is obviously our favourite Google Maps Quest The above is their official video. In a post in Google Plus they say about it as follows  Today  + Google Maps  announced Google Maps 8-bit for NES. With #8bitmaps , you can do everything you'd normally do in Maps—search for famous landmarks and sites around the world, get directions and even use Street View. Just in time for April Fool's Day, Google has introduced Google Maps Quest, a retro 8-bit version of its mapping tool that is... totally awesome. In a characteristically whimsical video, availabl...

Curious case of Cisco AnyConnect and WSL2

One thing Covid has taught me is the importance of VPN. Also one other thing COVID has taught me while I work from home  is that your Windows Machine can be brilliant  as long as you have WSL2 configured in it. So imagine my dismay when I realized I cannot access my University resources while being inside the University provided VPN client. Both of the institutions I have affiliation with, requires me to use VPN software which messes up WSL2 configuration (which of course I realized at 1:30 AM). Don't get me wrong, I have faced this multiple times last two years (when I was stuck in India), and mostly I have been lazy and bypassed the actual problem by side-stepping with my not-so-noble  alternatives, which mostly include one of the following: Connect to a physical machine exposed to the internet and do an ssh tunnel from there (not so reliable since this is my actual box sitting at lab desk, also not secure enough) Create a poor man's socks proxy in that same box to have...