Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

So I have this VM (I don't have access to the host system) running Debian Lenny, with the following kernel: 2.6.32-bpo.5-686 #1 SMP

This morning I upgraded the VM to Squeeze (finally), and as the system rebooted, I noticed that it was painfully slow. The dist-upgrade (after reboot) is still running, and has been for several hours. However, the load is below 1, CPU usage around 50%, no big disk activity, and there is plenty of RAM available. I don't understand where this performance problem (it's really, REALLY slow) come from. The odd thing though, is that the clock seems to be very slow as well: the seems to believe that only a few minutes have passed since it has been rebooted, even though it's actually been hours.

Has anyone experienced a similar problem? Or do you have suggestions about where to look for clues?

share|improve this question
up vote -1 down vote accepted

Ok, so I found what the problem was. As it turns out it wasn't a Xen VM, but anyway. Apparently the VM did pick the wrong clocksource (kvm-clock instead of acpi). Changing it in /sys/devices/system/clocksource/clocksource0/current_clocksource immediately solved the problem. According to the owner of the host system, it's a problem he has seen a few times before (seemingly randomly, he hasn't yet been able to pinpoint where the bug lies exactly), and is unrelated to the upgrade I was performing.

share|improve this answer
If KVM is similar to XEN there should be a clocksource-directive in the KVM configuration for your VM. These can differ from OS to OS. – Nils May 22 '12 at 20:27

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.