Another Vmserver 2.0 gotcha

Why change something thing when it aint broke?

I used to be able to run vmware-cmd to start and stop vmware server 1.0 vm’s from the command line it was a simple sort of.

bash# vmware-cmd /usr/local/vm/vm/vm.vmx start

Now is Vmware Server 2.0 I have to do

vmrun -p [password] -u [username] -T server -h https://localhost:8333/sdk start "[storage] vm/vm.vmx"

simple right? oh and you are forced to put your password in the command line which will be saved in bash history and to anyone who can run ps on the sever. I was really hoping that it would follow the mysql convention and prompt for a password, but I guess not

Thanks for the upgrade VMware, you just made the world less secure.

For future reference.
Install ubuntu
Download vmware server.tgz
Download vmware client.tgz
install the needed packages

sudo apt-get install linux-headers-$(uname -r) build-essential g++-3.4
sudo apt-get install xinet
cd vmware-server-distrib/
sudo ./vmware-install.pl

cd vmware-console-distrib/

sudo ./vmware-install.pl

I discovered why my vmware server virtual machines were running so slow. In Vitual Machine Settings, options, advanced there is a little ticket box that says run with debugging. I missed this since you can only change it when the VM is not running. Now my Asterisk and Windows XP VMs are running super fast.

I have been using vmware player for a few months now and was very impressed so I tried the free vmware server at work and now at home. The is server version is the one I really want to use. It allows you to run multiple instances and have them bootup and shutdown with the host computer. I have been noticing some serious hard disk slowness on the server at work. I was originally putting it down to a slow raid driver on linux but after whiching asterisk from vmware player to server this week I am going to blame vmware server. Asterisk was running very well with vmplayer but with server the cpu is sitting at a load of 2-3. Anything above 1 is bad news in linux land. I just created a new instance using asterisk@home 2.7 to see if anything has changed, otherwise I am flipping it back to vmware player till server comes outof beta. I have heard that the debug code in the beta server is to blame for a large chunk of the slowness.