# Use physical harddisk in Virtual Box

Using Virtual Box, how can I install an OS to a secondary, physical disk, and boot it in both (at separate times) Virtual Box, and as a typical secondary OS install?

• Dec 10 '18 at 22:59

I made a smug comment ("Straight forward") when this question was originally posted and found myself at this page some months later looking for the same answer

# Straight forward instructions

Today, I managed to boot from physical drives. This achievement required;

• 60 min straight forward reading
• 30 min writing this
• 20 min trying different options in VirtualBox

Dear reader, your attention is directed at the fact that it is equally straight forward to kill your data when the disc is accessed in this manner. The procedure on how to accomplish this is left as an exercise...

# 1. Create vmdk drives that read from real drives

To create an image that represents an entire physical hard disk (which will not contain any actual data, as this will all be stored on the physical disk), on a Linux host, use the command

VBoxManage internalcommands createrawvmdk \
-filename /path/to/file.vmdk \
-rawdisk /dev/sda

You must have read access to the physical disk device file /dev/sda. To accomplish this you can either change the owner and access rights of the device file or run VBoxManage internalcommands createrawvmdk… as root (put sudo before the command).

On a Windows host, instead of the above device specification, use e.g. \\.\PhysicalDrive0. On a Mac OS X host, use e.g. /dev/disk1 (and unmount all partitions on disk1).

(all on one line)
C:\VirtualBoxDrives>"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe"
internalcommands createrawvmdk
-filename C:\VirtualBoxDrives\raw-0.vmdk
-rawdisk \\.\PHYSICALDRIVE0

(output)
RAW host disk access VMDK file C:\VirtualBoxDrives\raw-0.vmdk created successf..

# 2. Assign the vmdk drives to a VM

VM -> Settings -> Storage -> add ide / sata -> Choose existing disk -> browse

# 3. Set one of the Writethrough modes.

File -> Virtual Media Manager -> e.g raw-0.vmdk -> [modify] -> (o) Writethrough

• repeat for all drives

# 3. Reorder boot-priority (semi optional)

VM -> Settings -> System -> Boot order

[./] Hard Disk
[./] CD/DVD
[  ] Floppy
[  ] Network

VM -> Settings -> Storage -> Controller: SATA -> e.g. raw-5.vmdk -> Hard Disk: Sata Port 0

# Relevant chapters (manual)

• 9.9.1. Using a raw host hard disk from a guest

• Chapter 5. Virtual storage

• 5.2. Disk image files (VDI, VMDK, VHD, HDD)
• 5.3. The Virtual Media Manager
• 5.4. Special image write modes

Enumerating physical drives in Windows:

C:\Users\win7>wmic diskdrive list brief

Caption                               DeviceID            Model                                 Partitions  Size
Samsung SSD 840 EVO 250GB ATA Device  \\.\PHYSICALDRIVE3  Samsung SSD 840 EVO 250GB ATA Device  6           250057228288
ST1000DM003-1CH162 ATA Device         \\.\PHYSICALDRIVE1  ST1000DM003-1CH162 ATA Device         5           1000202273280
ST1000DM003-1CH162 ATA Device         \\.\PHYSICALDRIVE2  ST1000DM003-1CH162 ATA Device         5           1000202273280
ST1000DM003-1CH162 ATA Device         \\.\PHYSICALDRIVE0  ST1000DM003-1CH162 ATA Device         5           1000202273280
WDC WD1000DHTZ-04N21V0 ATA Device     \\.\PHYSICALDRIVE5  WDC WD1000DHTZ-04N21V0 ATA Device     6           1000202273280
WDC WD1000DHTZ-04N21V0 ATA Device     \\.\PHYSICALDRIVE4  WDC WD1000DHTZ-04N21V0 ATA Device     5           1000202273280
ST1000DM 003-1CH162 SCSI Disk Device  \\.\PHYSICALDRIVE6  ST1000DM 003-1CH162 SCSI Disk Device  5           1000202273280

You can also get the drive numbers with PowerShell:

PS C:\ Get-Disk
• Thanks very much for the clear step by step instructions. One problem I have had however is that the virtual .vmdk file can be owned by me as a user but when I start VirtualBox and it tries to access it an error is generated. This appears to be because the physical /dev/sda is owned by root. I tried changing ownership but no joy - still same error. Starting VirtualBox as root does work (though I'm always cautious about running any application as root, and one such as this with the potential for so much to go wrong scares me silly).
– user339549
Jun 28 '14 at 17:44
• Most distros have a special group such as "disk" or "block". Bock devices in /dev/sd? should be writable by users belonging to one of those groups. Check the docs for your distro. Jun 28 '14 at 20:44
• Anybody got this working on Windows 10? I'm getting this error: The I/O cache encountered an error while updating data in medium "ahci-0-0" (rc=VERR_ACCESS_DENIED)., even when running VirtualBox as admin.
– szx
Feb 4 '17 at 15:37
• @szx I managed to get around the VERR_ACCESS_DENIED problem following these steps Feb 11 '17 at 19:23
• For users getting this error: The I/O cache encountered an error while updating data in medium "ahci-0-0" (rc=VERR_ACCESS_DENIED), typically when using a partition of in-use disk, it is required to enable "Host I/O Cache" on storage controller: virtualbox.org/manual/ch05.html#iocaching Nov 26 '19 at 12:10

The VirtualBox documentation refers to accessing a raw hard disk:

http://www.virtualbox.org/manual/ch09.html#rawdisk

To create an image that represents an entire physical hard disk (which will not contain any actual data, as this will all be stored on the physical disk), on a Linux host, use the command

VBoxManage internalcommands createrawvmdk -filename /path/to/file.vmdk
-rawdisk /dev/sda

This creates the image /path/to/file.vmdk (must be absolute), and all data will be read and written from /dev/sda.

To create a special image for raw partition support (which will contain a small >amount of data, as already mentioned), on a Linux host, use the command

VBoxManage internalcommands createrawvmdk -filename /path/to/file.vmdk
-rawdisk /dev/sda -partitions 1,5

VirtualBox uses the same partition numbering as your Linux host. As a result, the numbers given in the above example would refer to the first primary partition and the first logical drive in the extended partition, respectively.

See the documentation for caveats and Windows-specific instructions.

Just want to elaborate how to do this in Windows 10

1. Get the Physical disk ID
• Open powershell
• Type 'Get-Disk'
• Look for your disk (write down the number column value)
1. Clear readonly attributes (credits to: Korkman at https://forums.virtualbox.org/viewtopic.php?f=6&t=38914#p175089)
• run DISKPART (command line utility)
• select hard drive carefully using SELECT DISK. disk numbering starts at zero. you can roughly verify your selection with LIST PARTITION if you know what your partitions should look like or LIST DISK to see disk sizes.
• offline the disk using OFFLINE DISK. all volumes will disappear from windows explorer.
• verify with ATTRIBUTES DISK
1. Change VirtualBox service account (credits to Kapodamy: https://unix.stackexchange.com/questions/284704/verr-access-denied-when-trying-to-add-a-raw-disk-to-virtual-box)
• Run services.msc in Run
• Look for virtual box service, change account on Log On tab to Administrator
• Restart the service
1. Create VMDK disk
• Open command prompt as Administrator
• type "C:\Program Files\Oracle\VirtualBox\VBoxManage" internalcommands createrawvmdk -filename C:\VM\Kubernetes\linux.vmdk -rawdisk \\.\PHYSICALDRIVE2
• type "C:\Program Files\Oracle\VirtualBox\VBoxManage" modifyhd "C:\VM\Kubernetes\linux.vmdk" settype writethrough
• type "C:\Program Files\Oracle\VirtualBox\VBoxManage" storageattach Kubernetes --storagectl SATA --device 0 --port 0 --type hdd --medium "C:\VM\Kubernetes\linux.vmdk"

I was attempting to boot a Linux VM (specifically Ubuntu 19.10) on macOS where Ubuntu is installed on a physical ext4 formatted partition. Many of the answers I found, including that from @ЯрославРахматуллин got me most of the way there, but I kept getting the following error message:

FATAL: No bootable medium found! System halted.

One answer referred to booting into a LiveCD and then altering the GRUB configuration to address this. However, I don't even have GRUB installed on my Mac. Eventually, I found the key for my situation was to ensure the VM had access to the EFI partition on my physical disk, and to enable EFI support in the VM settings.

Below is the output of diskutil list from my host Mac machine:

/dev/disk0 (internal, physical):
#:                       TYPE NAME                    SIZE       IDENTIFIER
0:      GUID_partition_scheme                        *251.0 GB   disk0
1:                        EFI NO NAME                 536.9 MB   disk0s1
2:                  Apple_HFS Macintosh HD            161.1 GB   disk0s2
3:       Microsoft Basic Data Development             9.1 GB     disk0s3
4:                  Apple_HFS Recovery HD             650.0 MB   disk0s4
5:           Linux Filesystem                         79.2 GB    disk0s5

From this, I generated the VMDK file as follows, giving the guest VM read-only access to the EFI partition and full write access to the NTFS (3) and Ext4 (5) partitions.

sudo VBoxManage internalcommands createrawvmdk -filename disk0.vmdk -rawdisk -partitions 1r,3,5

Now I can dual-boot MacOS or Ubuntu, and when already in MacOS, I can boot Ubuntu as a VM if needed. Happy days!

I was unable to get this working in Windows 10 for the longest time; I kept getting a VERR_ACCESS_DENIED error when attempting to attach the VMDK.

However, I was (finally) able to get this working with a few tricks:

1. Open PowerShell as an administrator (I'm not sure why, but I couldn't get some of the commands to work in an administrator command prompt)

2. Run the following command to create the VMDK:

VBoxManage.exe internalcommands createrawvmdk \
-filename "path\to\physical\disk\file.vmdk" \
-rawdisk \\.\PhysicalDrive[n]

...where path\to\physical\disk\file.vmdk is the file that will be created to represent the disk and [n] is the disk number (use Disk Management to obtain this number)

3. Run the following command to attach the VMDK:

VBoxManage.exe storageattach [VM NAME] \
--storagectl [CONTROLLER] \
--device 0 \
--port 0 \
--type hdd \
--medium "path\to\physical\disk\file.vmdk"

...where [CONTROLLER] is the name of the disk controller you are attaching to - "IDE" in my case

4. Run the following command to start the VM:

VBoxManage.exe startvm [VM NAME]

I found that to add the raw vmdk file to a vbox guest (Running ubuntu as host) one needs to change the permissions of the /dev/sdx file to 777 before building the vmdk file.

I got this mostly working with a Windows host and Linux guest by following the accepted answer.

However, I ran into the problem that the physical drive numbering in Windows doesn't stay the same across reboots. This is apparently the expected behaviour for disk numbering:

So technically, if you have a Windows host and a Linux guest, you should take an extra step: check the output of wmic diskdrive list brief again before you run the VM. If the numbering is different than it was when you created the VM, then don't run it. Otherwise, there's a risk that it will boot the Windows hard drive from within itself, which is the dangerous behaviour that they warn you about (hasn't seemed to cause any permanent damage in my case though). Or, if you prefer, create a second VM with the hard drives swapped, and choose which one to start based on the output of wmic diskdrive list brief. It should be possible to do all this in a script, but the script would be dependent on your system.

Or, perhaps simpler, make Linux the host and Windows the guest, if possible. Linux can get a consistent drive identification using /dev/disk/by-id/..., as mentioned in a comment.

MacOS 10.14:

1. Create a virtual disk file corresponding to the real disk:

# First, find the device you want to use inside Virtual Box:
diskutil list

# Create the virtual disk
sudo VBoxManage internalcommands createrawvmdk \
-filename ~/realdisk.vmdk \
-rawdisk /dev/disk2

2. Launch VirtualBox as a super user:

sudo VirtualBox

3. Add ~/realdisk.vmdk in Storage --> Controller: Sata.

I'm using a Linux host and Windows 10 guest. My problem is that the Windows physical drive changes on every boot - it's ranged from /dev/sdc to /dev/sdm.

My solution was to create a script thats runs on startup. It detects the drive with the WIN10 label, and then uses sed to replace the device in the .vmdk file to the current drive device.

#!/bin/bash

windrive=$(blkid | grep WIN10 | awk 'END{print$1}')

drive_device="${windrive: -5:3}" sed -i "s/sd./${drive_device}/g" "/home/testuser/VirtualBox VMs/Win10/test.vmdk"
• You could also create the VMDK file with the physical partition's UUID (/dev/disk/by-uuid/uuid-of-your-partition), which is exactly what it's used for, to prevent issues in case it changes on boot. Oct 7 '20 at 14:25
• I've not been able to make that work with Windows 10. The drive has two partitions, and using the UUID method won't let it boot unless it can see both partitions. Dec 24 '20 at 13:45