Issue 1: The AMD proc-specific boot fail. If you can't even get Pfsense to load in your VM beyond the initial "post," you know what I'm referring to here. You'll see
something like the following:
Stopped at pmap_invalidate_cache_range+0x40 clflushl 0(%ebx)
Workaround: At initial menu, choose option 7 to escape to the command line. Type the following at the OK prompt:
Installation will continue as normal. After reboot, you need to escape again to the command line, re-enter the same command and boot into PFSense.
Now you can make the fix permanent. Once PFsense is at the main menu, shell out to a command prompt. Type the following:
arrow down to the last line, press "a" to append (make sure cursor is on a new line after last entry in file). on new line type:
press return, then escape, then the keys "wq!" to write the changes to the file.
Verify your changes by typing "more /boot/loader.conf" and look for your entry at the end.
Issue 2: No NICs found. You have to use Legacy NICs, the default nics are not recognized by Free BSD.
Issue 3: PFSense doesn't receive a DHCP address.
So you get all the way through the install, you can hit PF's Web configurator just fine, but it won't pick up dhcp from your WAN provider, huh?
Yeah, this one had me stumped for a bit. Thanks to some great posts in this forum, I was able to find a quick resolution, so I'm just
summarizing here and hopefully providing a consolidated reference for those seeking help in the future.
For whatever reason, DEx nics don't immediately listen for dhcp assignments in Hyper-V. If you down the adapter, bring it back up, then listen,
it works just fine. Shell out to the command prompt and type the following:
ifconfig de(x) down [where (x) corresponds to the nic you are troubleshooting for dhcp]
ifconfig de(x) up
now make the change permanent. create an /etc/rc.local file (vi /etc/rc.local), add those commands, save the file, then type
chmod 755 /etc/rc.local
to make it an executable for root.