OVFtool and importovf not working.

[Brodie@Kuemedia]

I cant for the bloody life of me get either of these things to work and im pulling my hair as it is. Im trying to import from ESXi 6.0-U2. But even doing a manual OVF import off ESXi and moving the files to the Proxmox host and trying importovf none of it works.

I've searched far a wide and have found very little to no documentation on these errors. Can someone please point me in the right direction.

 

[UdoB]

Hello,

when I migrated to Proxmox I exported the VMs from ESXi directly as .ovf - that was the easiest approach for me.

The second step was to import on Proxmox and it worked like a charm: qm importovf 205 /mnt/migrate/vmname2.ovf local-zfs

Best regards

 

[jsterr]

I recently did this aswell and it worked well. I know stupid question: but did you propably mistype storage "local-pool"? Do you have enough space avaiable on pool and on the location where you transfered the VMware-VM too. Thats double space you need for short time. Thats how it should look with ovftool:

root@pve-01:~/VMS# ovftool vi://root@10.2.2.112/JS-AD-01 .
Opening VI source: vi://root@10.2.2.112:443/JS-AD-01
Opening OVF target: .
Writing OVF package: ./JS-AD-01/JS-AD-01.ovf
Disk progress: 11%
Transfer Completed
Completed successfully

 

[Dominic]

Hi,

when it says completed with errors I wouldn't expect the following commands to work. Furthermore, your current location is

/mnt/pve...

so the path that you specify for the qm command is probably wrong because it says

/mnt/pvr...

To verify that you get the paths correct you can use ls. Make sure that you get one line as result, for example

root@desktop:/home/dominic# ls /mnt/pve/nfs/importing/Debian10OSBox.vmdk 
/mnt/pve/nfs/importing/Debian10OSBox.vmdk

Then copy & paste that line.

Copy & paste from

pvesm status

to make sure that you get your storage name correct.


If it still does not work, then please copy & paste the output of the following commands into [code][/code] tags or use the </> format button.

pveversion -v
pvesm status
df -h
zfs list
ls -lhR /mnt/pve/Datastore

 

[Brodie@Kuemedia]

Hello,

when I migrated to Proxmox I exported the VMs from ESXi directly as .ovf - that was the easiest approach for me.

The second step was to import on Proxmox and it worked like a charm: qm importovf 205 /mnt/migrate/vmname2.ovf local-zfs

Best regards

This is exactly what I've done and yet as you can see I still get an error when trying to import the OVF file.

Hi,

when it says completed with errors I wouldn't expect the following commands to work. Furthermore, your current location is

/mnt/pve...

so the path that you specify for the qm command is probably wrong because it says

/mnt/pvr...

To verify that you get the paths correct you can use ls. Make sure that you get one line as result, for example

root@desktop:/home/dominic# ls /mnt/pve/nfs/importing/Debian10OSBox.vmdk
/mnt/pve/nfs/importing/Debian10OSBox.vmdk

Then copy & paste that line.

Copy & paste from

pvesm status

to make sure that you get your storage name correct.


If it still does not work, then please copy & paste the output of the following commands into [code][/code] tags or use the </> format button.

pveversion -v
pvesm status
df -h
zfs list
ls -lhR /mnt/pve/Datastore

Thanks for the help. I Must be blind and didnt see the type. It has imported now. The other issue im having now though is it will not boot using UEFI and Q35. Now being that this is a ESXi 6.0-U2 VM those are required no?

 

[calperin]

And how did you converted the vm to OVF? all times I tried the vmdk is Ok, but the download allways is broken on my browser

 

[UdoB]

And how did you converted the vm to OVF?

Me? It was two and a half years ago and was done only at that time using .ovf - for an unknown reason. But there is an official "Export"-command in the context menu of a specific VM in ESXi.

A year later my documentation says I did migrate several VMs by using ghettoVCB to export them first. In the destination of this type of backup you can find the "myvm.vmdk". Probably you can simply use the original .vmdk without using ghettoVCB as an intermediate step. For me it was intended to have a "final migration backup" when leaving that platform.

Then on PVE I did repeatedly things like this:

~# qm create 2029  --name=myvm  --memory=1024  --balloon=768   --cores=2   --net0 bridge=vmbr818,virtio  --bootdisk=scsi0  --scsihw virtio-scsi-pci  --ostype=l26   --machine=q35 --boot order=scsi0 --agent enabled=1   
~# qm importdisk 2029  /mnt/xxxx/myvm.vmdk     ds0
~# qm set 2029 --scsihw virtio-scsi-pci  --scsi0  ds0:vm-2029-disk-0,discard=on

So basically I created the new VMs manually and imported only the disk. No magic involved...

Good luck