Fixing UEFI after migration

V

voyager529

New Member
Apr 5, 2024
8
5
3
Hi there friends!

I'm attempting to move off ESXi on a server (surprise, surprise), and one of my VMs is being particularly petulant.

It's a Debian 12 VM, running a pretty standard LAMP stack, set up to boot with UEFI.

I tried moving it with the ESXi Import function, and when I did, it sends me to the EFI shell. Manually selecting the boot drive doesn't seem to help, either. I then tried using Veeam to do a backup/restore from one ESXi host to another...and it starts up just fine when I boot the VM off the second ESXi host after a backup/restore...but when I do a Veeam Backup/Restore to Proxmox, it again fails to boot.

I've attempted deleting and recreating the EFI boot drive, but that didn't seem to help, either.

In this particular case, I can *probably* do a data migration to a native Proxmox VM, but I figure that it's equally a good test case, as it likely won't be the last time I face this issue, so if there's a solution that is known, I'd be interested to read about it.

Thank you for your time and attention!
 
Hi,
I've done the same migration several months ago.
Unfortunately, when I do the migration, Veeam does not support Proxmox environment yet.
So, I do it this way:
- Create a new backup configuration of the VM using Veeam Agent (similar to workstation backup, it uses ssh to install and manage the backup)
- Download the ISO for restoring the VM
- Create a new VM in Proxmox and set the Veeam Recovery ISO to boot.
- Use a wizard to restore the VM (I crate a restore token on Veeam and I do all the procedure via network)

This way I've migrated all my VM without any problem.
 
So, attempts at moving were unsuccessful, though admittedly I didn't try the restore-with-recovery-media method. What made a bit more sense in most of the more petulant cases was just to migrate the data; most of those machines were on CentOS 7 and I wanted to move them to newer versions of Debian anyway, so I took the opportunity to do those updates and conversions.

Thank you for your assistance and willingness to address the matter.
 
  • Like
Reactions: Gabro88 and Kingneutron
I think I had a similar issue when using Veeam to restore a Proxmox Debian VM. The UEFI disk would not boot. I found this forum post to re-create the EFI bootloader, and it fixed my problem: https://forum.proxmox.com/threads/failed-to-boot-from-uefi-vm-disk.65112/#post-623430

I've succeeded in fixing the boot.
The entry in the BIOS is kind of "corrupted".

When starting the VM I pressed escape until going in the Bios menu.
Then Boot Maintenance Manager > Boot options > Add a boot options

Select the disk > then EFI > <debian> (My distro) > shimx64.efi
And name it as u like.

I've moved it up so it boot first and it's working back.
 
Last edited:
You must log in or register to reply here.
Top Bottom