less than 1 minute read

If you’re using VMWare on a variable-speed processor (like all most modern cpu’s these days) you might have noticed that sometimes the guest OS runs a lot faster (causing the guest clock to run faster and all kinds of weird effects).

The fix for that is easy, and specified in this knowledgebase article:

Add to /etc/vmware/config the following lines:

host.cpukHz = 1700000
host.noTSC = TRUE
ptsc.noTSC = TRUE

replacing 1700000 with the actual top speed of your processor. Et voila, runs better ;)

Updated:

Leave a comment

You may also enjoy

Enabling native IPv6 on Proxmox and LXC using SDN

3 minute read

In my original deployment of Proxmox on my VPS I only enabled IPv4, and I was using socat to forward traffic from the IPv6 address of the host to the internal IPv4 addresses of the containers. Not ideal, since this masks the external IP addresses, and also creates some latency and additional CPU load when processing IPv6.

Proxmox, LXC, and Debian Trixie

3 minute read

I run Proxmox Virtual Environment as my virtualisation platform. On top of this I use virtual machines using KVM and Linux Containers using LXC - both of which are natively supported on ProxmoxVE.

Code storage

1 minute read

Code, and where to store it