Comment 3 for bug 399732

Revision history for this message
max (mikhmv) wrote :

dmesg | grep watchdog
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.31-3-generic root=UUID=b086dc0d-0fe7-4487-855b-494761765ca7 ro quiet acpi_osi=Linux nosplash [b]nmi_watchdog=0[/b]
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.31-3-generic root=UUID=b086dc0d-0fe7-4487-855b-494761765ca7 ro quiet acpi_osi=Linux nosplash[b] nmi_watchdog=0[/b]
[ 14.459621] vboxdrv: Trying to deactivate the NMI watchdog permanently...
[ 14.459625] vboxdrv: NMI watchdog either active or at least initialized. Please disable the NMI
[ 14.459626] vboxdrv: watchdog by specifying 'nmi_watchdog=0' at kernel command line.

Look like this bug can be fixed by virtualbox.
checking NMI could be done (in linux) by command:

    cat /proc/interrupts | grep NMI

in my case results:

    NMI: 0 0 Non-maskable interrupts

All 0 mean that NMI was initialized (because it present) but it is inactive.
This could be fixed by 2 ways:
First) Ask developers linux kernel to remove creation NMI records if NMI is inactive.
Second) Virtualbox developers could check value and if it is 0 assume than NMI is inactive.