Configuring VMware Server 2.0
Picking up where we left off, if you selected yes on the previous prompt the installer script will automatically start the vmware-config.pl script
1
2
3
4
5
6
7
8
9
10
11
12
| 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. |
Hit enter to display the EULA, (Hitting the Space Bar will move down to the bottom instead of using the down arrow which goes line by line). Once at the bottom, enter ‘yes’ to accept.
1
2
3
| 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] |
Hit enter to accept the default option ‘yes’ unless you would like to specify a differently.
1
2
3
| 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.28-11-server/build/include] |
Hit enter to accept the default option ‘/lib/modules/2.6.28-11-server/build/include’ unless you would like to specify a different directory.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
| 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.28-11-server/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.28-11-server'
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-headers-2.6.28-11-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] |
Hit enter to accept the default option ‘yes’ unless you would like to specify a differently.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
| 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.28-11-server/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.28-11-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.28-11-server'
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] |
Hit enter to accept the default option ‘yes’ unless you would like to specify a differently.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
| 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.28-11-server/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.28-11-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
/tmp/vmware-config0/vsock-only/linux/util.c: In function ‘VSockVmciLogPkt’:
/tmp/vmware-config0/vsock-only/linux/util.c:157: warning: format not a string literal and no format arguments
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.28-11-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] |
If you get a compile error after step 17, you most likely did not install the patch back on page two before we started the installation. You’ll have to break out of the install here, apply the patch as directed and then restart the vmware-configure.pl script. To verify that it patched and compiled correctly look at line 3 of the previous output. It should see the following,,,
3
4
5
| VMWare config patch VSOCK!
`/tmp/vmware-config0/../Module.symvers' -> `/tmp/vmware-config0/vsock-only/Module.symvers'
Building the vsock module. |
If you patched correctly and did not recieve any compile errors, hit enter to accept the default option ‘yes’ unless you would like to specify a differently.
1
| Do you want networking for your virtual machines? (yes/no/help) [yes] |
Hit enter to accept the default option ‘yes’ unless you would like to specify a differently.
1
2
3
4
| Configuring a bridged network for vmnet0.
Please specify a name for this network.
[Bridged] |
Hit enter to accept the default option ‘Bridged’ unless you would like to specify a differently.
1
2
3
4
5
6
7
8
| 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] |
Hit enter to accept the default option ‘yes’ unless you would like to specify a differently.
1
| Configuring a NAT network for vmnet8.Please specify a name for this network. [NAT] |
Hit enter to accept the default option ‘NAT’ unless you would like to specify a differently.
1
2
| Do you want this program to probe for an unused private subnet? (yes/no/help)
[yes] |
Hit enter to accept the default option ‘yes’ unless you would like to specify a differently.
1
2
3
4
5
6
| 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 NAT networks have been defined:
. vmnet8 is a NAT network on private subnet 192.168.159.0.
Do you wish to configure another NAT network? (yes/no) [no] |
Hit enter to accept the default option ‘no’ unless you would like to specify a differently.
1
2
| Do you want to be able to use host-only networking in your virtual machines?
[yes] |
Hit enter to accept the default option ‘yes’ unless you would like to specify a differently.
1
2
| Configuring a host-only network for vmnet1.Please specify a name for this network.
[HostOnly] |
Hit enter to accept the default option ‘HostOnly’ unless you would like to specify a differently.
1
2
| Do you want this program to probe for an unused private subnet? (yes/no/help)
[yes] |
Hit enter to accept the default option ‘yes’ unless you would like to specify a differently.
1
2
3
4
5
6
7
8
9
| Probing for an unused private subnet (this can take some time)...
The subnet 192.168.84.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.84.0.
Do you wish to configure another host-only network? (yes/no) [no] |
Hit enter to accept the default option ‘no’ unless you would like to specify a differently.
1
2
3
| 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] |
Hit enter to accept the default option ‘yes’ unless you would like to specify a differently.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
| 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.28-11-server/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.28-11-server'
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-headers-2.6.28-11-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] |
Hit enter to accept the default option ’902′ unless you would like to specify a differently.
1
| Please specify a port for standard http connections to use [8222] |
Hit enter to accept the default option ’8222′ unless you would like to specify a differently.
1
| Please specify a port for secure http (https) connections to use [8333] |
Hit enter to accept the default option ’8333′ unless you would like to specify a differently.
1
2
| The current administrative user for VMware Server is ''. Would you like to
specify a different administrator? [no] yes |
Hopefully you are still paying attention at this point, you do not want to say no here as there is no account associated with the VMware Server administrator. You will want to type in ‘yes’ so that we can add an account to become the administrator.
1
2
3
| Please specify the user whom you wish to be the VMware Server administrator
YOUR-USER-NAME-HERE (I used my name scott)
Using scott as the VMware Server administrator. |
1
2
| In which directory do you want to keep your virtual machine files?
[/var/lib/vmware/Virtual Machines] |
By default VMware wants to install to the /var/lib directory. As mentioned earlier it is best to store and run your guests from a separate hard drive from your host operation system to reduce I/O between the host swap and VMware guest swap files. So if you have a separate drive, enter the desired path. But if you have no other choice, hit enter to keep the default datastore on /var/lib/vmware/Virtual Machines. (This can be changed after install, so don’t worry too much if you leave it as default for now)
1
2
3
| 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] |
Depending on the datastore location you use, it may ask you to create the directory if it does not already exist. If it asks, its probably a good idea to accept the default here ‘yes’.
1
2
| Please enter your 20-character serial number.
Type XXXXX-XXXXX-XXXXX-XXXXX or 'Enter' to cancel: |
Enter the serial number from the VMware website where you downloaded the TAR file from in the beginning. It is located near the top of the download page after you have logged in.
1
2
3
4
5
| 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] |
Hit enter to accept the default option ‘/usr/bin’ unless you would like to specify a differently.
1
2
| In which directory do you want to install the VMware VIX API library files?
[/usr/lib/vmware-vix/lib] |
Hit enter to accept the default option ‘/usr/lib/vmware-vix/lib’ unless you would like to specify a differently.
1
2
3
| 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] |
Hit enter to accept the default option ‘yes’ unless you would like to specify a differently.
1
2
| In which directory do you want to install the VMware VIX API document pages?
[/usr/share/doc/vmware-vix] |
Hit enter to accept the default option ‘/usr/share/doc/vmware-vix’ unless you would like to specify a differently.
1
2
3
| 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] |
Hit enter to accept the default option ‘yes’ unless you would like to specify a differently.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
| The installation of VMware VIX API 1.6.2 build-156745 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.1 build-156745 for Linux for this
running kernel completed successfully. |
And we are done! Finally!
So many questions, luckily most of it is all accepting of the already inserted option unless you have a custom installation. At this point you should open a browser and point it to the address http://YOURSERVERIPADDRESS:8222. You’ll notice it will instantly fail to load the page! Don’t worry, it’s just your browser nagging you about the unsigned SSL certificate. You must add a exception to allow your browser to load the certificate.
After adding the exception you should be taken to the login page, use the account information that you entered during the install process. From here you can start to install your Guest operating systems till your eyes bleed!
Shortly I’ll be writing a continuation on VMware Server 2.0 and how to tweak your Host and Guest operating systems to run better. So come back soon and keep an eye out for that as there are quite a few things you can do to improve your Host and Guest performance by eliminating existing bottleneck’s.
Pages: 1 2 3 4
Tags: api howto linux Server ubuntu virtual machine virtualbox vmware
13 Comments
Nice website. I ubuntu and the arras theme. Great Job here. Tks
Perfectly answered questions. Many thanks.
I have now installed Ubuntu 9.04 on my mini-itx box with Vmware 2 up and running. I’m gonna have perhaps 5-6 vms but only 2-3 running at the same time. Mostly for testing before I apply the changes to my real computers.
To get around the problem with Firefox and e-ID, repeatedly getting promted for password, I used the solution commented by Arturo at the bootom of this post:
http://blogger.ziesemer.com/2008/11/vmware-server-20-under-ubuntu-intrepid.html
Again many thanks for all awesome guides!
To answer your first question, there are options you can configure to manipulate the boot order before a vboxheadless vm comes online. So simply choosing a bootable CD at install time will allow you to do what you want in that regards.
As far as choosing which to use, I would determine that by how many VM’s you plan to run? VirtualBox I think is faster “out of the box”, but much more difficult to manage several headless VM’s. Where as VMware Server has a web interface to control everything nicely. However the web interface is on the heavy side if you only have a few VM’s.
Ultimately VirtualBox is ideal for running VM’s on a desktop computer, with the potential for managing them via the command line. But if you have VM’s running on a headless server, it is much easier to manage them via the web interface. I personally use both with this in mind. If it’s something I’m just playing with I use VirtualBox. If it’s something I plan to set and forget, I use my VMware Server.
And yes, it is possible to used a network mounted drive as a datastore for a VM on either of the two. Once again, VMware Server has built in options to achieve this in the webgui. Where as VirtualBox (headless) would be done completely through the command line.
I hope that answers your questions
-Scott