|
|
发表于 2005-3-14 08:56:54
|
显示全部楼层
把Mandrakelinux中所有的kernel包安装后就可以了；不知安装那个kernel总之装好了；也运行良好装了win98还装了windwos2000也配置了vmware-tools很正常；关机后重起就不能运行了，提示配置vmware-config.pl
每次重起后就要重新配置vmware-config.pl才能运行。
[root@localhost cyg]# /etc/init.d/vmware start 这样做了也不行
VMware Workstation is installed, but it has not been (correctly) configured
for the running kernel. To (re-)configure it, invoke the
following command: /usr/bin/vmware-config.pl.
以下是配置vmware-config.pl所显示的全部信息；
[root@localhost cyg]# vmware-config.pl
Making sure services for VMware Workstation are stopped.
Stopping VMware services:
Virtual machine monitor [ OK ]
Bridged networking on /dev/vmnet0 [ OK ]
DHCP server on /dev/vmnet1 [ OK ]
SMB share server on /dev/vmnet1 [ OK ]
SMB name server on /dev/vmnet1 [ OK ]
Host-only networking on /dev/vmnet1 [ OK ]
DHCP server on /dev/vmnet2 [ OK ]
NAT service on /dev/vmnet2 [ OK ]
Host-only networking on /dev/vmnet2 [ OK ]
DHCP server on /dev/vmnet3 [ OK ]
NAT service on /dev/vmnet3 [ OK ]
Host-only networking on /dev/vmnet3 [ OK ]
DHCP server on /dev/vmnet4 [ OK ]
NAT service on /dev/vmnet4 [ OK ]
Host-only networking on /dev/vmnet4 [ OK ]
DHCP server on /dev/vmnet8 [ OK ]
NAT service on /dev/vmnet8 [ OK ]
Host-only networking on /dev/vmnet8 [ OK ]
Virtual ethernet [ OK ]
Trying to find a suitable vmmon module for your running kernel.
None of the pre-built vmmon modules for VMware Workstation is suitable for your
running kernel. Do you want this program to try to build the vmmon module for
your system (you need to have a C compiler installed on your system)? [yes]
Using compiler "/usr/bin/gcc". Use environment variable CC to override.
What is the location of the directory of C header files that match your running
kernel? [/lib/modules/2.6.8.1-10mdk/build/include]
Extracting the sources of the vmmon module.
Building the vmmon module.
Using 2.6.x kernel build system.
make: Entering directory `/root/tmp/vmware-config0/vmmon-only'
make -C /lib/modules/2.6.8.1-10mdk/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.8.1-10mdk'
CC [M] /root/tmp/vmware-config0/vmmon-only/linux/driver.o
CC [M] /root/tmp/vmware-config0/vmmon-only/linux/hostif.o
CC [M] /root/tmp/vmware-config0/vmmon-only/common/cpuid.o
CC [M] /root/tmp/vmware-config0/vmmon-only/common/memtrack.o
CC [M] /root/tmp/vmware-config0/vmmon-only/common/phystrack.o
CC [M] /root/tmp/vmware-config0/vmmon-only/common/task.o
CC [M] /root/tmp/vmware-config0/vmmon-only/common/vmx86.o
LD [M] /root/tmp/vmware-config0/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST
CC /root/tmp/vmware-config0/vmmon-only/vmmon.mod.o
LD [M] /root/tmp/vmware-config0/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-2.6.8.1-10mdk'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/root/tmp/vmware-config0/vmmon-only'
The module loads perfectly in the running kernel.
This program previously created the file /dev/vmmon, and was about to remove it.
Somebody else apparently did it already.
This program previously created the file /dev/parport0, and was about to remove
it. Somebody else apparently did it already.
This program previously created the file /dev/parport1, and was about to remove
it. Somebody else apparently did it already.
This program previously created the file /dev/parport2, and was about to remove
it. Somebody else apparently did it already.
This program previously created the file /dev/parport3, and was about to remove
it. Somebody else apparently did it already.
Extracting the sources of the vmnet module.
Building the vmnet module.
Using 2.6.x kernel build system.
make: Entering directory `/root/tmp/vmware-config0/vmnet-only'
make -C /lib/modules/2.6.8.1-10mdk/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.8.1-10mdk'
CC [M] /root/tmp/vmware-config0/vmnet-only/driver.o
CC [M] /root/tmp/vmware-config0/vmnet-only/hub.o
CC [M] /root/tmp/vmware-config0/vmnet-only/userif.o
CC [M] /root/tmp/vmware-config0/vmnet-only/netif.o
CC [M] /root/tmp/vmware-config0/vmnet-only/bridge.o
CC [M] /root/tmp/vmware-config0/vmnet-only/procfs.o
LD [M] /root/tmp/vmware-config0/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST
CC /root/tmp/vmware-config0/vmnet-only/vmnet.mod.o
LD [M] /root/tmp/vmware-config0/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-2.6.8.1-10mdk'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/root/tmp/vmware-config0/vmnet-only'
The module loads perfectly in the running kernel.
This program previously created the file /dev/vmnet0, 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/vmnet2, 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 /dev/vmnet4, and was about to remove
it. Somebody else apparently did it already.
This program previously created the file /dev/vmnet8, and was about to remove
it. Somebody else apparently did it already.
You have already setup networking.
Would you like to skip networking setup and keep your old settings as they are?
(yes/no) [yes]
Do you want this program to automatically configure your system to allow your
virtual machines to access the host's filesystem? (yes/no/help) [yes]
The version of Samba used in this version of VMware Workstation is licensed as
described in the "/usr/share/doc/vmware/SAMBA-LICENSE" file.
Hit enter to continue.
This system appears to have a CIFS/SMB server (Samba) configured for normal use.
If this server is intended to run, you need to make sure that it will not
conflict with the Samba server setup on the private network (the one that we use
to share the host's filesystem). Please check your /etc/samba/smb.conf file so
that:
. The "interfaces" line does not contain "192.168.55.1/255.255.255.0"
. There is a "socket address" line that contains only your real host IP address
Hit enter to continue.
Starting VMware services:
Virtual machine monitor [ OK ]
Virtual ethernet [ OK ]
Bridged networking on /dev/vmnet0 [ OK ]
Host-only networking on /dev/vmnet1 (background) [ OK ]
Host-only networking on /dev/vmnet2 (background) [ OK ]
NAT service on /dev/vmnet2 [ OK ]
Host-only networking on /dev/vmnet3 (background) [ OK ]
NAT service on /dev/vmnet3 [ OK ]
Host-only networking on /dev/vmnet4 (background) [ OK ]
NAT service on /dev/vmnet4 [ OK ]
Host-only networking on /dev/vmnet8 (background) [ OK ]
NAT service on /dev/vmnet8 [ OK ]
You have successfully configured VMware Workstation to allow your virtual
machines to access the host's filesystem. Your system appears to already be set
up with usernames and passwords for accessing the host's filesystem via network
interface vmnet1. Would you like to add another username and password at this
time? (yes/no/help) [no]
You can add more usernames at any time by invoking the following command as
root: "/usr/bin/vmware-smbpasswd vmnet1 -a <username>"
The configuration of VMware Workstation 4.5.2 build-8848 for Linux for this
running kernel completed successfully.
You can now run VMware Workstation by invoking the following command:
"/usr/bin/vmware".
Enjoy,
--the VMware team 到这也配置完成（都是一路回车）
[root@localhost cyg]# vmware 回车也就能正常运行了，之前安装的系统也不能运行，
我是*ly*;
请版主检查一下*ly*这个号不能登入现我又申了一个是*liying* |
|
IP卡
狗仔卡
提升卡
置顶卡
沉默卡
喧嚣卡
变色卡
显身卡