Failing to create bootable virtual machine from existing drive

Discussions related to using VirtualBox on Windows hosts.
Post Reply
Steve K
Posts: 1
Joined: 25. Mar 2024, 02:13

Failing to create bootable virtual machine from existing drive

Post by Steve K »

Hi,

I last used VirtualBox maybe a decade ago and then only to create new virtual machines from Windows installation media. Now I'm facing a different use case: I want to image my aging fathers laptop so I can run it on VirtualBox. I did some research and followed a blog post that described how to accomplish what

Here's what I've done:
  1. The guest OS is Windows 10 Pro on 2-3 year old Dell Latitude 5521
  2. Utilized Disk2vhd to produce a VHD file (selected all partitions, all 3 options NOT selected)
  3. In VirtualBox, created a new Virtual Machine, selected my VHD file as the virtual disk
  4. Ensured the boot sequence is correct (virtual drive is first)
When I attempt to start the machine, I receive error:

Code: Select all

No bootable medium found!
Please insert a bootable medium and reboot.
What I've tried:
  • Enabling EFI on the VM
  • Verified boot sequence is correct
  • Created a new VHD file (just in case something odd happened with the first)
  • Searching the web for clues & solutions (coming up empty)
I'm unsure which logs are useful to assist me. I've attached what I believe is the main log, but to be honest I'm confused about the various logs.
OK, I'm sure I've failed to supply some information that is useful, please let me know if there is anything else I can provide that will help.


Regards,
Steve
Attachments
JK Laptop-2024-03-24-17-50-39.log
(185.96 KiB) Downloaded 6 times
BillG
Volunteer
Posts: 5105
Joined: 19. Sep 2009, 04:44
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows 10,7 and earlier
Location: Sydney, Australia

Re: Failing to create bootable virtual machine from existing drive

Post by BillG »

There are a few things to consider with this.

1. Copy all partitions. (You did that one).

2. Use the vhdx option. (.vhd has serious problems).

3. You must use the correct disk format for the boot method you use. If the PC used legacy boot, so must the vm. Ditto for UEFI, otherwise you will need to change the disk format from MBR to GPT (or vice versa). You will find tutorials online to do this, if you need to.

It won't stop you booting, but your log shows that your host PC has the Windows hypervisor loaded. This will slow down the vm when you get it to boot. See this tutorial. viewtopic.php?t=99390
Bill
Post Reply