FS#21736 - Kernel26 2.6.36-3 incompatible with Virtualbox-bin

Attached to Project: Arch Linux
Opened by Eric Waller (ewaller) - Thursday, 18 November 2010, 06:52 GMT
Last edited by Ionut Biru (wonder) - Thursday, 02 December 2010, 01:13 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 10
Private No

Details

Description:

When using Kernel 2.6.36 as a host for Virtualbox, The host (x86_64 Arch) reboots without warning and with no indication as to problems in the logs. The system goes from a running state directly to what appears to be a power-on reset. The system is an HP Pavilion DV-4 with a Core 2 Duo processor.

Research on Google seems to indicate this is a problem with Virtualbox, and upstream seems to be working the problem.

Since 3.6.36 is in testing, I wanted to raise this issue before the decision to move it to core is made.


Steps to reproduce:
Boot 2.6.36 kernel. Insert vboxdrv and vboxnetflt modules. Launch Virtualbox and boot a guest (Microsoft Windows XP Professional SP3, in my case) Wait. System reboots in, at most, a few minutes.
This task depends upon

Closed by  Ionut Biru (wonder)
Thursday, 02 December 2010, 01:13 GMT
Reason for closing:  Fixed
Additional comments about closing:  virtualbox 3.2.12
Comment by Ionut Biru (wonder) - Thursday, 18 November 2010, 10:53 GMT
recompile the modules, rmmod vboxdrv vboxnetflt and reload the modules. there is no incompatibility with the kernel from testing
Comment by Pierre Schmitz (Pierre) - Thursday, 18 November 2010, 11:14 GMT
I have seen random reboot without the vbox modules being loaded. So this might not be related to vbox itself. It might be triggered due to using vbox though. The kernel itself seems to be quite broken.
Comment by Lukas Fleischer (lfleischer) - Thursday, 18 November 2010, 11:31 GMT
Yes, I've seen some others reporting this when using virtualbox_bin. Iirc there are (or at least have been) also some tickets on the VirtualBox bug tracker.
Comment by Eric Waller (ewaller) - Thursday, 18 November 2010, 15:53 GMT
>>recompile the modules, rmmod vboxdrv vboxnetflt and reload the modules.
I should have mentioned that I had done that when I installed the Kernel.
Comment by Eric Waller (ewaller) - Sunday, 21 November 2010, 20:19 GMT
I note that Kernel 2.6.36 has moved from testing to core. I expect this problem to become a little more mainstream.

pacman grabbed the new kernel this morning. I rebuilt the vbox drivers, and the problem still exists.
Comment by Ionut Biru (wonder) - Sunday, 21 November 2010, 20:24 GMT
kernel 2.6.36 is still in testing and last update was 20 days ago
Comment by Eric Waller (ewaller) - Sunday, 21 November 2010, 20:28 GMT
You are correct, my mistake. I thought I had testing turned off. I didn't, and it pacman grabbed the kernel from testing. My sincere apologies.
Comment by Greg Darke (skunktrader) - Friday, 26 November 2010, 03:54 GMT
Since upgrading to 2.6.36 today, and rebuilding the modules etc, virtualbox_bin freezes the host machine within a couple of seconds of starting any virtual machine. A hard reboot is required. Host machine is x86_64
Comment by Semen Soldatov (simplexe) - Friday, 26 November 2010, 16:57 GMT
with latest virtualbox-ose and kernel 2.6.36-3 from stable, system reboots in, at most, a few minutes.
revert kernel to 2.6.35.8 and virtualbox 3.2.10-2 - fixed this problem
Comment by Ionut Biru (wonder) - Friday, 26 November 2010, 17:01 GMT
do you guys have a CPU that doesn't support hardware visualization ?

cat /proc/cpuinfo
Comment by Semen Soldatov (simplexe) - Friday, 26 November 2010, 17:07 GMT
yes, my cpu doesn't support hardware virtualization

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 nx lm constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm
Comment by Ionut Biru (wonder) - Friday, 26 November 2010, 17:17 GMT
then report it to virtualbox/kernel bugtracker. something changed and one of them have to fix it. Is not our problem.
Comment by Semen Soldatov (simplexe) - Friday, 26 November 2010, 17:24 GMT
>> This bug will be most probably fixed in the next maintenance release. You could also install a test build of the upcoming release to verify that your problem is indeed fixed.

http://www.virtualbox.org/ticket/7605
Comment by Geraldo (geraldoav) - Saturday, 27 November 2010, 15:30 GMT
Test build found in this link solved the problem for me: http://www.virtualbox.org/ticket/7733#comment:4
Comment by Ionut Biru (wonder) - Saturday, 27 November 2010, 16:49 GMT
i don't think that the changes from ticker 7733 would fix virtualbox-ose. can somebody with this issue and using -ose version try that patch?
Comment by Ognjen Maric (oggy) - Tuesday, 30 November 2010, 13:25 GMT
FWIW: I'm experiencing the same problem on 2.6.36 and virtualbox-ose (CentOS guest), even though my cpuinfo shows the vmx flag. Downgrading to 2.6.35.8 fixes the problem as well.
Comment by Benedikt (bbbarch) - Tuesday, 30 November 2010, 22:38 GMT
I suffered from the same problem. Thanks for providing the hint with the testbuild geraldo. It works like a charm.
Comment by Ionut Biru (wonder) - Wednesday, 01 December 2010, 22:31 GMT
please check out 3.2.12. ose version should hit repos soonish
Comment by Greg Darke (skunktrader) - Thursday, 02 December 2010, 01:08 GMT
virtualbox_bin 3.2.12-1 fixes the problem for me.

Loading...