"/config/bigip.license" has read permission for all and write for tomcat.
Those are expected permissions for the license file.
Funny though, content of /config/bigip.license is now actually populated with the correct new license.
But "Registration Key" in "tmsh show sys hardware" is empty.
There are several other file system related warnings or errors in logs.. so I suspect that the whole issue is with how F5 VE is accessing file system on Proxmox. But I don't know what to check or fix further.
Is it even possible to run F5 VE on Proxmox? (although F5 clearly states it should be.)
Yes, I got it working, I had the exact same problem as you. I used a converted vmdk image, but that behaves exactly like the qcow2 image so I dont think that has anything to do with it. In short, I activated the license via CLI instead of GUI. Here is the complete procedure:
Create a VM, with any disk. It will be deleted later anyway. I used 16 Gb RAM, 2 sockets 4 cores CPU, Machine: i440fx, SCSI-controller: VirtIO SCSI, NICs: VirtIO
Detach the disk from the VM and delete it.
Download the qcow2 image from F5
SCP it to Proxmox
unzip it. apt install unzip if needed.
Attach the qcow2 file to the VM, and move it to designated storage: qm importdisk <vm-id> BIGIP15.1.x.y.z.qcow2 VM-storage
Doubleclick on the now unused disk image in the VM hardware settings. Add it.
Boot VM. Bring up a console. It shows nothing of the boot process except the GRUB menu, but the login prompt eventually comes.
Login. Set root password.
mcpd reboots in a loop. Kill it: tmsh stop sys service mcpd
mkdir /shared/.snapshots_d
tmsh start sys service mcpd
Wait a while. Then run config and set mgmt IP.
Login to GUI. You are forced to update GUI password.
Go though license activation procedure.
Dont know if it matters, but I chose offline activation. It "succeded" but when provisioning modules in the next step AVR is the only licensed module.
Leave it there and bring up a console.
Active license via CLI: tmsh install sys license registration-key <regkey>
Magic happens
Complete the setup in the GUI.
I used BIGIP 15.1 on Proxmox 6.1. Maybe license activation in the CLI right away works, but the above procedure is exactly how I did it. As far as I can tell, F5 states that VE should run under KVM, this seems to be a Proxmox-specific thing. I have run multiple BIGIP under KVM earlier (like GNS3 server) and never had this issues.
I have not run my unit very long so I have no idea how it will behave over time... but hopefully this helps someone.
UPDATE: The VM behaved weird in several ways. It seems fine in the GUI but there are issues. sshd would not start via systemd, and several services failed to start, big3d rebooted in a loop after a while. Some of it seems related to SELinux, sshd did start when SELinux was set to permissive ("setenforce 0"). sshd also started if you started it manually. Other services like network and f5-label did however not start. Never found out why. However a better workaround for me was booting 13.1, which start without issues. Then upgrade to the version you want. I got no errors at all. The exact version I used was BIGIP-13.1.3-0.0.6.ALL.qcow2.zip, then jumped to BIGIP-14.1.2.3-0.0.5 and then BIGIP-15.1.0.1-0.0.4 and they all worked just fine.
Thanks ECCE, works really well installing Big-IP V15.1 - from scratch too !
Struggled a bit with BigIQ, but finally made it work:
Proxmox 6.2-4 , BigIQ 7.1::, (It helps if you've installed Big-IP first, following ECCE's manual above ..)
Import the QCOW2 image in Proxmox CLI ( I’m importing it to VM 107) :"qm importdisk 107 BIG-IQ-7.1.0.2.0.0.21.qcow2 local-lvm --format qcow2"
Go into the GUI and observe your virtual machine: you’ll see the newly imported disk
Now, here’s the trick; don’t just add the disk, but first change it from SCSI into SATA
Once you changed “Bus/Device” into “sata”, hit the blue “add” button
Now’ your disk is added to the virtual machine, but it won’t boot yet ..
Go into the virtual machine “options” menu on the left, and edit the boot order. You will see it’s set to boot from scsi, but there is no scsi disk, so the border around “boot device 1” is red.
