I have switched back to e1000 from vmx3 - even though freebsd has native support now.  I don't like that it only shows autoselect for speed and was giving errors with cdp reporting half duplex..  While e1000 works fine and don't have these issues. I use the ladvd package to have pfsense report via cdp and lldp, etc.. While there is most like a bit of performance benefit with using vmx3 over the e1000, not an issue for me since only routing traffic for home network with a 50/10 internet connection.  While I wish it could have more bandwidth between segments.  The testing I did between vmx3 and e1000 was so small better to get my cdp and lldp info

So clearly if you have 1 IP and expected both pfsense and esxi vmkern to share that you were doing something wrong ;) Your vmkern is going to have to be behind pfsense, so as I showed in my drawing it has a rfc1918 address BEHIND pfsense.  You then setup pfsense to forward to your vmkern IP when you hit port X on pfsense wan IP.

Yeah but at first after i changed both NICs to bridge win2k8 still could not get IP from pfsense till i did the above reconfiguring

@kapara: Just out of curiosity and why would you want to set up CARP in hyper-v sense both virtual machines are on the same physical hardware?  Unless you are setting up two separate hyper -v hosts and putting a PF sense on each. Correct. It is two separate hosts, with their own network cabling. Sorry if that was not clear in the original post. (updated) Yak.

I can push 1000Mbit.

Cool thanks for the pointer I will have another go.

Depending on what you have access to I would recommend hyper-v.  I used to use VMware but due to issues like expensive support and limitations with API on free version I decided to go with Hyper-V.  As a Microsoft partner I get unlimited free critical support from Microsoft. There is also a free version if Altaro which you install ib the host And will give you up to 2 vm backups for free. Also if you want with hyper-v 2012 you get free replication which is really nice!!!

Nothing wrong with that dashboard display. However it does seem as though your other interface is being emulated as compatible with the amd le driver which is not great. You should try to make sure they all appear as Intel NICs or better that the hardware is actually passed through so they appear as the real NIC. Steve

There's one every month. Not sure we'll revisit virtualization this year but the recording of the June 2014 session is available for gold subscribers in the members area.

You are having the shmem-offloading-bug. See https://forum.pfsense.org/index.php?topic=88467.0 (I actually spelled IMPORTANT all-caps in there for a reason :p hah. ) The commands you want for XenServer are the 'xe' commands. Don't reboot pfSense, but shutdown and freshly start the VM after updating the settings. You can use ethtool to test it without rebooting the VM.

that early in your boot shouldn't know.  Do you have serial disabled in the bios of the vm.  There have been some threads about serial interface causing some really slow boots. When get a chance will try to duplicate this by bringing up a vm in hw 10 version, and then installing pfsense 32 bit.  And then trying to boot the cd after upgrading to hw 11.

hmm - will have to do something with a custom script to test.  Something simple that can validate works or doesnt work or if get same error, etc.

dude it works on 6 just fine..  But if you install the native tools and use vmx3 pfsense is not going to work unless you disable csumming at with ifconfig vmx? -rxcsum -txcsum -tso4 and this has to be done every boot. Just install the openvm tools package in pfsense there you go done. I can tell you for fact that these instructions work on getting the tools installed http://www.v-front.de/2015/01/pfsense-22-was-released-how-to-install.html This works on esxi 6, have done it many times on many different vms of psense..  But again if your wanting to use vmx3 nic in pfsense doing so will break pfsense from passing traffic.

Just switched back to e1000 interfaces from vmxnet 3 interfaces and now pfsense is seeing broadcasts including arps.

No its not recommended for security reasons. Makes sense but I never remember that because my users couldn't crack a vending machine if you gave them a bag full of coins.

Found this… though it doesn't mention why exactly FreeBSD head fixes the issue: http://lists.freebsd.org/pipermail/freebsd-net/2015-March/041801.html