我用Microsoft Hyper-V安装了FreeBSD9.0

star_in_sky

虚拟机真是个好东西 部门内部有一台HP Server（1U），上面安装了Win2008，配置了Microsoft Hyper-V；安装了两台Win2003的虚拟机，作为部门内部的开发测试平台（WEB+DB）。

嘻嘻，我偷偷的在Hyper-V中又安装了FreeBSD9.0，作为一个学习平台。Microsoft的虚拟机非常不错，FreeBSD已经顺利的运行起来了。
现在发现有三个问题
1）因为驱动的原因，FreeBSD只能用Hyper-V的老式虚拟的网卡，导致远程登录速度比较慢。好消息是，Microsoft很快就会在Hyper-V中增加对FreeBSD的支持。
2）开机不能够自动用dhclient抓取IP地址；必须手动的运行dhclient命令才行。
3）我不能通过GDM远程登录FreeBSD的图形终端；后来改用KDM就可以。

下面是两个截图

ulovko

感谢分享 赞！ ^_^

enous

不错哈。。。。。。顶你一下。

oily1314

要想开机自动dhclient，就在/etc/rc.conf添加

1. background_dhclient="YES"

复制代码

star_in_sky

回复 4# oily1314


    谢谢楼上的各位。

不过这样的方法也无法自动抓取IP地址，原因还是因为Hyper-V的网卡对于FreeBSD来说不太兼容。

有个老外和我遇见的问题一样。
http://cncc.bingj.com/cache.aspx ... h-CN&w=8e4166db,1f5409a7

FreeBSD under Hyper-V
OK.  I'm playing with FreeBSD 8.0 under Hyper-V R2.  I looked at FreeBSD 7.0 under Hyper-V R1 about this time last year and without a kernel patch, it had issues shutting down (and starting, and running...).  Well, the shutdown bug and the starting bug and all others seem to have been addressed fully aside from one slight networking issue.  So here's the lowdown on this one remaining issue...

As there's no synthetic network adapter driver for the "good" NIC in Hyper-V for FreeBSD (nor OpenBSD nor Linux), then you need to use the "bad" NIC - the Legacy Network Adapter.  The issue with this is that it is slow - only 100 Mbps.  Under FreeBSD it is detected as a "de" NIC - the first one being "de0".

You can either configure this during the initial setup of FreeBSD using sysinstall, or by manually editing the /etc/rc.conf file and adding ifconfig_de0="DHCP" to that file.

There seems to be an issue with the way Microsoft built this adapter as under FreeBSD it doesn't properly obtain a DHCP-assigned address no matter where the DHCP server is - on a Windows box, a *nix box or a firewall/router/modem device.  Real, physical "de" NICs work fine.  At least there's a workaround that allows the DHCP-assigned address to work - you need to stop, start and re-acquire the DHCP-assigned address by running:

ifconfig de0 down
ifconfig de0 up
dhclient de0

Now, you can run this manually every time after you reboot the box, however that means that the box is offline until you log into it using Hyper-V Manager.  A better way to handle this is to create an /etc/rc.local file, add these commands to it, then chmod 755 /etc/rc.local to make it an executable file for root.

Obviously, once this has been done, a portsnap fetch then portsnap extract is a good idea.  (Or whatever way you want to keep your FreeBSD ports up to date.)  And then installing any updated portss that are available using ports, portmanager or portupgrade or whatever method floats your boat.

Regards,

The Outspoken Wookie

chysk

楼主所说的前面两个问题我昨天安装freebsd 10.0时都遇到了。
在hyper-v中，默认使用“网络适配器”，在freebsd中运行ifconfig根本就看不到网卡；使用“旧版网络适配器”才可以识别到网卡（de0）；
但是在安装过程中不能自动获取到IP地址，启动后也是不能获取到，当时ping 127.0.0.1，判断网卡工作正常，只是没有获取IP。
今天早晨搜索到这篇文件，得到印证，尝试用dhclient命令，可以顺利获取到IP。
准备按照老外的方法，以在启动时可以自动获取IP地址。

chysk

刚刚试过了，把下面三条命令做成一个文件/ect/rc.loca
ifconfig de0 down
ifconfig de0 up
dhclient de0
再执行下面的命令，即可让系统在启动时获取到IP地址，确实有效。
chmod 755 /etc/rc.local

beyondfly

还可以这么玩，学习了

shang2010

linux才是未来，