Hello out there, Kind of surprising not to see any comments or feedbackson this topic, as my exprience has always been otherwise. But for all it's worth I am responsding to my own comments as I was able to find some answers as to why the VM (VM-100) FW breaks as more vNIC are added. By applying the following solution I was able to resolve the issue I was facing on my PAN VM-100. All VM-series firewalls do require vmxnet3 type vNIC. By default when a vNIC is added to the VM-100 (or to All VM-series firewalls for that matter) VMware Worksatation by adds the vNIC as e1000 (I believe this Intel and not VMware propietory NIC). So to resolve this issue, xxxx.vmx file (where xxxx respresnt the name of the VM you have selected when the VM was built) needs to be opened in notepad. All references, in case mulitple vNICs were added, to "e1000" need to be replaced by "vmxnet3". After the file, is saved, (better power off the VM before you make this chage), the VM can be powered back on, the boot process should complete, and the log on prompt should be presented at the CLI. This is also a good article from PAN itself, describing the requirments of the VM-series: https://docs.paloaltonetworks.com/vm-series/7-1/vm-series-deployment/set-up-a-vm-series-firewall-on-an-esxi-server/vm-series-on-esxi-system-requirements-and-limitations Cheers Lord
... View more