How To Install VMware Server 1.0.x On A Kubuntu 10.04 Desktop

Version 1.0
Author: Pierino, la peste!!! <mum_laris*AT*yahoo [dot] com> http://utenti.multimania.it/Pierino_lapeste/
Last edited 05/17/2010

Update of: http://www.howtoforge.com/how-to-install-vmware-server-1.0.x-on-an-ubuntu-9.10-desktop

This tutorial provides step-by-step instructions on how to install VMware Server 1.0.x (1.0.10 at the time of this writing) on a Kubuntu 10.04 desktop system. This is for those who prefer VMware Server 1.0.x over VMware Server 2.

With VMware Server you can create and run guest operating systems ("virtual machines") such as Linux, Windows, FreeBSD, etc. under a host operating system. This has the benefit that you can run multiple operating systems on the same hardware which saves a lot of money, and you can move virtual machines from one VMware Server to the next one (or to a system that has the VMware Player which is also free).

Also, with VMware Server you can let your old Windows desktop (that you previously converted into a VMware virtual machine with VMware Converter, as described in this tutorial: http://www.howtoforge.com/vmware_converter_windows_linux) run under your Kubuntu desktop. This can be useful if you depend on some applications that exist for Windows only, or if you want to switch to Linux slowly.

I do not issue any guarantee that this will work for you!

 

Installing VMware Server 1.0.x

To download VMware Server, go to http://downloads.vmware.com/d/info/datacenter_downloads/vmware_server/1_0 and click on the VMware Server 1.0.10 link:

On the next page, click on the Download button next to VMware Server for Linux (file type: tar.gz, not rpm!):

Accept the license agreement by clicking on Yes:

Then download the VMware Server for Linux .tar.gz file (not the rpm file!) to your computer (e.g. to /home/mum/Downloads):

To get the serial number that you need to run VMware Server, go to http://register.vmware.com/content/registration.html.

Fill in your personal details. Afterwards you will get a page with a serial number for VMware Server. Write it down or print it out:

Then open a terminal (Applications > System > Terminal):

Run the following command to install some necessary packages:

sudo apt-get install build-essential xinetd

If you are on an x86_64 system, you also need to install the package ia32-libs:

sudo apt-get install ia32-libs

Then go to the location where you saved the VMware Server .tar.gz file, e.g. /home/mum/Downloads (replace mum with your own username!):

cd /home/mum/Downloads

Unpack the VMware Server .tar.gz file and run the installer:

tar xvfz VMware-server-*.tar.gz
cd vmware-server-distrib
sudo ./vmware-install.pl

The installer will ask you a lot of questions. You can always accept the default values simply by hitting <ENTER>. Answer the following question with no...

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] <-- no

.. because you'll get an error like this one otherwise when the installer tries to compile the kernel modules needed by VMware (if you answer with yes and get the errors, that's no problem either - just read on):

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-22-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.32-22-generic'
CC [M] /tmp/vmware-config0/vmmon-only/linux/driver.o
In file included from /tmp/vmware-config0/vmmon-only/./include/vmware.h:25,
from /tmp/vmware-config0/vmmon-only/linux/driver.c:48:
/tmp/vmware-config0/vmmon-only/./include/vm_basic_types.h:104:7: warning: "__FreeBSD__" is not defined
In file included from /tmp/vmware-config0/vmmon-only/./include/x86.h:20,
from /tmp/vmware-config0/vmmon-only/./include/machine.h:24,
from /tmp/vmware-config0/vmmon-only/linux/driver.h:15,
from /tmp/vmware-config0/vmmon-only/linux/driver.c:49:
/tmp/vmware-config0/vmmon-only/./include/x86apic.h:79:1: warning: "APIC_BASE_MSR" redefined
In file included from /usr/src/linux-headers-2.6.32-22-generic/arch/x86/include/asm/apic.h:11,
from /usr/src/linux-headers-2.6.32-22-generic/arch/x86/include/asm/smp.h:13,
from /usr/src/linux-headers-2.6.32-22-generic/arch/x86/include/asm/mmzone_64.h:12,
from /usr/src/linux-headers-2.6.32-22-generic/arch/x86/include/asm/mmzone.h:4,
from include/linux/mmzone.h:773,
from include/linux/gfp.h:4,
from include/linux/kmod.h:22,
from include/linux/module.h:13,
from /tmp/vmware-config0/vmmon-only/linux/driver.c:12:
/usr/src/linux-headers-2.6.32-22-generic/arch/x86/include/asm/apicdef.h:133:1: warning: this is the location of the previous definition
In file included from /tmp/vmware-config0/vmmon-only/./include/x86.h:21,
from /tmp/vmware-config0/vmmon-only/./include/machine.h:24,
from /tmp/vmware-config0/vmmon-only/linux/driver.h:15,
from /tmp/vmware-config0/vmmon-only/linux/driver.c:49:
/tmp/vmware-config0/vmmon-only/./include/x86desc.h:593:7: warning: "_MSC_VER" is not defined
In file included from /tmp/vmware-config0/vmmon-only/./include/machine.h:24,
from /tmp/vmware-config0/vmmon-only/linux/driver.h:15,
from /tmp/vmware-config0/vmmon-only/linux/driver.c:49:
/tmp/vmware-config0/vmmon-only/./include/x86.h:830:1: warning: "PTE_PFN_MASK" redefined
In file included from /usr/src/linux-headers-2.6.32-22-generic/arch/x86/include/asm/paravirt.h:7,
from /usr/src/linux-headers-2.6.32-22-generic/arch/x86/include/asm/irqflags.h:61,
from include/linux/irqflags.h:57,
from /usr/src/linux-headers-2.6.32-22-generic/arch/x86/include/asm/system.h:11,
from /usr/src/linux-headers-2.6.32-22-generic/arch/x86/include/asm/processor.h:17,
from include/linux/prefetch.h:14,
from include/linux/list.h:6,
from include/linux/module.h:9,
from /tmp/vmware-config0/vmmon-only/linux/driver.c:12:
/usr/src/linux-headers-2.6.32-22-generic/arch/x86/include/asm/pgtable_types.h:182:1: warning: this is the location of the previous definition
In file included from /tmp/vmware-config0/vmmon-only/./include/vcpuset.h:78,
from /tmp/vmware-config0/vmmon-only/./include/modulecall.h:22,
from /tmp/vmware-config0/vmmon-only/./common/vmx86.h:18,
from /tmp/vmware-config0/vmmon-only/linux/driver.h:16,
from /tmp/vmware-config0/vmmon-only/linux/driver.c:49:
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:226:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:230:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:298:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:304:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:357:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:402:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:446:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:489:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:533:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:576:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:620:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:663:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:665:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:705:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:748:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:750:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:790:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:831:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:833:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:871:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:912:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:914:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:952:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1073:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1077:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1124:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1329:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1454:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1587:7: warning: "_MSC_VER" is not defined
In file included from /tmp/vmware-config0/vmmon-only/linux/driver.h:20,
from /tmp/vmware-config0/vmmon-only/linux/driver.c:49:
/tmp/vmware-config0/vmmon-only/./include/compat_wait.h:37:5: warning: "VMW_HAVE_EPOLL" is not defined
/tmp/vmware-config0/vmmon-only/./include/compat_wait.h:43:5: warning: "VMW_HAVE_EPOLL" is not defined
In file included from /tmp/vmware-config0/vmmon-only/linux/driver.h:20,
from /tmp/vmware-config0/vmmon-only/linux/driver.c:49:
/tmp/vmware-config0/vmmon-only/./include/compat_wait.h:60: error: conflicting types for ‘poll_initwait’
include/linux/poll.h:70: note: previous declaration of ‘poll_initwait’ was here
In file included from /tmp/vmware-config0/vmmon-only/./include/vm_asm_x86_64.h:23,
from /tmp/vmware-config0/vmmon-only/./include/vm_asm.h:28,
from /tmp/vmware-config0/vmmon-only/linux/driver.c:52:
/tmp/vmware-config0/vmmon-only/./include/vm_asm_x86.h:430:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_asm_x86.h:676:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_asm_x86.h:716:7: warning: "_MSC_VER" is not defined
In file included from /tmp/vmware-config0/vmmon-only/./include/vm_asm.h:28,
from /tmp/vmware-config0/vmmon-only/linux/driver.c:52:
/tmp/vmware-config0/vmmon-only/./include/vm_asm_x86_64.h:40:7: warning: "_MSC_VER" is not defined
In file included from /tmp/vmware-config0/vmmon-only/linux/vmhost.h:13,
from /tmp/vmware-config0/vmmon-only/linux/driver.c:71:
/tmp/vmware-config0/vmmon-only/./include/compat_semaphore.h:5:27: error: asm/semaphore.h: No such file or directory
/tmp/vmware-config0/vmmon-only/linux/driver.c:146: error: unknown field ‘nopage’ specified in initializer
/tmp/vmware-config0/vmmon-only/linux/driver.c:147: warning: initialization from incompatible pointer type
/tmp/vmware-config0/vmmon-only/linux/driver.c:150: error: unknown field ‘nopage’ specified in initializer
/tmp/vmware-config0/vmmon-only/linux/driver.c:151: warning: initialization from incompatible pointer type
/tmp/vmware-config0/vmmon-only/linux/driver.c: In function ‘LinuxDriver_Ioctl’:
/tmp/vmware-config0/vmmon-only/linux/driver.c:1650: error: ‘struct task_struct’ has no member named ‘euid’
/tmp/vmware-config0/vmmon-only/linux/driver.c:1650: error: ‘struct task_struct’ has no member named ‘uid’
/tmp/vmware-config0/vmmon-only/linux/driver.c:1651: error: ‘struct task_struct’ has no member named ‘fsuid’
/tmp/vmware-config0/vmmon-only/linux/driver.c:1651: error: ‘struct task_struct’ has no member named ‘uid’
/tmp/vmware-config0/vmmon-only/linux/driver.c:1652: error: ‘struct task_struct’ has no member named ‘egid’
/tmp/vmware-config0/vmmon-only/linux/driver.c:1652: error: ‘struct task_struct’ has no member named ‘gid’
/tmp/vmware-config0/vmmon-only/linux/driver.c:1653: error: ‘struct task_struct’ has no member named ‘fsgid’
/tmp/vmware-config0/vmmon-only/linux/driver.c:1653: error: ‘struct task_struct’ has no member named ‘gid’
/tmp/vmware-config0/vmmon-only/linux/driver.c:1670: error: too many arguments to function ‘smp_call_function’
make[2]: *** [/tmp/vmware-config0/vmmon-only/linux/driver.o] Error 1
make[1]: *** [_module_/tmp/vmware-config0/vmmon-only] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.32-22-generic'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-config0/vmmon-only'
Unable to build the vmmon module.

For more information on how to troubleshoot module-related problems, please
visit our Web site at "http://www.vmware.com/download/modules/modules.html" and
"http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html".

Execution aborted.

mum@KubuMuM1004lts:~/Downloads/vmware-server-distrib$

Share this page:

11 Comment(s)

Add comment

Comments

From: bkrec at: 2010-07-15 14:02:08

Nice Guide,

but in the end i hoped it will work with Ubuntu 10.4 ,too....It doesn´t

You can install the Server but you will not connect from a Remote Vmware Server Console :-(

From: bifferos at: 2010-07-11 15:14:36

VirtualBox is, indeed slower for certain applications, however most users won't notice the difference, and when it comes down to Linux installs, VirtualBox installation is *significantly* easier, I'd say 'trivial'.  My own benchmarks indicate VirtualBox as much as 20% slower for compilation tasks, but it makes up for this with a seemingly more responsive GUI. Not sure where the 'unusable' part comes in, that's certainly not been my experience - I use it daily!

I was a keen VMWare 1.0 user, but once they brought out VMWare server 2.0 I switched to VirtualBox, and apart from a few rather dodgy versions they put out in the beginning (release early, release often mentality) it's been good.

There is only one reason to use VMWare server as far as I'm concerned and that's for operating systems that don't run on VirtualBox.  VMWare server still has the edge in terms of accuracy of virtualisation - NetBSD worked with that, but not with the latest version of VB.  VB requires AMD-V/VT-x extensions to accurately virtualise, whereas VMWare does a better job without.

From: Innocent Bystander at: 2010-05-28 02:23:21

VMWare Server is a very old product. I strongly advise to use Virtualbox version 3.18. If you start from scratch, Virtualbox is the way to go, the learning curve is equivalent or may be even easier. VB has Open Source version and a also binary ready to install. It's all free and better yet, in terms of performance and features, it is way superior to VMWare Server.

In VMWare the product that compares to Virtualbox is VMWare Workstation version 7.x (cost $200).

 

From: Luc at: 2010-06-20 03:42:42

Virtual Box is terribly slow!It's so slow it's borderline unusable. No wonder so many people still prefer VMWare.

From: krisum at: 2010-05-28 16:06:56

VMware server 1.0.x is far too much hassle and building new kernel etc. is very dicey particularly since users will need to redo this once a new bugfix/security fix comes out for a kernel version. I think you should strongly recommend using the latest VMware player instead of VMware server for desktop machines since that now provides option to create a new machine (with all options that are in VMware server 1.0.x) with extra stuff for desktop machines like sharing directories, unity desktop. A large number of linux users may be mislead upon reading this while a much more straightword option exists which is now better for desktops in every way.

From: at: 2010-06-08 08:29:49

Hi all.

I'd like let anyone "choose" what they prefer...

And if they prefer to still use "old" Vmware server 1.x, I'd like help them to do it...

Do You think I'm wrong?

 

From: Tony Heskett at: 2010-07-01 12:33:43

Thanks, that was extremely helpful (saved me hours :-)

 

BTW, I use VMware server 1.x because:

- it's fast and easy

- no learning required, and my friends understand it ("it's old" helps :-)

- it's worked nicely, in setups where VirtualBox and Xen have hung

- VMware server 2.0 is fat and hence slow.

VMware Workstation would require me to pay, for just the same features I'm using for free, so there's no point in switching.

From: MaxPower at: 2010-08-21 23:20:06

Thank you very very very much for this article, I was looking for this on the web months ago and didn't find a clue, but finally it works. The only thing I had to do additionally is to run "update-grub" after creating the initrd for the new kernel. Just wanted to say that if someone else is having trouble booting up ("Kernel Panic - not syncing: VFS: Unable to mount root fs")

From: Anonymous at: 2010-09-14 01:20:58

I get a kernel panic error after rebooting with the new compiled kernel:

Kernel panic: VFS: Unable to mount root fs

My filesystem for / is ext4 and I thing it is supported in this kernel.

 Any help please?

From: Anonymous at: 2011-03-19 05:01:12

I got this too and was able to work around it by changing one of the SATA modules to be compiled-in, in the .config. Just search for CONFIG_SATA_AHCI and make sure it =y instead of =m before compiling.

From: Fritz at: 2011-02-20 07:59:38

Works. Thank you! Have followed the process and although compiling the kernel takes ages my I have VMware server 10.09 running on Ubuntu 10.04. Unfortunately I was unable to connect and login to remotely to the vmware serverFound several solutions that involved editing /etc/pam.d/vmware-auth but none worked.... but this fixed the problem:
//change contents /etc/pam.d/vmware-auth from

#%PAM-1.0
auth       sufficient       /lib/security/pam_unix2.so shadow nullok
auth       required         /lib/security/pam_unix_auth.so shadow nullok
account    sufficient       /lib/security/pam_unix2.so
account    required         /lib/security/pam_unix_acct.so

//to

#%PAM-1.0
auth       sufficient       /lib/security/pam_unix.so shadow nullok
auth       required         /lib/security/pam_unix_auth.so shadow nullok
account    sufficient       /lib/security/pam_unix.so
account    required         /lib/security/pam_unix_acct.so

 

Hope this helps someone!