Virtual machines refuse to start with a custom host kernel

Discussions related to using VirtualBox on Linux hosts.
Post Reply
aadfadfa
Posts: 1
Joined: 8. May 2012, 16:31

Virtual machines refuse to start with a custom host kernel

Post by aadfadfa »

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:

Code: Select all

[ 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.

Packages installed will be posted tomorrow because I've pastebinned the list to reduce post length.
What package(s) might be 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.
rsb
Posts: 1
Joined: 18. May 2012, 15:46

Re: Virtual machines refuse to start with a custom host kern

Post by rsb »

Identical symptoms running VirtualBox 4.1.14 r77440 on stock ubuntu kernel
Ubuntu 10.04 LTS - Linux masham 2.6.32-40-server #87-Ubuntu SMP Tue Mar 6 02:10:02 UTC 2012 x86_64 GNU/Linux

Code: Select all

[   29.983127] vboxdrv: Found 2 processor cores.
[   29.983355] VBoxDrv: dbg - g_abExecMemory=ffffffffa04ea6a0
[   29.983381] vboxdrv: fAsync=0 offMin=0x364 offMax=0x937
[   29.983445] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
[   29.983446] vboxdrv: Successfully loaded version 4.1.14 (interface 0x00190000).
[   30.200020] vboxpci: IOMMU not found (not compiled)
[   34.690032] eth0: no IPv6 routers present
[   36.960057] virbr0: no IPv6 routers present
[ 1235.412858] /dev/vmmon[6330]: Module vmmon: registered with major=10 minor=165
[ 1235.412869] /dev/vmmon[6330]: Initial HV check: anyNotCapable=0 anyUnlocked=0 anyEnabled=1 anyDisabled=0
[ 1235.412875] /dev/vmmon[6330]: HV check: anyNotCapable=0 anyUnlocked=0 anyEnabled=1 anyDisabled=0
[ 1235.412879] /dev/vmmon[6330]: Module vmmon: initialized
[ 1235.426606] /dev/vmci[6338]: VMCI: Driver initialized.
[ 1235.426699] /dev/vmci[6338]: Module vmci: registered with major=10 minor=53
[ 1235.426702] /dev/vmci[6338]: Module vmci: initialized
[ 1235.531954] /dev/vmnet: open called by PID 6395 (vmnet-bridge)
[ 1235.531965] /dev/vmnet: hub 0 does not exist, allocating memory.
[ 1235.531990] /dev/vmnet: port on hub 0 successfully opened
[ 1235.532008] bridge-eth0: up
[ 1235.532013] bridge-eth0: attached
[ 1236.691339] /dev/vmnet: open called by PID 6403 (vmnet-dhcpd)
[ 1236.691351] /dev/vmnet: hub 1 does not exist, allocating memory.
[ 1236.691378] /dev/vmnet: port on hub 1 successfully opened
[ 1236.718082] /dev/vmnet: open called by PID 6405 (vmnet-netifup)
[ 1236.718098] /dev/vmnet: port on hub 1 successfully opened
[ 1236.794130] /dev/vmnet: open called by PID 6421 (vmnet-dhcpd)
[ 1236.794143] /dev/vmnet: hub 8 does not exist, allocating memory.
[ 1236.794170] /dev/vmnet: port on hub 8 successfully opened
[ 1236.879599] /dev/vmnet: open called by PID 6425 (vmnet-natd)
[ 1236.879615] /dev/vmnet: port on hub 8 successfully opened
[ 1236.882453] /dev/vmnet: open called by PID 6426 (vmnet-netifup)
[ 1236.882469] /dev/vmnet: port on hub 8 successfully opened
[ 1247.610011] vmnet1: no IPv6 routers present
[ 1247.721260] vmnet8: no IPv6 routers present
[ 1812.187651] warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
[ 2272.237088] general protection fault: 0000 [#1] SMP 
[ 2272.237094] last sysfs file: /sys/devices/system/cpu/cpu1/online
[ 2272.237097] CPU 0 
[ 2272.237099] Modules linked in: vmnet vmblock vsock vmci vmmon binfmt_misc pci_stub vboxpci vboxnetadp vboxnetflt vboxdrv ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT xt_tcpudp iptable_filter ip_tables x_tables bridge stp kvm_intel kvm nfsd exportfs nfs lockd nfs_acl auth_rpcgss sunrpc fbcon tileblit font bitblit softcursor vga16fb vgastate snd_hda_codec_idt snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event usbhid snd_seq radeon snd_timer ttm drm_kms_helper snd_seq_device ppdev parport_pc lp parport snd i82975x_edac soundcore drm i2c_algo_bit snd_page_alloc edac_core hid ohci1394 ieee1394 sata_sil e1000e
[ 2272.237162] Pid: 6953, comm: VirtualBox Not tainted 2.6.32-40-server #87-Ubuntu         
[ 2272.237165] RIP: 0010:[<ffffc90006ff9b82>]  [<ffffc90006ff9b82>] 0xffffc90006ff9b82
[ 2272.237172] RSP: 0018:ffff880037393d00  EFLAGS: 00010006
[ 2272.237174] RAX: 0000000000000274 RBX: ffffc90006f71340 RCX: 0000000000000000
[ 2272.237177] RDX: ffffc90006f71340 RSI: 0000000000000000 RDI: 0000000000000006
[ 2272.237179] RBP: ffff880037393d58 R08: 000000000001ae80 R09: ffffc90006f71000
[ 2272.237182] R10: 0000000000040000 R11: 0000000000000000 R12: 0000000000000000
[ 2272.237184] R13: 0000000000000206 R14: ffff880037326fd0 R15: ffff8800373dd3c0
[ 2272.237188] FS:  00007f50d2ee1700(0000) GS:ffff880001c00000(0000) knlGS:0000000000000000
[ 2272.237190] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 2272.237193] CR2: 00007f50e70a61f0 CR3: 00000000792fb000 CR4: 00000000000026f0
[ 2272.237196] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 2272.237198] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 2272.237201] Process VirtualBox (pid: 6953, threadinfo ffff880037392000, task ffff8800601c4500)
[ 2272.237204] Stack:
[ 2272.237205]  ffffc90006ff98f2 0000000000000010 ffffffffa0501319 ffffffff81013c6e
[ 2272.237209] <0> ffff880037393e38 ffff880037393d38 00ffffff81039889 ffff880037393d58
[ 2272.237214] <0> ffff880037326fd0 ffff880060129810 ffffffffa0679440 ffff880037393d98
[ 2272.237220] Call Trace:
[ 2272.237235]  [<ffffffffa0501319>] ? g_abExecMemory+0x16c79/0x180000 [vboxdrv]
[ 2272.237242]  [<ffffffff81013c6e>] ? apic_timer_interrupt+0xe/0x20
[ 2272.237253]  [<ffffffffa0501c05>] g_abExecMemory+0x17565/0x180000 [vboxdrv]
[ 2272.237258]  [<ffffffff810f658e>] ? find_get_page+0x1e/0xa0
[ 2272.237262]  [<ffffffff810f7fab>] ? filemap_fault+0x8b/0x450
[ 2272.237274]  [<ffffffffa04d1d8d>] supdrvIOCtl+0x14cd/0x28b0 [vboxdrv]
[ 2272.237287]  [<ffffffffa04d65af>] ? rtR0MemAllocEx+0x7f/0x150 [vboxdrv]
[ 2272.237291]  [<ffffffff810f6897>] ? unlock_page+0x27/0x30
[ 2272.237302]  [<ffffffffa04cc3b1>] VBoxDrvLinuxIOCtl_4_1_14+0x111/0x1d0 [vboxdrv]
[ 2272.237308]  [<ffffffff81156fe2>] vfs_ioctl+0x22/0xa0
[ 2272.237313]  [<ffffffff8155e299>] ? thread_return+0x48/0x41f
[ 2272.237316]  [<ffffffff81157181>] do_vfs_ioctl+0x81/0x410
[ 2272.237321]  [<ffffffff81563223>] ? do_page_fault+0x153/0x3b0
[ 2272.237325]  [<ffffffff81157591>] sys_ioctl+0x81/0xa0
[ 2272.237329]  [<ffffffff81013172>] system_call_fastpath+0x16/0x1b
[ 2272.237331] Code: 00 0f 20 d8 4a 89 84 02 80 06 00 00 0f 20 e0 4a 89 84 02 88 06 00 00 48 83 e0 70 42 8b 8c 02 68 0a 00 00 23 4a 20 09 c8 0b 42 24 <0f> 22 e0 42 8b 84 02 50 0a 00 00 83 e0 04 0d 3b 00 00 80 0f 22 
[ 2272.237370] RIP  [<ffffc90006ff9b82>] 0xffffc90006ff9b82
[ 2272.237375]  RSP <ffff880037393d00>
[ 2272.237378] ---[ end trace ac596cbf5d40e369 ]---


cat /proc/cpuinfo
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 15
model name	: Intel(R) Core(TM)2 CPU          6300  @ 1.86GHz
stepping	: 6
cpu MHz		: 1596.000
cache size	: 2048 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 2
apicid		: 0
initial apicid	: 0
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
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 est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow
bogomips	: 3733.51
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		: 15
model name	: Intel(R) Core(TM)2 CPU          6300  @ 1.86GHz
stepping	: 6
cpu MHz		: 1596.000
cache size	: 2048 KB
physical id	: 0
siblings	: 2
core id		: 1
cpu cores	: 2
apicid		: 1
initial apicid	: 1
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
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 est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow
bogomips	: 3733.58
clflush size	: 64
cache_alignment	: 64
address sizes	: 36 bits physical, 48 bits virtual
power management:
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Virtual machines refuse to start with a custom host kern

Post by Perryg »

rsb wrote:Identical symptoms running VirtualBox 4.1.14 r77440 on stock ubuntu kernel
Ubuntu 10.04 LTS - Linux masham 2.6.32-40-server #87-Ubuntu SMP Tue Mar 6 02:10:02 UTC 2012 x86_64 GNU/Linux
Looks like you are running VMWare. Pick one or the other as two virtualizers that use VMX will not work.
Deb-multimedia Packages
Posts: 2
Joined: 27. May 2012, 11:55

Re: Virtual machines refuse to start with a custom host kern

Post by Deb-multimedia Packages »

Same problem here with Debian 4.1.14 packages and oracle 4.1.16 packages, kernel 3.3 and/or 3.4

Code: Select all

[ 159.166400] Oops: 0000 [#1] SMP 
[ 159.166402] Modules linked in: vboxdrv(O) bnep binfmt_misc fuse btusb snd_seq_dummy snd_seq_oss snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device nvidia(PO) ath3k crc32c_intel psmouse aesni_intel aes_i586 cryptd serio_raw pcspkr microcode 
[ 159.166410] 
[ 159.166411] Pid: 3737, comm: VirtualBox Tainted: P           O 3.4.0 #2 System manufacturer System Product Name/P8P67 REV 3.1 
[ 159.166414] EIP: 0060:[<f85d5aee>] EFLAGS: 00210297 CPU: 0 
[ 159.166418] EIP is at VBoxHost_RTR0MemObjGetPagePhysAddr+0x0/0x67 [vboxdrv] 
[ 159.166419] EAX: f05c4810 EBX: edb93810 ECX: f8319000 EDX: 00000000 
[ 159.166420] ESI: eb20dde4 EDI: 00000004 EBP: eb20ddc0 ESP: eb20dd54 
[ 159.166421]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 
[ 159.166422] CR0: 80050033 CR2: 00000004 CR3: 2b211000 CR4: 000407f0 
[ 159.166423] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000 
[ 159.166424] DR6: ffff0ff0 DR7: 00000400 
[ 159.166428]  f960831e f05c4810 00000000 00000000 f9677490 ef4f6054 00020200 ffffffff 
[ 159.166432]  00000000 00000001 f2f7d514 edb93810 00000000 ef4f6010 00000000 f8319000 
[ 159.166436]  0000002f 00000001 f8480000 00000e8c f088ece0 c1625f80 00000200 00000007 
[ 159.166445]  [<c11d137f>] ? xfs_iext_bno_to_ext+0xda/0x18a 
[ 159.166448]  [<c11becc9>] ? xfs_bmbt_get_all+0x11/0x15 
[ 159.166451]  [<c11b5a3a>] ? xfs_bmap_search_multi_extents+0x71/0xbd 
[ 159.166454]  [<c11bc9b5>] ? xfs_bmapi_read+0xd4/0x2c3 
[ 159.166459]  [<f85d319f>] ? supdrvIOCtl+0x10a7/0x1fee [vboxdrv] 
[ 159.166464]  [<f85d654f>] ? rtR0MemAllocEx+0x69/0xbc [vboxdrv] 
[ 159.166469]  [<f85cf276>] ? VBoxDrvLinuxIOCtl_4_1_16+0xea/0x16c [vboxdrv] 
[ 159.166471]  [<c11aa1b9>] ? xfs_free_eofblocks+0xc2/0x1dd 
[ 159.166475]  [<f85cf18c>] ? SUPR0Printf+0x69/0x69 [vboxdrv] 
[ 159.166478]  [<c10d5c7c>] ? vfs_ioctl+0x18/0x21 
[ 159.166480]  [<c10d6659>] ? do_vfs_ioctl+0x400/0x440 
[ 159.166483]  [<c1078c75>] ? __call_rcu+0x4d/0x11f 
[ 159.166485]  [<c1049a61>] ? should_resched+0x5/0x1e 
[ 159.166487]  [<c1440587>] ? _cond_resched+0x5/0x18 
[ 159.166489]  [<c10d8f9c>] ? dput+0x22/0xcc 
[ 159.166491]  [<c10cc00a>] ? fput+0x175/0x19c 
[ 159.166494]  [<c10dd56d>] ? mntput_no_expire+0x1f/0xd9 
[ 159.166496]  [<c10d66d3>] ? sys_ioctl+0x3a/0x5b 
[ 159.166498]  [<c144569f>] ? sysenter_do_call+0x12/0x28 
[ 159.166517] CR2: 0000000000000004 
[ 159.166519] ---[ end trace 39c2fd92a895b91d ]---
Deb-multimedia Packages
Posts: 2
Joined: 27. May 2012, 11:55

Re: Virtual machines refuse to start with a custom host kern

Post by Deb-multimedia Packages »

Deb-multimedia Packages"]Same problem here with Debian 4.1.14 packages and oracle 4.1.16 packages, kernel 3.3 and/or 3.4

The problem is gcc 4.7

A module rebuild with gcc 4.6 solve this problem.
Roonkin
Posts: 1
Joined: 11. Jan 2013, 19:40

Re: Virtual machines refuse to start with a custom host kern

Post by Roonkin »

Try Resetting the MAC Address in the VBOX settings before you switch it on
frank
Oracle Corporation
Posts: 3362
Joined: 7. Jun 2007, 09:11
Primary OS: Debian Sid
VBox Version: PUEL
Guest OSses: Linux, Windows
Location: Dresden, Germany
Contact:

Re: Virtual machines refuse to start with a custom host kern

Post by frank »

Deb-multimedia Packages wrote:Deb-multimedia Packages"]Same problem here with Debian 4.1.14 packages and oracle 4.1.16 packages, kernel 3.3 and/or 3.4

The problem is gcc 4.7

A module rebuild with gcc 4.6 solve this problem.
Very right. See here and here.
Post Reply