vmware_server 1.0.8

Description:  Headless Virtual machine software for x86 CPUs
Maintainer:  Roman Plessl <roman.plessl@oetiker.ch>
Created:  2009-02-19
Updated:  2009-02-19 (Package Prepared)
Support:  Roman Plessl <roman.plessl@oetiker.ch>
Links:  Homepage, SEPP Dir, INSTALL
OS:  linux
Categories:  system
Binaries:  vm-supportvmnet-bridgevmnet-dhcpdvmnet-natdvmnet-netifupvmnet-sniffervmrunvmwarevmware-authtrustedvmware-cmdvmware-config.plvmware-loopvmware-mount.plvmware-pingvmware-serverdvmware-uninstall.plvmware-vdiskmanagervmware.bin
More Info

VMware Server works by enabling multiple operating systems and their applications to run concurrently on a single physical machine. These operating systems and applications are isolated in secure virtual machines that co-exist on a single piece of hardware. The VMware virtualization layer maps the physical hardware resources to the virtual machine's resources, so each virtual machine has its own CPU, memory, disks, I/O devices, etc. Virtual machines are the full equivalent of a standard x86 machine.

The VMware SEPP package is a bit special, because running VMware requires some things to be in fix locations:

1) /etc/vmware must be a directory which contains configuration files (among other the locations file that defines all other directories where VMware is located). But /etc/vmware is hardcoded in a lot of places. We recommend making it a symbolic link to /usr/pack/vmware../etc or copy all files from a central repository to /etc/vmware.

2) VMware needs a boot time script in /etc/init.d (linked into /etc/rc?.d of course).

3) 2 kernel modules (vmmon.o and vmnet.o) must be installed as root in the kernel module tree (/lib/modules/`uname -r`). We recommend placing them in /lib/modules/`uname -r`/misc

4) It needs several device nodes in /dev

5) One binary (.../lib/vmware/bin/vmware-vmx) needs to be setuid root

These 5 things need to be performed before the VMware package becomes functional. The init-Script ist provided in the SEPP directory.

So to build the package, the sequence of steps is:

1) create a local packages (bind mount package stub)

2) activate unionfs with unionshadow

3) run the INSTALL script. It downloads and builds everything. One requirement is that /lib/modules/`uname -r`/build points to the valid kernel source tree that has been used for building the kernel