Hyper-V integration installed with pfSense 2.0.1
-
A couple general news on this topic.
Looking in the git repository, there have been considerable improvements in the source code for the integration component drivers and are now at a 1.0 release level. I've been trying to figure out a way to inject these newer drivers into a running pfSense VM or to generate a new pfSense ISO build with this new code (been at it for a few days). I'll report back once I figure out a way to build it (or if I give up for the time being).
These newer drivers are considered stable enough to be included in FreeBSD 10. Hopefully, it'll be a considerable improvement that will solve some of the issues we've experienced. There is also the possibility that a near future version of pfSense (maybe 2.2) will be based on FreeBSD 10 (rather than 8.3 as 2.1), making it easier to support Hyper-V going forward.
-
What are your VM settings? Are you giving it only 1 CPU by chance? There is code in the source that has something to do with tying to a certain CPU.
I'am using 2 or 4 CPU and 1 Gb RAM
Config on my test lab:
2 CPU 1Gb RAM
WAN1 Link 1 Gigabit (True 1 Gigabit internet link)
WAN2 Link 5 Megabit (Backup link, and some services published to internet) -
hmh,
I tried those instructions on a vanila 2.1 installation, and it crashes the VM as soon as you try and enable the interface or to assign them. There are other users attempting similar strategies, but so far, all have reported that the precompiled (or trivially recompiled) drivers break pfSense (and we're having to go through hoops to try and compile a version that is more compatible with pfSense).
Can anyone confirm they got the new precompiled drivers using the instructions on https://github.com/FreeBSDonHyper-V/Hyperv-Ports/wiki/Install-pre&minus%3Bbuilt-FreeBSD-8-Hyper&minus%3BV-Integration-Components-using-packages? Are you sure you're using the synthetic driver (ie, shutdown and remove the Legacy NIC from the VM so it attemtps a reassign on the following boot). You can re-add the Legacy NICs to get the VM back online (and/or you should make a backup of your VHD before installing these drivers).
-
FreeBSD 10
Let's wait for branch.
-
….........
Can anyone confirm they got the new precompiled drivers using the instructions on ...........Confirm.
-
That's not enough to confirm. You have to access the interfaces (that is when the VM crashes for me and other users). Please assign them an IP address (or run the assign interfaces command in the menu and assign WAN/LAN to the hnX adapters) and if it doesn't crash, please post the output of ifconfig showing the hnX interfaces with IP addresses.
Independently if these instructions work (which if they do, at best might only work on some systems). I just had a breakthrough and I finally was able to load recompiled hyperv-1.0 drivers on pfSense 2.1. I still need to do more testing and do my due diligence, but if the precompiled drivers don't work for you and/or if you're having issues with the August 2012 drivers (used in Alex Appleton method and in my and PollyPy's installer ISOs), don't waste too much time: a new improved version is likely coming in the next few days.
-
…. don't waste too much time: a new improved version is likely coming in the next few days.
This is very good news!!! Thank you, i will wait few days, please post news in this thread!
-
windows server 2012 with pfSense-LiveCD-2.1-RELEASE-amd64-hyperv-kernel-20130915-1129.iso + squid3 + lightsquid causes Panic String: sleeping thread (same as https://forum.pfsense.org/index.php?topic=72539.0). Uninstalling squid3 + lightsquid seems to solve the problem, but can't make more test as it's in production
-
Waiting patiently :)
-
I started a new thread and uploaded the new drivers in https://forum.pfsense.org/index.php/topic,73258.0.html
I decided to start a new thread because the new drivers are a considerable departure from the methods discussed on this thread, and to make it easier to find them (since the first couple pages in this thread are a bit preliminary and a bit obsolete).
If you had issues with the old drivers, please give the new drivers a try and let us know how they work in your environment.
-
Hey everyone, so I got the image running in hyper-v (2008r2) but I cant make any changes to the firewall or NAT. It takes system preferences changes like users and passwords, dns changes but that's about it. any ideas?
im also getting scrolling message every 5 min or so on the console.
hv_kvp_negotiate_version Hyperv-utils1: detached hyperv-utils1 on vmbus0 hyperv-utils1: Hyper-V service attching: Hyper-v sevice attaching; Hyper-v KVP Service -
Please see the ESF response: https://forum.pfsense.org/index.php?topic=73258.msg402614#msg402614