Sunday, 15 June 2008

Updating VMWare Server, MUI and Console

Updating VMware Server 1.0.5 to 1.0.6 works fine. However, installing VMware MUI afterwards breaks with VMware MUI 1.0.6.
VMware Server must be installed on this machine for the VMware Management Interface to work
Installation aborts.

In order to fix this I had to remove the library libgcc_s.so.1 in /usr/lib/vmware/lib/libgcc_s.so.1:
mv libgcc_s.so.1 libgcc_s.so.1_orig
Installation of MUI worked fine afterwards.

In order to start the management interface during the next reboot one has to add a few lines at the beginning of /etc/init.d/httpd.vmware:
RUNDIR="/var/run/vmware/httpd"
OWNER="www-data"
GROUP="www-data"

/usr/bin/test -d "$RUNDIR" || \
/bin/mkdir -p "$RUNDIR" && /bin/chown "$OWNER:$GROUP" "$RUNDIR"
Now, the management interface survives a reboot.

This workaround fixed the installation problem of the server console on the workstation as well.

2 comments:

Mattias R said...

The VMware Management Interface's startup scripts (/etc/init.d/httpd.vmware and /usr/lib/vmware-mui/src/lib/httpd.vmware) have a bug which makes the Apache server start fail after reboot. To fix the script apply the following patch.

# cd /tmp
# wget http://www.iki.fi/kuparine/comp/ubuntu/en/httpd.vmware.diff
# cd /
# patch -b -p0 < /tmp/httpd.vmware.diff

winky said...

Thanks Matthias!
the mui problem is still present in vmware server 1.0.8
This really saved me!