Did Moving It To A New Host Break My VM, Or Is It The Firmware Setting??

Solvedbootvirtualizationvm5 replies · 215 views · started
Accepted solution by Maya Ziegler — hmmm firmware mismacth is the most common cause. A disk with an MBR partition table needs BIOS/legacy boot (Hyper V Generation 1), while a…
  1. guys pls help ive been tasked with moving it to a new host for an old sevrer, now running on VMware ESXi. everything looked fine until i powered it on:

    Reboot and Select proper Boot device

    Reboot and Select proper Boot device
    or Insert Boot Media in selected Boot device and press a key
    
    No bootable device -- insert boot disk and press any key
    

    The virtual disk is attached and teh right size. The original machine booted fine yesterday. Where did my OS go?

    i can see the disk in the VM settings, so its definitely attached lmao the original server is still around, powered off, so i can check settings there if needed. what usually goes wrong when moving an OS like this?? im about to throw this thing out the window lol

    2
  2. ok but whats first in teh VMs boot order right now??

    2 0 helpful
  3. lol same thing happened to me if Secure Boot is on for a Linux guest in Hyper-V Gen 2, pick the 'Microsoft UEFI Certificate Authority' template or disable Secure Boot... with teh wrong template the VM falls through to 'No operating system was loaded'. good luck man!

    0 1 helpful
  4. Accepted solution

    hmmm firmware mismacth is the most common cause. A disk with an MBR partition table needs BIOS/legacy boot (Hyper-V Generation 1), while a GPT disk with an EFI partition needs UEFI (Generation 2)... check the guest disk with any parittion tool, then match teh VMs firmware type. hope that helps :)

    1 5 helpful
  5. @maya.ziegler Switched back to IDE, installed teh storage driver in the guest, then moved to SCSI. Boots fine now lol Thanks, all.

    6 5 helpful

Reply to this topic

Sign in or create an account to reply.