After I've read this
post in the Heise newsticker that VMware server 2.0 BETA 2 is available, I've started downloading the new RPM to upgrade my VMware server 2.0 BETA 1 installations. So I've started to upgrade with the "normal" procedure:
service vmware stop
Next I took the opportunity to upgrade my system to the latest and greatest patch level with a reboot because the kernel was replaced by a new version:
yum update all
yum clean all
reboot
After the reboot I've logged in again and start the configuration of vmware:
/usr/bin/vmware-config.pl
I've used the proposed values except the license which I've reentered (didn't remember if it was the same license key as used with BETA 1 or not). The start of the server was from my point of view the last step:
service vmware start
Unfortunately I wasn't able to connect (http/https). So I've checked the ports with:
netstat -tulpn
Hmm, indeed, nothing was listening on port 80/443. I've googled around and found an entry in the VMware forum stating that SElinux could be the problem:
sestatus
Oh, SElinux is activated, that explain a lot (the following command change some SElinux security context for the shared libraries):
find /usr/lib/vmware -name '*.so*' \
-exec chcon -t texrel_shlib_t {} \;
Now I've only need to restart the VMware server:
service vmware restart
Eureka! VMware server 2.0 BETA is upgraded and running, let's see how stable it already is.
No comments:
Post a Comment