on 14-Apr-2016 04:00 - edited on 05-Jun-2023 22:55 by JimmyPackets
-drive=blah blah blah
command. The output of that command is an OVA file. For those unfamiliar with it, an OVA file is just a tarball that includes an OVF file, a number of disks, and some other "stuff" that you might want to include (certificates, eula files, yada yada yada).
SEA-ML-RUPP1:tim trupp$ tar xvf BIGIP-184.108.40.206.0.606.ALL-ide.ova x BIGIP-220.127.116.11.0.606-ide.ovf x BIGIP-18.104.22.168.0.606-ide.mf x BIGIP-22.214.171.124.0.606-ide.cert x BIGIP-126.96.36.199.0.606-disk1.vmdk x BIGIP-188.8.131.52.0.606-disk2.vmdk SEA-ML-RUPP1:tim trupp$
BIGIP-184.108.40.206.0.606-ide.ovf BIGIP-220.127.116.11.0.606-ide.mf BIGIP-18.104.22.168.0.606-ide.cert BIGIP-22.214.171.124.0.606-disk1.vmdk BIGIP-126.96.36.199.0.606-disk2.vmdk
<Item> <rasd:AddressOnParent>0</rasd:AddressOnParent> <rasd:ElementName>disk2</rasd:ElementName> <rasd:HostResource>ovf:/disk/vmdisk2</rasd:HostResource> <rasd:InstanceID>6</rasd:InstanceID> <rasd:Parent>3</rasd:Parent> <rasd:ResourceType>17</rasd:ResourceType> </Item>
tar -cvf BIGIP-188.8.131.52.0.606.ALL-ide-FIXED.ova -T files.txt
SEA-ML-RUPP1:tim trupp$ tar -cvf BIGIP-184.108.40.206.0.606.ALL-ide-FIXED.ova -T files.txt a BIGIP-220.127.116.11.0.606-ide.ovf a BIGIP-18.104.22.168.0.606-ide.mf a BIGIP-22.214.171.124.0.606-ide.cert a BIGIP-126.96.36.199.0.606-disk1.vmdk a BIGIP-188.8.131.52.0.606-disk2.vmdk SEA-ML-RUPP1:tim trupp$
<Item> <rasd:Address>1</rasd:Address> <rasd:Description>IDE Controller</rasd:Description> <rasd:ElementName>ideController1</rasd:ElementName> <rasd:InstanceID>3</rasd:InstanceID> <rasd:ResourceType>5</rasd:ResourceType> </Item> <Item> <rasd:Address>0</rasd:Address> <rasd:Description>IDE Controller</rasd:Description> <rasd:ElementName>ideController0</rasd:ElementName> <rasd:InstanceID>4</rasd:InstanceID> <rasd:ResourceType>5</rasd:ResourceType> </Item>
Hey Tim -
This is still broken (probably dev pri 99), but there's now a signature for the manifest included in the .cert file. If that isn't updated, then importing the OVA fails. Can that be regenerated as well, or is the best answer (as recommended elsewhere) to just delete the .cert file before rebuilding the OVA?
@CP Scott, the recommended way to run things in virtualbox these days is to use our packerfiles and vagrantfiles repositories here
Given the ISO file that you can get from , you can use those to generate vagrant boxes using the given packerfiles. Instructions are in each README file in the version subfolders.
Hope that helps.
Thanks. I needed that for PoC purposes.
It worked for me BUT I had to remove the extra (unused) SCSI controller.
So it worked when I did all you did, AND removed all these lines before re-creating the .ova
1 SCSI Controller scsiController1 3 lsilogic 6 `
IMPORTANT : I also had to delete de .cert and .mf files, because the signature of the OVA did not match since the .ovf file is changed.
what tool could i use to extract its contents? Am i able to make it through Windows environment, looks like you ran it through Linux?
i want to install Big IP through VirtualBox in Windows 10, could anyone help me?
ChansonNZ this requires 2 things from you.
First, you must build the Vagrant box using one or more of the packerfiles available here
Then, you need to use one of the Vagrantfiles that we provide here
Yes, this works fine on Windows as both Packer and Vagrant run fine on Windows.
One thousand thanks Tim Rupp for this workaround!
I am now able to run BIGIP-13.1.1-0.0.4.ALL-ide.ova on Virtual Box Version 5.1.10 r112026 (Qt5.6.2) (all done on Win7)
ChansonNZ - I used 7zip to open OVA file, removed .cert and .mf files as suggested by Ghislain Cote and then edited OVF file as per Tim's guideline. Advantage to use 7zip is that you can just open OVA file and remove included files as well as edit some and then 7zip automatically "compress" it back so no need to uncompress everything prior. I also recommend to use notepad++ as editor - you can edit OVF via 7zip directly but you need to configure notepad++ as editor in settings of 7zip else it uses default windows notepad. Notepad was not parsing the output of OVF properly.
Sure wish F5 would just start supporting VirtualBox going forward. Other team members at my company feel the same way.
@T-Heron you may be interested in the Packerfiles that I published in the past. You can build your own boxes using those tools.