Windows ovf to Qcow2

[Clarin]

Hello,

I folow this steps to import one VM of VMware to Proxmox

https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE#VMware

VMware
This explains the migration from a VMware ESXi 6.7 hypervisor to Proxmox VE 6.1. It is tested with guests with the following operating systems:

• Debian 10
• Windows 10 Pro
• Windows Server 2016 Standard

In VMware ESXi navigate to your virtual machine in the tree on the left. Choose Actions->Export. This will download disk images and information about your virtual machine in the .ovf format in the browser. Move those files to a storage that is accessible by your Proxmox VE host.

Go to the command line interface of Proxmox VE. Use the command "qm importovf" to import the virtual machine. This will create a new virtual machine, using cores, memory and VM name as read from the OVF manifest, and import the disks. You have to configure the network manually. You can find syntax and an example on how to use this command on its man page.

If I run my machine in this moment Windows don't start:




Configuration file:

bootdisk: scsi0
cores: 4
memory: 6208
name: WindowsServer2012
scsi0: local:104/vm-104-disk-0.qcow2
smbios1: uuid=285d750b-361d-4749-8dab-a697df4001b8
vmgenid: 5c8c7d43-8476-4521-8562-ce89bf341bc9


If your guest is Windows, you additionally have to execute the following commands. This example assumes that your imported virtual machine has the ID 130.

• qm set 130 --bios ovmf
• sed -i 's/scsi/ide/g' /etc/pve/qemu-server/130.conf

At this moment Windows don't boot:




Configuration file:

bios: ovmf
bootdisk: ide0
cores: 4
memory: 6208
name: WindowsServer2012
ide0: local:104/vm-104-disk-0.qcow2
smbios1: uuid=285d750b-361d-4749-8dab-a697df4001b8
vmgenid: 5c8c7d43-8476-4521-8562-ce89bf341bc9

Thanks for this product and for you Help.

BR

 

[wolfgang]

Hi,

Do you are sure that in ESXi it was an EFI system?
I would try again with seebios.

 

[Clarin]

Hello,

That's it.

Many Thanks Wolfgang.

If is not abuse, can you explain a little why with UEFI don't work?.

BR and you are an Angel.

Thanks again.

 

[wolfgang]

The most VirtualEnviroments use classical Bios instead UEFI, because a virtual BIOS is faster than a baremetal.
Virtual Setups are simple to compare with HW, so there is no benefit for it.
Windows decide at installation what type it is and install only the needed things.
You could change it see https://www.maketecheasier.com/convert-legacy-bios-uefi-windows10/