![Ova to proxmox](https://kumkoniak.com/14.jpg)
Next we'll go into vcenter or esxi itself and create a new VM. You'll see some messages about cloning disk and things whilst this is progress. Vmkfstools -i quasselog.vmdk -d thin quassel.vmdk Then, using scp (or any other tool to copy files around your network) run: scp quasselog.vmdk :/vmfs/volumes/5d80ea2d-f02fde58-9186-902b343139aa/Īfter the file is copied, you'll need to use vmkfstools and run the following: cd /vmfs/volumes/your-datastore vmfs/volumes contains symlinks to your datastores and you can use scp to copy your VMDK there for processing. This will be different from everyone depending on the datastores you have set up. Then you'll want to enable SSH on your ESXI box in order to utilise vmkfstools on the hypervisor itself.įirstly, you'll need to locate where images are stored.
![ova to proxmox ova to proxmox](https://help.netonboard.com/wp-content/uploads/2020/08/image-27-768x490.png)
![ova to proxmox ova to proxmox](https://www.inett.de/assets/images/blog/2019/samuel-zeller-118178-unsplash.jpg)
![ova to proxmox ova to proxmox](https://www.itsfullofstars.de/wp-content/uploads/2019/07/word-image-29.png)
You can run the conversion thus: qemu-img convert -f qcow2 -O vmdk quassel.qcow2 quasselog.vmdk I ran these steps on my laptop running Fedora, any Linux box should do here though.
![ova to proxmox ova to proxmox](https://www.itsfullofstars.de/wp-content/uploads/2019/07/word-image-26.png)
If you were using qcow2 images for your KVM VMs this will also work from any KVM based system, not just Proxmox.įirst step is to convert your qcow2 image to a vmdk file that VMWare uses. I didn't fancy rebuilding some of my VMs and instead wanted to find out how to migrate them instead. I recently switched from Proxmox to ESXI for my primary Hypervisor due to better support for automation tools like Ansible and Terraform plus better integrations with Red Hat Satellite.
![Ova to proxmox](https://kumkoniak.com/14.jpg)