Hyper-V integration installed with pfSense 2.0.1
-
- Looking for the rrd error in the log, it seems that you only need to reinstall rrdtool (pkg_add -r rrdtool, per http://forum.pfsense.org/index.php?topic=37489.0). It takes a while (it downloads several X related packages) and displays some warnings along the way, but rrd graphs are back and I haven't noticed any ill effects.
works :).
- Still see "calcru: runtime went backwards" warning, usually shortly after a reboot (but no different from 2.0.2 w/o Hyper-V).
I'm not sure if that is some kind of wanted behaviour. Because this behaviour occours an an XP VM, too. But right after this message the web interface stops respondung and I have to restart it manually.
Edit: if you have an idea how vlans could work on an 2012 machine, let me know :).
-
Hyper-V as a host will allow vlans connected to different virtual adapters on 2008 version
It however requires that the physical nic that is connected to the virtual switch is Vlan enabled.Hyper-V as a host will allow Vlan trunking on one virtual adapter in 2012 Version.
Edit: Don't do advanced networking before 10 a clock :)
I have a testbox running now and it seems to work. Now it's just a matter of getting this into the stable release :) -
I have a testbox running now and it seems to work. Now it's just a matter of getting this into the stable release Smiley
With a pfSense box? In my case the console configuration script says me that there are no vlan captable interfaces.
Same config is running with a Windows Server 2012 so the Hyper-V config seems to be correct. -
Thank you for this :)
2.1 on Hyper-V 2012, I have 3 vNics (vlans set on host), PPPoE and DHCP WAN's load balanced plus IPSec VPN and all seems much like my physical 2.0.1 box. I can live migrate it between Hyper-V hosts with only one dropped packet at the clients.
I used "sysctl kern.timecounter.hardware=TSC" to fix the calc runtime error.
Only potential issue I have is spikes in CPU usage despite no activity, plus I'm only 60/20 VDSL and its on a Xeon E5620 host so plenty of power.
-
I have a testbox running now and it seems to work. Now it's just a matter of getting this into the stable release Smiley
With a pfSense box? In my case the console configuration script says me that there are no vlan captable interfaces.
Same config is running with a Windows Server 2012 so the Hyper-V config seems to be correct.Yes and no :)
2008R2SP1 as base OS running a Hyper-V server.
I do feed that server with Vlans so my virtual Switch called trunk has a number of VLans on it.When i Created my virtual machine fpr PFSense i gave it to Network cards attached to the Trunk Vswitch.
On for Vlan 1 and one for Vlan 666 (guess wich is the Evil internet)In Pfsense I get two non-vlan capable Nics witch i Assaign to Internal and Wan.
If i try to use Vlan here I get the same message as you did.Im not sure if the nic driver for Hyper-v is Capable of Vlans. The BSD driver has the function if it's of the right version but it didn't have it from the beggining.
-
Thak you for your explanation. That's how I use pfSene at the moment.
-
I am running this is On a Windows 2012 Hyper-V host and are seeing some errors when I start the pfSense VM
A storage device in 'pfSense' loaded but has a different version from the server. Server version 5.1 Client version 2.0
Networking driver in pfSense loaded but has a different version from the server. Server version 4.0 Client version 3.2
Also there is an error later after about an 10-28 hour period of running perfectly that the adapter connected to the Hyper-V switch disconnects (mostly the WAN side but the LAN side also) The only way to correct the issue is to restart the Hyper-V Host. I have tried disconnecting the cables and replacing the cables, disabling and enabling the network cards associated to those virtual switches, upgrading the Intel 82574L drivers to Intel’s latest, and disabled most settings in different combinations to see if a setting was to blame. Still the network adapter seems to disappear randomly. Also tried a different network card fearing the integrated NIC was faulty. Still no joy
Is there any plans from Microsoft to release the updated drivers for FreeBSD on Hyper-V and if so zootie do you think you can update the ISOs that you created because this is the best integration I have seen with Hyper-V
Shout out to zootie for the time he took to make the ISO
-
There are maybe plans because the driver is in beta state. For that time you maybe should enable MAC Adress spoofing at the HyperV Network configuration interface.
With Server 2008 R2 there are no Problems.I used "sysctl kern.timecounter.hardware=TSC" to fix the calc runtime error.
This resolves the error outputs but makes the pfSense clock run. I get +8 hours a day.
-
I am running this is On a Windows 2012 Hyper-V host and are seeing some errors when I start the pfSense VM
A storage device in 'pfSense' loaded but has a different version from the server. Server version 5.1 Client version 2.0
Networking driver in pfSense loaded but has a different version from the server. Server version 4.0 Client version 3.2
Also there is an error later after about an 10-28 hour period of running perfectly that the adapter connected to the Hyper-V switch disconnects (mostly the WAN side but the LAN side also) The only way to correct the issue is to restart the Hyper-V Host. I have tried disconnecting the cables and replacing the cables, disabling and enabling the network cards associated to those virtual switches, upgrading the Intel 82574L drivers to Intel’s latest, and disabled most settings in different combinations to see if a setting was to blame. Still the network adapter seems to disappear randomly. Also tried a different network card fearing the integrated NIC was faulty. Still no joy
Is there any plans from Microsoft to release the updated drivers for FreeBSD on Hyper-V and if so zootie do you think you can update the ISOs that you created because this is the best integration I have seen with Hyper-V
Shout out to zootie for the time he took to make the ISO
I'm sorry this is no help but I'm having good luck with it :-\ I hope you can get it sorted!
Host 1 = Xeon E5620, Asus Z8NA-D6 server board, 2 x 82574L onboard. Fresh install of 2012 Std, both NIC's teamed 802.3ad into one switch with Intel Proset 17.4.95, all other settings at default. One vSwitch on the NIC team. 10 other VMs running.
Host 2 = Fresh install 2012 Std, Intel NUC, 1 x 82579V NIC, Proset 18.0.1 connected to a different model switch to above. 2-4 other VMs running.
I present 3 synthetic vnics, mac spoofing enabled each on a different vlan in Hyper-V, 2 x wans and 1 x lan. One PPPOE and one DHCP.
I have used vmdq off and on, seems to be no difference. Not sure either of my nics actually support vmdq despite the option being there so maybe why..
I have remote site OpenVPN up and dialin IPSec VPN.
I get the old intergration components error plus the time error in console but other than that it is all good. I have tried to use pf 2 beta on hyper-v without these components ages ago and after days of maddness had to buy a physical box, back then I had real issues with the same hardware although 2008 R2 host. I have full device monitoring and have barely a dropped packet in the 5 days it's been up. I've migrated it between hosts without issue and its spent a few days on both with no difference.
I really hope it stays working because this is great, Hyper-V 2012 has a really strong business case vs ESXi and I'd like to use it more.
Fehler20 :
I don't know, I sync to external NTP time source so my clock is good.
-
It would make sense to say which of the 2 versions you are using? There is after all 2 different versions posted.
I'd expect 2.0 branch to have issues because the drivers don't officially support the FreeBSD that's based on. I'd have thought if they did they'd have advertised that fact.
The 2.1 branch however should in theory be OK because of the upgraded FreeBSD.
Anyway please say which of the 2 is working for you or if you have problems again please say which version.
-
This issue was happening on both versions but I have solved the issue. Well I think I did. The VM has been running for 52 hours so far no issues. It was related to the processor C states allowing the NIC cards that are integrated to be powered off to conserve energy. I have been analyzing the logs off the host machine for the past few days and tried a few tweeks in the bios to not allow power saving anywhere and disabled C states also in windows I have turned off the settings in the device manager for the NICs for power saving.
Seems with the updated Hyper-V integrated services for 2012 has power management settings that can be passed to the host for correct CPU low power states but the drivers currently for FreeBSD in beta only fully support 2008 R2 which do not have the new power management capabilities.
The host box is a Supermicro 5017P-TLN4F
http://www.supermicro.com/products/system/1u/5017/sys-5017p-tln4f.cfm16gb ram
RAID 1 Intel 520 480GB SSDI use it for a low power house router and secondary domain controller and remote management for Microsoft system center 2012.
Thanks for all your help everyone hope to see an update version soon and maybe full support in the next official release.
-
Cool, glad you got it sorted :)
Mine has been fine although I did have an incident where I lost all configuration inside the VM, however I did cluster the hosts and mess with snapshots so I think I probably caused that.
That Supermicro box is to die for, do you know how much power that is drawing from the wall because it looks exactly like what I want! :D
-
@zootie! terrific work! thanks for taking the effort to build the iso.
@all - I have been trying for a long time to get pfsense working on hyper-v. The LAN side is all sorted out (completely virtualized), I'm having a problem with the WAN side.
my setup is as follows
Internet <-> router (DHCP for WAN) <-> pfsense WAN (connected to an external virtual switch) <-> pfsense (DHCP for the LAN) <-> LAN VM's (All connected to a private switch).
No matter what I do, the pfsense WAN interface does not pick up an IP address from the router. Ideally, this should pick up a 192.168.1.x address
Only things I can think of are 1) uncheck the setting on the WAN interface so that it can accept an RFC 1918 address and 2) enabling mac spoofing on the WAN interface.
Any suggestions / pointers? Thanks in advance!
-
I'd just like to add my thanks as well. I'd tried it before on Hyper-V without the Integration Components and the performance was so poor that it was unusable. I had to switch to ESXi which was a shame because I liked some of the new features in Hyper-V 2012.
However I've been running this in Hyper-V for around a week now with no issues. I don't use VLAN's and haven't played with QOS on it but I've got 2 WAN's, IPsec and OpenVPN all running off it with no issues.
I'm using the 2.1 ISO. Obviously it tells me there's updates but I've not applied any incase it overrides the custom kernel with a default one and the Hyper-V integration is lost. Has anyone tried updating? I guess I could just snapshot it, try it and roll it back if it gets nuked. The advantages of it being a VM :)
Hopefully 2.1 will be final in the not too distant future and can run off a none beta version of pfSense.
Looking at the git repo for the Hyper-V drivers the development doesn't really seem to be moving much. It looks a bit slow to say the least which is a shame. I'm hoping they'd update the drivers to 2012 Hyper-V levels (Does that break backwards compatibility though with 2008 versions of Hyper-V? If so that's not such a good idea).
-
@zootie! terrific work! thanks for taking the effort to build the iso.
@all - I have been trying for a long time to get pfsense working on hyper-v. The LAN side is all sorted out (completely virtualized), I'm having a problem with the WAN side.
my setup is as follows
Internet <-> router (DHCP for WAN) <-> pfsense WAN (connected to an external virtual switch) <-> pfsense (DHCP for the LAN) <-> LAN VM's (All connected to a private switch).
No matter what I do, the pfsense WAN interface does not pick up an IP address from the router. Ideally, this should pick up a 192.168.1.x address
Only things I can think of are 1) uncheck the setting on the WAN interface so that it can accept an RFC 1918 address and 2) enabling mac spoofing on the WAN interface.
Any suggestions / pointers? Thanks in advance!
Well it could be the nicdriver for the Physical card you are using for Wan. Some dumb manufacturers (Realtec! for example) doesn't include everything you need for hyper-V in their base driver.
Saw this Issue with Hyper-V and a virtual ISA server. Exactly the same problem. Completly impossible to get an IP on Wan. Replaced the card with a Intel card and problem solved.
There are articles on how you can fix it with additanl doenloads too but I didn't try them -
@mats - thanks a lot for your response.
I tried that too, but still no luck. The NIC is an intel 6200 wifi, with the latest drivers (released by intel towards the end of October). Can you post the links to the additional articles - I'll see if it helps!
Only thing left now to try is to see if it works with a wired connection - but then, it would be a pain to be chained to a desk.
Any other suggestions appreciated :).
-
@mats - thanks a lot for your response.
I tried that too, but still no luck. The NIC is an intel 6200 wifi, with the latest drivers (released by intel towards the end of October). Can you post the links to the additional articles - I'll see if it helps!
Only thing left now to try is to see if it works with a wired connection - but then, it would be a pain to be chained to a desk.
Any other suggestions appreciated :).
WAN and WLAN is 2 different things. Don't mix them up :)
-
WAN and WLAN is 2 different things. Don't mix them up :)
yes, I'm totally aware of the difference between the two. The WLAN interface is assigned to the external virtual switch in hyper-v, with the OS managing the interface - this means that the hyper-v layer will route traffic from the external switch and the physical machine over the same physical interface.
The WAN interface of pfsense connects to the external switch - hence it should either pick up an ip address from the router on the 192.168.1.x network thru DHCP, or should be able to connect to the internet using a 192.168.1.0/32 static address.
-
WAN and WLAN is 2 different things. Don't mix them up :)
yes, I'm totally aware of the difference between the two. The WLAN interface is assigned to the external virtual switch in hyper-v, with the OS managing the interface - this means that the hyper-v layer will route traffic from the external switch and the physical machine over the same physical interface.
The WAN interface of pfsense connects to the external switch - hence it should either pick up an ip address from the router on the 192.168.1.x network thru DHCP, or should be able to connect to the internet using a 192.168.1.0/32 static address.
So it doesn't work even if you give it a static address?
-
WAN and WLAN is 2 different things. Don't mix them up :)
yes, I'm totally aware of the difference between the two. The WLAN interface is assigned to the external virtual switch in hyper-v, with the OS managing the interface - this means that the hyper-v layer will route traffic from the external switch and the physical machine over the same physical interface.
The WAN interface of pfsense connects to the external switch - hence it should either pick up an ip address from the router on the 192.168.1.x network thru DHCP, or should be able to connect to the internet using a 192.168.1.0/32 static address.
So it doesn't work even if you give it a static address?
nope. It doesn't! that's what's very wierd!
there are only two things I have to try out - 1) hook up the laptop to the internet connection directly (that way, the interface address will be in the routable public internet) and 2) try using the wired nic to see if the WAN interface can pick up a 192.168.1.x address via DHCP.