@johnpoz: Its a few years old, its a HP Microserver N40L, it has AMD Turion II 1.5ghz dual core.  I bumped it to 8GB of ram, using a SSD for datastore and added some nics.  It runs really sweet, uses very little power,  I have 5 disks in it not counting the SSD.  I get 100MBps pulling files from the storage VM that I have raw mounted the other disks too. Nice.  I'm just hoping my Xeon X3 will perform well in conjuction with my Plex server.  My site to site VPN should be the most taxing thing it has to handle.

I'm curious, what is the recommended method for disabling tx checksums on the hypervisor side for kvm/qemu? I'm running proxmox and it creates tap interfaces for each VM (tap110i0), ethtool doesn't seem to support tap interfaces, it returns: ethtool -K tap118i0 tx off Cannot change tx-checksumming Actual changes: generic-segmentation-offload: on I would prefer to not disable it on the bridge interface (vmbr0) due to the performance hit johnkeates mentions. Also, does this only affect virtio, is e1000e unaffected?

SOLVED! a simple "sudo dhclient eth0:1" solved it…

Probably the same geniuses who made my KVM with a hardcoded command key of Num Lock. If I boot a VM and it has focus, the Num Lock toggling by the VM causes the KVM to switch. Brilliant.

could you try with a clean install without vmware-tools ? (to try with the builtin vmxnet3 drivers). most people manage to get around 1.5-2 gbit/s  pushed through when using vmxnet3 adapters  … so something is probably going wrong. are the cpu's maxed out when checking this from your vsphere client? see this thread: https://forum.pfsense.org/index.php?topic=87675.0

I can report that the 2.2 releases, both Beta and Release, work fine with Hyper-V, and with CARP. 6 Pf's on different hosts/clusters & I have a CARP array doing OpenVPN Site-to-Sites to other PF's, works fine. Only thing you need to do i've found is: Use a Gen1 VM. Set the disk to be fixed size. Enable MAC Spoofing on the NICs that will have CARP addresses. Disable dynamic memory.

Damn thats fast…. haha

The answer for me was – my schema worked, but I went crazy thinking I had weird issues with my setup.. ended up just being my NIC card. You NEED 2 nic cards without the 2nd one being ghetto in any form. Mine was ghetto :P I ended up doing this: https://docs.google.com/presentation/d/18daTkuC344aqCuJ_qOgGhEMz9_DGi_Ek0R9I_uYMc3Q/edit?usp=sharing This is about as detailed/friendly as it gets. Please note the 2nd slide for details. Good luck ;)

Wow, believe it or not, it looks like my issue was caused by my DNS server settings. I was using Google DNS in the pfsense config (8.8.8.8) and for some reason it appears that it was breaking things. I've switched to my FiOS router as the DNS (192.168.1.1) and it appears to be working both externally (web requests) and internally now. How bizarre. Thanks for everyones help, here's hoping this thread helps someone else in need lol. Edit: I also upgraded to 2.2 during this process…I don't THINK that has anything to do with it, but I suppose it's possible.

This is just what I needed.  ;D  I was having issues setting up this as well, and while I had set the SR-IOV in the network manager setup, I missed it under the VM/Network/HW Acceleration.

what is the status of the open vm tools package being compatible without doing CLI hacking ?

you can try to go to setup wizard and tick on allow DHCP dns also put in the primary DNS your DNS or put 8.8.8.8 Thanks Ali Chouman

quick update I did an install of an virtual smoothwall and all works fine… :o So its has something to do with pfsense for sure....

Are you in the wrong thread then??? This thread is about vmware tools "VMware 2.2 RC and VMware Tools - can only ping  (Read 877 times) "

Well this is what I ended up doing. Did a fresh new VM, set with bsd 8.x preconfig. Copied host cpu configurations and disabled xsave feature Did virtIO on the disk/5G image Got rid of all the nics. Did pci-passthrough of eth1 on the host to VM. Then did vlan setup from pfsense side. Result LAN to LAN2 50MB/s which is what I expected. Both interfaces pushing about 400Mbit/s according to the pfsense traffic graphs, which would stature a single gigabit link. Eh, it's much better than what it was before; and now I'm running 2.2.

Hi, And the answer is no. The provider doesn't currently permit to pass VLAN taggs between two hosts. It will be added in a future release though. But for now, I can't use VLANs. So what is the best option to isolate the subnets? Am I right in assuming that if I create a new vswitch with no attached interface to it, the CARP won't work at all for the subnet in this vswitch? Thanks, Nicolas