It's great to be able to test the beta, but it comes with a few problems: debug mode is forced on us, and there's the WebUI...
Debug mode: I have use the beta for a few weeks now, and if I had come across anything where it would have been useful, I would have by now. As I don't need it anymore, I should be able to turn it off to get some better performance.
WebUI: by now I am sure most people agree that it's a useless piece of junk, and it has no place in this product.
-
cd /usr/lib/vmware/bin
mv vmware-vmx-debug vmware-vmx-debug.old
ln -s vmware-vmx vmware-vmx-debug
mv vmware-remotemks-debug vmware-remotemks-debug.old
ln -s vmware-remotemks vmware-remotemks-debug
-
If you have a Linux host you can download it from the server (https://ip_of_your_vmware_server/client/VMware-viclient.exe)
If you have a Windows host you need to download the Linux version and get it from there.
-
Edit /etc/init.d/vmware
Find the following lines at the end of the file:
case $1 in
start)
service_vmware "$1"
service_vmware_mgmt "$1"
service_vmware_autostart "$1"
;;
Comment out the service_vmware_mgmt line, and add a line to start the
remote management interface, as below:
service_vmware "$1"
service_vmware_mgmt "$1"
vmware_start_hostd
service_vmware_autostart "$1"
To start WebAccess, use:
service vmware-mgmt start
and to stop it:
service vmware-mgmt stop
-
With the tweaks above, on a minimal CentOS 5.1 64bit server, linux + vmware only use 75MB ram.
-
Or just wait for VMware Server 2.0 RC.
Unfortunately proposed adjustments address only a small portion of issues found in Beta 1.
Unless you want to be a brave contributor to Beta testing, I suggest to wait for RC.
For Windows users
cd to vmware\VMware Server
rename vmware-vmx-debug.exe vmware-vmx-debug.old
rename vmware-vmx.exe vmware-vmx-debug.exe
rename vmware-remotemks-debug.exe vmware-remotemks-debug.old
rename vmware-remotemks.exe vmware-remotemks-debug.exe
The VI 2.5 client will only install on 32 bit Windows OS not 64 bit.
I see nothing wrong with the steps arman68 took to make this beta "usable". I think however everybody that installs this beta should at least work with the web UI for a while. Just to make up your own opinion.
A note to the vmware people: either fix the web ui (see forum posts for the complaints) or port the VI client to linux (and preferably Mac OS X as well).
should the vi client work by default? I'm using windows ent. 64bits as Host and the vmware server 2 beta, did the rename action but can't connect with the vi client that coms with the ESX 3.5 server.
Do you have the VI 2.5 client ? for me it would not install on Vista 64 but worked okay on 32 bit XP , you need to specfiy the host name and port number, <host name>:8333 .
adding the port number did the job! thanx
rosspcs wrote:
Do you have the VI 2.5 client ? for me it would not install on Vista 64 but worked okay on 32 bit XP ,
If you have an MSI editor you can make it work in 64 bit mode too: http://communities.vmware.com/message/821756
Lars
I agree about the WebUI. I don't see the point. WebUIs should only be used for applications used by a large number of people or people in a number of different locations where deployment is a problem.
To use a WebUI for this is just ridiculous and it really doesn't work for me. I find it so frustrating that such an excellent product can be bundled with such a poor interface when they had a much better interface before.
I will give the VI client a try and see if that works.