vmware for linux

[root@localhost mycomputer]# cd /
[root@localhost /]# vmware
vmware is installed, but it has not been (correctly) configured
for this system. To (re-)configure it, invoke the following command:
/usr/bin/vmware-config.pl.

[root@localhost /]# /usr/bin/vmware-config.pl
Making sure services for VMware Workstation are stopped.

Stopping VMware services:
   Virtual machine monitor                                 [ OK ]
   Blocking file system:                                   [ OK ]
   Bridged networking on /dev/vmnet0                       [ OK ]
   Host network detection                                  [ OK ]
   DHCP server on /dev/vmnet1                              [ OK ]
   Host-only networking on /dev/vmnet1                     [ OK ]
   DHCP server on /dev/vmnet8                              [ OK ]
   NAT service on /dev/vmnet8                              [ OK ]
   Host-only networking on /dev/vmnet8                     [ OK ]
   Virtual ethernet                                        [ OK ]

Configuring fallback GTK+ 2.4 libraries.

In which directory do you want to install the theme icons?
[/usr/share/icons] /usr/share/icons

What directory contains your desktop menu entry files? These files have a
.desktop file extension. [/mycomputer] /mycomputer

In which directory do you want to install the application's icon?
[/mycomputer] /mycomputer

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.9-5.34DT/build/include] /lib/modules/2.6.9-5.34DT/build/include

Extracting the sources of the vmmon module.

Building the vmmon module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmmon-only'
make -C /lib/modules/2.6.9-5.34DT/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.9-5.34DT-i686'
CC [M] /tmp/vmware-config0/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-config0/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-config0/vmmon-only/common/comport.o
CC [M] /tmp/vmware-config0/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-config0/vmmon-only/common/hash.o
CC [M] /tmp/vmware-config0/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-config0/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-config0/vmmon-only/common/task.o
CC [M] /tmp/vmware-config0/vmmon-only/common/vmciContext.o
CC [M] /tmp/vmware-config0/vmmon-only/common/vmciDatagram.o
CC [M] /tmp/vmware-config0/vmmon-only/common/vmciDriver.o
CC [M] /tmp/vmware-config0/vmmon-only/common/vmciDs.o
CC [M] /tmp/vmware-config0/vmmon-only/common/vmciGroup.o
CC [M] /tmp/vmware-config0/vmmon-only/common/vmciHashtable.o
CC [M] /tmp/vmware-config0/vmmon-only/common/vmciProcess.o
CC [M] /tmp/vmware-config0/vmmon-only/common/vmciResource.o
CC [M] /tmp/vmware-config0/vmmon-only/common/vmciSharedMem.o
CC [M] /tmp/vmware-config0/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-config0/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/vmware-config0/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST
CC      /tmp/vmware-config0/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-config0/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.9-5.34DT-i686'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config0/vmmon-only'
The module loads perfectly in the running kernel.

Extracting the sources of the vmblock module.

Building the vmblock module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmblock-only'
make -C /lib/modules/2.6.9-5.34DT/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.9-5.34DT-i686'
CC [M] /tmp/vmware-config0/vmblock-only/linux/block.o
CC [M] /tmp/vmware-config0/vmblock-only/linux/control.o
CC [M] /tmp/vmware-config0/vmblock-only/linux/dbllnklst.o
CC [M] /tmp/vmware-config0/vmblock-only/linux/dentry.o
CC [M] /tmp/vmware-config0/vmblock-only/linux/file.o
CC [M] /tmp/vmware-config0/vmblock-only/linux/filesystem.o
CC [M] /tmp/vmware-config0/vmblock-only/linux/inode.o
CC [M] /tmp/vmware-config0/vmblock-only/linux/module.o
CC [M] /tmp/vmware-config0/vmblock-only/linux/stubs.o
CC [M] /tmp/vmware-config0/vmblock-only/linux/super.o
LD [M] /tmp/vmware-config0/vmblock-only/vmblock.o
Building modules, stage 2.
MODPOST
CC      /tmp/vmware-config0/vmblock-only/vmblock.mod.o
LD [M] /tmp/vmware-config0/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.9-5.34DT-i686'
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/vmware-config0/vmblock-only'
The module loads perfectly in the running kernel.

You have already setup networking.

Would you like to skip networking setup and keep your old settings as they are?
(yes/no) [yes]

Extracting the sources of the vmnet module.

Building the vmnet module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmnet-only'
make -C /lib/modules/2.6.9-5.34DT/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.9-5.34DT-i686'
CC [M] /tmp/vmware-config0/vmnet-only/driver.o
CC [M] /tmp/vmware-config0/vmnet-only/hub.o
CC [M] /tmp/vmware-config0/vmnet-only/userif.o
CC [M] /tmp/vmware-config0/vmnet-only/netif.o
CC [M] /tmp/vmware-config0/vmnet-only/bridge.o
CC [M] /tmp/vmware-config0/vmnet-only/filter.o
CC [M] /tmp/vmware-config0/vmnet-only/procfs.o
CC [M] /tmp/vmware-config0/vmnet-only/smac_compat.o
SHIPPED /tmp/vmware-config0/vmnet-only/smac_linux.x386.o
LD [M] /tmp/vmware-config0/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST
CC      /tmp/vmware-config0/vmnet-only/vmnet.mod.o
LD [M] /tmp/vmware-config0/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.9-5.34DT-i686'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-config0/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]

A previous installation of VMware VIX API has been detected.

The previous installation was made by the tar installer (version 4).

Keeping the tar4 installer database format.

Uninstalling the tar installation of VMware VIX API.

The removal of VMware VIX API 1.1.0 build-45731 for Linux completed
successfully. Thank you for having tried this software.

Installing VMware VIX API. This may take from several minutes to over an hour
depending upon its size.

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.

SDK 4.05.07



Do you accept? (yes/no) yes

Thank you.

In which directory do you want to install the VMware VIX API binary files?
[/usr/bin] /usr/bin

In which directory do you want to install the VMware VIX API library files?
[/usr/lib/vmware-vix/lib] /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]

In which directory do you want to install the VMware VIX API document pages?
[/usr/share/doc/vmware-vix] /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]


The installation of VMware VIX API 1.1.0 build-45731 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                                 [ OK ]
   Blocking file system:                                   [ OK ]
   Virtual ethernet                                        [ OK ]
   Bridged networking on /dev/vmnet0                       [ OK ]
   Host network detection                                  [ OK ]
   Host-only networking on /dev/vmnet1 (background)        [ OK ]
   DHCP server on /dev/vmnet1                              [ OK ]
   Host-only networking on /dev/vmnet8 (background)        [ OK ]
   DHCP server on /dev/vmnet8                              [ OK ]
   NAT service on /dev/vmnet8                              [ OK ]

The configuration of VMware Workstation 6.0.0 build-45731 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 /]#vmware
WC5FW-V0CFX-4804A-4WTNL

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/12592/viewspace-163542/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/12592/viewspace-163542/