Arch Linux

moted

Member

Registered: 2010-06-25

Posts: 14

[SOLVED] Virtual Box PUEL causes reboot, seems to be a kernel issue

Edit: this issue has been resolved with VirtualBox version 3.2.12

About 1 - 2 minutes after launching a Windows VM vbox crashes and causes a hard reboot.  I've recompiled the modules and completely reinstalled the package from AUR with no joy.  Below are the package versions and segments of log files that are relatively pertinent to the issue.

virtualbox_bin 3.2.10-2
kernel26 2.6.36-3

depends:
'libidl2' 0.8.14-1
'libxcursor' 1.1.11-1
'libxinerama' 1.1.1-1
'libxslt' 1.1.26-2
'curl' 7.21.2-2
'gcc'  4.5.1-1
'make' 3.82-2
'kernel26-headers' 2.6.36-3
'python2' 2.7-3

Seems very similar to this issue: https://bbs.archlinux.org/viewtopic.php?id=105631

vbox-install.log

 
ld -r -m elf_x86_64 -T /usr/src/linux-2.6.36-ARCH/scripts/module-common.lds --build-id  -o /tmp/vbox.0/vboxdrv.ko /tmp/vbox.0/vboxdrv.o /tmp/vbox.0/vboxdrv.mod.o
make KBUILD_VERBOSE=1 -C /lib/modules/2.6.36-ARCH/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (                \
echo;                                                           \
echo "  ERROR: Kernel configuration is invalid.";               \
echo "         include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo "         Run 'make oldconfig && make prepare' on kernel src to fix it.";  \
echo;                                                           \
/bin/false)
mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*
make -f scripts/Makefile.build obj=/tmp/vbox.0

 ld -r -m elf_x86_64 -T /usr/src/linux-2.6.36-ARCH/scripts/module-common.lds --build-id  -o /tmp/vbox.0/vboxnetflt.ko /tmp/vbox.0/vboxnetflt.o /tmp/vbox.0/vboxnetflt.mod.o
make KBUILD_VERBOSE=1 -C /lib/modules/2.6.36-ARCH/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (                \
echo;                                                           \
echo "  ERROR: Kernel configuration is invalid.";               \
echo "         include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo "         Run 'make oldconfig && make prepare' on kernel src to fix it.";  \
echo;                                                           \
/bin/false)
mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*

kernel.log/dmesg.log/errrors.log

 
Nov  8 09:51:06 athos kernel: vboxdrv: Trying to deactivate the NMI watchdog permanently...
Nov  8 09:51:06 athos kernel: vboxdrv: Warning: 2.6.31+ kernel detected. Most likely the hardware performance
Nov  8 09:51:06 athos kernel: vboxdrv: counter framework which can generate NMIs is active. You have to prevent
Nov  8 09:51:06 athos kernel: vboxdrv: the usage of hardware performance counters by
Nov  8 09:51:06 athos kernel: vboxdrv:   echo 2 > /proc/sys/kernel/perf_counter_paranoid
Nov  8 09:51:06 athos kernel: vboxdrv: Found 2 processor cores.
Nov  8 09:51:06 athos kernel: VBoxDrv: dbg - g_abExecMemory=ffffffffa105f580
Nov  8 09:51:06 athos kernel: vboxdrv: fAsync=0 offMin=0x18f offMax=0x87f
Nov  8 09:51:06 athos kernel: vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
Nov  8 09:51:06 athos kernel: vboxdrv: Successfully loaded version 3.2.10 (interface 0x00140001).
Nov  8 09:52:25 athos kernel: warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)

everything.log

Nov  8 11:29:31 athos kernel: vboxdrv: Trying to deactivate the NMI watchdog permanently...
Nov  8 11:29:31 athos kernel: vboxdrv: Warning: 2.6.31+ kernel detected. Most likely the hardware performance
Nov  8 11:29:31 athos kernel: vboxdrv: counter framework which can generate NMIs is active. You have to prevent
Nov  8 11:29:31 athos kernel: vboxdrv: the usage of hardware performance counters by
Nov  8 11:29:31 athos kernel: vboxdrv:   echo 2 > /proc/sys/kernel/perf_counter_paranoid
Nov  8 11:29:31 athos kernel: vboxdrv: Found 2 processor cores.
Nov  8 11:29:31 athos kernel: VBoxDrv: dbg - g_abExecMemory=ffffffffa0126580
Nov  8 11:29:31 athos kernel: vboxdrv: fAsync=0 offMin=0x198 offMax=0x1342
Nov  8 11:29:31 athos kernel: vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
Nov  8 11:29:31 athos kernel: vboxdrv: Successfully loaded version 3.2.10 (interface 0x00140001).

cpu info

processor    : 0
vendor_id    : GenuineIntel
cpu family    : 6
model        : 23
model name    : Intel(R) Core(TM)2 Duo CPU     P8700  @ 2.53GHz
stepping    : 10
cpu MHz        : 2526.876
cache size    : 3072 KB
physical id    : 0
siblings    : 2
core id        : 0
cpu cores    : 2
apicid        : 0
initial apicid    : 0
fpu        : yes
fpu_exception    : yes
cpuid level    : 13
wp        : yes
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm ida dts tpr_shadow vnmi flexpriority
bogomips    : 5055.32
clflush size    : 64
cache_alignment    : 64
address sizes    : 36 bits physical, 48 bits virtual
power management:

processor    : 1
vendor_id    : GenuineIntel
cpu family    : 6
model        : 23
model name    : Intel(R) Core(TM)2 Duo CPU     P8700  @ 2.53GHz
stepping    : 10
cpu MHz        : 2526.876
cache size    : 3072 KB
physical id    : 0
siblings    : 2
core id        : 1
cpu cores    : 2
apicid        : 1
initial apicid    : 1
fpu        : yes
fpu_exception    : yes
cpuid level    : 13
wp        : yes
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm ida dts tpr_shadow vnmi flexpriority
bogomips    : 5055.55
clflush size    : 64
cache_alignment    : 64
address sizes    : 36 bits physical, 48 bits virtual
power management:

Last edited by moted (2010-12-04 00:19:53)

Max__

Member

Registered: 2010-10-06

Posts: 4

Re: [SOLVED] Virtual Box PUEL causes reboot, seems to be a kernel issue

I am having a similar issue, I haven't used vbox for a few days, until just now, several upgrades have taken place.
Namely the kernel upgrade and udev come to mind, however after I rebuilt the kernel modules and attempted to use vbox puel it seems to have stopped all events and thrown the laptop on a "loop" type thing. That's the best I can describe it coming from a programming point of view, where it blocks all events until vbox finishes or something it is doing finishes but it never finishes causing me to hard reboot because no key events or mouse events get through(just freezes). Normally in a program I'd just control-c it, for my own that is, and then hunt down the loop, although this loop seems to be at a much deeper level.

Although my issue doesn't happen in any given timeframe, just at a specific point, when it gets to the Windows Logo during the boot after it gets through grub and all of that(I have a dual boot vbox setup).

I was going to post my own bug report here, although since I'm new at this, I'll just share my thoughts in your thread(Hope I'm not breaking any rules or disturbing anyone by posting in your thread, although I didn't see any rules in this forum)

I'm using the same virtualbox_bin version.

Most of the packages are the same version as your except kernel26-headers 2.6.36.1-3 & kernel26 2.6.361-3

Pulled the versions from pacman -Qi <package>

Cpu info(underclocked using cpufrequtils ondemand) pulled from lscpu

Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
CPU(s):                4
Thread(s) per core:    2
Core(s) per socket:    2
CPU socket(s):         1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 37
Stepping:              2
CPU MHz:               1199.000
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:   

Anyhow hope I helped in some way.

Last edited by Max__ (2010-11-24 20:02:30)

skunktrader

Member

From: Brisbane, Australia

Registered: 2010-02-14

Posts: 1,543

Re: [SOLVED] Virtual Box PUEL causes reboot, seems to be a kernel issue

Same issue here.  Since upgrading to 2.6.36, virtualbox_bin freezes the host requiring a hard reboot within a couple of seconds after starting any virtual machine

falconindy

Developer

From: New York, USA

Registered: 2009-10-22

Posts: 4,111

Website

Re: [SOLVED] Virtual Box PUEL causes reboot, seems to be a kernel issue

Rebuild the vbox kernel modules... standard fare after a kernel upgrade.

---

blog | ±github

airstep

Member

Registered: 2008-01-21

Posts: 54

Re: [SOLVED] Virtual Box PUEL causes reboot, seems to be a kernel issue

Same here and after rebuild vbox kernel modules - it didn't help me.

airstep

Member

Registered: 2008-01-21

Posts: 54

Re: [SOLVED] Virtual Box PUEL causes reboot, seems to be a kernel issue

Represents all day randomly now. Can't normal work.

Last edited by airstep (2010-11-26 13:47:38)

wonder

Developer

From: Bucharest, Romania

Registered: 2006-07-05

Posts: 5,941

Website

Re: [SOLVED] Virtual Box PUEL causes reboot, seems to be a kernel issue

http://www.virtualbox.org/ticket/7605

---

Give what you have. To someone, it may be better than you dare to think.

skunktrader

Member

From: Brisbane, Australia

Registered: 2010-02-14

Posts: 1,543

Re: [SOLVED] Virtual Box PUEL causes reboot, seems to be a kernel issue

Thanks wonder

airstep

Member

Registered: 2008-01-21

Posts: 54

Re: [SOLVED] Virtual Box PUEL causes reboot, seems to be a kernel issue

Done.

airstep

Member

Registered: 2008-01-21

Posts: 54

Re: [SOLVED] Virtual Box PUEL causes reboot, seems to be a kernel issue

Downgrade to kernel26 2.6.35.8-1 helps a lot. Now virtualbox-ose 3.2.10-3 works good. So this bug depends on kernel issue.

nixpunk

Member

Registered: 2009-11-23

Posts: 271

Re: [SOLVED] Virtual Box PUEL causes reboot, seems to be a kernel issue

Same here running x86_64 and Virtualbox-OSE.  Luckily, I am not using VBox for work ATM.

skunktrader

Member

From: Brisbane, Australia

Registered: 2010-02-14

Posts: 1,543

Re: [SOLVED] Virtual Box PUEL causes reboot, seems to be a kernel issue

virtualbox_bin 3.2.12-1 fixes the problem for me

airstep

Member

Registered: 2008-01-21

Posts: 54

Re: [SOLVED] Virtual Box PUEL causes reboot, seems to be a kernel issue

+1 For me too.

starfry

Member

From: Surrey, UK

Registered: 2010-08-18

Posts: 230

Re: [SOLVED] Virtual Box PUEL causes reboot, seems to be a kernel issue

3.2.12 installed and being tested... up and running for 3 hours now, no reboots. looking good

Last edited by starfry (2010-12-02 20:16:25)

moted

Member

Registered: 2010-06-25

Posts: 14

Re: [SOLVED] Virtual Box PUEL causes reboot, seems to be a kernel issue

Confirmed that the issue is now resolved with 3.2.12

franco4657

Member

From: Italy

Registered: 2006-10-24

Posts: 11

Re: [SOLVED] Virtual Box PUEL causes reboot, seems to be a kernel issue

virtualbox_bin 3.2.12-1 + kernel26 2.6.36-3 + nvidia-96xx 96.43.19-2 = freeze pc while launch w7
I did downgrade to virtualbox_bin 3.2.10-1 + kernel26 2.6.35-8 + nvidia-96xx 96.43.18-2....for now