On a previous post we have gone through a basic Windows 10 VM setup. A lot of steps involved, where we had to specify the RAM, CPU, Disk space etc. It would be nice if there was a template that can do that for us. Actualy there is.We can use OVA or OVF templates and actually extract that information to our Virtual Box.
We can use 7zip and open any OVA file. For example the VyOS OVA was mentioned on another post
We can see that this file contains:
- OVF: An XML file that has various settings/options, for example CPU, RAM, HDD etc.
We can see that this specific VM will use Linux - Debian x64 OS.
<OperatingSystemSection ovf:id="96" ovf:version="6" vmw:osType="debian6_64Guest">
<Info>The operating system installed</Info>
<Description>Debian GNU/Linux 6 (64-bit)</Description>
</OperatingSystemSection>
- VMDK (Virtual Machine Disk) file
- Cert - A certificate that the OVA file is signed and needs to be trusted by our HyperVisor.
- MF - Manifest file used for integrity checks. The MF file contains the SHA-1 hash of all files except the .mf (itself) and the .cert file, ovf and vmdk in our example.
SHA1(VyOS-1.1.8-amd64.ovf)= 89cac831437d96ca728917e73227e895fd70e9eb
SHA1(VyOS-1.1.8-amd64-disk1.vmdk)= 21a7cdf0f47fa32ca148017f459c6d1ea59d777b
As we can see the disk size is around 250MB and actually it does contain the installed OS.
In other OVA files, for example the Cisco CSR 1000V we can see that the disk is a few kb (almost empty), so there is no OS installed. But we can also see that this OVA file includes the ISO image that we can use to install the Cisco Virtual Router.
The manifest file is shown
SHA1(csr1000v-universalk9.16.09.02-vga.ovf)= c7c2e4c299f055c841e061550392b0a43e1ecfc1
SHA1(csr1000v_harddisk.vmdk)= 94bdfb796ae9635b188e75efb52f5b895eca8340
SHA1(bdeo.sh)= aac24513098ec6c2f0be5d595cd585f6a3bd9868
SHA1(README-OVF.txt)= c5bb6a9c5e8455b8698f49a489af3082c1d9e0a9
SHA1(README-BDEO.txt)= 39bcf8ed259e5a9c9f1b5671f738fb904d73f635
SHA1(cot.tgz)= a305b8a9bc67e1f00d5b6ab8ac0c076f2af9f495
SHA1(csr1000v-universalk9.16.09.02-vga.iso)= 86400b573a6bcab7509aef22008b21db2d39c3f0
Cisco (CUCM) Call Manager 12.0.(1) OVA file: The last example doesn't contain any ISO files and the disks do not have an OS installed. Why should we use it? Some vendors, like Cisco have strict specifications when you create VMs. If you ignore the specific VM Requirements that are contained on the OVA file, then Cisco may not be able to offer you technical support, until you adjust your system to the correct settings. So we can use the OVA file to create the VM Settings and then download the ISO file and install the OS.
Load the OVA file
Our VM has been automagically created and we can Power it on.
Or we can further Edit the VM.
We can use 7zip and open any OVA file. For example the VyOS OVA was mentioned on another post
We can see that this file contains:
- OVF: An XML file that has various settings/options, for example CPU, RAM, HDD etc.
We can see that this specific VM will use Linux - Debian x64 OS.
<OperatingSystemSection ovf:id="96" ovf:version="6" vmw:osType="debian6_64Guest">
<Info>The operating system installed</Info>
<Description>Debian GNU/Linux 6 (64-bit)</Description>
</OperatingSystemSection>
- VMDK (Virtual Machine Disk) file
- Cert - A certificate that the OVA file is signed and needs to be trusted by our HyperVisor.
- MF - Manifest file used for integrity checks. The MF file contains the SHA-1 hash of all files except the .mf (itself) and the .cert file, ovf and vmdk in our example.
SHA1(VyOS-1.1.8-amd64.ovf)= 89cac831437d96ca728917e73227e895fd70e9eb
SHA1(VyOS-1.1.8-amd64-disk1.vmdk)= 21a7cdf0f47fa32ca148017f459c6d1ea59d777b
As we can see the disk size is around 250MB and actually it does contain the installed OS.
In other OVA files, for example the Cisco CSR 1000V we can see that the disk is a few kb (almost empty), so there is no OS installed. But we can also see that this OVA file includes the ISO image that we can use to install the Cisco Virtual Router.
The manifest file is shown
SHA1(csr1000v-universalk9.16.09.02-vga.ovf)= c7c2e4c299f055c841e061550392b0a43e1ecfc1
SHA1(csr1000v_harddisk.vmdk)= 94bdfb796ae9635b188e75efb52f5b895eca8340
SHA1(bdeo.sh)= aac24513098ec6c2f0be5d595cd585f6a3bd9868
SHA1(README-OVF.txt)= c5bb6a9c5e8455b8698f49a489af3082c1d9e0a9
SHA1(README-BDEO.txt)= 39bcf8ed259e5a9c9f1b5671f738fb904d73f635
SHA1(cot.tgz)= a305b8a9bc67e1f00d5b6ab8ac0c076f2af9f495
SHA1(csr1000v-universalk9.16.09.02-vga.iso)= 86400b573a6bcab7509aef22008b21db2d39c3f0
Cisco (CUCM) Call Manager 12.0.(1) OVA file: The last example doesn't contain any ISO files and the disks do not have an OS installed. Why should we use it? Some vendors, like Cisco have strict specifications when you create VMs. If you ignore the specific VM Requirements that are contained on the OVA file, then Cisco may not be able to offer you technical support, until you adjust your system to the correct settings. So we can use the OVA file to create the VM Settings and then download the ISO file and install the OS.
Let's see how we can create a new VM using the OVA file
File > Import Appliance...
Load the OVA file
We are getting a Certificate warning (expired) but we can skip that, press Yes
Below we can see all the settings that the OVA file will select for us - we will only change the location Folder and press Import
Our VM has been automagically created and we can Power it on.
Or we can further Edit the VM.
No comments:
Post a Comment