Find the answer to your Linux question:
Results 1 to 3 of 3
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1

    [SOLVED] VirtualBox: Failed to open a session for the virtual machine


    Hello, i'am using gentoo linux. After some system's updates VirtualBox stoped loading any virtual machine with error:

    Code:
    Failed to open a session for the virtual machine.
    Virtual machine has terminated unexpectedly during startup.
    
    Details:
    Result Code: NS_ERROR_FAILURE (0x80004005)
    Component: Machine
    Interface: IMachine {99404f50-dd10-40d3-889b-dd2f79f1e95e}
    Kernel log

    Code:
    Apr 06 12:22:49 [kernel] [  815.071881] vboxdrv: Trying to deactivate the NMI watchdog permanently...
    Apr 06 12:22:49 [kernel] [  815.071891] vboxdrv: Successfully done.
    Apr 06 12:22:49 [kernel] [  815.071897] vboxdrv: Found 2 processor cores.
    Apr 06 12:22:49 [kernel] [  815.072149] VBoxDrv: dbg - g_abExecMemory=ffffffffa033b040
    Apr 06 12:22:49 [kernel] [  815.072188] vboxdrv: fAsync=1 offMin=0x20a9e0 offMax=0x20a9e0
    Apr 06 12:22:49 [kernel] [  815.074559] vboxdrv: TSC mode is 'asynchronous', kernel timer mode is 'normal'.
    Apr 06 12:22:49 [kernel] [  815.074568] vboxdrv: Successfully loaded version 3.1.4 (interface 0x00100001).
    Apr 06 12:23:02 [kernel] [  828.678193] BUG: unable to handle kernel NULL pointer dereference at 0000000000000064
    Apr 06 12:23:02 [kernel] [  828.678208] IP: [<ffffffff8156ccba>] _spin_lock_irq+0xa/0x20
    Apr 06 12:23:02 [kernel] [  828.678231] PGD 3c0bd067 PUD 3b46a067 PMD 0 
    Apr 06 12:23:02 [kernel] [  828.678260] CPU 0 
    Apr 06 12:23:02 [kernel] [  828.678264] Modules linked in: vboxnetflt vboxnetadp vboxdrv snd_seq snd_seq_device snd_hda_codec_atihdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec fglrx(P) snd_hwdep snd_pcm snd_timer snd snd_page_alloc
    Apr 06 12:23:02 [kernel] [  828.678300] Pid: 3110, comm: VirtualBox Tainted: P           2.6.31-gentoo-r6 #12 Satellite A210
    Apr 06 12:23:02 [kernel] [  828.678307] RIP: 0010:[<ffffffff8156ccba>]  [<ffffffff8156ccba>] _spin_lock_irq+0xa/0x20
    Apr 06 12:23:02 [kernel] [  828.678322] RSP: 0018:ffff880064813bd8  EFLAGS: 00010096
    Apr 06 12:23:02 [kernel] [  828.678327] RAX: 0000000000000100 RBX: 0000000000000060 RCX: 0000000000000000
    Apr 06 12:23:02 [kernel] [  828.678334] RDX: ffff88005755a090 RSI: 0000000000000000 RDI: 0000000000000064
    Apr 06 12:23:02 [kernel] [  828.678340] RBP: ffff880064813bd8 R08: 0000000000000000 R09: ffff88005755a090
    Apr 06 12:23:02 [kernel] [  828.678346] R10: 0000000000000003 R11: ffff880064813e98 R12: 0000000000000060
    Apr 06 12:23:02 [kernel] [  828.678352] R13: 0000000000000064 R14: ffff88007661ebd0 R15: ffff880063dd3c10
    Apr 06 12:23:02 [kernel] [  828.678360] FS:  00007fa279a62700(0000) GS:ffff8800019c1000(0000) knlGS:0000000000000000
    Apr 06 12:23:02 [kernel] [  828.678367] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Apr 06 12:23:02 [kernel] [  828.678373] CR2: 0000000000000064 CR3: 000000003b474000 CR4: 00000000000006f0
    Apr 06 12:23:02 [kernel] [  828.678379] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    Apr 06 12:23:02 [kernel] [  828.678385] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    Apr 06 12:23:02 [kernel] [  828.678392] Process VirtualBox (pid: 3110, threadinfo ffff880064812000, task ffff88007661ebd0)
    Apr 06 12:23:02 [kernel] [  828.678402]  ffff880064813c28 ffffffff8156ca6c 0000000000000002 0000000000000000
    Apr 06 12:23:02 [kernel] [  828.678412] <0> 0000000000000058 0000000000000008 0000000000001000 0000000000000060
    Apr 06 12:23:02 [kernel] [  828.678423] <0> 0000000000000001 0000000000001000 ffff880064813c38 ffffffff8156cb1b
    Apr 06 12:23:02 [kernel] [  828.678447]  [<ffffffff8156ca6c>] __down_write_nested+0x1c/0xc0
    Apr 06 12:23:02 [kernel] [  828.678456]  [<ffffffff8156cb1b>] __down_write+0xb/0x10
    Apr 06 12:23:02 [kernel] [  828.678466]  [<ffffffff8156c169>] down_write+0x19/0x20
    Apr 06 12:23:02 [kernel] [  828.678510]  [<ffffffffa032f23c>] rtR0MemObjNativeMapUser+0x9c/0x2b0 [vboxdrv]
    Apr 06 12:23:02 [kernel] [  828.678544]  [<ffffffffa032c70e>] RTR0MemObjMapUser+0x11e/0x220 [vboxdrv]
    Apr 06 12:23:02 [kernel] [  828.678572]  [<ffffffffa032638e>] SUPR0GipMap+0x20e/0x240 [vboxdrv]
    Apr 06 12:23:02 [kernel] [  828.678601]  [<ffffffffa0328dac>] supdrvIOCtl+0xbbc/0x2450 [vboxdrv]
    Apr 06 12:23:02 [kernel] [  828.678633]  [<ffffffffa032e3f5>] ? rtMemAlloc+0x85/0xf0 [vboxdrv]
    Apr 06 12:23:02 [kernel] [  828.678661]  [<ffffffffa032e3f5>] ? rtMemAlloc+0x85/0xf0 [vboxdrv]
    Apr 06 12:23:02 [kernel] [  828.678688]  [<ffffffffa032e308>] ? rtMemFree+0x28/0x90 [vboxdrv]
    Apr 06 12:23:02 [kernel] [  828.678713]  [<ffffffffa03252c3>] VBoxDrvLinuxIOCtl+0x103/0x1c0 [vboxdrv]
    Apr 06 12:23:02 [kernel] [  828.678725]  [<ffffffff8110a911>] vfs_ioctl+0x31/0xa0
    Apr 06 12:23:02 [kernel] [  828.678734]  [<ffffffff8110aa9a>] do_vfs_ioctl+0x8a/0x5c0
    Apr 06 12:23:02 [kernel] [  828.678743]  [<ffffffff8110b069>] sys_ioctl+0x99/0xa0
    Apr 06 12:23:02 [kernel] [  828.678755]  [<ffffffff8100beab>] system_call_fastpath+0x16/0x1b
    Apr 06 12:23:02 [kernel] [  828.678829] RIP  [<ffffffff8156ccba>] _spin_lock_irq+0xa/0x20
    Apr 06 12:23:02 [kernel] [  828.678839]  RSP <ffff880064813bd8>
    Apr 06 12:23:02 [kernel] [  828.678851] ---[ end trace f575b629973d87a7 ]---
    I'am testing unstable CFLAGS,CXXFLAGS and LDFLAGS. So, i've rebuilded all VirtualBox dependencies with safe flags, then i've recompiled most of the sys-* packages also with safe flags. However VirtualBox still doesn't work.

    UPD: virtualbox-bin-3.1.4
    UPD2: 3.1.6 and ose-versions crashes with same errors

  2. #2

    Talking Solved...

    Great... It is my style... More than a week i tried to solve this problem. So i posted the question and found the solution in less than 24 hours... And again thread is monologue. =)

    Solution: just upgrade to kernel 2.6.32. It is strange, cause it worked on 2.6.31 kernel.

  3. #3

    Another solution(better)

    I've found new solution, much better, than upgading to new kernel. The problem was caused by incorrect .config file into the linux-source directory.(it happened after building non-working kernel). So i just returned working config and rebuilded virtualbox-modules.

  4. $spacer_open
    $spacer_close

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •