FS#20972 - [kernel26-headers] 2.6.35.6-1 breaks virtualbox

Attached to Project: Arch Linux
Opened by Mike DeTuri (Scrivener) - Tuesday, 28 September 2010, 07:35 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 29 September 2010, 06:20 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description:
I installed kernel 2.6.35.6-1 using pacman -Syu and rebooted. Then I installed the latest version of VirtualBox from AUR with yaourt -Syu --aur. I turned off my computer for a few hours. When I came back I was able to start VirtualBox, but when I started a guest VM my system froze.

I tried recompiling the Vbox modules with /etc/rc.d/vboxdrv setup and rebooted again, but that didn't help.

I got VirtualBox working again by downgrading to kernel 2.6.35.5-1 and the headers for kernel 2.6.35.5-1. Then I recompiled the Vbox modules and VirtualBox is working fine again.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Wednesday, 29 September 2010, 06:20 GMT
Reason for closing:  Fixed
Additional comments about closing:  2.6.35.6-2
Comment by Gaetan Bisson (vesath) - Tuesday, 28 September 2010, 10:52 GMT
For what it's worth, it works fine for me with the i686 version of virtualbox-ose from [community].
Could you try if this package works for you? And maybe be a little bit more specific about your setting?
Comment by Thomas Hopkins (Snowknight) - Tuesday, 28 September 2010, 13:19 GMT
I have the same issue with virtualbox_bin from AUR. But I have issues with virtualbox-ose as well. Yes, I rebuilt VirtualBox's kernel modules against the kernel 2.6.35.6 headers each time.

I rebooted my machine after virtualbox_bin (3.2.8-5) froze on kernel 2.6.35.6-1. I tried VirtualBox before loading any other applications. (Granted, Gnome/GDM/Compiz run at boot.) VirtualBox threw an error after I tried to boot my Windows XP virtual machine: "Failed to open a session for the virtual machine xp-machine. No error info. Result Code: NS_ERROR_FAILURE (0x80004005) Component: ProgressProxy Interface: IProgress [...]." I saved a screenshot of this error and have attached it to this post. After I attempted to close VirtualBox, my system became unstable: I opened my system's rc.conf to remove the vboxdrv module from my MODULES array, and nano seemed to freeze. I hit my machine's reset button and eventually discovered that there must've been some problem writing rc.conf; I restored it with a livecd. I have a VBox log from around then. I have attached it to this message.

I used virtualbox-ose (3.2.8-3) after this and still couldn't load my XP VM or run new VMs. Virtualbox-ose threw an error (VERR_MM_HYPER_NO_MEMORY) and caused similar system instability. I have attached a VBox log from one of my attempts.

I, too, moved back to kernel 2.6.35.5, and VirtualBox works.
   virtualbox_bin-error.png (14.7 KiB)
   VBox_PUEL.log (0.9 KiB)
   VBox_OSE.log (40.1 KiB)
Comment by Mauro Santos (R00KIE) - Tuesday, 28 September 2010, 15:21 GMT
I am experiencing this too, I did rebuild and use the rebuilt modules before retrying it.
The error message and log contents are also similar.
Comment by Mike DeTuri (Scrivener) - Tuesday, 28 September 2010, 15:39 GMT
I'm not sure what else I can add to the comments already posted. I'm running Arch x86_64 on an Intel CPU, Core2Quad Q6600. I have 4 gigs of RAM. The latest version of VirtualBox in AUR works fine with kernel 2.6.35.5.
Comment by Tobias Powalowski (tpowa) - Tuesday, 28 September 2010, 18:22 GMT
Please try -2 package
Comment by Green (The_Green_Arrow) - Tuesday, 28 September 2010, 18:31 GMT
I can confirm this bug too (for now it's still unconfirmed)
Comment by Patrick Fernie (nogoma) - Tuesday, 28 September 2010, 19:28 GMT
This bug was causing the insmod loop (https://bbs.archlinux.org/viewtopic.php?pid=832582#p832582) for me w/ the VMWare modules; I can confirm that upgrading to -2 (and recompiling VMware modules) has fixed it here.
Comment by Mauro Santos (R00KIE) - Tuesday, 28 September 2010, 20:58 GMT
I confirm that -2 works for me.
Comment by Mike DeTuri (Scrivener) - Tuesday, 28 September 2010, 22:53 GMT
I also confirm that -2 works for me.
Comment by Thomas Hopkins (Snowknight) - Wednesday, 29 September 2010, 03:52 GMT
-2 fixes the problem for me also.

Loading...