I am so happy – I managed to make it work…
What we need to make FreeBSD run on Hyper-V:
– download FreeBSD ISO image from:
Download this ISO image:
– create new Virtual Machine using Hyper-V
– remove default network card that is added by wizard
– add hardware and chose Legacy network adapter
– start the machine and “mount” ISO image to start booting FreeBSD…
– install it with parameters you want…
– **** NETWORK PROBLEMS **** Even if you are runing DHCP server on your network your FreeBSD machine will not get IP from your DHCP server (my machine did not) so I used ifconfig to add IP and gateway this way:
ifconfig de0 10.70.60.201 – this is IP in my subnet you should use one of your free IP’s
ifconfig de0 down
ifconfig de0 up
You can now chec status of your IP with:
Ok, now we need a gateway to get to the internet:
route add 0.0.0.0 10.70.60.1 This will add your default gateway (for example my gateway is 10.70.60.1)…
try to ping an public IP address to see it is working… As you can see in my screenshots it works for me. 🙂
FreeBSD on Hyper-V [docx]
FreeBSD on Hyper-V [pdf]
*** There is still one problem unsolved for now… If you try to reboot Free BSD, Hyper-V does not Turn off the machine … I am trying to solve that with some Nejc tricks 🙂
Could you please describe how are you solving reboot trouble?
You can check my newest post regarding this problem… I solved it by using shutdown -p now and then turning FreeBSD up again using Hyper-V manager…
So do not use reboot or shutdown -r now but “power off” FreeBSD and then turn it back on…
Hope it helps,
Thank you, very much! This “reboot failure” was the last unresolved (now resolved!) point before move my FreeBSD to Hyper-V
Found a temporary solution to the “shutdown” issue — this site has a WMI script that you can use to find the PID of the VM worker process (vmwp.exe):
Once found, kill it from Task Manager and then the VM will finally shutdown and restart.
How do you have your host networking set up? I can’t get my guest to work. DHCP works ~50% of the time, but I can’t ping anything from the guest.
Oops, spoke too soon. Strangely, even though DHCP gave me an address and default gateway, nothing worked. I went static with down/up and it did…
I made an easy patch for the kernel.
As a result, a virtual machine comes never to stop.
I expect someone to make the patch by a smarter method.
My patch can be downloaded from the following blogs.
This patched kernel confirmed the operation with
Server 2008 Enterprise w/Hyper-V and Hyper-V Server.
You can fix DHCP in FreeBSD. Just read this
I found a simple workaround to my FreeBSD on Hyper-V woes! This solution also works for saving hang cause by VSS when running server backup.
ifconfig de0 down
shutdown –p now
Wow! I wish I could have found this 8 hours ago! It would have saved me a lot of time and frustration.
Your suggestions worked without problems.
Legacy network adapter is slow.
If you insist to use openbsd, run it on Xen