Archive for the ‘VMWare’ Category

Installing Linux with a GUI under MS Virtual PC

Saturday, June 14th, 2008

Since I haven’t been able to find a version of VMWare Server that works properly under Vista as a host system, I have fallen back to using MS Virtual PC 2007 to run the VMs on my desktop machine. This works well enough for the windows VMs, but installing linux can be frustrating. The X-Windows installer always seems to want to come up in 24 bit colour mode, but Virtual PC thinks it’s 16 bit colour mode. This results in a corrupt display and the failure to continue the installation. To work around this, you need to remember to tell the linux installer to run in either text mode or vesa compatibility mode.

Use text mode if you won’t be installing X-Windows…

boot: linux text

Use vesa compatibility mode if you want the full GUI experience…

boot: linux vesa

I’ve tried this with various Fedora/Centos releases, but it should work with whatever your favorite flavour of linux is.

VMWare Guest clocks running too fast

Friday, June 13th, 2008

I use VMWare Server on a couple of machines to run various linux and windows guest virtual machines. Depending on what cpu and what kind of power management I have enabled on the host machine I can see some very severe clock drift on the guests. To work around the clock drift I usually need to add a few items to the vmware hosts global config file.

For linux hosts, the config file can usually be found at…

/etc/vmware/config

For windows hosts, the config file location is…

C:\Documents and Settings\All Users\Application Data\VMware\VMware Server\config.ini

Open the global config file and add the following lines then restart the vmware server service/daemon…

host.cpukHz = 2000000
hostinfo.noTSC = TRUE
tools.syncTime = TRUE

The first line tells vmware what the maximum clock frequency of the host cpu is (2GHz in my example). The ‘hostinfo.noTSC’ line informs VMWare that the cpu is not running at a constant clock rate (speedstep or cpufreq or power management is active) and the timestamp counter can’t be trusted so use it as little as possible. The last line sets the default to use vmware-tools timesync function. The addition of these items is usually enough to keep the guest clocks running close enough to proper time that ntp will stay locked.