vmware-server

URL:

about:config

Wert:

security.enable_ssl2

auf true setzen.

http://wiki.debian.org/VMware

In general the installation is similiar to that in Lenny, with the following differences:

• There are different versions of the linux kernel and gcc.
• Different patches are required for the installer and the modules.

Instructions:

1. Get the VMWare Server archive (at least version 2.0.2) and your license. Hopefully the issues will be fixed in later versions.
2. Install the prerequisites (including kernel-headers for your version, and gcc version 4.3).
3. Get the patches archive from http://codebin.cotescu.com/vmware/vmware-server-2.0.x-kernel-2.6.3x-install.sh.
4. Unzip the VMWare archive, install VMWare, but do not configure it yet, i. e. answer the question to run „vmware-config.pl“ with „no“.
5. Patch vmware-config.pl using a file from the patch archive (choose the directory where you installed the binaries, if not „/usr/bin“).

   cd /usr/bin
   patch -p3 < vmware-config.patch

6. Patch the module sources using another file from the patch archive (choose the directory where you installed the libraries, if not „/usr/lib“).

   cd /usr/lib/vmware/modules/source
   for i in *.tar ; do tar xpf $i ; done
   patch -p4 < vmware-server-2.0.2-203138-update.patch
   for i in vmci vmmon vmnet vsock ; do tar cpf $i.tar $i-only ; done

7. Now run vmware-config.pl.
   After that the installation is complete, but a bug related to Tomcat/Java may prevent the web admin interface at http://localhost:8222 from being operational. If you get the message „Error 503: Service unavailable“, then continue patching.
   
   [Note: If you want to learn more about this issue, see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572048. As Java is embedded in VMWare, switching to a current version is no option, neither should be disabling IPv6.]
   
8. IPv6 must be disabled for the „WebAccess“ service only. Create a patch file named „vmware.patch“ (see the „Lenny“ section for how to do this using an editor):

   --- vmware.orig 2010-05-24 17:05:09.251864323 +0200
   +++ vmware      2010-05-24 21:40:37.563871986 +0200
   @@ -675,7 +675,7 @@
    watchdog="${vmdb_answer_BINDIR}/vmware-watchdog"
    webAccessServiceName="VMware Virtual Infrastructure Web Access"
    CATALINA_HOME="${vmdb_answer_LIBDIR}/webAccess/tomcat/apache-tomcat-6.0.16"
   -webAccessOpts="-client -Xmx64m -XX:MinHeapFreeRatio=30 -XX:MaxHeapFreeRatio=30 -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.endorsed.dirs=$CATALINA_HOME/common/endorsed -classpath $CATALINA_HOME/bin/bootstrap.jar:$CATALINA_HOME/bin/commons-logging-api.jar -Dcatalina.base=$CATALINA_HOME -Dcatalina.home=$CATALINA_HOME -Djava.io.tmpdir=$CATALINA_HOME/temp org.apache.catalina.startup.Bootstrap"
   +webAccessOpts="-Djava.net.preferIPv4Stack=true -client -Xmx64m -XX:MinHeapFreeRatio=30 -XX:MaxHeapFreeRatio=30 -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.endorsed.dirs=$CATALINA_HOME/common/endorsed -classpath $CATALINA_HOME/bin/bootstrap.jar:$CATALINA_HOME/bin/commons-logging-api.jar -Dcatalina.base=$CATALINA_HOME -Dcatalina.home=$CATALINA_HOME -Djava.io.tmpdir=$CATALINA_HOME/temp org.apache.catalina.startup.Bootstrap"
    
    #
    # Utilities

9. Patch /etc/init.d/vmware, and restart the daemon.

   cd /etc/init.d
   patch < vmware.patch
   ./vmware-mgmt restart 

Done.

Installing VMware Server 2 on Lenny

Howto install VMware Server 2 on Debian Lenny. Since kernel modules for the Lenny Kernel are not shipped with VMware server 2, the kernel modules need to be build. However, there is a bug in the file vmware-config.pl. See here for more details. The patch available for Ubuntu works for Debian Lenny too. You can chooose to follow this instructions to install correctly VMWare Server 2.0.x into Debian Lenny. Before you install you need ensure that thefollowing dependencies are installed into your system:

binutils
gcc
libc6
libc6-dev
make
linux-headers-2.6.26-2-amd64 (or other version according to your installed kernel. Use "uname -a" to get you kernel version)
psmisc

Download vmware server 2 from VMware - Official Site and register to obtain your licence key.

Unzip the tar.gz

tar -zxvf VMware-server-2.0.x-xxx.tar.gz
cd vmware-server-distrib/

let the installer use gcc 4.1 and not gcc 4.3 and run the installer

export CC=/usr/bin/gcc-4.1
./vmware-install.pl

Probably you will receive an error in building the vsock module:

...
Unable to make a vsock module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config5/vsock.o'
...

To avoid this problem and build correctly the vsock module, you will need to create and apply a patch. Create a vmware-config.pl-patch

nano vmware-config.pl.patch

paste the following text into the editor:

--- /usr/bin/vmware-config.pl.orig      2008-11-28 12:06:35.641054086 +0100
+++ /usr/bin/vmware-config.pl   2008-11-28 12:30:38.593304082 +0100
@@ -4121,6 +4121,11 @@
     return 'no';
   }
 
+  if ($name eq 'vsock') {
+    print wrap("VMWare config patch VSOCK!\n");
+    system(shell_string($gHelper{'mv'}) . ' -vi ' . shell_string($build_dir . '/../Module.symvers') . ' ' . shell_string($build_dir . '/vsock-only/' ));
+  }
+
   print wrap('Building the ' . $name . ' module.' . "\n\n", 0);
   if (system(shell_string($gHelper{'make'}) . ' -C '
              . shell_string($build_dir . '/' . $name . '-only')
@@ -4143,6 +4148,10 @@
     if (try_module($name, $build_dir . '/' . $name . '.o', 0, 1)) {
       print wrap('The ' . $name . ' module loads perfectly into the running kernel.'
                  . "\n\n", 0);
+      if ($name eq 'vmci') {
+       print wrap("VMWare config patch VMCI!\n");
+       system(shell_string($gHelper{'cp'}) . ' -vi ' . shell_string($build_dir.'/vmci-only/Module.symvers') . ' ' . shell_string($build_dir . '/../'));
+      } 
       remove_tmp_dir($build_dir);
       return 'yes';
     }

save the file and apply the patch:

patch /usr/bin/vmware-config.pl vmware-config.pl.patch

now you can re-run the installed vmware-config.pl and build correctly the vsock module:

cd /usr/bin/
./vmware-config.pl

Once you are done with no errors, you can check that all vmware's modules are loaded corretly:

# lsmod | grep v
vmnet                  43460  13 
vsock                  26032  0 
vmci                   52904  1 vsock
vmmon                  72144  0 

VMWare server 2 web interface problems

People find that that the Vmware Server 2 web interface stops responding properly (Browsing the datastore, adding hardware to a virtual machine). Perhaps this problems are caused by Java runtime environment (JRE) shipped with VMware which can be found in the directory vmware/webAccess/java/jre1.5.0_15. The JRE in this directory can be updated with a newer one. However, the file vmware/webAccess/java/jre1.5.0_15/bin/webAccess needs to be retained. Otherwise the web interface would not work. See Constant NullPointerException: Operation failed. errors in web UI.

Scripts to start and stop the VMWare server 2 Web Interface

If you don't manage your virtual machines everyday you should consider to free you ram by turning off the Web Interface.

# nano vmware-stopWebAccess 

and paste the following code

# Web Access configuration
webAccess="/usr/lib/vmware/webAccess/java/jre1.5.0_15/bin/webAccess"
watchdog="/usr/bin/vmware-watchdog"
webAccessServiceName="VMware Virtual Infrastructure Web Access"
CATALINA_HOME="/usr/lib/vmware/webAccess/tomcat/apache-tomcat-6.0.16"
webAccessOpts="-client -Xmx64m -XX:MinHeapFreeRatio=30 -XX:MaxHeapFreeRatio=30 -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.endorsed.dirs=$CATALINA_HOME/common/endorsed -classpath $CATALINA_HOME/bin/bootstrap.jar:$CATALINA_HOME/bin/commons-logging-api.jar -Dcatalina.base=$CATALINA_HOME -Dcatalina.home=$CATALINA_HOME -Djava.io.tmpdir=$CATALINA_HOME/temp org.apache.catalina.startup.Bootstrap"

echo 'Shut down the webAccess watchdog...'
$watchdog -k webAccess > /dev/null 2>&1
echo 'ok'
echo 'Shut down webAccess itself...'
$webAccess $webAccessOpts stop > /dev/null 2>&1
echo 'ok'
echo 'killall webAcces...'
killall webAccess > /dev/null 2>&1
echo 'ok'

echo '   '"$webAccessServiceName"' OFF'
<code/>


Watch out that the variable webAccessOpts ' must be written on a single line! and if you have installed a vmware's 64 bit version you need to set webAccess variabel to /usr/lib64/vmware/webAccess/java/jre1.5.0_15/bin/webAccess"

Save and exit. Now you will create the startup script

  # nano vmware-startWebAccess 

and again paste the following code
<code>
# Web Access configuration
webAccess="/usr/lib/vmware/webAccess/java/jre1.5.0_15/bin/webAccess"
watchdog="/usr/bin/vmware-watchdog"
webAccessServiceName="VMware Virtual Infrastructure Web Access"
CATALINA_HOME="/usr/lib/vmware/webAccess/tomcat/apache-tomcat-6.0.16"
webAccessOpts="-client -Xmx64m -XX:MinHeapFreeRatio=30 -XX:MaxHeapFreeRatio=30 -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.endorsed.dirs=$CATALINA_HOME/common/endorsed -classpath $CATALINA_HOME/bin/bootstrap.jar:$CATALINA_HOME/bin/commons-logging-api.jar -Dcatalina.base=$CATALINA_HOME -Dcatalina.home=$CATALINA_HOME -Djava.io.tmpdir=$CATALINA_HOME/temp org.apache.catalina.startup.Bootstrap"

$watchdog -s webAccess -u 30 -q 5 "$webAccess $webAccessOpts start" > /dev/null 2>&1 &
echo '   '"$webAccessServiceName"' ON'

Watch out that the variable webAccessOpts ' must be written on a single line! and if you have installed a vmware's 64 bit version you need to set webAccess variabel to /usr/lib64/vmware/webAccess/java/jre1.5.0_15/bin/webAccess„

Save and exit. Now make them executable

# chmod +x vmware-stopWebAccess 
# chmod +x vmware-startWebAccess 

and you are done!