VirtualBox

Ticket #1984 (closed defect: worksforme)

Opened 6 years ago

Last modified 6 years ago

Slow clock in VM in comparison to host => recompile kernel+vboxdrv

Reported by: Tatsh Owned by:
Priority: major Component: VM control
Version: VirtualBox 1.6.4 Keywords: clock, timer, os-neutral
Cc: Guest type: Windows
Host type: Linux

Description

Hello everyone.

Gentoo is my distro, and I installed VirtualBox via emerge, upgrading from 1.6.2 to 1.6.4 in the process. I've rebooted several times since then and only today did I decide to run a VM again. vboxdrv is in my autoloaded modules and was working before with version 1.6.2. (I do not have an /etc/init.d/vboxdrv or vboxnet). I've tried re-emerging (and even emerge -C first) and then modprobing again but this does not have any effect. Also tried chowning the module to vboxusers group.

Basically, once the VM starts, the clock ticks slower than my normal computer clock. By the time a VM loads up, its time is lesser than my time and it is ticking slowly. The Windows XP time is always off and performance is spotty in comparison to before. The boot splash fades very slow, as well as the fade in of the BIOS text 'Press F12...'.

Log and kernel configuration are included.

This happened before with 1.6.2 but I messed around with the kernel configuration and VBox started working randomly again.

I describe it all here as well.  http://forums.virtualbox.org/viewtopic.php?p=32844#32844

I'd appreciate any help with this. ~Tatsh

Attachments

VBox.log Download (35.1 KB) - added by Tatsh 6 years ago.
Example VBox log
.config Download (46.6 KB) - added by Tatsh 6 years ago.
Kernel configuration

Change History

Changed 6 years ago by Tatsh

Example VBox log

Changed 6 years ago by Tatsh

Kernel configuration

comment:1 in reply to: ↑ description Changed 6 years ago by Tatsh

dmesg says the following when I modprobe vboxdrv:

vboxdrv: Trying to deactivate the NMI watchdog permanently... vboxdrv: Successfully done. vboxdrv: Found 1 processor cores. vboxdrv: fAsync=0 u64DiffCores=1. vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. vboxdrv: Successfully loaded version 1.6.2 (interface 0x00070002). vboxdrv: Trying to deactivate the NMI watchdog permanently... vboxdrv: Successfully done. vboxdrv: Found 1 processor cores. vboxdrv: fAsync=0 u64DiffCores=1. vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. vboxdrv: Successfully loaded version 1.6.4 (interface 0x00080000).

comment:2 Changed 6 years ago by Tatsh

sorry, reformatting above

vboxdrv: Trying to deactivate the NMI watchdog permanently...
vboxdrv: Successfully done.
vboxdrv: Found 1 processor cores.
vboxdrv: fAsync=0 u64DiffCores=1.
vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 1.6.2 (interface 0x00070002).
vboxdrv: Trying to deactivate the NMI watchdog permanently...
vboxdrv: Successfully done.
vboxdrv: Found 1 processor cores.
vboxdrv: fAsync=0 u64DiffCores=1.
vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 1.6.4 (interface 0x00080000).

comment:3 Changed 6 years ago by Tatsh

Fixed by recompiling kernel then recompiling vboxdrv module and re-modprobing. No idea why this fixed it, but it did.

comment:4 Changed 6 years ago by frank

  • Status changed from new to closed
  • Resolution set to worksforme
  • Summary changed from Slow clock in VM in comparison to host; Not just Windows; happens with ANY OS to Slow clock in VM in comparison to host => recompile kernel+vboxdrv

Thanks for the report, this is what I thought: Some inconsistence between the running kernel and the kernel sources vboxdrv is compiled against. I will close the bug.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use