Immer wieder kommen Besucher vorbei um 2 Posts aus 2011 anzusehen. Anscheinend dürften die Probleme noch nicht ganz behoben sein oder auch immer wieder einmal auftreten.
Im Speziellen handelt es sich um die Handhabung von OVA und OVF Dateien.
Aber was ist eine OVF bzw. OVA Datei überhaupt?
Continue reading “Unterschiede zwischen OVF, OVA und VMDK”
Everybody knows vmnetcfg.exe – but with VMWare Player 5.0 it has gone missing. A lot of instructions can be found how to extract the handy network editor from the Workstation Version or download it from a torrent site.
Much easier is to use the command line – because the well known network editor is still present – but not as a single executable. In this case start cmd.exe and change to the VMWare Players install directory and run in elevated cmd.exe-box
rundll32.exe vmnetui.dll VMNetUI_ShowStandalone
It is not ending at all – the series of problems using Cisco OVAs within my VMWare Workstation installation. After solving some minor issues I found out that VMWare got shipped with a pretty old OVF-tool. Hitting to the VMWare site and downloading the new one took me one stop closer.
The OVA can be directly converted to a VMWare Virtual Appliance by using ovftool.exe (located in the program directory of ovftool). It is pretty straight forward
ovftool.exe <location of the ova file> <location and name of the VMX file>
After that, the ovftool starts creating and converting any OVA to a VMWare Virtual Appliance. In the meantime you can read through the ovftool documentation – it is a very amazing tool at all.
Downloaded a OVA file and tried to import it into my VMWare Workstation and if something can go wrong – it does.
“the ova package name does not match the ovf file inside it” was the error message, after some searching I found out that a OVA is nothing else than a compressed tar file with another ending but includes the OVF and VHD files.
Using 7-zip to look into it I found the name of the OVF and renamed the OVA to the same name – voila – it works 🙂