KVM FreeBSD timing

flosoft

Member
Jul 6, 2008
68
0
6
Howdy There,

running FreeBSD 7.2 RELEASE as guest OS inside KVM on a linux machine.

Problem: "time sleep 1" shows that sleep needs 3 seconds. For sleep 2 it needs 6 seconds and so on.

Tried reducing kern.hz from 1000 to 100 and even to 50. Didn't change the described behavior of the problem.

How to fix this?

Cheers,

Florian
 
Try adding this line into /boot/loader.conf and rebooting, it solves timing issues under pfSense (FreeBSD 7.1)/KVM for me..

hint.apic.0.disabled="1"

Let me know if that helps, cheers
 
Try adding this line into /boot/loader.conf and rebooting, it solves timing issues under pfSense (FreeBSD 7.1)/KVM for me..

hint.apic.0.disabled="1"

Let me know if that helps, cheers

this happened when i tried that line.
 

Attachments

  • proxmox-freebsd-time-fail.png
    proxmox-freebsd-time-fail.png
    35 KB · Views: 23
Er, not sure what happened there (i'm no freebsd expert) but it shouldn't of caused that problem.

Did you leave all the other lines in /boot/loader.conf and just add it as a new line at the end of the file? No spaces/etc?

Maybe try removing all the custom clock settings you have implimented and just try that line by itself, it's always worked for me.
 
Same problem exists if /boot/loader.conf only contains the line you posted. Are you sure this workaround worked for you with FreeBSD 7.2 RELEASE?
 
I haven't tested for 7.2-RELEASE, only 7.1-RELEASE. /boot/loader.conf should contain a couple of other lines as well which should not be removed, the line I posted above should be added to the end of whatever is there by default when you install.
 
I am getting a similar problem with FreeBSD 8.0-RELEASE as a kvm guest using full virtualization. Sleep 1 takes 3 seconds. If you do a ping -c 10 localhost it takes 3 sec between pings instead of 1 sec.

Overall the FreeBSD command line is sluggish to respond. Something is wrong with the timing. I don't get this problem under Xen or ESXi with FreeBSD 8.0-RELEASE as a guest OS.

Any ideas where to start looking?
 
I ran the apt-get update/dist-upgrade for Proxmox which installed the later 2.6.24-9-pve kernel, and rebooted, the problem seems to have cleared. Just testing to be sure.

- Ernie.