I believe this is impossible based on the post by JohnaL:
I'm running a PA-VM in VMware workstation 9. It is important that your network adapters supports vmxnet3.
It runs smootly.
If VMware proprietary vmxnet3 adapters are "baked into" the VM series appliance and they are required, then there's no way to get the appliance to work in VirtualBox. The only way to even possibly get it to work is if some generic adapter were used in VirtualBox, that the VM series appliance kernel would happen to see and recognize as valid eth interfaces.
Sorry! I basically gave up after seeing that vmxnet3 was required as the adapter.
I've got the 8.1 PA-VM running on VirtualBox 5.2 with exactly the same message, it just takes, like, 5+ minutes before it actually boots.
Even after that the system needs several more minutes until the default login of admin/admin is available.
This also happens in VMware environments (delayed bootup) when you upgrade the "VM Hardware" compatibility past a certain level. I believe it has something to do with a virtual serial port or somesuch, but don't have the details at my fingertips.
I'm sure you could dig in the Palo Alto Networks documentation and find which VM Hardware versions are fully supported, and then look at what VMware changed in subsequent hareware compatibility updates/versions.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!