Download the latest ovftool from vMware and convert it into vmx
ovftool e:\myvirtualmachines\myovf\myimage.ovf e:\myvirtualmachines\myvmx\myimage.vmx
Now you have the vmx and vmdk with you.
Copy the vmdk to the vmfs datastore
use command on ESXi vmkfstools -i <<source vmdk >> -d thin <<destination vmdk>>
It should fix the issue, i used it couple of times
Award me points if it answers your question.
Venkat told you the tool to use but couple of changes. These are the steps you need to follow.
Download and install the OVFTool. Here's a link for that.
Then run the following command.
ovftool <path of .ovf file> <path for converted .vmx file>
Then you will get a VMX file. You will have to edit the Hardware version in it. Change it to a version that is compatible with your hardware. Once you do this, save the VMX file.
Then you need to convert the VMX back to OVF.
The command for that is
ovftool <path of .vmx file> <path for converted .ovf file>
After this is done you can deploy the OVF.------------------------------------------------------------------------------------------------------------------------------------
If you find this or any other answer useful please mark the answer as correct or helpful.
| Blog : http://vpirate.in | Twitter : @abhilashhb |
To avoid wasting time extracting/rebuilding with OVF tool you can just edit the OVF file, change the line that says "VMX-XX" (in my case was 10) to read "07" or whatever version works with your ESXI. Then use a hashing utility to calculate the SHA-1 of the edited OVF file and replace the corresponding SHA-1 hash in the ".mf" file.
Guys, I have the solution for this, so let me know how it goes;
I'm typing this in a hurry so please excuse typos
We wanted to offload ESXi v6 since we have installed the hypervisor only on a few basic unmanaged servers which dont need advanced features. However, we (and looks like most of the vm community) are having problems with the vi client v6 and from my experiences guys, you have to go with vcenter and use the web gui as its not a recommended practise to use the vi client to manage each host. For our purposes though (and to not go off topic) we wanted to downgrade to esxi 5.1. The problem is that when you export vm's that are running esxi v6, it might shoot the following error
" the ovf package requires unsupported hardware, details line 25: unsupported hardware family vmx-11 "
What im describing here is the "free" path to doing this. There are much more streamlined and efficient ways to do this but I will not go into that here.
- Take ova / ovf backups with the existing version of the hypervisor you are using
- First, try to see whether you can deploy the exported ova / ovf format
- if you are greeted with teh above mentioned error or similar, then do the following
- Download the free vmware player and install it
- open vm player and then open your virtual machine (it will start the importing process since its in ova / ovf format and vm player like workstation uses vmx and vmdk files)
- once the import is complted and the relevant vmx and vmdk files have been generated, go forth and download & install vmware converter (also free)
- then open it up and go to "convert machine" - select source type as "vmware workstation or other vmware virtual machine" - choose the vmx files that you saved in an earlier step, then type in your esxi host details (ip address, username an password)
- now finish the wizard, sit back and see your files being sent and prepared by the host for use.
Hoping this will assist you guys, as it did for me. Thanks Gianni CoronaGianni Corona as I used that as a basis for this
I used this method today to go from vmx-11 to vmx-10. Needed to move an Ubuntu production OVA from a newer host running ESXi 6.1 to a slightly older server running ESXi 5.5.
Because ovftool is a supported vmware tool, it seems less risky than other methods. But I am no expert in this area.
Just glad it worked, hoping it keeps running without issue...
I want to thank
dilshandiss Oct 6, 2015 11:44 PM (Import OVF Template - Unsupported hardware family 'vmx-10'in response to victorhooi)
who provided a solution that worked for me. My issue was that I had to change the networking settings. I had a hardware failure on my home development hosts and I decided to do backups of all of my machines. i also was building a MariaDB 10.1 cluster and I wanted to clone a VM and I could not figure out an easy way to export it with the ESXI 6.5.
Thanks for providing a solution that worked for me.