[SOLVED] Using the Proxmox converter from esxi, for windows UEFI.

[Tictac]

Using the Proxmox converter from esxi, for windows UEFI. No matter what I do I get the secure boot is grayed out that I can't enable it, and looks like it doesn't auto select windows boot manager.
Our company is looking at jumping ship from ESXI with Broadcom taking over and testing items in my home lab.
Decom two of my servers from ESXI, and brought them over to Proxmox.
Still having everything running on the other two servers while I test the process with a few of my none major servers.
Transfer comes over and it does say that I will have to deal with UEFI, once it comes over. That is when I find it will not take no matter what I do.

I can create servers from scratch with UEFI, with no issues, but having servers that I can't rebuild that easy for myself and some of the company servers. I need to figure that hurdle. Any help would be greatly appreciated.

I believe once I figure out this hurdle, I will be flying through everything. Fun part is all documentation I find is always fixing issues for Linux and not windows.

Note that It will not allow me to change to enable no matter what I do.

 

[Moayad]

Hello,


May you post the VM config?

Have you imported a UEFI VM and secure boot is not enabled?

 

[Tictac]

.encoding = "UTF-8"
config.version = "8"
virtualHW.version = "14"
vmci0.present = "TRUE"
floppy0.present = "FALSE"
numvcpus = "8"
memSize = "4096"
powerType.suspend = "soft"
tools.upgrade.policy = "manual"
sched.cpu.units = "mhz"
vm.createDate = "1647143922557101"
scsi0.virtualDev = "lsisas1068"
scsi0.present = "TRUE"
sata0.present = "TRUE"
sata0:0.deviceType = "atapi-cdrom"
sata0:0.fileName = "/vmfs/devices/cdrom/mpx.vmhba2:C0:T5:L0"
sata0:0.present = "TRUE"
scsi0:0.deviceType = "scsi-hardDisk"
scsi0:0.fileName = "Groot-Dc02.vmdk"
sched.scsi0:0.shares = "normal"
sched.scsi0:0.throughputCap = "off"
scsi0:0.present = "TRUE"
ethernet1.virtualDev = "vmxnet3"
ethernet1.networkName = "VM Network"
ethernet1.addressType = "vpx"
ethernet1.generatedAddress = "00:50:56:9e:d8:12"
ethernet1.uptCompatibility = "TRUE"
ethernet1.present = "TRUE"
displayName = "Groot-Dc02"
guestOS = "windows9srv-64"
toolScripts.afterPowerOn = "TRUE"
toolScripts.afterResume = "TRUE"
toolScripts.beforeSuspend = "TRUE"
toolScripts.beforePowerOff = "TRUE"
tools.syncTime = "FALSE"
uuid.bios = "56 4d 23 6a 90 70 b6 92-06 81 6a 11 21 51 20 fc"
vc.uuid = "52 d1 bb cc f3 10 5d 43-03 fe d5 f7 87 d0 9b 24"
tools.guest.desktop.autolock = "FALSE"
nvram = "Groot-Dc02.nvram"
pciBridge0.present = "TRUE"
svga.present = "TRUE"
pciBridge4.present = "TRUE"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge4.functions = "8"
pciBridge5.present = "TRUE"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge5.functions = "8"
pciBridge6.present = "TRUE"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge6.functions = "8"
pciBridge7.present = "TRUE"
pciBridge7.virtualDev = "pcieRootPort"
pciBridge7.functions = "8"
hpet0.present = "TRUE"
RemoteDisplay.maxConnections = "-1"
sched.cpu.latencySensitivity = "normal"
svga.autodetect = "TRUE"
disk.EnableUUID = "TRUE"
numa.autosize.cookie = "80001"
numa.autosize.vcpu.maxPerVirtualNode = "8"
pciBridge0.pciSlotNumber = "17"
pciBridge4.pciSlotNumber = "21"
pciBridge5.pciSlotNumber = "22"
pciBridge6.pciSlotNumber = "23"
pciBridge7.pciSlotNumber = "24"
scsi0.pciSlotNumber = "160"
usb_xhci.pciSlotNumber = "-1"
vmci0.pciSlotNumber = "32"
sata0.pciSlotNumber = "33"
scsi0.sasWWID = "50 05 05 6a 90 70 b6 90"
vm.genid = "745321842921180116"
vm.genidX = "4854329423202831661"
monitor.phys_bits_used = "43"
vmotion.checkpointFBSize = "4194304"
vmotion.checkpointSVGAPrimarySize = "16777216"
softPowerOff = "FALSE"
svga.guestBackedPrimaryAware = "TRUE"
tools.remindInstall = "FALSE"
toolsInstallManager.lastInstallError = "0"
toolsInstallManager.updateCounter = "5"
guestInfo.detailed.data = "architecture='X86' bitness='64' buildNumber='17763' distroName='Windows' distroVersion='10.0' familyName='Windows' kernelVersion='17763.5329' prettyName='Windows Server 2019, 64-bit (Build 17763.5329)'"
usb_xhci:4.present = "TRUE"
usb_xhci:4.deviceType = "hid"
usb_xhci:4.port = "4"
usb_xhci:4.parent = "-1"
guestOS.detailed.data = "architecture='X86' bitness='64' buildNumber='17763' distroName='Windows' distroVersion='10.0' familyName='Windows' kernelVersion='17763.3650' prettyName='Windows Server 2019, 64-bit (Build 17763.3650)'"
cpuid.coresPerSocket = "2"
SCSI0:0.ctkEnabled = "TRUE"
ctkEnabled = "TRUE"
ethernet1.pciSlotNumber = "224"
migrate.hostLog = "Groot-Dc02-61fa91ed.hlog"
sched.cpu.min = "0"
sched.cpu.shares = "normal"
sched.mem.min = "0"
sched.mem.minSize = "0"
sched.mem.shares = "low"
migrate.encryptionMode = "opportunistic"
ftcpt.ftEncryptionMode = "ftEncryptionOpportunistic"
viv.moid = "2f447d9f-59b0-4f62-9a5e-62b522cb8439:vm-18:HYQA71KEY8h6aHZOKrt5hVEk77XOAHTuDADlA3UQ1XU="
guestinfo.driver.vmci.version = "9.8.18.0"
guestinfo.driver.vsock.version = "9.8.19.0"
guestinfo.vmware.components.available = "salt_minion"
guestinfo.driver.wddm.version = "9.17.04.0002"
guestinfo.vmtools.buildNumber = "20735119"
guestinfo.vmtools.description = "VMware Tools 12.1.5 build 20735119"
guestinfo.vmtools.versionNumber = "12325"
guestinfo.vmtools.versionString = "12.1.5"
guestinfo.Cb.InstallStatus = "3013"
guestinfo.Cb.LauncherVersion = "1.1.0"
guestinfo.toolsInstallErrCode = "0"
sched.swap.derivedName = "/vmfs/volumes/64f4ef75-ba3fb042-4bf6-f01fafdd62a9/Groot-Dc02/Groot-Dc02-b20b7f6f.vswp"
uuid.location = "56 4d 5a 82 2c a4 f4 80-e4 d1 84 08 73 03 ae c3"
scsi0:0.redo = ""
svga.vramSize = "16777216"
vmci0.id = "558964988"
cleanShutdown = "FALSE"
extendedConfigFile = "Groot-Dc02.vmxf"
bios.bootDelay = "1000"
checkpoint.vmState = ""
firmware = "efi"


As I import it does say that I will need to do extra steps for UEFI, and when I go and follow the directions your company provided it is all greyed out.
This is the config before converting over from ESXI.

 

[Moayad]

May you please also provide us with the VM config from the Proxmox VE side, you can get the VM config using the following command:

qm config <VMID>

 

[Tictac]

bios: ovmf
boot: order=scsi0
cores: 2
cpu: x86-64-v2-AES
efidisk0: Main:vm-102-disk-0,size=4M
memory: 4096
meta: creation-qemu=8.1.5,ctime=1712652088
name: Groot-Dc02
net1: vmxnet3=00:50:56:9e:d8:12,bridge=vmbr0
ostype: l26
scsi0: Main:vm-102-disk-1,size=100G
scsihw: virtio-scsi-single
smbios1: uuid=564d236a-9070-b692-0681-6a11215120fc
sockets: 4
vmgenid: 50bd6754-aef7-4309-a740-bfba7ce4f92e

Since I saw there was an update on the converson software I did do an update and retry it to see if that would help, with no luck.

 

[Tictac]

Want to update that I have been able to successfully move to Windows 10 computers over and seems to be only the Windows 2019 servers that I'm having issues with. I do notice that it looks like I did the transfer with it thinking it was Linux. So redid it with still the same issues. Here is a new pull of the information.
bios: ovmf
boot: order=scsi0
cores: 2
cpu: x86-64-v2-AES
efidisk0: Main:vm-102-disk-0,size=4M
ide0: none,media=cdrom
machine: pc-i440fx-8.1
memory: 4096
meta: creation-qemu=8.1.5,ctime=1712667689
name: Groot-Dc02
net1: virtio=00:50:56:9e:d8:12,bridge=vmbr0
ostype: win10
scsi0: Main:vm-102-disk-1,size=100G
scsihw: virtio-scsi-single
smbios1: uuid=564d236a-9070-b692-0681-6a11215120fc
sockets: 4
vmgenid: b3cc50e0-0c33-4c93-a108-569721921a70

It comes up as inaccessible boot device and wont

 

[Tictac]

Just checking in if you have any ideas from the information provided.

 

[_gabriel]

inaccessible boot device

You need to switch scsi controller to vmware as virtio drivers aren't installed.

 

[Tictac]

Well it seems that the latest updates that was pushed last fixed things. I did it without modifying everything and it just worked. Already moved a few over and all are working as expected.
_Gabriel when I tried what you suggested it made it worst.

I will say also did notice that the converter did not like a high MTU on the ESXI, When that was upped to fix an issue I was having with my camera system, it dropped that server off from being able to import from. As soon as I lowered it, the transfers would start working again. While the MTU where high I couldn't even connect to the server to import. Just want to pass that along.