1
0 Comments

I have installed both Windows and Linux on separate drives, but their boot managers are located on the same drive, which is the Linux drive.

My intention is to use VirtualBox in Linux to run my existing Windows installation. To do this, I created a vdmk image of /dev/sda and added it to the VirtualBox VM.

However, when I attempted to boot the VM, I received the following error message: “FATAL: Could not read from the boot medium! System halted.

I believe this is because the boot manager for Windows is on a different drive. The output of fdisk -l confirms this.

Disk /dev/nvme0n1: 119.25 GiB, 128035676160 bytes, 250069680 sectors
Disk model: SAMSUNG MZVLW128HEGR-000L2              
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 4FE65E84-A0C4-4173-AD7F-CE3C128F56B4

Device             Start       End   Sectors  Size Type
/dev/nvme0n1p1      2048 234883071 234881024  112G Linux filesystem
/dev/nvme0n1p2 234883072 247875583  12992512  6.2G Linux swap
/dev/nvme0n1p3 247875584 250069646   2194063    1G EFI System

Disk /dev/sda: 465.78 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 850 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 369746B4-CA1B-47E1-84C8-237D4200861E

Device         Start       End   Sectors   Size Type
/dev/sda1       2048 634562559 634560512 302.6G Linux filesystem
/dev/sda2  634562560 976773119 342210560 163.2G Microsoft basic data

The boot manager for Windows 10 is stored on the EFI System Partition (/dev/nvme0n1p3), along with the boot manager for my Linux partition, which is rEFInd.

I am unsure how to inform VirtualBox about the location of Windows’ boot manager.

Askify Moderator Edited question April 26, 2023