| Summary: | app-emulation/virtualbox-5.0.4 - Failed to open a session - The virtual machine '*' has terminated unexpectedly during startup with exit code 1 (0x1). | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Juergen Rose <rose> |
| Component: | Current packages | Assignee: | Lars Wendler (Polynomial-C) (RETIRED) <polynomial-c> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | emerge --info virtualbox | ||
After rebooting with 4.2.0-gentoo-r1 the issue disappeared. Most likely you tried to start the VM without loading the host's vbox kernel modules fist. I've observed the same and it seems like virtualbox-5.0.4 doesn't show the error window for lack of the kernel modules anymore like previous versions did. (In reply to Lars Wendler (Polynomial-C) from comment #2) > Most likely you tried to start the VM without loading the host's vbox kernel > modules fist. I've observed the same and it seems like virtualbox-5.0.4 > doesn't show the error window for lack of the kernel modules anymore like > previous versions did. I suppose, that was not the reason. I have a script vbox_init.sh: root@caiman:/root(7)# cat /root/scripts/vbox_init.sh #!/bin/bash ############################################################################ ### vbox_init.sh j.r. 30-Jul-14 ### ############################################################################ if [ -d /run/systemd/system ]; then if systemctl status libvirtd 2>&1 | grep "Active: active" ; then systemctl stop libvirtd fi else if /etc/init.d/libvirtd status 2>&1 | grep started >/dev/null ; then /etc/init.d/libvirtd stop fi fi if lsmod | grep kvm >/dev/null ; then module=`lsmod | grep kvm | ( read mod dummy; echo $mod)` rmmod $module fi for module in vbox{drv,netadp,netflt} ; do modprobe $module done I was running this script, and it did not help. Did this happen with earlier 5.0.x versions as well? If you don't know please try 5.0.2 version. Oh and please attach the vbox logfiles of a failed start to this bug. Now that vortialbox-5.0.8 is available I'd also like to know if you can still trigger this problem. |
Created attachment 411632 [details] emerge --info virtualbox Since some days I can't start any VM. E.g. I see: VirtualBox - Error Failed to open a session for the virtual machine Ubuntu-with-XIMEA. Details: The virtual machine 'Ubuntu-with-XIMEA' has terminated unexpectedly during startup with exit code 1 (0x1). Result Code: NS_ERROR_FAILURE (0x80004005) Component: MachineWrap Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd} I am running virtualbox-5.0.4 on linux-4.2.0-gentoo: root@cheetahnew:/usr/src/linux(51)# uname -a Linux cheetahnew 4.2.0-gentoo #1 SMP Tue Sep 1 18:12:32 CEST 2015 x86_64 Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz GenuineIntel GNU/Linux root@cheetahnew:/usr/src/linux(52)# qlist -Iv virtualbox app-emulation/virtualbox-5.0.4 app-emulation/virtualbox-additions-5.0.4 app-emulation/virtualbox-extpack-oracle-5.0.4.102546 app-emulation/virtualbox-modules-5.0.4 On similar systems the combination of virtualbox-5.0.4 on linux-4.2.0-gentoo works.