Ticket #5544 (closed defect: duplicate)

Opened 13 years ago

Last modified 13 years ago

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

Reported by: amain Owned by:
Component: guest smp Version: VirtualBox 3.0.12
Keywords: Cc:
Guest type: Linux Host type: Linux


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.


VBox.log Download (38.4 KB) - added by amain 13 years ago.
Schermafdruk-OEL 5.4 [Running] - Sun VirtualBox.png Download (23.4 KB) - added by amain 13 years ago.
Screenshot kernel panic

Change History

Changed 13 years ago by amain


Changed 13 years ago by amain

Screenshot kernel panic

comment:1 Changed 13 years ago by frank

  • Status changed from new to closed
  • Resolution set to duplicate

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

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use