To reach this VM we need to configure a static management IP.

Once logged into the VM run the show system info and note that the management interface is running as a DHCP client. It will look as if it has stalled, but eventually eth0 interface status will be displayed and the VM will cycle through the usual PA-VM login prompts The console output form bootup will then be displayed in the terminal. # /usr/sbin/bhyve -c 2 -m 4G -AHP -s 0:0,hostbridge -s1:0,lpc -s 2:0,virtio-net,tap0 -s 3:0,virtio-blk./PA-10.0.4.img -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI_CSM.fd -l com1,stdio vm0 The PA VM must be booted in leagcy BIOS mode, so you will need to ensure you have the sysutils/bhyve-firmware package installed. Plus the VM is for development work and doesn’t need network connectivity beyond the confines of my laptop so I am creating a ‘host-only adapter’. There is a great many pages online detailing the creating of bridge interfaces and connecting the VM and LAN interfaces, however this does not seem to work with wlan0 interfaces. # pkg search qemu-utilsĮxtract the contents of the OVA and convert the VMDK file into a format which we can use with bhyve. To covert a VMDK file into a raw format image, the utility qemu-img is found in the qemu-utils package. this post will look at getting the VM running under the BSD homegrown bhyve. It is not a supported environment but VMware Player is not available under FreeBSD. Try as I might I had no luck in running the Palo Alto VM under VirtualBox.

Palo alto ova for vmware