We have quite many virtual machines running under VMWare server. Some for testing purposes, some for quite real systems serving real webpages.
It’s wonderful. Need a new server? Just cp -r the template I created. Need more RAM in your server? No problem. Just add it via the virtual machine configuration file. Move to another machine? No problem at all. Power down the virtual machine and move the file where you want it to be.
Today I noticed something strange: The clocks on the virtual machines were way slow.
One virtual second was about ten real seconds.
This was so slow that chrony which I used on the virtual machines thought that the data sent from the time servers was incorrect, so chrony was of no use.
After a bit of digging around, I learned that VMware server needs access to /dev/rtc to provide the virtual machines with an usable time signal (usable as in “not too slow”).
The host’s /var/log/messages was full of lines like this (you’ll notice that I found yet another girl from a console RPG to name that host):
Dec 15 16:12:58 rikku /dev/vmmon: /dev/rtc open failed: -16 Dec 15 16:13:08 rikku /dev/vmmon: host clock rate change request 501 -> 500
-16 means “device busy”
The fix was to stop chrony from running on the host machine so VMWare could open /dev/rtc. This made the error messages vanish and additionally it allowed the clocks of the virtual machines to work correctly.
Problem solved. Maybe it’s useful for you too.