重新卸载,开始:
jyfish@jyfish-laptop:~/download/vmware-any-any-update116$ sudo ./
runme.pl
Updating /usr/bin/vmware ... No patch needed/available
Updating /usr/bin/vmnet-bridge ... No patch needed/available
Updating /usr/lib/vmware/bin/vmware-vmx ... No patch needed/available
Updating /usr/lib/vmware/bin-debug/vmware-vmx ... No patch needed/
available
VMware modules in "/usr/lib/vmware/modules/source" has been updated.
Before running VMware for the first time after update, you need to
configure it
for your running kernel by invoking the following command:
"/usr/bin/
vmware-config.pl". Do you want this script to invoke the
command for
you now? [no] yes
Making sure services for VMware Workstation are stopped.
Stopping VMware services:
Virtual machine monitor
done
Configuring fallback GTK+ 2.4 libraries.
In which directory do you want to install the theme icons?
[/usr/share/icons]
What directory contains your desktop menu entry files? These files
have a
.desktop file extension. [/usr/share/applications]
In which directory do you want to install the application's icon?
[/usr/share/pixmaps]
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] 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.24-20-generic/build/include]
Extracting the sources of the vmmon module.
Building the vmmon module.
Unknown VMware Workstation 6.0.3 build 80004 detected. Building for
Workstation 6.0.0.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config6/vmmon-only'
make -C /lib/modules/2.6.24-20-generic/build/include/.. SUBDIRS=$PWD
SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.24-20-generic'
CC [M] /tmp/vmware-config6/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-config6/vmmon-only/linux/driverLog.o
CC [M] /tmp/vmware-config6/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-config6/vmmon-only/common/comport.o
CC [M] /tmp/vmware-config6/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-config6/vmmon-only/common/hash.o
CC [M] /tmp/vmware-config6/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-config6/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-config6/vmmon-only/common/task.o
cc1plus: 警告: 命令行选项“-Werror-implicit-function-declaration”对 C/ObjC 是有效的,
但对 C++ 无效
cc1plus: 警告: 命令行选项“-Wdeclaration-after-statement”对 C/ObjC 是有效的,但对 C++ 无
效
cc1plus: 警告: 命令行选项“-Wno-pointer-sign”对 C/ObjC 是有效的,但对 C++ 无效
cc1plus: 警告: 命令行选项“-Wstrict-prototypes”对 Ada/C/ObjC 是有效的,但对 C++ 无效
cc1plus: 警告: 命令行选项“-ffreestanding”对 C/ObjC 是有效的,但对 C++ 无效
In file included from /tmp/vmware-config6/vmmon-only/common/task.c:
1194:
/tmp/vmware-config6/vmmon-only/common/task_compat.h: In function ‘int
Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage =
VMCrossPageV321]’:
/tmp/vmware-config6/vmmon-only/common/task_compat.h:2491: 警告: 此函数中
的‘sysenterState.SysenterStateV45::rsp’在使用前未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::rsp’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h:2492: 警告: 此函数中
的‘sysenterState.SysenterStateV45::rip’在使用前未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::rip’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 警告: 此函数中
的‘sysenterState.SysenterStateV45::validEIP’在使用前可能未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::validEIP’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 警告: 此函数中
的‘sysenterState.SysenterStateV45::cs’在使用前可能未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::cs’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h: In function ‘int
Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage =
VMCrossPageV3]’:
/tmp/vmware-config6/vmmon-only/common/task_compat.h:2491: 警告: 此函数中
的‘sysenterState.SysenterStateV45::rsp’在使用前未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::rsp’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h:2492: 警告: 此函数中
的‘sysenterState.SysenterStateV45::rip’在使用前未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::rip’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 警告: 此函数中
的‘sysenterState.SysenterStateV45::validEIP’在使用前可能未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::validEIP’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 警告: 此函数中
的‘sysenterState.SysenterStateV45::cs’在使用前可能未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::cs’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h: In function ‘int
Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage =
VMCrossPageGSX1]’:
/tmp/vmware-config6/vmmon-only/common/task_compat.h:2491: 警告: 此函数中
的‘sysenterState.SysenterStateV45::rsp’在使用前未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::rsp’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h:2492: 警告: 此函数中
的‘sysenterState.SysenterStateV45::rip’在使用前未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::rip’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 警告: 此函数中
的‘sysenterState.SysenterStateV45::validEIP’在使用前可能未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::validEIP’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 警告: 此函数中
的‘sysenterState.SysenterStateV45::cs’在使用前可能未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::cs’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h: In function ‘int
Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage =
VMCrossPageV2]’:
/tmp/vmware-config6/vmmon-only/common/task_compat.h:2491: 警告: 此函数中
的‘sysenterState.SysenterStateV45::rsp’在使用前未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::rsp’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h:2492: 警告: 此函数中
的‘sysenterState.SysenterStateV45::rip’在使用前未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::rip’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 警告: 此函数中
的‘sysenterState.SysenterStateV45::validEIP’在使用前可能未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::validEIP’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 警告: 此函数中
的‘sysenterState.SysenterStateV45::cs’在使用前可能未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::cs’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h: In function ‘int
Vmx86_RunVM_V4(VMDriver*, Vcpuid) [with VMCrossPage = VMCrossPageV4]’:
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 警告: 此函数中
的‘sysenterState.SysenterStateV45::validEIP’在使用前可能未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::validEIP’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 警告: 此函数中
的‘sysenterState.SysenterStateV45::cs’在使用前可能未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::cs’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 警告: 此函数中
的‘sysenterState.SysenterStateV45::rsp’在使用前可能未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::rsp’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 警告: 此函数中
的‘sysenterState.SysenterStateV45::rip’在使用前可能未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::rip’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h: In function ‘int
Vmx86_RunVM(VMDriver*, Vcpuid)’:
/tmp/vmware-config6/vmmon-only/common/task_compat.h:2491: 警告: 此函数中
的‘sysenterState.SysenterStateV45::rsp’在使用前未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::rsp’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h:2492: 警告: 此函数中
的‘sysenterState.SysenterStateV45::rip’在使用前未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::rip’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 警告: 此函数中
的‘sysenterState.SysenterStateV45::validEIP’在使用前可能未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::validEIP’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 警告: 此函数中
的‘sysenterState.SysenterStateV45::cs’在使用前可能未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::cs’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 警告: 此函数中
的‘sysenterState.SysenterStateV45::validEIP’在使用前可能未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::validEIP’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 警告: 此函数中
的‘sysenterState.SysenterStateV45::cs’在使用前可能未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::cs’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 警告: 此函数中
的‘sysenterState.SysenterStateV45::rsp’在使用前可能未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::rsp’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 警告: 此函数中
的‘sysenterState.SysenterStateV45::rip’在使用前可能未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::rip’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 警告: 此函数中
的‘sysenterState.SysenterStateV45::validEIP’在使用前可能未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::validEIP’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 警告: 此函数中
的‘sysenterState.SysenterStateV45::cs’在使用前可能未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::cs’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 警告: 此函数中
的‘sysenterState.SysenterStateV45::rsp’在使用前可能未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::rsp’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 警告: 此函数中
的‘sysenterState.SysenterStateV45::rip’在使用前可能未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:3028: 附注:
‘sysenterState.SysenterStateV45::rip’的上一个声明在此
/tmp/vmware-config6/vmmon-only/common/task_compat.h: In function ‘void
Task_Switch_V45(VMDriver*, Vcpuid)’:
/tmp/vmware-config6/vmmon-only/common/task_compat.h:2666: 警告: 此函数中
的‘sysenterState.SysenterStateV45::validEIP’在使用前可能未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:2666: 警告: 此函数中
的‘sysenterState.SysenterStateV45::cs’在使用前可能未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:2666: 警告: 此函数中
的‘sysenterState.SysenterStateV45::rsp’在使用前可能未初始化
/tmp/vmware-config6/vmmon-only/common/task_compat.h:2666: 警告: 此函数中
的‘sysenterState.SysenterStateV45::rip’在使用前可能未初始化
CC [M] /tmp/vmware-config6/vmmon-only/common/vmciContext.o
CC [M] /tmp/vmware-config6/vmmon-only/common/vmciDatagram.o
CC [M] /tmp/vmware-config6/vmmon-only/common/vmciDriver.o
CC [M] /tmp/vmware-config6/vmmon-only/common/vmciDs.o
CC [M] /tmp/vmware-config6/vmmon-only/common/vmciGroup.o
CC [M] /tmp/vmware-config6/vmmon-only/common/vmciHashtable.o
CC [M] /tmp/vmware-config6/vmmon-only/common/vmciProcess.o
CC [M] /tmp/vmware-config6/vmmon-only/common/vmciResource.o
CC [M] /tmp/vmware-config6/vmmon-only/common/vmciSharedMem.o
CC [M] /tmp/vmware-config6/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-config6/vmmon-only/vmcore/compat.o
CC [M] /tmp/vmware-config6/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/vmware-config6/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config6/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-config6/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.24-20-generic'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config6/vmmon-only'
The module loads perfectly in the running kernel.
/dev is dynamic:
Trying to find a suitable vmblock module for your running kernel.
None of the pre-built vmblock modules for VMware Workstation is
suitable for
your running kernel. Do you want this program to try to build the
vmblock
module for your system (you need to have a C compiler installed on
your
system)? [yes] yes
Extracting the sources of the vmblock module.
Building the vmblock module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config6/vmblock-only'
make -C /lib/modules/2.6.24-20-generic/build/include/.. SUBDIRS=$PWD
SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.24-20-generic'
CC [M] /tmp/vmware-config6/vmblock-only/linux/block.o
CC [M] /tmp/vmware-config6/vmblock-only/linux/control.o
CC [M] /tmp/vmware-config6/vmblock-only/linux/dbllnklst.o
CC [M] /tmp/vmware-config6/vmblock-only/linux/dentry.o
CC [M] /tmp/vmware-config6/vmblock-only/linux/file.o
CC [M] /tmp/vmware-config6/vmblock-only/linux/filesystem.o
CC [M] /tmp/vmware-config6/vmblock-only/linux/inode.o
CC [M] /tmp/vmware-config6/vmblock-only/linux/module.o
CC [M] /tmp/vmware-config6/vmblock-only/linux/stubs.o
CC [M] /tmp/vmware-config6/vmblock-only/linux/super.o
LD [M] /tmp/vmware-config6/vmblock-only/vmblock.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config6/vmblock-only/vmblock.mod.o
LD [M] /tmp/vmware-config6/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.24-20-generic'
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/vmware-config6/vmblock-only'
The module loads perfectly in the running kernel.
/dev is dynamic:
Do you want networking for your virtual machines? (yes/no/help) [yes]
yes
Configuring a bridged network for vmnet0.
Your computer has multiple ethernet network interfaces available:
eth0,
eth0:avahi, wlan0. Which one do you want to bridge to vmnet0? [eth0]
The following bridged networks have been defined:
. vmnet0 is bridged to eth0
Do you wish to configure another bridged network? (yes/no) [no] yes
Configuring a bridged network for vmnet2.
Your computer has multiple ethernet network interfaces available:
eth0:avahi,
wlan0. Which one do you want to bridge to vmnet2? [eth0]
The ethernet device "eth0" is already configured as a bridged device.
Your computer has multiple ethernet network interfaces available:
eth0:avahi,
wlan0. Which one do you want to bridge to vmnet2? [eth0]
The ethernet device "eth0" is already configured as a bridged device.
Your computer has multiple ethernet network interfaces available:
eth0:avahi,
wlan0. Which one do you want to bridge to vmnet2? [eth0] eth1
The ethernet device "eth1" was not detected on your system. Available
ethernet
devices detected on your system include eth0:avahi, wlan0. Are you
sure you
want to use this device? (yes/no) [no] no
Your computer has multiple ethernet network interfaces available:
eth0:avahi,
wlan0. Which one do you want to bridge to vmnet2? [eth0] eth1
The ethernet device "eth1" was not detected on your system. Available
ethernet
devices detected on your system include eth0:avahi, wlan0. Are you
sure you
want to use this device? (yes/no) [no] yes
The following bridged networks have been defined:
. vmnet0 is bridged to eth0
. vmnet2 is bridged to eth1
Do you wish to configure another bridged network? (yes/no) [no] no
Do you want to be able to use NAT networking in your virtual machines?
(yes/no)
[yes] yes
Configuring a NAT network for vmnet8.
Do you want this program to probe for an unused private subnet? (yes/
no/help)
[yes]
Probing for an unused private subnet (this can take some time)...
The subnet
172.16.127.0/255.255.255.0 appears to be unused.
The following NAT networks have been defined:
. vmnet8 is a NAT network on private subnet 172.16.127.0.
Do you wish to configure another NAT network? (yes/no) [no]
Do you want to be able to use host-only networking in your virtual
machines?
[yes] no
Trying to find a suitable vmnet module for your running kernel.
None of the pre-built vmnet modules for VMware Workstation is suitable
for your
running kernel. Do you want this program to try to build the vmnet
module for
your system (you need to have a C compiler installed on your system)?
[yes] yes
Extracting the sources of the vmnet module.
Building the vmnet module.
Unknown VMware Workstation 6.0.3 build 80004 detected. Building for
Workstation 6.0.0.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config6/vmnet-only'
make -C /lib/modules/2.6.24-20-generic/build/include/.. SUBDIRS=$PWD
SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.24-20-generic'
CC [M] /tmp/vmware-config6/vmnet-only/driver.o
CC [M] /tmp/vmware-config6/vmnet-only/hub.o
CC [M] /tmp/vmware-config6/vmnet-only/userif.o
CC [M] /tmp/vmware-config6/vmnet-only/netif.o
CC [M] /tmp/vmware-config6/vmnet-only/bridge.o
CC [M] /tmp/vmware-config6/vmnet-only/filter.o
CC [M] /tmp/vmware-config6/vmnet-only/procfs.o
CC [M] /tmp/vmware-config6/vmnet-only/smac_compat.o
CC [M] /tmp/vmware-config6/vmnet-only/smac_linux.x386.o
LD [M] /tmp/vmware-config6/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config6/vmnet-only/vmnet.mod.o
LD [M] /tmp/vmware-config6/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.24-20-generic'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-config6/vmnet-only'
The module loads perfectly in the running kernel.
Do you want to install the Eclipse Integrated Virtual Debugger? You
must have
the Eclipse IDE installed. [no]
Creating a new VMware VIX API installer database using the tar4
format.
Installing VMware VIX API.
You must read and accept the VMware VIX API End User License Agreement
to
continue.
Press enter to display it.
-----------------------------
VMware(R) Software Developer Kit (SDK) Agreement
VMware, Inc. ("VMware") provides this Software Developer Kit ("SDK")
for VIX
Application Programming Interface ("VIX API") to you subject to the
following terms and conditions. If you disagree with any of the
following
terms, then do not use this SDK.
1. This SDK contains a variety of materials, including but not
limited to,
interface definitions, documentation, Redistributable Code and Sample
Code
regarding programming interfaces to one or more VMware products as
referenced in such materials ("VMware Software"). This SDK is
intended to
serve as a guide for writing programs to interact with the VMware
Software.
For the purpose of this Agreement, "Sample Code" means sample software
in
source code format designated as "Sample Code" in the SDK
documentation, and
"Redistributable Code" means object code files designated as
"Redistributable Code" in the SDK documentation.
2. Subject to the restrictions below, you may download and make a
reasonable number of copies of the SDK contents for your personal use
solely
for the purpose of creating software that communicates with VMware
Software
("Developer Software"). You agree to defend, indemnify and hold
harmless
VMware, and any of its directors, officers, employees, affiliates or
agents,
from and against any and all claims, losses, damages, liabilities and
other
expenses (including reasonable attorneys' fees), arising from your
modification and distribution of the Sample Code, distribution of
Redistributable Code or breach of this SDK Terms and Conditions.
3. Restrictions: You may create and distribute Developer Software
based on
the Sample Code and Redistributable Code, provided that (1) you do not
use
the SDK to design or develop anything other than Developer Software;
(2) you
do not modify, create derivative works of, reverse engineer, reverse
compile, or disassemble the Redistribution Code, except that you may
modify
and create derivative works of the Sample Code in connection with
Developer
Software; (3) you distribute the Redistributable Code in object code
form
only and solely in conjunction with, and as part of your Developer
Software;
(4) you do not make any more copies of the SDK than are reasonably
necessary
for the authorized use and backup and archival purposes; (5) you do
not
permit further distribution of the SDK by your end users; (6) you do
not
permit sub-licensees or end users to reverse engineer or reverse
compile the
Redistributable Code; and (7) you do not use the SDK to design or
develop
software to upload or otherwise transmit any material containing
software
viruses or other computer code, files or programs designed to
interrupt,
destroy, or limit the functionality of any software or hardware.
4. VMware retains ownership of the SDK, including without limitation
all
copyrights and other intellectual property rights therein.
5. For open source software components included with the SDK, you are
subject to the terms of those applicable open source license
agreements.
The open source software licenses can be found in the
open_source_licenses.txt file, other materials accompanying the SDK,
the
documentation or corresponding source files available at
http://www.vmware.com/download/open_source.html.
6. You may not represent that the programs you develop using the SDK
are
certified or otherwise endorsed by VMware. You may not use the VMware
name
or any other trademarks or service marks of VMware in connection with
programs that you develop using the SDK.
7. You will not receive any VMware support or subscription services
for the
SDK or any other services from VMware in connection with the SDK. If
you
have purchased support and/or subscription services for a VMware
product,
such support and/or subscription services shall not apply to the SDK
or your
use of the SDK.
8. Term, Termination and Changes: This Agreement shall continue as
long as
you are in compliance with the terms specified herein or until
otherwise
terminated. You and or VMware each may terminate this Agreement for
any
reason at any time. You agree, upon termination, to destroy all
copies of
the SDK within your possession or control. The Confidential
Information,
Limitations of Warranties, Liability and Indemnification sections set
out in
this Agreement shall survive any termination or expiration of this
Agreement.
9. Limitations of Warranties and Liability: THE SDK IS PROVIDED "AS
IS"
WITHOUT ANY WARRANTIES OF ANY KIND. TO THE MAXIMUM EXTENT PERMITTED
BY
APPLICABLE LAW, VMWARE DISCLAIMS ANY IMPLIED WARRANTIES, INCLUDING,
WITHOUT
LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE AND NON-INFRINGEMENT OF INTELLECTUAL PROPERTY
RIGHTS.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT WILL
VMWARE
BE LIABLE FOR ANY LOST PROFITS OR BUSINESS OPPORTUNITIES, LOSS OF USE,
BUSINESS INTERRUPTION, LOSS OF DATA, OR ANY OTHER INDIRECT, SPECIAL,
INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE SDK OR YOUR
USE OF
THE SDK, UNDER ANY THEORY OF LIABILITY, WHETHER BASED IN CONTRACT,
TORT,
NEGLIGENCE, PRODUCT LIABILITY, OR OTHERWISE. BECAUSE SOME
JURISDICTIONS DO
NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL
OR
INCIDENTAL DAMAGES, THE PRECEDING LIMITATION MAY NOT APPLY TO YOU.
VMWARE'S LIABILITY ARISING OUT OF THE SDK PROVIDED HEREUNDER WILL NOT,
IN
ANY EVENT, EXCEED US$5.00.
THE FOREGOING LIMITATIONS SHALL APPLY TO THE MAXIMUM EXTENT PERMITTED
BY
APPLICABLE LAW, REGARDLESS OF WHETHER VMWARE HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES AND REGARDLESS OF WHETHER ANY REMEDY FAILS
OF
ITS ESSENTIAL PURPOSE.
10. These terms are governed by the laws of the State of California
and the
United States of America without regard to conflict of laws
principles. You
may not assign any part of this Agreement without the prior written
consent
of VMware. Any attempted assignment without consent shall be void.
These
terms constitute the entire agreement between you and VMware with
respect to
the SDK, and supersede all prior written or oral communications,
understandings and agreements. Any waiver of these terms must be in
writing
to be effective. If any provision of these terms is found to be
invalid or
unenforceable, the remaining terms will continue to be valid and
enforceable
to the fullest extent permitted by law.
Do you accept? (yes/no) yes
Thank you.
In which directory do you want to install the VMware VIX API binary
files?
[/usr/bin]
In which directory do you want to install the VMware VIX API library
files?
[/usr/lib/vmware-vix/lib]
The path "/usr/lib/vmware-vix/lib" does not exist currently. This
program is
going to create it, including needed parent directories. Is this what
you want?
[yes] yes
In which directory do you want to install the VMware VIX API document
pages?
[/usr/share/doc/vmware-vix]
The path "/usr/share/doc/vmware-vix" does not exist currently. This
program is
going to create it, including needed parent directories. Is this what
you want?
[yes] yes
The installation of VMware VIX API 1.1.3 build-80004 for Linux
completed
successfully. You can decide to remove this software from your system
at any
time by invoking the following command: "/usr/bin/vmware-uninstall-
vix.pl".
Starting VMware services:
Virtual machine monitor
done
Blocking file system:
done
Virtual ethernet
done
Bridged networking on /dev/vmnet0
done
Host network detection
done
Bridged networking on /dev/vmnet2
done
Host-only networking on /dev/vmnet8 (background)
done
DHCP server on /dev/vmnet8
done
NAT service on /dev/vmnet8
done
The configuration of VMware Workstation 6.0.3 build-80004 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
完成了 哈哈哈哈!!谢谢josh!