Skip to main content

Increasing hard disk space (vdi) size of a VirtualBox guest VM

I had to create a VM for searching some 6TB (that is 3 years of mails for 800 users) of mails from a NAS storage. I installed VirtualBox on a desktop with Linux Mint 19 with 16GB RAM and 1TB HDD. Then created a VM for Windows 7 with default configuration. The size was only 32GB which was much less than what was needed. I couldn't spare much time as the search request was very urgent. After a 3 week search ordeal the Windows 7 guest OS crashed which made me search for VDI resizing in DuckDuckGo. I got the below command from ASKUBUNTU.

VBoxManage modifyhd YOUR_HARD_DISK.vdi --resize SIZE_IN_MB

I wanted 100Gb so I converted it in DuckDuckGo with command 100 GB to MB and it gave 100000. So the command I derived is as below.

VBoxManage modifyhd /home/rhs/VirtualBox\ VMs/Windows7/Windows7.vdi --resize 100000

It gave the result/output as below if the command is correct.


When I started the VM Guest Windows 7 OS I found the HDD space was only 32GB still.

So something struck me like I saw in the disk resize option in Windows 7. So I headed to the Control Panel > Administrative Tools > Computer Management > Disk Management option and saw that 60GB odd was left as unpartitioned space. So I right clicked on C Drive and saw extend option. The extend option gave me the full available space. Click Next two times and viola the total 100000MB was converted to 99GB.

By the way I restarted the VirtualBox before the Guest OS resize.

Problem solved


Popular posts from this blog

Create Great looking diagrams -

I was looking for an online diagram creating tool. Came across where I could create actually great looking diagrams without much of learning curve. The tool is 1. Very easy to use 2. Has drag and drop of elements to your diagram 3. Collaboration (which I have not tested). 4. Works from anywhere on a browser with Internet connection (I used it in Google Chrome on Linux Mint 10) When you click on the "Try it now" a new screen will open as below. You can either create a blank page to create a diagram from scratch or select from a bunch of samples and work on them to create one for your requirement. There are options to export the diagrams you created to SVG, JPEG, PNG and XML format once you register for free on the website. Once you register you can save the diagrams that you created in the site itself and retrieve it at a later time by logging into the website. I made three diagrams and it was real easy and simple. The site has two kind of pa

How to Configure Samba to Share a Folder with Two Users on Ubuntu (with Read/Write and Read-Only Permissions)

Samba is a file sharing software that allows you to share files between Linux and Windows computers. It is a popular choice for home users and businesses alike. In this article, we will show you how to configure Samba to share a folder with two users, one with read/write permissions and one with only read permissions, on Ubuntu. Prerequisites Before you begin, you will need the following: A Linux computer running Ubuntu Two user accounts A shared folder Steps Install Samba. sudo apt install samba Create the shared folder. sudo mkdir /shared Configure Samba's global options. Open the Samba configuration file /etc/samba/smb.conf in a text editor. Add the following lines to the [global] section: security = user passdb backend = tdbsam This will set the security mode to user , which means that users will be authenticated using their local Linux accounts. The passdb backend option specifies the database that Samba will use to store user passwords. In this case, we are using the tdbsa

Kerio Connect - SQLLite journal.db error

Today I noted that the Keio Connect mail server had thousands of error.log files with 75MB size filled up in the server. As always Google gave the answer. The error looks some what like below. [10/Aug/2011 10:49:35] SQLiteDbWriteCache.h: write_thread - file '/path/to/file/<user>/.journal.db', SQLite error: code 1, error SQLITE_ERROR[1]: no such table: journal_temp The solution is as below 1. Delete the cache from the client's workstation 2. Delete the profile 3. Stop the server 4. Go to the server and navigate through the user's store folder 5. Delete the .journal.db (for Linux it is  find . -name "FILE-TO-FIND"-exec rm -rf {} \; ) 6. Start the server 7. Create a new profile for the clients workstation With help from Kerio Forum Cyberciti