Virtual machine terminated unexpectedly with exit code 1

Discussions related to using VirtualBox on Linux hosts.
Post Reply
Detergency
Posts: 7
Joined: 19. Jan 2012, 17:41
Primary OS: openSUSE
VBox Version: OSE other
Guest OSses: Windows XP SP3

Virtual machine terminated unexpectedly with exit code 1

Post by Detergency »

I'm using Virtualbox 4.3.14 under openSUSE 13.1.

VB used to work fine until a few days ago.
Now, when I try to start a virtual machine, it displays this error:

Code: Select all

Failed to open a session for the virtual machine Windows XP.
The virtual machine 'Windows XP' has terminated unexpectedly during startup with exit code 1.
A second error window tells me:

Code: Select all

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing

'/etc/init.d/vboxdrv setup'

as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.
So I've run this command in a console:
sudo /etc/init.d/vboxdrv setup

The output is:
Stopping VirtualBox kernel modules done
Removing old VirtualBox pci kernel module done
Removing old VirtualBox netadp kernel module done
Removing old VirtualBox netflt kernel module done
Removing old VirtualBox kernel module done
Recompiling VirtualBox kernel modules done
Starting VirtualBox kernel modules failed
(modprobe vboxdrv failed. Please use 'dmesg' to find out why)
I've attached the output of dmesg.
I haven't attached vbox-install.log, because it's 6 MB, but here are the first few lines that seem relevant:

Code: Select all

/usr/share/virtualbox/src/vboxhost/build_in_tmp: line 62: make: command not found
make KBUILD_VERBOSE=1 SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 CONFIG_MODULE_SIG= -C /lib/modules/3.11.6-4-desktop/build modules
make -C /usr/src/linux-3.11.6-4-obj/i386/desktop \
KBUILD_SRC=/usr/src/linux-3.11.6-4 \
KBUILD_EXTMOD="/tmp/vbox.0" -f /usr/src/linux-3.11.6-4/Makefile \
modules
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (                \
echo >&2;                                                       \
echo >&2 "  ERROR: Kernel configuration is invalid.";           \
echo >&2 "         include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 "         Run 'make oldconfig && make prepare' on kernel src to fix it.";      \
echo >&2 ;                                                      \
/bin/false)
Even though I have "make" installed, the first line of vbox-install.log says that it isn't.
Attachments
dmesg.txt
(126.29 KiB) Downloaded 22 times
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 machine terminated unexpectedly with exit code 1

Post by Perryg »

The lines you have posted are just programming code and do not reflect the cause of your error. It appears you have had a kernel update though and that can cause issues if you do not have dkms installed. Make sure that you have matching headers and devel packages that match your running kernel.
Detergency
Posts: 7
Joined: 19. Jan 2012, 17:41
Primary OS: openSUSE
VBox Version: OSE other
Guest OSses: Windows XP SP3

Re: Virtual machine terminated unexpectedly with exit code 1

Post by Detergency »

I've been able to solve the problem myself.
Looking at the output of dmesg again, I noticed the following lines:

[ 12.540915] vmap allocation for size 1052672 failed: use vmalloc=<size> to increase size.
[ 12.540057] vmap allocation for size 1052672 failed: use vmalloc=<size> to increase size.
[ 12.541841] vmap allocation for size 1052672 failed: use vmalloc=<size> to increase size.
etc.

So I set vmalloc=256MB as described here:
http://www.mythtv.org/wiki/Common_Probl ... mall#grub2

Now I can recompile the VB kernel modules and run VB again.
Cause of the problem was most likely the graphics card I installed recently.
Unlke the onboard graphics chip I was using before, the graphics card needs virtual address space.
Post Reply