- Full compatibility: Uses native VDI as well as VMDK/VHD with appropriate drivers.
- Advanced management: UUID, encryption, bridge/NAT networking, and optimized resources.
- Storage Flexible: Expand VDI or add disks without reinstalling the guest.
If you have a virtual disk already prepared and want to get it up and running as soon as possible, learn how to install a VDI image on VirtualBox is just what you need. This guide covers, step by step, everything you need to open a machine with an existing VDI in Windows o Linux, without having to reinstall the guest operating system from scratch.
You will find everything from basic VDI import to fine-tuning such as change the disk UUID, configure network, clipboard and shared folders, expanding the size of the VDI, or adding a second virtual disk. The goal is to have your virtual machine sleek, stable, and ready to work without wasting time with a little TLC.
What is a VDI file and when should you use it?
VDI is the VirtualBox native disk format. It's basically the file that contains your machine's virtual hard drive (system, programs, and data). Mounting it on an existing or new VM avoids reinstalling the system, which is key when that VDI already has configured or licensed software which would be a hassle to replicate.
A common scenario is reinstalling your Linux or Windows host, only to find that VirtualBox doesn't recognize your previous VMs. Instead of starting from scratch, you can create a new machine and attach the existing VDI. So, in minutes you can restart that Windows XP, 7, 10, 11 or the Linux distro you already had running.
The same idea applies whether you have downloaded a ready-made VM from the Internet or if you come from another computer: with the VDI in hand and a couple of clicks, the machine will be ready. ready to start on your current host.
If you also handle other formats, VirtualBox also opens VMDK of VMware and Microsoft VHDs, so you can reuse disks from different hypervisors quite comfortably; see the comparison of disk image formats for more details.
The same idea applies whether you have downloaded a ready-made VM from the Internet or if you come from another computer: with the VDI in hand and a couple of clicks, the machine will be ready. ready to start on your current host.
Requirements and preparations
Before you get started, make sure you have the following things in place to make the import process as smooth as possible: VDI in VirtualBox be fluent:
- A computer with a graphical environment (Linux or Windows) and VirtualBox installed.
- The file of virtual disk .VDI (or .VMDK/.VHD) that you are going to use.
- Sufficient free space on the host disk and read/write permissions on the VDI folder.
- (Optional) The Extension Pack of VirtualBox for features such as disk encryption.
- (Recommended) Install Guest Additions in the guest for better integration.
Having all this in place reduces errors and speeds up implementation, which is especially useful if the VDI comes from another computer or a backup previous.
Create or import a machine from a VDI
There are two valid ways to boot a VM with an existing VDI disk: create the machine and choose "use an existing virtual disk", or create the machine no disk and attach the VDI from the storage section. Both methods are simple and essentially equivalent.
Option 1 (the most direct): open VirtualBox, click on "New" and complete the wizard indicating name, type and version of the system. When it asks you for the disk, select "Use an existing virtual hard disk file", click the folder icon, locate the VDI and confirm with “Create”.
Option 2 (useful if you prefer to prepare the VM first): Create the machine by checking “Do not add a hard drive». Then, in Settings > Storage, add (or verify) a SATA controller and tap “Add Hard Drive” for “Select Existing Drive”. Navigate to the VDI and accept it to attach it.
In both cases, check parameters such as RAM, processors, video, and network. It's a good idea to adjust them before starting so that the guest Boot in optimal conditions.
Resolving UUID conflicts when cloning VDI disks
VirtualBox identifies each virtual disk by a Unique UUIDIf you make copies of the same VDI and try to use them on the same host, you may receive a duplicate UUID error. The solution is to assign a new UUID to the copy using VBoxManage.
To do this, open a terminal o PowerShell and execute the command sethduuid about the VDI file. You can either first navigate to the folder where the VDI is located or specify the full path in the command to avoid confusion.
On Windows, from the VirtualBox installation directory (by default) C:\\Program Files\\Oracle\\VirtualBox) you can open PowerShell by Shift + right clicking on an empty space ("Open PowerShell window here") and launch:
VBoxManage internalcommands sethduuid 'disco.vdi'
It works the same on Linux (with VBoxManage in PATH). Open the terminal in the VDI folder and run the same command. sethduuid to regenerate the identifier:
VBoxManage internalcommands sethduuid 'disco.vdi'
If VBoxManage is not recognized in Windows, add the VirtualBox folder to the System PATH. These are the steps:
- Right-click on “This PC” and go to “Properties.”
- Open “Advanced system settings.”
- On the Advanced tab, click Environment Variables.
- Under “System Variables,” find and edit “Path.”
- At the end of the value, add a semicolon and the path: C:\\Program Files\\Oracle\\VirtualBox.
- Save with "OK" in all windows to apply the changes.
Once the UUID is unique, attach the VDI in Configuration > Storage. If no controller exists, add one SATA controller and, on the right, use "Add Hard Drive" to link the file. This will prevent VirtualBox from complaining about duplicate IDs.
Key Settings: CPU, ISO, Guest Additions, Folders, and Clipboard
After importing the VDI, it's a good idea to fine-tune resources and tools for smooth performance. In Settings > System > Processor, decide how many cpu cores you will give in to the guest without drowning the host.
If you need to start with a ISO (for example, to repair the system or install drivers), go to Storage, select the CD icon and choose “Select virtual optical disk file” to mount the image for use on the next boot.
Install the Guest Additions from the VM menu to improve video, mouse, time sync, and integration extras. This makes a difference in usability and performance.
With Additions, activate the shared clipboard and "Drag and Drop" in Settings > General > Advanced. Select "Bidirectional" if you want to move text and files both ways comfortably.
To shared foldersIn Settings > Shared Folders, tap the folder icon with a "+," choose the host folder, give it a name, and enable the options you need (read-only, automount, permanent mount). You'll see that folder in the guest's browser.
If you are looking to encrypt the VM disk, please install the Extension Pack. Then, under General > Disk Encryption, enable the option, define a password, and set the encryption algorithm. This is useful for protecting sensitive data within the guest.
Also remember the "Host key» in VirtualBox (usually right Ctrl). It allows you to combine shortcuts like "Ctrl+Alt+Del" within the guest without affecting the host and manage inputs from the "Input" menu in the top bar.
Network: Choose the appropriate mode
In Settings > Network, you have several ways to adjust connectivity. The default setting is NAT, which allows the guest to access the Internet but it is not visible from the local network.
These are them main options and when to use them:
- Not connected: : the VM is left without a network, useful for isolated tests.
- NAT: Internet access via the host; simple and fast to navigate.
- NAT Network: Similar to NAT, but allows multiple VMs to communicate with each other.
- bridge adapter: : the VM gets IP from the router y appears on your network like any other piece of equipment (ideal for sharing and being accessible).
- Internal network: Total isolation from the outside; only VMs on the same internal network are visible.
- Host only: The VM talks to the host, but not to the external network.
- Generic controller: Advanced option for special hardware/driver cases.
For most LAN work scenarios, «bridge adapter» is the most useful choice: the VM will be detected by other computers and can share resources as if it were a physical PC. For multiple labs, «NAT Network» can be a great option.
Manage storage: expand a VDI and add a second disk
If you run out of space, you can expand the VDI from the line of commandsIt is important that the disk be of the dynamic type for the operation to work as expected.
On Windows, open PowerShell in the VirtualBox installation folder (or add the path to the PATH) and run:
.\VBoxManage.exe modifyhd 'ruta-al-disco.vdi' --resize 80000
In the example, the VDI is expanded to 80.000 MB (about 80 GB). Adjust the value to your needs and check that the command completes without errors.
Then, within the Windows guest, open Disk Management. You'll see the new space as "unallocated" in black. Right-click on the system partition and select "Extend volume» so that Windows consumes that space and grows the partition.
As an alternative to expanding, add a second disc to the VM. In Settings > Storage, create a new disk (VDI/VMDK/VHD), select "dynamically allocated" and define the size. Optionally, you can select it to be SSD or that allows hot plugging.
Boot the VM, open Disk Manager, initialize the new disk and create a "simple volume». If it doesn't appear, restart the guest so it detects it. This is a safer way to gain space without touching your main drive.
Export, import and clone machines
To move VMs between machines or hypervisors, use "File > Export virtualized service» and generates an OVF/OVA package. OVA packages everything into a single file, while OVF separates the descriptor and disks. Most platforms (e.g., VMware) support it well.
The reverse process is done with "File > Import virtualized service». Choose the OVF/OVA, check the parameters and that's it. It's a standard way to share and transport VMs with less friction.
If you only need to duplicate a VM on the same host, use "Clone» on the powered-off machine. Assign a name and enable the "Reset MAC Address" option to avoid network conflicts. You'll have two identical machines without reinstalling.
Open VMware disks (VMDK) or create from existing VDI
VirtualBox allows you to create a new VM by choosing "Use an existing virtual hard disk file» for both VDI and VMDK. After selecting the file, define the memory and name, and click "Create" to have the machine ready.
If you prefer more manual control, create the diskless VM and attach the VMDK/VDI from Storage, making sure to use a suitable controller (SATA, NVMe, IDE) depending on the system and how the original disk was created.
Practical notes on Linux (Ubuntu and other distros)
On Linux, the import and configuration steps are identical to those of Windows within VirtualBox. The difference is in the use of the terminal for VBoxManage and the location of the files, but the logic is the same.
If you work a lot on servers, consider using VirtualBox in virtual mode. Headless to run VMs without a graphical interface. And if you're looking for a lightweight Linux desktop alternative, Gnome Boxes can be useful for quick testing, although VirtualBox is more comprehensive.
With all this, you should be able to go from having a VDI "in hand" to a fully functional virtual machine, with a well-configured network, tight resourcesHost-Guest integration (clipboard, drag and drop, folders), and storage sized to your liking. If you also leverage OVF/OVA to move machines and cloning to duplicate them, you'll have a robust and repeatable workflow for any environment.
Passionate writer about the world of bytes and technology in general. I love sharing my knowledge through writing, and that's what I'll do on this blog, show you all the most interesting things about gadgets, software, hardware, tech trends, and more. My goal is to help you navigate the digital world in a simple and entertaining way.