Kernel panic: Instable time source when running OEL Linux 64 bit Guest on Core2 Duo Linux Host

[amain]

After upgrading from VirtualBox 3.0.10 to 3.0.12, my OEL 5.4 Linux Guest does not want to boot anymore. Kernel is started but fails with a kernel panic during boot:

Kernel panic - not syncing: Aiee, killing interrupt handler!
Warning: many lost ticks.
Your time source seems to be instable or some driver is hogging interupts

note: starting this guest a couple of times in row does not always show the same kernel-panic but also other messages. But does not want to start.

In 3.0.10 and before I experienced many problems with the timer clock, running twice as fast or way to slow. One time somehow with 3.0.12 ( without changing anything to the Guest config ), I managed to get the OEL Guest to run, and the clock worked fine.

[amain]

VBox.log

[amain]

Screenshot kernel panic

[Frank Mehnert]

Please add the parameter nmi_watchdog=0 to the kernel command line. This problem is related to #3135.