After the release of pfSense 2.2 it was time to upgrade some installations. They resides on Windows Server 2012 R2 Hyper-V. After the first reboot my test machine did not come up. The screen looks like this:
The error message is quite interesting at first:
Mounting from ufs:/dev/ad0s1a failed with error 19.
After little goggling I’ve found this article:
Mounting from ufs:/dev/adaxs1a failed with error 19.
and after simple entering of one ? the answer to the problem was in front of me:
The disk names were change from
So to boot I’ve typed:
Now the only thing that is left if to make changes to the boot configuration
You have the option to for form console
8) Shelland edit the file Mine looked like this:and after the change like this
Of if you will you can make the change using the web gui
go in the Diagnostics menu and selecting the Edit FileFrom there you just naviage to the “/etc/fstab” and edit the text.After changes test that the system is booting from the correct partition.
As you probably know, on the Build conference was announced the Developer Previews of Windows 8 and Windows Server 8.
Because of the numerous new features in Hyper-V 3.0 I want to check them personally. Because I do not have two spare boxes on which to install them, virtualization comes in play.
Before Hyper-V role is added to the server, there is configuration to be made on the Virtual Machine:
The best description of the process that I find is in this article:
Nesting Hyper-V with VMware Workstation 8 and ESXi 5
In the Processors configuration Virtualize Intel VT-x/EPT must be checked,
And one line must be added to the configuration file vmx:
hypervisor.cpuid.v0 = “FALSE”
That’s it, now you can add Hyper-V role and play with it.
Today pfSense 2.0 RC1 was officially released. So I’ve quickly downloaded it and setup one test VM in VMWare. The new interface reveals a lot more features than the previous version 1.2.3. For full list of improvements look here: http://doc.pfsense.org/index.php/2.0_New_Features_and_Changes
What I was more interested in was the performance on Hyper-V VM. Recently I’ve setup a Hyper-V VM with 1.2.3 version and legacy network interface cards. Make a few quick file transfer tests and did not like the performance.
I’ve repeat the tests, and there is a 25% improvement over 1.2.3. This is encouraging. Unfortunately event with the new version, it is necessary to use Legacy NIC for the Hyper-V VM.
As it is stated in the Digest this is considered a stable release suitable for production use. I will continue the testing in production environment to get more realistic results.
After seeing pfSense working more than half year flawlessly on Alix, recently I’ve test it as virtual machine.
To avoid some compatibility issues a “Legacy Network Adapters” must be used.
For my surprise even with that trick, there was no network connectivity. The work around for this problem is explained in this thread: Pfsense 2.0-BETA4 in Hyper-V: Throughput not as expected
Open shell from the console, create new document
and type in
ifconfig de1 down
ifconfig de0 down
ifconfig de0 up
ifconfig de1 up
Just check before that the names of your interfaces, mine were de0,1.
For now it is stable, no issues, with very basic configuration. On the forums there are topics about possible problems with VLANs, but I didn’t need this functionality.