Comments on: FreeBSD on Microsoft Hyper-V

By: cheesyboofs

cheesyboofs — Thu, 11 Jun 2009 09:20:29 +0000

Google Translate?

http://translate.google.com/translate?hl=en&sl=ru&u=http://blogs.technet.com/abeshkov/archive/2008/12/15/3169299.aspx&ei=FcwwSs_MDsagjAf31YzYBw&sa=X&oi=translate&resnum=1&ct=result&prev=/search%3Fq%3Dhttp://blogs.technet.com/abeshkov/archive/2008/12/15/3169299.aspx%26hl%3Den

By: William

William — Fri, 26 Dec 2008 16:53:51 +0000

Hey, genius, see the western characters on this site? That means we speak english. That link you provided? Yea, that’s not English. How about something in non-Cyrillic characters?

By: Andrey Beshkov

Andrey Beshkov — Tue, 16 Dec 2008 20:28:04 +0000

You can install FreeBSD 6.4, 7.1 RC1, Current 8.0 in Hyper-V. In order to do it you need to apply special patch to kernel. And by the way network card will work with DHCP. Read here how to do it http://blogs.technet.com/abeshkov/archive/2008/12/15/3169299.aspx

By: Doug

Doug — Sat, 30 Aug 2008 01:41:02 +0000

I just finished installing FreeBSD on my system. Here’s how it went.

Couldn’t boot off of 7.0-RELEASE, so I used a 7.0-STABLE snapshot (2008-07). Even after setting up the the legacy network card, it couldn’t see the network, so I had to use the full CD (couldn’t use network install). No network means no package list as well. Otherwise, the install went smoothly.

On boot, the network wasn’t working correctly, and I got no DHCP responses. Static network configuration didn’t work either, and after a while I started getting “buffer full” messages back from ping. I did “ifconfig de0 down;ifconfig de0 up” and suddenly the network started functioning correctly, so I added that to my startup script before the call to dhclient. Unfortunately, it isn’t very long before the network goes down again.

By: Michael Lind Mortensen

Michael Lind Mortensen — Sat, 09 Aug 2008 17:03:22 +0000

Just discovered something kinda funny!

This is what Ziad Elmalki wrote here:
”
Hi,

I tried 7 i386 on lastest hyperv and no go. I get the same error as you. Cannot load kernel. I was gonna try 8 but if no network card then no point I guess I will try virtual pc and see if it works on that. Can’t really dedicate an entire machine to freebsd where I work at
”

The funny part: “Where I work at ” – I just found out Ziad works for Microsoft, he’s Software Development Engineer at Microsoft. Ziad, if you’re reading this, can’t you pull some strings and get native support for FreeBSD on Hyper-V ?

By: Michael Mortensen

Michael Mortensen — Tue, 08 Jul 2008 15:49:32 +0000

Are you using the beta-release or the newly released version? I’m currently using the beta, because I have servers that I can’t just shut down right now, so I have to wait a bit before updating – but if you’ve tried with an updated version and it still doesn’t work, then there’s probably a problem with using that specific FreeBSD version. When I used FreeBSD 8.0 I don’t remember having any of these issues.

By: Alex Labunets

Alex Labunets — Fri, 04 Jul 2008 11:19:08 +0000

Yes, I have the same “Stopping” as you and have no idea how to fix it.

By: Michael Mortensen

Michael Mortensen — Thu, 03 Jul 2008 19:36:53 +0000

Actually the DHCP problem is easy to solve.. Just force the device down “ifconfig de0 down”, then up again “ifconfig de0 up” and then just use dhclient “dhclient de0″. For some non-obvious reason, this works.. while just doing “ifconfig de0 up; dhclient de0″ or “dhclient de0″ does not.

Have any of you run into the problem of FreeBSD virtual machines not shutting down correctly and just stalling on “Stopping” for.. well ever.. until you restart Hyper-V.? I’m afraid to turn off my virtual machines

By: luka manojlovic

luka manojlovic — Wed, 02 Jul 2008 13:39:38 +0000

If you want FreeBSD 7.0 to work you need to use Legacy network adapter – you should first remove the one that Hyper-V wizard adds when you create virtual machine. And somehow FreeBSD does not get IP from your DHCP server – I solved this issue by setting static IP to the FreeBSD. You can check how to do that on my website http://luka.manojlovic.net

By: Alex Labunets

Alex Labunets — Mon, 30 Jun 2008 17:57:13 +0000

Also I have a deeper look at the documentations and VM settings, and it seems to me I have discovered the answer. Emulated “Network Adapter” used by default are also called “synthetic” and it will work ONLY AFTER installing VM Integration Services (which is only available for an officially supported OSes, FreeBSD currently are not in that list and does not have it). So, for us, there is only one chance to have network under FreeBSD is to use “Legacy Network Adapter”. Microsoft also propose to use it if you need a PXE supported network adapter for all officially supported OSes. And MS says that “Legacy Network Adapter” are slower than “synthetic”. I’ve checked this and here the result: “Synthetic NIC” speed is equal to 1Gbps and “Legacy” – 100Mbps.