关于Citrix公司的XenServer免费使用,个人理解,虽然为免费版本,但为了方便管理, 以及获取用户的相关信息,Citrix采用了Free License管理的模式,在到期后,用户只需要再次重复申请新的License文件并进行License安装即可.不会影响XenServer的正常使 用.但是,Citrix公司并未发表声明永久性提供免费使用,至少我没有找到.特别在正式的生产环境,还是建议大家购买正式的服务,以提供更高的性能以及安全的合法的保障.

转载自：http://hi.baidu.com/ts%B4%F3%D1%BC%C0%E6/blog/item/c58976fb885250809f514653%2Ehtml

A上的操作192.168.1.2
yum -y install nfs*
yum -y install portmap
mkdir /data/nfs
chmod 777 /data/nfs
允许192.168.1.0/24网段的计算机挂载/home/nfs
echo '/data/nfs 192.168.1.*(rw,root_squash)' >> /etc/exports
service portmap start
service nfs start

XenServer主机1上操作
mkdir /data/export
mount -t nfs 192.168.1.2:/data/nfs /data/export

开始导出
先把要导出的vm关掉，然后查看要导出vm的UUID
xe vm-list params=all

xe vm-export filename=/data/export/017-otrs.xva vm=09faa5ff-ceea-1234-e02e-97cae69878d5

XenServer主机2上操作
mkdir /data/export
mount -t nfs 192.168.1.2:/data/nfs /data/export

xe vm-import filename=/data/nfs/017-otrs.xva

等一下就可以了

我vm分了30G的空间，导出来的文件大概7G，应该也就是vm实际存储的文件大小吧

参考文章：http://tiri.li/schneller-xen-vm-import-auch-via-befehlszeile

停止 xinetd：[  确定  ]
启动 xinetd：[  确定  ]
Stopping VMware services:
Virtual machine monitor[  确定  ]
Bridged networking on /dev/vmnet0[  确定  ]
DHCP server on /dev/vmnet8[  确定  ]
NAT service on /dev/vmnet8[  确定  ]
Host-only networking on /dev/vmnet8[  确定  ]
Virtual ethernet[  确定  ]

File /etc/vmware/config is backed up to /etc/vmware/config.old.0.

This program previously created the file /dev/vmnet5, and was about to remove
it.  Somebody else apparently did it already.

This program previously created the file /dev/vmnet2, and was about to remove
it.  Somebody else apparently did it already.

This program previously created the file /dev/vmnet4, and was about to remove
it.  Somebody else apparently did it already.

This program previously created the file /dev/vmnet1, and was about to remove
it.  Somebody else apparently did it already.

This program previously created the file /dev/vmnet7, and was about to remove
it.  Somebody else apparently did it already.

This program previously created the file /dev/vmnet9, and was about to remove
it.  Somebody else apparently did it already.

This program previously created the file /dev/vmnet6, and was about to remove
it.  Somebody else apparently did it already.

This program previously created the file /dev/vmnet3, and was about to remove
it.  Somebody else apparently did it already.

This program previously created the file /etc/vmware/not_configured, and was
about to remove it.  Somebody else apparently did it already.

This program previously created the file /etc/pam.d/vmware-authd, and was about
to remove it.  Somebody else apparently did it already.

This program previously created the directory /var/log/vmware, and was about to
remove it. Since there are files in that directory that this program did not
create, it will not be removed.

This program previously created the directory /var/run/vmware, and was about to
remove it. Since there are files in that directory that this program did not
create, it will not be removed.

This program previously created the directory /etc/vmware, and was about to
remove it. Since there are files in that directory that this program did not
create, it will not be removed.

The removal of VMware Server 1.0.6 build-91891 for Linux completed
successfully. Thank you for having tried this software.

2、我还真的不知道VMware自带NAT的转发功能，我原来是打算把宿主系统和虚拟系统用Host only连接，然后用iptables把访问特定端口的服务转发到虚拟系统上。但因为数据一直出不去，Google了一些资料，发现VMware有NAT转发功能，才决定用NAT方式连接。

NAT的设置和转发设置均在这里/etc/vmware/vmnet8/nat/nat.conf
这个文件是只读的，为了编辑，可以chmod +w /etc/vmware/vmnet8/nat/nat.conf
也可以在编辑完成后用:wq!来强行写入。

不过，网上有文章说VMware的NAT转发不是很稳定。

Unfortunately, VMware Server on Linux currently lacks a user friendly equivalent of the Windows Manage Virtual Networks tool, instead requiring the manual editing of the /etc/vmware/vmnet8/nat/nat.conf file (keeping in mind that the vmnet8 name will need to be changed if the settings are to be configured for a custom created virtual network).
The nat.conf file contains a number of different sections, each allowing a different aspect of the NAT device to be configured:
[host]
ip - The IP address of the NAT device on the virtual network. By default this will be <xxx>.2 where the <xxx> is the subnet address assigned to the virtual network (for example, 172.16.86.2).
netmask - The subnet mask to be used for the NAT device.
configport - The port to be used for accessing information about the NAT device. By default this directive is commented out with a # character for security purposes and is supposedly only for use by VMware Inc's technical support staff.
device - The VMnet virtual network switch to which the NAT device is attached.
activeFTP - A value of 1 indicates that active FTP sessions (i.e connections initiated by remote FTP servers) are supported. A setting of 0 limits connections to passive sessions.
[udp]
timeout - The amount of time, in seconds, to keep UDP mapping for the NAT device. This is essentially the amount of time for which the NAT device remembers which virtual machine initiated a specific UDP based connection with an external system. If the external system responds after the timeout period has elapsed, the NAT will no longer know to which virtual machine the data should be forwarded, and the UDP packet will be discarded.
[incomingtcp]
The [incomingtcp] section of the nat.conf file is used to configure TCP port forwarding. This essentially involves mapping an incoming TCP port on the host to the IP address and TCP port of a virtual machine. For example, to map data coming into TCP port 8080 on the host to port 80 on a virtual machine with an IP address of 172.16.86.128, the following directive would need to be entered into the [incomingtcp] section of the configuration file:
8080 = 172.16.86.128:80
As many TCP port forwarding directives as necessary may added to this section of the NAT configuration file.
[incomingudp]
The [incomingudp] section of the nat.conf file is used to configure UDP port forwarding. Similar to the [incomingtcp]] section, this essentially involves mapping an incoming UDP port on the host to the IP address and UDP port of a virtual machine. For example, to map data coming into UDP port 8081 on the host to port 8082 on a virtual machine with an IP address of 172.16.86.128, the following directive would need to be entered into the [incomingudp] section of the configuration file:
8081 = 172.16.86.128:8082
As many port UDP forwarding directives as necessary may added to this section of the NAT configuration file.

主要参考文章：http://www.virtuatopia.com/index.php/VMware_Server_NAT_Configuration#Configuring_NAT_on_Linux_Hosts

因为上面有运行一个2003系统，正在破解一个rar文件的密码，不能重启，想到如果把esxi的物理网卡地址改成跟虚拟机的网卡不同网段，是否依然会产生风暴呢？我打开显示器，把IP地址设置为10.1.2.22，连接到路由器2上，同时，本地计算机也连到路由器2，连接上后，本地网卡显示流量依然为几百K每秒，无法用infrastructure client连接服务器端。既然连接到路由器上不可以，那就试下host to host把，真是天助我也，服务器连路由器的线是交叉线，连做线都省了，本机和服务器连起来后，一切正常，也可以用infrastructure client连接，马上把装了panabit的机器关掉，重新将本机和服务器连接到路由器1，哈哈，可以用Remote Desktop连接2003，看来物理网卡的IP网管跟虚拟机的网卡网段是没有关联的，即使不在同一网段，不影响本机对虚拟机的访问，只是不能用infrastructure client管理esxi了，因为物理网卡的地址依然是10.1.2.22，重新回到显示器前，这下好了，Configure Management Network那个不能用了，按ESC、ENTER也没有用，幸好昨天查如何开启ESXi的SSH时知道如何进命令行模式，进入后，以为在/etc/sysconfig/下会有类似于eth0,eth1之类的文件，结果发现没有，整个磁盘都差不多找遍了，都没有，幸好网上找到这篇文章:

更改esx console的物理IP地址及esx console命令

http://aiirii.spaces.live.com/blog/cns!E59E9AB7297384A7!692.entry?sa=578345425

但上面所写的命令，在esxi 3.5 update 2上已经不适用了，在/sbin下主要有如下的命令
~ # cd /sbin
/sbin # ls esxcfg*
esxcfg-advcfg     esxcfg-init-eesx  esxcfg-nas        esxcfg-swiscsi
esxcfg-dhcp       esxcfg-locker     esxcfg-nics       esxcfg-vmhbadevs
esxcfg-dumppart   esxcfg-loglevel   esxcfg-rescan     esxcfg-vmknic
esxcfg-hwiscsi    esxcfg-module     esxcfg-resgrp     esxcfg-vswitch
esxcfg-info       esxcfg-mpath      esxcfg-route

查看vmknic信息
/sbin # esxcfg-vmknic -l
Interface  Port Group          IP Address      Netmask         Broadcast       MAC Address       MTU     TSO MSS   Enabled
vmk4       Management Network  192.168.100.120 255.255.255.0   192.168.100.255 00:1e:c9:ff:3c:cd 1500    40960     true

修改vmknic的IP地址等
/sbin # esxcfg-vmknic -i 192.168.100.120 -n 255.255.255.0 "Management Network"

修改网关
/sbin # esxcfg-route 192.168.100.1

修改马上生效，不用重启network

以上各命令均可加-h参数显示帮助信息，另外说下查看物理网卡信息的命令
/sbin # esxcfg-nics -l
Name    PCI      Driver      Link Speed    Duplex MTU    Description
vmnic1  05:00.00 tg3         Down 0Mbps    Half   1500   Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet
vmnic0  04:00.00 tg3         Up   100Mbps  Full   1500   Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet

经过以上设置，可以用infrastructure client连接了。

copy以上介绍那篇文章的内容：

今天安装了另外一台esx 3.5 测试，安装完成后，发觉设置错了网段，本来想用修改linux网卡Ｉｐ的方法操作，后来，上网找了下，有专用的命令可用，很简单，如下：
列出当前网卡信息
esxcfg-vswif -l

删除原来的配置vswif0, 没有修改的命令，该文件应该在：/etc/sysconfig/network-scripts/ifcfg-vswif0
esxcfg-vswif -d vswif0

新增配置
esxcfg-vswif -a vswif0 -p "Service Console" -i 172.28.2.2 -n 255.255.255.0 -b 172.28.2.255
（也可使用-i命令直接修改，没测试过）

检查修改后配置是否正确
esxcfg-vswif -l

修改原来hosts的IP, 及网关
vi /etc/hosts
vi /etc/sysconfig/network

附：vmware esx 上的命令行

http://leesun.blog.51cto.com/58664/60092

esx上特有的命令很多，有些是很方便，就用这个来记录我平时在esx上用到的命令
1：看你的esx版本。
vmware -v
2：列出esx里知道的服务
esxcfg-firewall -s
3：查看具体服务的情况
esxcfg-firewall -q sshclinet
4：重新启动vmware服务
service mgmt-vmware restart
5: 修改root的密码
passwd root
6：列出你当前的虚拟交换机
esxcfg-vswitch -l
7：查看控制台的设置
esxcfg-vswif -l
8：列出系统的网卡
esxcfg-nics -l
9：添加一个虚拟交换机，名字叫（internal）连接到两块物理网卡，（重新启动服务，vi就能看见了）
esxcfg-vswitch -a vSwitch1
esxcfg-vswitch -A internal vSwitch1
esxcfg-vswitch -L vmnic1 vSwitch1
esxcfg-vswitch -L vmnic2 vSwitch1
10：删除交换机,(注意，别把控制台的交换机也删了）
esxcfg-vswitch -D vSwitch1
11：删除交换机上的网卡
esxcfg-vswitch -u vmnic1 vswitch2
12：删除portgroup
esxcfg-vswitch -D internel vswitch1
13：创建 vmkernel switch ，如果你希望使用vmotion，iscsi的这些功能，你必须创建( 通常是不需要添加网关的）
esxcfg-vswitch -l
esxcfg-vswitch -a vswitch2
esxcfg-vswitch -A "vm kernel" vswitch2
esxcfg-vswitch -L vmnic3 vswitch2
esxcfg-vmknic -a "vm kernel" -i 172.16.1.141 -n 255.255.252.0
esxcfg-route 172.16.0.254
14：打开防火墙ssh端口
esxcfg-firewall -e sshclient
esxcfg-firewall -d sshclient
15: 创建控制台
esxcfg-vswitch -a vSwitch0
esxcfg-vswitch -A "service console" vSwitch0
esxcfg-vswitch -L vmnic0 vSwitch0
esxcfg-vswif -a vswif0 -p "service console" -i 172.16.1.140 -n 255.255.252.0
16: 添加nas设备(a 添加标签，-o，是nas服务器的名字或ip，-s 是nas输入的共享名字）
esxcfg-nas -a isos -o nas.vmwar.cn -s isos
17：列出nas连接
esxcfg-nas -l
18: 强迫esx去连接nas服务器(用esxcfg-nas -l 来看看结果）
esxcfg-nas -r
esxcfg-nas -l
19：连接iscsi 设备(e:enable q:查询 d：disable s:强迫搜索）
esxcfg-swiscsi -e
20：设置targetip
vmkiscsi-tool -D -a 172.16.1.133 vmhba40
21：列出和target的连接
vmkiscsi-tool -l -T vmhba40
22：列出当前的磁盘
ls -l /vmfs/devices/disks

http://itil.org.cn/thread-1336-1-1.html
There are two ways you can change the IP address:
From the VI Client
Or, from the Physcial Console Connection
See the following sections for details on each method.

From the VI Client

Using the Virtual Infrastructure Client, the DNS information (Configuration tab > DNS and Routing) can be changed on the fly. Similarly, the gateway address (routing subtab of the DNS and Routing window) and the hostname (DNS Configuration subtab of DNS and Routing) can be changed through the user interface. Hostname and domain changes through the VI Client do not take place until the ESX host is rebooted.

From the Physical Console Connection

Changing the IP for the service console must be done from a physical console connection, either at the host, through a KVM or other remote console connection. If you make changes through a network connection such as SSH, network connectivity to the service console will disconnect because the service console's network interface will change.
For this example, it is assumed that vswif0 is the service console adapter that is the interface to which to apply the IP address change. Running the command

esxcfg-vswif -i x.x.x.x vswif0

will set the IP address to the value substituted for x.x.x.x in the command. You will need to edit the /etc/hosts file and change it so that it reflects the new IP address in use for the service console.
The gateway address and hostname are in /etc/sysconfig/network.

After you edit these files, you must reboot the host or restart the network service using the following command:

service network restart

Note: This command breaks any current network connections to the service console.

You can also dynamically change the host name using the command:

hostname newname

Note: This command creates a temporary host name change. This change is lost when the system is rebooted.

To change the DNS server settings, edit the /etc/resolv.conf file and update the nameserver IPs and search domain if applicable.

一、服务启动、关闭等,跟普通服务的启动一样
/etc/init.d/vmware {start|stop|status|restart}

如果启动正常，用status参数查看，则应该会有如下信息：
[root@vmware svn.abc.net]# /etc/init.d/vmware status
At least one instance of VMware Server is still running.

Bridged networking on /dev/vmnet0 is running
Host-only networking on /dev/vmnet8 is running
NAT networking on /dev/vmnet8 is running
Module vmmon loaded
Module vmnet loaded

查看进程 ps aux | grep vmware,信息如下：

root      4623  0.0  0.0  1636  328 ?        Ss   09:43   0:00 /usr/bin/vmnet-natd -d /var/run/vmnet-natd-8.pid -m /var/run/vmnet-natd-8.mac -c /etc/vmware/vmnet8/nat/nat.conf
root      4629  0.0  0.3 17380 14692 ?       Ss   09:43   0:02 /usr/sbin/vmware-serverd -s -d
root      4653  0.0  0.0  1640  220 ?        Ss   09:43   0:00 /usr/bin/vmnet-dhcpd -cf /etc/vmware/vmnet8/dhcpd/dhcpd.conf -lf /etc/vmware/vmnet8/dhcpd/dhcpd.leases -pf /var/run/vmnet-dhcpd-vmnet8.pid vmnet8
root      4919  5.1 28.2 1277260 1172768 ?   S<sl 09:55   7:43 /usr/lib/vmware/bin/vmware-vmx -C /vmware/vmware/Windows.2003/Windows Server 2003 Enterprise Edition.vmx -@ ""
root      5669 13.6  5.6 362908 234864 ?     S<sl 11:04  11:16 /usr/lib/vmware/bin/vmware-vmx -C /vmware/vmware/svn.abc.net/Red Hat Enterprise Linux 4.vmx -@ ""
root      5686  1.1  0.0     0    0 ?        S<   11:04   0:57 [vmware-rtc]
root      5767  0.0  0.0  4872  648 pts/1    S+   12:26   0:00 grep vmware

二、命令行启动虚拟机
vmrun命令参数：
[root@vmware svn.abc.net]# vmrun --help
Invalid switch -help
vmrun version 1.0.6 build-91891

Usage: vmrun [Authentication flags] COMMAND [PARAMETERS]

Authentication flags
-h <hostName>
-P <hostPort>
-u <userName>
-p <password>

COMMAND          PARAMETERS                  DESCRIPTION
list                                         List all running VMs
start            Path to vmx file            Start a VM
stop             Path to vmx file            Stop a VM
reset            Path to vmx file            Reset a VM
suspend          Path to vmx file            Suspend a VM
upgradevm        Path to vmx file            Upgrade VM file format, virtual hw
installtools     Path to vmx file            Install Tools in Guest OS
snapshot         Path to vmx file            Create a snapshot of a VM
deleteSnapshot   Path to vmx file            Remove a snapshot from a VM
revertToSnapshot Path to vmx file            Set VM state to a snapshot

Examples:
vmrun list
vmrun upgradevm w2k.vmx

因为新建虚拟机时，vmware新建的机器名默认是有空格的，不过不要紧，系统会自动在空格前添加转移字符:\，如下

vmrun start /vmware/wmware/Red\ Hat\ Enterprise\ Linux\ 4.vmx

Vmware-server 安装过程问题

今天安装VMware-server-1.0.3遇到不少问题,让我熟悉了”目标主机积极拒绝,无法连接”,以前安装读非常顺利,今天就这么特别,KAO.
这次用的centos5 X64位的系统,可能的因素应该就是他,安装过程提示xinetd未安装,那我就
yum install xinetd
安装嘛.安装好后再次安装vmware,到最后出现
Starting VMware services:
Virtual machine monitor
done
Virtual ethernet done
Bridged networking on /dev/vmnet0
done
Host-only networking on /dev/vmnet1 (background) done
Bridged
networking on /dev/vmnet2 done
Host-only networking on /dev/vmnet8
(background) done
NAT service on /dev/vmnet8 done
Virtual ethernet
failed
经过网上查呀查,发现是vmware-player 服务引起的,并在/etc/vmware/目录下产生了not_configured文件,
具体地址是:http://www.debuntu.org/vmware-server-not-starting-after-reboot
按照这方法操作完,reboot,无效.他NND,邪门了真是.因为以前32位的系统安装都没问题的,所以就去32位的系统上查查了,费了9牛2虎之力,终于发现现在的机器缺少一个vmnet的模块,如
[root@localhost ~]# lsmod|grep vmnet
# vmnet                 106288  13
难道是这模块没有编译通过?把32位系统的vmnet.ko复制到64位系统上加载此模块,失败.郁闷了..
执行vmware-uninstall.pl
把vmware卸了先,重新安装,这次/lib/modules/2.6.18-8.el5/misc终于看见vmnet.ko
vmnet.o两个文件了,安装完毕,启动服务过程先前的问题消失.
新的问题来鸟,ifconfig能看到启动的vmnet1和vmnet8设备,用VMware-console却连接不上…
telnet IP xinetd_port(telnet 125.65.110.121
904)
能连接,出现
220 VMware Authentication Daemon Version 1.10: SSL Required,
MKSDisplayProtocol:
VNC
说明vmware服务对外对了,怎么VMware-console就是出现”目标主机积极拒绝,无法连接”
再一次进32位的系统,检查他的xinetd分配给vmware端口居然是902,现在装的杂就变成904了呢….
2话不说,将现在的机器xinetd分配给vmware端口改为902
vi /etc/xinetd.d/vmware-authd
# default: on
# # description: The VMware remote access authentification daemon
# service vmware-authd
# {
#     disable         = no
#     port            = 902
#     socket_type     = stream
#     protocol        = tcp
#     wait            = no
#     user            = root
#     server          = /usr/sbin/vmware-authd
#     type            = unlisted
# }
重新启动xinetd,
oh….能连接了.

转载的：本文来自ChinaUnix博客，如果查看原文请点：http://blog.chinaunix.net/u/31547/showart_1082299.html

虚拟机<--->互联网通信的方法。
顺便写了下如何不重新编译整个内核支持某个功能,对系统无影响,编译速度要快于编译整个内核。
如果你的XXX卡没被内核支持,又怕自己编译的内核会造成系统损坏就可以试试这个方法喽

^_^

vmware三种网络连接上网设置：

1.bridge :
默认使用vmnet0
将虚拟机的ip设置与主机同网段未使用ip,其余与主机相同:
例如主机ip是10.70.54.31,设置虚拟机ip为10.70.54.22。netmask,broadcast,gateway,dns都与主机相同即可实现虚拟机<--->主机

虚拟机<---->互联网 通信。

2.nat

:
默认使用vmnet8
将虚拟机设置成使用dhcp方式上网,windows下选择"自动获取ip",linux下开启dhcp服务即可
也可以手动设置:
ip设置与vmnet8同网段,gateway设置成vmnet8的gateway(/etc/vmware/vmnet8/nat/nat.conf)中可以查到vmnet8的gateway,通常是xxx.xxx.xxx.2。
netmask,broadcast设置与vmnet8相同,dns设置与主机相同。
例如

vmnet8 ip:172.16.249.1 gw :172.16.249.2
虚拟机设置: ip :172.16.249.100  gw:

172.16.249.2

3.host-only

:
默认使用vmnet1

将虚拟机ip设置与vmnet1同网段,gateway设置成vmnet1的ip,其余设置与vmnet1相同,dns设置与主机相同
例如

vmnet1 ip :172.16.245.1
虚拟机设置: ip :172.16.245.100 gateway :172.16.245.1

这样就实现了虚拟机<--->主机 通信,但是 虚拟机<--->互联网 仍无法通信

虚拟机与互联网通信：
1.开启主机路由功能
2.设定iptables，使主机成为一台nat server
1. echo 1 >/proc/sys/net/ipv4/ip_forward

这样就主机就具有了路由功能
2. iptables -t nat

-A POSTROUTING -o eth0 -s 172.16.245.0/24 -j

MASQUERADE
这条规则意思是将来自172.16.245.0/24封包的来源ip伪装成eth0的ip，实现虚拟机与互联网通信
如果网络接口是ppp+或pppoe则需要修改成-o

pppoe
当然-s  172.16.245.0/24 也要根据实际情况修改

qemu两种上网方式：

user mode network

:
这种方式实现虚拟机上网很简单，类似vmware里的nat，qemu启动时加入-user-net参数，虚拟机里使用dhcp方式，即可与互联网通信，但是这种方式虚拟机与主机的通信不方便。

tap/tun network :
这种方式要比user

mode复杂一些，但是设置好后 虚拟机<-->互联网 虚拟机<-->主机 通信都很容易

这种方式设置上类似vmware的host-only,qemu使用tun/tap设备在主机上增加一块虚拟网络设备(tun0),然后就可以象真实网卡一样配置它.

首先内核中支持tap/tuns设备：
Device Drivers

--->
Networking support  --->
[M] Universal TUN/TAP

device driver support
如果当前内核没有支持，可以重新只编译相应模块加入，方法很简单：

将当前内核配置文件cp到内核源码目录下:
[root@LFS

~]#cp /boot/config-[kernel-version]

/usr/src/linux
[root@LFS ~]#cd

/usr/src/linux
配置内核，将TUN/TAP选择模块(M)，如上所示:
[root@LFS ~]#make menuconfig
重新只编译模块(M),不编译核心(*)支持的东东:
[root@LFS ~]#make

modules
编译好后在/usr/src/linux/drivers/net下可以找到tun.ko:
[root@LFS

net]#ls -l

/usr/src/linux/drivers/net/tun.ko
-rw-r--r--  1 root root 11116 Mar 23

20:29 /usr/src/linux/drivers/net/tun.ko
[root@LFS

net]#
将它cp到当前内核的模块目录的相应位置：
[root@LFS net]#cp /usr/src/linux/drivers/net/tun.ko

/lib/modules/`uname -r`/kernel/drivers/net
重新建立模块依赖关系：
[root@LFS

net]#depmod
现在就可以加载它了

:
[root@LFS net]#modprobe

tun
检查一下：
[root@LFS net]#lsmod

|grep tun
tun                     8704  0
[root@LFS net]#
OK. 成功不重新编译整个内核加入特殊模块支持

如果你的xx卡不被内核支持，又可以编译成模块，自己怕重新编译内核后出问题就可以用这个办法只编译自己需要的模块，然后手动安装到相应位置，再加载它。
这样编译速度要也比编译整个内核快，不会对系统有任何损害，就可以使用上XX卡喽。^_^

要注意三点：
1.内核源码必须与当前内核版本完全一致，否则编译出的模块是不能用的。
2.注意只make modules(编译模块),没有make

modules_install(自动安装模块到/lib/modules下)
3.加载新编译的模块前必须先运行depmod，否则modprobe找不到它

其实使用当前内核配置文件(/boot/config-[kernel-version]),只加入自己需要的模块，不做任何其他改，make

modules_install应该也不会有问题的。
不过最稳妥的办法还是手动安装它,控制权在自己手里更踏实嘛

:-)

OK,转回qemu上网问题 :)

如果使用udev管理设备(通常2.6.x内核的发行版都已经使用udev),当modprobe

tun后就会自动建立/dev/net目录，并创建出tun设备，做好相关链接：
[root@LFS net]#ls -l /dev/net/tun
lrwxrwxrwx  1 root

root 6 Mar 25 15:35 /dev/net/tun -> ../tun
[root@LFS

net]#

如果很不幸，你没看到它，就需要自己手动做这些工作了 :(
[root@LFS ~]#mkdir /dev/net
[root@LFS ~]#mknod /dev/net/tun c 10

200
OK,相关设备已经准备好了，还需要一个tun/tap的初始化脚本 :
/etc/qemu-ifup

:
#!/bin/sh
/sbin/ifconfig $1 172.20.0.1
再给予qemu-ifup

x执行权限放在/etc下就可以了。
这个脚本只能root用户执行，如果需要普通用户使用qemu，就需要改成sudo /sbin/ifconfig

.....再设置sudo相关权限。
启动qemu后，它会在主机上增加一块虚拟网络设备(tun0):
[root@LFS

~]#ifconfig tun0
tun0      Link

encap:Ethernet  HWaddr 0A:D3:8A:5D:97:CD
inet addr:172.20.0.1 Bcast:172.20.255.255 Mask:255.255.0.0
UP BROADCAST

RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0

dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0

overruns:0 carrier:0
collisions:0 txqueuelen:500
RX

bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
[root@LFS

~]#
现在就可以启动qemu配置虚拟机网络参数了，和vmware host-only一样:
ip与tun0相同网段,gateway为tun0 ip

其余参数与tun0相同,dns与主机相同：
tun0 : ip

:172.20.0.1 broadcast:172.20.255.255 netmask :255.255.0.0
qemu :

ip :172.20.0.100

broadcast:172.20.255.255 netmask :255.255.0.0 gateway:172.20.0.1

与host-only一样，这样只实现了虚拟机<---->主机间通信,还需要设置router,nat才可以连上互联网

[root@LFS ~]#echo 1 >

/proc/sys/net/ipv4/ip_forward
[root@LFS ~]#iptables -t nat -A POSTROUTING -o eth0 -s

172.20.0.0/24 -j MASQUERADE
[root@LFS ~]#

OK，虚拟机<--->主机

虚拟机<---->互联网通信 都完成啦
快去做网络实验吧 ^_^

转载自：http://www.vmware.cn/Article/376.html