Starting from FreeBSD 10 the GENERIC kernel configuration on both i386 and amd64 contains full Xen PVHVM support, so there's no need to compile a specific kernel in order to get Xen drivers. Previous versions of FreeBSD (8.x and 9.x) required the user to compile a custom (XENHVM) kernel in order to make use of the PV optimizations when running inside of a HVM container.

What do you expect if PV is enabled at hypervisor and em0 was an fall back and suddenly PV is available in a new kernel?
It's like with all other drivers. If there is a new driver in a new kernel which fits better it will be loaded first.

But as I said: I really want the new xn0 because it needs less CPU time. But tagging must be possible. Please report it upstream.
If you patch the config.xml tagging was possibe for ICMP and UDP.

The next step after migrating to debian jessie (Xen 4.4) is to test PVH (without QEMU): https://wiki.freebsd.org/FreeBSD/XenNG
But I guess pygrub has to learn more about UFS to grab the kernel from the image.

Is it possible to boot pfsense disk less from nfs?

There is an issue of some sort with services not starting post-package reinstall after upgrade in some circumstances, but haven't seen packages missing. That plus the log you're getting from Unbound and the fact that NTP isn't working since your time and date is way off suggest the system is having some kind of issue sending network traffic. Not enough info to suggest why. System logs might be telling.

Thanks charliem, that did the trick!

cmb - I understand the importance of the digital signature and that there are much more important problems to iron out first. This is for personal use and testing so I am not concerned with everything being "proper" just yet. Once it hits the stable release then I will re-evaluate the install and probably redo it.

Thanks again for the help!!

It was confirmed fixed a couple days ago.

I tired  again with no bind and no extra commands but it is still reverting the config on save.
I see my LastPass plugin pop up on save  as well..will try disabling that.

EDIT:
Got it all working. At some point right after I started a pfsense beta update was pushed out so not sure if it was disabling the LastPass or the update that fixed things but the settings were kept along with the certs.
So fully working now on openVPN over PIA vpn service. Seems stable and quite quick.

Question: I'm not keen on continuing updates to beta as it's stable now. When the final release is out can I just auto update to that?

That's fixed, thanks.

You can disregard / close this problem report.

I was not able to find a reproducible Issue.  I have everything working like I need at the moment.

Fixed on 2.2-BETA-amd64-20141121-0816

Bug #4007 ("Last activity" in CP status blank) is fixed too.

you are running x64, when I get a chance will fire up a copy of that.  But I didn't have any problems getting them installed with i386 snapshot from the other day.

Thank you for reporting.
Fixed for newer snapshots.

None of those reports are relevant to 2.2, those are all in reference to 2.1.x or older versions which have a much older base OS. 2.2 is fully up to date with FreeBSD and we'll be able to stay more current with FreeBSD going forward, which will eliminate most all of those issues. For the rare edge cases that may remain, it's not hard to drop in a kernel module and kldload it. The hard part is applying the relevant patches and building it, which isn't something you want to or can do on pfSense, you have to setup a stock FreeBSD system that has the build tools to do so.

Is that a system you could get me access to? That's not an issue I've been able to replicate and I'd like to check out what it's doing when it's showing down. If so, PM me and we can figure out details.

Just to update - this has been running fine the last few weeks. I have upgraded every couple of days to test stuff. No panics, no system problems at all. I will assume something got fixed in a late FreeBSD 10.1-RC.

Those should come back after either a gitsync to master, or upgrading to tomorrow's snapshot.

I deleted the bad snapshot's update files, there won't be any until the next run is finished and it'll show "unable to check for updates" until then.

I built a kernel with the latest from git and it works.  I'll update to the snapshot when it is ready.

Thank you.

It will be used by openvpn do not worry about that :)