Sorry that this is a bit late but I've had a couple of instances where it seemed that the network performance was sluggish under Hyper-V 2012R2. We have found the problem to be with the Broadcom network cards and their handling of VMQ. I believe that there is a firmware and driver update to fix this but have found that just disabling the "Virtual Machine Queues" under the properties of the network car on the host fixes the issue.

Which build did you use? I cannot get mine to properly work.

@jimp: Have you tried posting on the Turkish support board? The code for the Turkish language was all contributed, we don't maintain it internally as none of us speak Turkish. Im Turkish board Moderator :) I will translate so many word in the translation. But I cant found a problem the translate Apply Button Area in http://pootle.pfsense.org.br/tr/pfSense/ Okey I found it and Apply changes not be translate now updated. Can u recomplie pfSense.mo file and update out last changes? thank you.

Are you on 2.1.4 or 2.2? This board is only for 2.2 If you are on 2.2 and that is happening, try this from the shell and post the output: pfctl -f /tmp/rules.debug If you're on 2.1.4, get that output and post it in the Installation and Upgrades board.

Sorry it's taken awhile for me to get back to this… I'm using the latest 2.2 snapshots (from a fresh install) and they seem to be working fine. No idea what happened before,  but must have been an upgrade-related fluke in a much older build. A 2.1 fresh install still works fine off USB but hangs when trying to boot to hard disk. So I'll stick with 2.2 on this hardware for now.

@jimp: Try a current snapshot, not the older ones. The latest snapshot resolved it.

Sorry. Could have swore I posted this in the snapshot forum originally. Yeah. A missing module was my first thought but have not been able to wrap my head around yet how to deal with that stuff in FreeBSD. Looks like I'll have to do some more reading on it.

My pleasure.

I managed to resolve this issue. I cut down the partition size to 12 gb (it was 200gb) and it booted fine.

You have to do more than that and tell us which drivers!!!

I'm also using it at home now - IPv6 is broken for me (issue 3361, I believe), but it's less broken than 2.1 was - and everything else seems fine.  :) (I hear IPv6 in 2.1 works fine for others, I've just not had any luck with it myself.)

OK, please respond on this thread which is specifically for interactions with Unbound: https://forum.pfsense.org/index.php?topic=78356.0

Not seeing it here, after updating from (about) 20-May alpha to 20-June alpha.  x86-64, physical machines, no packages.  Also cannot reproduce it with i386 or x86-64 virtual box machines. When it hangs, is there anything interesting in the logs or on the console?  What about the last few lines of /cf/conf/upgrade_log.txt?  Mine typically look like so: . . . local/livefs/lib:         modification time (Tue May 20 15:58:13 2014, Fri Jun 20 09:10:24 2014) Checking for /tmp//tmp/post_upgrade_command.php... Running /tmp/post_upgrade_command.php Adding serial port settings ()... Reading /boot/loader.conf... Fri Jun 20 12:23:20 EDT 2014 Firmware upgrade is complete. Rebooting in 10 seconds.

Yep, fixed with a gitsync.  Thanks!

OK, I will concede that Notepad++ does have some useful features over MS-DOS edit.  ;)

i386 version running on real hardware (AMD Athlon dual core). 2.1.3 on the same machine does not complain about memory. I worked around the issue by hard coding the memory … ;-)