We have several Linux VMs that use BIOS-based boot partitions.
When we restore them through the GUI into our 2025 Hyper‑V environment, the system defaults to creating a Gen2 VM.
After restore, the VM fails to boot because it requires Gen1.
Our current workaround is to delete the auto‑created VM, re‑import it manually, choose Gen1, attach the disks, and then it boots correctly.
This process works but is clunky and requires too many manual steps.
We’re looking for a way to streamline or automate this setup.
Any suggestions?
Note we are migrating from vSphere 7.0 to MS Windows 2025 Hyper-v
Thanks.
Roger.
-
rschmeits
- Lurker
- Posts: 1
- Liked: never
- Joined: Nov 03, 2025 3:36 pm
- Full Name: Roger Schmeits
- Contact:
-
haslund
- Veeam Software
- Posts: 905
- Liked: 164 times
- Joined: Feb 16, 2012 7:35 am
- Full Name: Rasmus Haslund
- Location: Denmark
- Contact:
Re: vSphere to Hyper-v BIOS partition.
There are cases where the VM will be restored as a Gen1 VM.
It would be a good idea to check the Guest OS disk layout:
- Check if the boot partition is marked EFI or BIOS inside the VM
- Check if you have GPT partitions or MBR ones
Can you share the output?
It would be a good idea to check the Guest OS disk layout:
- Check if the boot partition is marked EFI or BIOS inside the VM
- Check if you have GPT partitions or MBR ones
Can you share the output?
Rasmus Haslund | Twitter: @haslund | Blog: https://rasmushaslund.com
Who is online
Users browsing this forum: No registered users and 23 guests