Slackerbox

Kali ini tentang VMware server 2.0 di Slackware 12.1 :)
Tertarik install gara2 ingin tau (bukan yg muluk2) file VMware sebesar hampir 534MB itu isinya apa saja yach ? Bandingkan dengan virtualbox yg gak lebih dari 35 MB.

Baiklah, sebelum download, Anda musti register dulu di http://vmware.com. Celakanya, dowload pake wget gak bisa :P Jadi musti download pakai browser standart.

Karena proses otorisasi login ke VMware server 2.0 nantinya pake pam, maka mesti install paket pam dulu. Untuk mudahnya, download dari http://linuxpackages.net paket linux-pam.

http://www.linuxpackages.net/search_view.php?by=name&name=linux-pam&ver=...

# installpkg linux-pam-*.tgz

Kalau sudah register, cari paket 'For Linux' dan pilih format TAR Image.

The core application needed to run VMware Server 2.
Version 2.0.0 | 116503 - 09/23/08

.................................................Menunggu berapa jam nich ?

Ekstrak file VMware-server-2.0.0-116503.i386.tar.gz

#tar -xvvzf VMware-server-2.0.0-116503.i386.tar.gz

Masuk ke folder hasil ekstrak :

#cd vmware-server-distrib

Install :

#./vmware-install.pl

Baiklah, sebelum proses yg bertele2, setelah selesai, edit file /etc/pam.d/vmware-authd dan ubah path pam jadi seperti dibawah ini:

#%PAM-1.0
auth required /usr/lib/pam/pam_unix.so shadow nullok
account required /usr/lib/pam/pam_unix.so


Jangan lupa save file :P

Ubah ke mode init slackware
lihat : http://slackware.linux.or.id/wiki/index.php/Installasi_VMWare_di_Slackware

cp /etc/init.d/vmware /etc/rc.d/rc.vmware
chmod +x /etc/rc.d/rc.vmware
rm /etc/init.d -r


Edit /etc/rc.local dan tambahkan :

if [ -x /etc/rc.d/rc.vmware ]; then
/etc/rc.d/rc.vmware start
fi

Oke, restart sistem Anda supaya module pam aktif. Kemudian coba browse http://localhost:8222
Jangan kuatir,VMware server 2.0 sudah include apache tomcat jadi tidak perlu mengaktifkan apache default slackware.

Untuk login, gunakan username root dan password root sistem Anda.

Semoga bermanfaat :)

Salam.

..................................................Kalau ingin tau proses instalasi...Kebanyakan ENTER saja kok :P

Proses :

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/rc.d]
..........................
What is the directory that contains the init scripts?
[/etc/rc.d/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.0 build-116503 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 [ OK ]
Virtual machine monitor [ OK ]
.............................
You must read and accept the End User License Agreement to continue.
Press enter to display it.
............................................................................
bla..bla..bla....VMware Server is intended for your personal
non-commercial use only. If you are interested in distributing the
Software for internal or external use, promotion, review or as part of a
solution, please apply now at http://www.vmware.com/go/distribution.
............................................................................
Do you accept? (yes/no)
.............................
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/ygycc". 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.5-smp/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.24.5-smp/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.24.5'
CC [M] /tmp/vmware-config0/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-config0/vmmon-only/linux/driverLog.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/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
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 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-2.6.24.5'
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.24.5-smp/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.24.5'
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-2.6.24.5'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-config0/vmci-only'
The vmci module loads perfectly into the running kernel.
................................................................................
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.
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.24.5-smp/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.24.5'
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
WARNING: "VMCIDatagram_CreateHnd" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIDatagram_DestroyHnd" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCI_GetContextID" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIDatagram_Send" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
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-2.6.24.5'
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.28.0/255.255.255.0 appears to be unused.
This system appears to have a DHCP server configured for normal use. Beware
that you should teach it how not to interfere with VMware Server's DHCP server.
There are two ways to do this:
1) Modify the file /etc/dhcpd.conf to add something like:
subnet 192.168.28.0 netmask 255.255.255.0 {# Note: No range is given, vmnet-dhcpd will deal with this subnet.}
2) Start your DHCP server with an explicit list of network interfaces to deal
with (leaving out vmnet8). e.g.:
dhcpd eth0
Consult the dhcpd(8) and dhcpd.conf(5) manual pages for details.
Hit enter to continue.
................................................................................
The following NAT networks have been defined:
. vmnet8 is a NAT network on private subnet 192.168.28.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.153.0/255.255.255.0 appears to be unused.
................................................................................
This system appears to have a DHCP server configured for normal use. Beware
that you should teach it how not to interfere with VMware Server's DHCP server.
There are two ways to do this:
1) Modify the file /etc/dhcpd.conf to add something like:
subnet 192.168.153.0 netmask 255.255.255.0 {
# Note: No range is given, vmnet-dhcpd will deal with this subnet.
}
2) Start your DHCP server with an explicit list of network interfaces to deal
with (leaving out vmnet1). e.g.:
dhcpd eth0
Consult the dhcpd(8) and dhcpd.conf(5) manual pages for details.
Hit enter to continue.
................................................................................
The following host-only networks have been defined:
. vmnet1 is a host-only network on private subnet 192.168.153.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.24.5-smp/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.24.5'
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
CC [M] /tmp/vmware-config0/vmnet-only/smac.o
CC [M] /tmp/vmware-config0/vmnet-only/vnetEvent.o
CC [M] /tmp/vmware-config0/vmnet-only/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-2.6.24.5'
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]
.................................................................................
Using root as the VMware Server administrator.
.................................................................................
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 MMMM-MMMM-MMMM-MMMM or 'Enter' to cancel:
.................................................................................
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.0 build-116503 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 [ OK ]
Virtual machine communication interface [ OK ]
VM communication interface socket family: [ OK ]
Virtual ethernet [ OK ]
Bridged networking on /dev/vmnet0 [ 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 ]
VMware Server Authentication Daemon (background) [ OK ]
Shared Memory Available [ OK ]
Starting VMware management services:
VMware Server Host Agent (background) [ OK ]
VMware Virtual Infrastructure Web Access
Starting VMware autostart virtual machines:
Virtual machines [ OK ]
The configuration of VMware Server 2.0.0 build-116503 for Linux for this
running kernel completed successfully.
.................................................................................