Arch Linux

onexused

Member

Registered: 2009-10-07

Posts: 115

Virtualbox and a custom kernel

Virtualbox works fine with Arch's default kernel, but not with my custom kernel, although it used to.  I haven't used it in a month or two, and have done updates since then.  The custom kernel I'm using on all three machines I'll be talking about is vanilla 3.0.3 + tuxonice.  "Mercury" and "Aesculapius" both had their kernels built with a slightly modified config from "Posidon".  At some point in time, VBox has worked on all of them.  It is currently broken on Posidon and Aesculapius but works on Mercury.  Aesculapius is up to date as of yesterday (April 28th).  Posidon was last updated April 20th.  Mercury was last updated March 28th.

- It's not (just) the kernel version.  I've tried vanilla 3.3.3 with the same config on Aesculapius.  VBox was still broken. (VBox worked with Arch's linux 3.3.3 on Aesculapius.)
- It's not (just) the config.  Mercury (on which VBox works) has its kernel built from the same config as Posidon (with the processor optimization changed from Intel Dual Core to Intel Atom and a module for an Atheros wireless card and the built-in webcam added.  ca0106 is removed and intel-hda is added.)  Aesculapius was built from the same config as Posidon (with processor optimization changed from Intel Dual Core to Intel Pentium 4, ca0106 removed and emu101k(?) added, with a few other modules for USB webcams added.)
- I have virtualbox-source installed on all three machines, and the modules were built with no complaint with /usr/bin/vboxbuild since the last updates of any package.
- I have vboxdrv, vboxnetadp, and vboxnetflt modules loaded when attempting to start VMs.

"Broken" means:
- When starting a VM in VBox, a progress bar appears, "Starting virtual machine ..." and hangs at 0%.  Soon a second progress bar appears, "Starting virtual machine ... (2/2)" and hangs at 20%.  I cannot close the VM window except by killing all instances of VirtualBox, VBoxSVC, and VBoxXPCOMIPCD .
- dmesg contains this:

[ 4639.150180] warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
[ 4645.606088] BUG: unable to handle kernel paging request at 19330825
[ 4645.606094] IP: [<f8b7cad9>] VBoxHost_RTR0MemObjGetPagePhysAddr+0x13/0x67 [vboxdrv]
[ 4645.606106] *pde = 00000000 
[ 4645.606108] Oops: 0000 [#1] PREEMPT SMP 
[ 4645.606112] Modules linked in: fuse lgdt330x cx88_dvb videobuf_dvb cx88_vp3054_i2c nvidia(P) tuner_simple tuner_types tda9887 tda8290 snd_ca0106 snd_ac97_codec tuner cx8800 cx8802 cx88_alsa cx88
xx tveeprom btcx_risc videobuf_dma_sg videobuf_core i2c_algo_bit ac97_bus snd_rawmidi e1000e vboxnetflt vboxnetadp vboxdrv
[ 4645.606131] 
[ 4645.606134] Pid: 2481, comm: VirtualBox Tainted: P            3.0.3-toi #5 MapleTronic                      D975XBX2/D975XBX2
[ 4645.606139] EIP: 0060:[<f8b7cad9>] EFLAGS: 00210212 CPU: 1
[ 4645.606145] EIP is at VBoxHost_RTR0MemObjGetPagePhysAddr+0x13/0x67 [vboxdrv]
[ 4645.606148] EAX: 00000001 EBX: f5142010 ECX: 19330825 EDX: 19331825
[ 4645.606150] ESI: f8848000 EDI: f5133c10 EBP: e649ddcc ESP: e649dd60
[ 4645.606152]  DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
[ 4645.606155] Process VirtualBox (pid: 2481, ti=e649c000 task=f517ce60 task.ti=e649c000)
[ 4645.606157] Stack:
[ 4645.606158]  f8c673d8 f49d5110 00000000 00000000 f8cd585c f5142054 eda1b814 f
5a8a270
[ 4645.606164]  e67bf480 00000085 0001f50a 0001f50a f514204c f5142054 00025000 00025000
[ 4645.606170]  00000025 f8822000 00000000 000009a0 f517ce60 00200246 00200246 000003b1
[ 4645.606176] Call Trace:
[ 4645.606185]  [<c109f394>] ? __free_one_page+0xe4/0x1ba
[ 4645.606191]  [<c10a888e>] ? zone_page_state_add+0x12/0x1f
[ 4645.606195]  [<c109f510>] ? free_pcppages_bulk+0xa6/0xb6
[ 4645.606201]  [<c119e2db>] ? avc_has_perm_noaudit+0x2d0/0x2da
[ 4645.606208]  [<f8b7a177>] ? supdrvIOCtl+0x10a7/0x1fee [vboxdrv]
[ 4645.606216]  [<f8b7d4c3>] ? rtR0MemAllocEx+0x4a/0x9d [vboxdrv]
[ 4645.606222]  [<f8b7624f>] ? VBoxDrvLinuxIOCtl_4_1_12+0xea/0x16b [vboxdrv]
[ 4645.606228]  [<f8b76165>] ? SUPR0Printf+0x42/0x42 [vboxdrv]
[ 4645.606232]  [<c10cfa49>] ? do_vfs_ioctl+0x42d/0x463
[ 4645.606235]  [<c10cfac3>] ? sys_ioctl+0x44/0x65
[ 4645.606239]  [<c13c214c>] ? sysenter_do_call+0x12/0x22
[ 4645.606241] Code: 8d 34 8d fc ff ff ff 89 4c 24 04 e9 5c ff ff ff 83 c4 08 5b 5e 5f 5d c3 8b 0f 8b 47 04 8d 91 00 10 00 00 81 fa ff 1f 00 00 76 45 
[ 4645.606261]  39 10 12 61 19 75 3d 55 89 e5 57 53 8b 51 08 8d 5a ff 83 fb 
[ 4645.606271] EIP: [<f8b7cad9>] VBoxHost_RTR0MemObjGetPagePhysAddr+0x13/0x67 [vboxdrv] SS:ESP 0068:e649dd60
[ 4645.606279] CR2: 0000000019330825
[ 4645.606282] ---[ end trace 41ed8e68e0cd1714 ]---

- The vboxdrv module cannot be unloaded until after a reboot.
- Hibernation (tuxonice) fails back to X.
- Shutdown freezes some time after X is stopped.  I see no messages in the console other than those left over from start up.

Here are the packages (and versions) installed on Mercury (VBox works) (pastebinned to cut post length): http://bpaste.net/show/28064/
and for Posidon (VBox is broken): http://bpaste.net/show/28063/
and for your convenience, the diff -u: http://bpaste.net/show/28065/
What package(s) is/are causing the problem?  I've already tried downgrading linux-api-headers and glibc to no effect.  Alternately, what options should I change on my custom kernels?  I can post some kernel configs if that would be helpful.

Last edited by onexused (2012-04-29 19:31:23)

onexused

Member

Registered: 2009-10-07

Posts: 115

Re: Virtualbox and a custom kernel

Ideas anyone?

brebs

Member

Registered: 2007-04-03

Posts: 3,742

Re: Virtualbox and a custom kernel

You'll probably get a better response on the virtualbox bugzilla.

randomize46

Member

From: Moldova

Registered: 2011-11-16

Posts: 3

Re: Virtualbox and a custom kernel

I got the same problem with custom kernel-netbook, vboxdrv  is freshly built and loaded, but I got two progress bars, one at 0%  other at 20% and zombie unclosable window of hanged VM. Searching for solution...
Got it! Kernel was compiled with GCC 4.6, while modules with GCC 4.7.

Last edited by randomize46 (2012-06-01 08:04:06)

frank-vb

Member

Registered: 2013-01-16

Posts: 1

Re: Virtualbox and a custom kernel

This sounds like a gcc bug reported here: https://www.virtualbox.org/ticket/11035 and here: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55940