wiki:TipAndDoc/VM/VMware/Server/Lucid/evilninja
  • ~/vmware/vmware-server-distrib$ sudo ./vmware-install.pl
    Creating a new VMware Server installer database using the tar4 format.
    
    Installing VMware Server.
    
    In which directory do you want to install the binary files?
    [/usr/bin]
    
    What is the directory that contains the init directories (rc0.d/ to rc6.d/)?
    [/etc]
    
    What is the directory that contains the init scripts?
    [/etc/init.d]
    
    In which directory do you want to install the daemon files?
    [/usr/sbin]
    
    In which directory do you want to install the library files?
    [/usr/lib/vmware]
    
    The path "/usr/lib/vmware" 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 manual files?
    [/usr/share/man]
    
    In which directory do you want to install the documentation files?
    [/usr/share/doc/vmware]
    
    The path "/usr/share/doc/vmware" 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 Server 2.0.2 build-203138 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.pl".
    
    Before running VMware Server for the first time, you need to configure it by
    invoking the following command: "/usr/bin/vmware-config.pl". Do you want this
    program to invoke the command for you now? [yes]
    
    Making sure services for VMware Server are stopped.
    
    Stopping VMware autostart virtual machines:
       Virtual machines                                                   failed
    Stopping VMware management services:
       VMware Virtual Infrastructure Web Access
       VMware Server Host Agent                                           failed
    Stopping VMware services:
       VMware Authentication Daemon                                        done
       Virtual machine monitor                                             done
    
    You must read and accept the End User License Agreement to continue.
    Press enter to display it.
    
    (snip)
    
    Do you accept? (yes/no) yes
    
    Thank you.
    
    None of the pre-built vmmon modules for VMware Server 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.32-21-server/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.32-21-server/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
    make[1]: Entering directory `/usr/src/linux-headers-2.6.32-21-server'
      CC [M]  /tmp/vmware-config0/vmmon-only/linux/driver.o
    In file included from /tmp/vmware-config0/vmmon-only/./include/vm_asm.h:41,
                     from /tmp/vmware-config0/vmmon-only/linux/driver.c:103:
    /tmp/vmware-config0/vmmon-only/./include/vm_asm_x86_64.h:56:7: warning: "_MSC_VER" is not defined
    In file included from /tmp/vmware-config0/vmmon-only/./include/vm_asm.h:41,
                     from /tmp/vmware-config0/vmmon-only/linux/driver.c:103:
    /tmp/vmware-config0/vmmon-only/./include/vm_asm_x86_64.h:56:7: warning: "_MSC_VER" is not defined
      CC [M]  /tmp/vmware-config0/vmmon-only/linux/driverLog.o
      CC [M]  /tmp/vmware-config0/vmmon-only/linux/hostif.o
    In file included from /tmp/vmware-config0/vmmon-only/./include/vm_asm.h:41,
                     from /tmp/vmware-config0/vmmon-only/linux/hostif.c:66:
    /tmp/vmware-config0/vmmon-only/./include/vm_asm_x86_64.h:56:7: warning: "_MSC_VER" is not defined
    /tmp/vmware-config0/vmmon-only/linux/hostif.c:3601:2: warning: #warning current->cred->fsuid = 0;
    /tmp/vmware-config0/vmmon-only/linux/hostif.c:3608:2: warning: #warning current->cred->fsuid = fsuid;
    /tmp/vmware-config0/vmmon-only/linux/hostif.c:3626:2: warning: #warning cap_lower(current->cred->cap_effective, CAP_SYS_RESOURCE);
    /tmp/vmware-config0/vmmon-only/linux/hostif.c: In function ‘HostIFReadUptimeWork’:
    /tmp/vmware-config0/vmmon-only/linux/hostif.c:1862: warning: ‘newUpBase’ may be used uninitialized in this function
      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/hashFunc.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
    In file included from /tmp/vmware-config0/vmmon-only/./include/vm_asm.h:41,
                     from /tmp/vmware-config0/vmmon-only/common/task.c:50:
    /tmp/vmware-config0/vmmon-only/./include/vm_asm_x86_64.h:56:7: warning: "_MSC_VER" is not defined
      CC [M]  /tmp/vmware-config0/vmmon-only/common/vmx86.o
    In file included from /tmp/vmware-config0/vmmon-only/./include/vm_asm.h:41,
                     from /tmp/vmware-config0/vmmon-only/common/vmx86.c:43:
    /tmp/vmware-config0/vmmon-only/./include/vm_asm_x86_64.h:56:7: warning: "_MSC_VER" is not defined
      CC [M]  /tmp/vmware-config0/vmmon-only/vmcore/moduleloop.o
      LD [M]  /tmp/vmware-config0/vmmon-only/vmmon.o
      Building modules, stage 2.
      MODPOST 1 modules
      CC      /tmp/vmware-config0/vmmon-only/vmmon.mod.o
      LD [M]  /tmp/vmware-config0/vmmon-only/vmmon.ko
    make[1]: Leaving directory `/usr/src/linux-headers-2.6.32-21-server'
    cp -f vmmon.ko ./../vmmon.o
    make: Leaving directory `/tmp/vmware-config0/vmmon-only'
    The vmmon module loads perfectly into the running kernel.
    
    None of the pre-built vmci modules for VMware Server is suitable for your
    running kernel.  Do you want this program to try to build the vmci module for
    your system (you need to have a C compiler installed on your system)? [yes]
    
    Extracting the sources of the vmci module.
    
    Building the vmci module.
    
    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/vmware-config0/vmci-only'
    make -C /lib/modules/2.6.32-21-server/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
    make[1]: Entering directory `/usr/src/linux-headers-2.6.32-21-server'
      CC [M]  /tmp/vmware-config0/vmci-only/linux/driver.o
      CC [M]  /tmp/vmware-config0/vmci-only/linux/driverLog.o
      CC [M]  /tmp/vmware-config0/vmci-only/linux/vmciKernelIf.o
      CC [M]  /tmp/vmware-config0/vmci-only/common/vmciContext.o
      CC [M]  /tmp/vmware-config0/vmci-only/common/vmciDatagram.o
      CC [M]  /tmp/vmware-config0/vmci-only/common/vmciDriver.o
      CC [M]  /tmp/vmware-config0/vmci-only/common/vmciDs.o
      CC [M]  /tmp/vmware-config0/vmci-only/common/vmciEvent.o
      CC [M]  /tmp/vmware-config0/vmci-only/common/vmciGroup.o
      CC [M]  /tmp/vmware-config0/vmci-only/common/vmciHashtable.o
      CC [M]  /tmp/vmware-config0/vmci-only/common/vmciProcess.o
      CC [M]  /tmp/vmware-config0/vmci-only/common/vmciQueuePair.o
      CC [M]  /tmp/vmware-config0/vmci-only/common/vmciResource.o
      LD [M]  /tmp/vmware-config0/vmci-only/vmci.o
      Building modules, stage 2.
      MODPOST 1 modules
      CC      /tmp/vmware-config0/vmci-only/vmci.mod.o
      LD [M]  /tmp/vmware-config0/vmci-only/vmci.ko
    make[1]: Leaving directory `/usr/src/linux-headers-2.6.32-21-server'
    cp -f vmci.ko ./../vmci.o
    make: Leaving directory `/tmp/vmware-config0/vmci-only'
    The vmci module loads perfectly into the running kernel.
    
    VMWare config patch VMCI!
    `/tmp/vmware-config0/vmci-only/Module.symvers' -> `/tmp/vmware-config0/../Module.symvers'
    None of the pre-built vsock modules for VMware Server is suitable for your
    running kernel.  Do you want this program to try to build the vsock module for
    your system (you need to have a C compiler installed on your system)? [yes]
    
    Extracting the sources of the vsock module.
    
    VMWare config patch VSOCK!
    `/tmp/vmware-config0/../Module.symvers' -> `/tmp/vmware-config0/vsock-only/Module.symvers'
    Building the vsock module.
    
    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/vmware-config0/vsock-only'
    make -C /lib/modules/2.6.32-21-server/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
    make[1]: Entering directory `/usr/src/linux-headers-2.6.32-21-server'
      CC [M]  /tmp/vmware-config0/vsock-only/linux/af_vsock.o
      CC [M]  /tmp/vmware-config0/vsock-only/linux/driverLog.o
      CC [M]  /tmp/vmware-config0/vsock-only/linux/util.o
      CC [M]  /tmp/vmware-config0/vsock-only/linux/vsockAddr.o
      LD [M]  /tmp/vmware-config0/vsock-only/vsock.o
      Building modules, stage 2.
      MODPOST 1 modules
      CC      /tmp/vmware-config0/vsock-only/vsock.mod.o
      LD [M]  /tmp/vmware-config0/vsock-only/vsock.ko
    make[1]: Leaving directory `/usr/src/linux-headers-2.6.32-21-server'
    cp -f vsock.ko ./../vsock.o
    make: Leaving directory `/tmp/vmware-config0/vsock-only'
    The vsock module loads perfectly into the running kernel.
    
    Do you want networking for your virtual machines? (yes/no/help) [yes]
    
    Configuring a bridged network for vmnet0.
    
    Please specify a name for this network.
    [Bridged]
    
    The following bridged networks have been defined:
    
    . vmnet0 is bridged to eth0
    
    All your ethernet interfaces are already bridged.
    
    Do you want to be able to use NAT networking in your virtual machines? (yes/no)
    [yes]
    
    Configuring a NAT network for vmnet8.
    
    Please specify a name for this network. [NAT]
    
    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 192.168.70.0/255.255.255.0 appears to be unused.
    
    The following NAT networks have been defined:
    
    . vmnet8 is a NAT network on private subnet 192.168.70.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]
    
    Configuring a host-only network for vmnet1.
    
    Please specify a name for this network.
    [HostOnly]
    
    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 192.168.159.0/255.255.255.0 appears to be unused.
    
    The following host-only networks have been defined:
    
    . vmnet1 is a host-only network on private subnet 192.168.159.0.
    
    Do you wish to configure another host-only network? (yes/no) [no]
    
    None of the pre-built vmnet modules for VMware Server 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]
    
    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.32-21-server/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
    make[1]: Entering directory `/usr/src/linux-headers-2.6.32-21-server'
      CC [M]  /tmp/vmware-config0/vmnet-only/linux/driver.o
      CC [M]  /tmp/vmware-config0/vmnet-only/linux/hub.o
      CC [M]  /tmp/vmware-config0/vmnet-only/linux/userif.o
      CC [M]  /tmp/vmware-config0/vmnet-only/linux/netif.o
      CC [M]  /tmp/vmware-config0/vmnet-only/linux/bridge.o
    /tmp/vmware-config0/vmnet-only/linux/bridge.c:652:2: warning: #warning EHUD gotta figure out what this does and how to fix it: atomic_add(skb->truesize, &sk->sk_wmem_alloc);
      CC [M]  /tmp/vmware-config0/vmnet-only/linux/filter.o
      CC [M]  /tmp/vmware-config0/vmnet-only/linux/procfs.o
      CC [M]  /tmp/vmware-config0/vmnet-only/linux/smac_compat.o
      CC [M]  /tmp/vmware-config0/vmnet-only/linux/smac.o
      CC [M]  /tmp/vmware-config0/vmnet-only/linux/vnetEvent.o
      CC [M]  /tmp/vmware-config0/vmnet-only/linux/vnetUserListener.o
      LD [M]  /tmp/vmware-config0/vmnet-only/vmnet.o
      Building modules, stage 2.
      MODPOST 1 modules
      CC      /tmp/vmware-config0/vmnet-only/vmnet.mod.o
      LD [M]  /tmp/vmware-config0/vmnet-only/vmnet.ko
    make[1]: Leaving directory `/usr/src/linux-headers-2.6.32-21-server'
    cp -f vmnet.ko ./../vmnet.o
    make: Leaving directory `/tmp/vmware-config0/vmnet-only'
    The vmnet module loads perfectly into the running kernel.
    
    Please specify a port for remote connections to use [902]
    
    Please specify a port for standard http connections to use [8222]
    
    Please specify a port for secure http (https) connections to use [8333]
    
    The current administrative user for VMware Server  is ''.  Would you like to
    specify a different administrator? [no] yes
    
    Please specify the user whom you wish to be the VMware Server administrator
     mitty
    
    Using mitty as the VMware Server administrator.
    
    The script you are attempting to invoke has been converted to an Upstart
    job, but lsb-header is not supported for Upstart jobs.
    insserv: warning: script 'hostname' missing LSB tags and overrides
    The script you are attempting to invoke has been converted to an Upstart
    job, but lsb-header is not supported for Upstart jobs.
    insserv: warning: script 'network-interface-security' missing LSB tags and overrides
    The script you are attempting to invoke has been converted to an Upstart
    job, but lsb-header is not supported for Upstart jobs.
    insserv: warning: script 'network-interface' missing LSB tags and overrides
    insserv: warning: current start runlevel(s) (0) of script `halt' overwrites defaults (empty).
    insserv: warning: current start runlevel(s) (0 6) of script `umountnfs.sh' overwrites defaults (empty).
    insserv: warning: current start runlevel(s) (0 6) of script `umountfs' overwrites defaults (empty).
    insserv: warning: current start runlevel(s) (0 6) of script `umountroot' overwrites defaults (empty).
    insserv: warning: current start runlevel(s) (6) of script `reboot' overwrites defaults (empty).
    insserv: warning: current start runlevel(s) (0 6) of script `sendsigs' overwrites defaults (empty).
    The script you are attempting to invoke has been converted to an Upstart
    job, but lsb-header is not supported for Upstart jobs.
    insserv: warning: script 'module-init-tools' missing LSB tags and overrides
    insserv: warning: current start runlevel(s) (0 6) of script `networking' overwrites defaults (empty).
    The script you are attempting to invoke has been converted to an Upstart
    job, but lsb-header is not supported for Upstart jobs.
    insserv: warning: script 'plymouth' missing LSB tags and overrides
    The script you are attempting to invoke has been converted to an Upstart
    job, but lsb-header is not supported for Upstart jobs.
    insserv: warning: script 'plymouth-log' missing LSB tags and overrides
    The script you are attempting to invoke has been converted to an Upstart
    job, but lsb-header is not supported for Upstart jobs.
    insserv: warning: script 'plymouth-splash' missing LSB tags and overrides
    The script you are attempting to invoke has been converted to an Upstart
    job, but lsb-header is not supported for Upstart jobs.
    insserv: warning: script 'plymouth-stop' missing LSB tags and overrides
    The script you are attempting to invoke has been converted to an Upstart
    job, but lsb-header is not supported for Upstart jobs.
    insserv: warning: script 'procps' missing LSB tags and overrides
    The script you are attempting to invoke has been converted to an Upstart
    job, but lsb-header is not supported for Upstart jobs.
    insserv: warning: script 'udev' missing LSB tags and overrides
    The script you are attempting to invoke has been converted to an Upstart
    job, but lsb-header is not supported for Upstart jobs.
    insserv: warning: script 'udev-finish' missing LSB tags and overrides
    The script you are attempting to invoke has been converted to an Upstart
    job, but lsb-header is not supported for Upstart jobs.
    insserv: warning: script 'udevtrigger' missing LSB tags and overrides
    The script you are attempting to invoke has been converted to an Upstart
    job, but lsb-header is not supported for Upstart jobs.
    insserv: warning: script 'udevmonitor' missing LSB tags and overrides
    The script you are attempting to invoke has been converted to an Upstart
    job, but lsb-header is not supported for Upstart jobs.
    insserv: warning: script 'hwclock' missing LSB tags and overrides
    The script you are attempting to invoke has been converted to an Upstart
    job, but lsb-header is not supported for Upstart jobs.
    insserv: warning: script 'hwclock-save' missing LSB tags and overrides
    The script you are attempting to invoke has been converted to an Upstart
    job, but lsb-header is not supported for Upstart jobs.
    insserv: warning: script 'console-setup' missing LSB tags and overrides
    The script you are attempting to invoke has been converted to an Upstart
    job, but lsb-header is not supported for Upstart jobs.
    insserv: warning: script 'cron' missing LSB tags and overrides
    The script you are attempting to invoke has been converted to an Upstart
    job, but lsb-header is not supported for Upstart jobs.
    insserv: warning: script 'rsyslog' missing LSB tags and overrides
    The script you are attempting to invoke has been converted to an Upstart
    job, but lsb-header is not supported for Upstart jobs.
    insserv: warning: script 'dmesg' missing LSB tags and overrides
    The script you are attempting to invoke has been converted to an Upstart
    job, but lsb-header is not supported for Upstart jobs.
    insserv: warning: script 'atd' missing LSB tags and overrides
    The script you are attempting to invoke has been converted to an Upstart
    job, but lsb-header is not supported for Upstart jobs.
    insserv: warning: script 'irqbalance' missing LSB tags and overrides
    The script you are attempting to invoke has been converted to an Upstart
    job, but lsb-header is not supported for Upstart jobs.
    insserv: warning: script 'ufw' missing LSB tags and overrides
    The script you are attempting to invoke has been converted to an Upstart
    job, but lsb-header is not supported for Upstart jobs.
    insserv: warning: script 'apport' missing LSB tags and overrides
    insserv: warning: current start runlevel(s) (0 6) of script `wpa-ifupdown' overwrites defaults (empty).
    insserv: script vmware-core: service VMware already provided!
    insserv: script vmware-mgmt: service VMware already provided!
    insserv: script vmware-autostart: service VMware already provided!
    insserv: There is a loop between service rsyslog and rsyncd if stopped
    insserv:  loop involving service rsyncd at depth 3
    insserv:  loop involving service rsyslog at depth 2
    insserv:  loop involving service udev at depth 1
    insserv: There is a loop between service rsyncd and rsyslog if stopped
    insserv: exiting now without changing boot order!
    In which directory do you want to keep your virtual machine files?
    [/var/lib/vmware/Virtual Machines]
    
    The path "/var/lib/vmware/Virtual Machines" does not exist currently. This
    program is going to create it, including needed parent directories. Is this
    what you want? [yes]
    
    Please enter your 20-character serial number.
    
    Type XXXXX-XXXXX-XXXXX-XXXXX or 'Enter' to cancel:  XXXXX-XXXXX-XXXXX-XXXXX
    
    Creating a new VMware VIX API installer database using the tar4 format.
    
    Installing VMware VIX API.
    
    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]
    
    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]
    
    The installation of VMware VIX API 1.6.2 build-203138 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".
    
    Enjoy,
    
    --the VMware team
    
    Starting VMware services:
       Virtual machine monitor                                             done
       Virtual machine communication interface                             done
       VM communication interface socket family:                           done
       Virtual ethernet                                                    done
       Bridged networking on /dev/vmnet0                                   done
       Host-only networking on /dev/vmnet1 (background)                    done
       DHCP server on /dev/vmnet1                                          done
       Host-only networking on /dev/vmnet8 (background)                    done
       DHCP server on /dev/vmnet8                                          done
       NAT service on /dev/vmnet8                                          done
       VMware Server Authentication Daemon (background)                    done
       Shared Memory Available                                             done
    Starting VMware management services:
       VMware Server Host Agent (background)                               done
       VMware Virtual Infrastructure Web Access
    Starting VMware autostart virtual machines:
       Virtual machines                                                    done
    
    The configuration of VMware Server 2.0.2 build-203138 for Linux for this
    running kernel completed successfully.
    
Last modified 14 years ago Last modified on Jun 8, 2010 10:53:47 AM