VBox 6.1 cannot start any VM

Discussions related to using VirtualBox on Linux hosts.
Post Reply
Totalvirtual
Posts: 4
Joined: 18. Apr 2019, 04:20
Primary OS: openSUSE
VBox Version: OSE other
Guest OSses: Windows

VBox 6.1 cannot start any VM

Post by Totalvirtual »

Hi,

I just installed 6.1.0_135406_openSUSE150-1 from the Oracle repo.
Before I had the openSUSE version installed which I wiped from the system, also wiped the old kernel modules.

Now installed VBox 6.1 and the corresponding kernel modules vboxdrv,vboxnetflt,vboxnetadp. By the way, is vboxpci.ko obsolete? It does not exit in 6.1.

Okay, when now trying to start any VM I get this error:

Code: Select all

NS_ERROR_FAILURE (0x80004005)
MachineWrap
Interface: 
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
The only thing I find strange is, there seem to be no vboxpci module and no source code for vboxpci. Is this module obsolete with VB 6.1?

Below I can give you the content of VBoxSVC.log.

Thanks for any hints!

Code: Select all

00:00:00.000604 main     VirtualBox XPCOM Server 6.1.0 r135406 linux.amd64 (Dec 10 2019 17:18:14) release log
00:00:00.000614 main     Log opened 2020-01-10T04:33:19.895676000Z
00:00:00.000618 main     Build Type: release
00:00:00.000634 main     OS Product: Linux
00:00:00.000638 main     OS Release: 5.4.7-2.tp
00:00:00.000642 main     OS Version: #2 SMP PREEMPT Mon Jan 6 01:40:09 CET 2020
00:00:00.000710 main     DMI Product Name: 20KV0006GE
00:00:00.000725 main     DMI Product Version: ThinkPad E585
00:00:00.000755 main     Firmware type: UEFI
00:00:00.001631 main     Secure Boot: Enabled
00:00:00.001748 main     Host RAM: 31721MB (30.9GB) total, 28411MB (27.7GB) available
00:00:00.001760 main     Executable: /usr/lib/virtualbox/VBoxSVC
00:00:00.001763 main     Process ID: 31678
00:00:00.001767 main     Package type: LINUX_64BITS_OPENSUSE_15_0
00:00:00.004054 main     IPC socket path: /tmp/.vbox-foobar-ipc/ipcd
00:00:00.109237 nspr-2   VirtualBox: object creation starts
00:00:00.109412 nspr-2   Home directory: '/home/foobar/.config/VirtualBox'
00:00:00.109721 nspr-2   Loading settings file "/home/foobar/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:00:00.114113 nspr-2   USB: Unknown USB device detected (idVendor: 0x0cf3, idProduct: 0xe500)
00:00:00.114380 nspr-2   Successfully initialised host USB using sysfs
00:00:00.121856 nspr-2   Failed to retrive disk info: getDiskName(/dev/mapper/cr_root) --> cr_root
00:00:00.122495 nspr-2   HostDnsMonitor: initializing
00:00:00.122968 nspr-2   NAT: resolv.conf: nameserver 127.0.0.1
00:00:00.122987 nspr-2   NAT: resolv.conf: nameserver 192.168.178.1
00:00:00.123020 nspr-2   HostDnsMonitor: updating information
00:00:00.123084 nspr-2   HostDnsMonitor: old information
00:00:00.123092 nspr-2     no server entries
00:00:00.123103 nspr-2     no domain set
00:00:00.123113 nspr-2     no search string entries
00:00:00.123124 nspr-2   HostDnsMonitor: new information
00:00:00.123134 nspr-2     server 1: 127.0.0.1
00:00:00.123146 nspr-2     server 2: 192.168.178.1
00:00:00.123156 nspr-2     domain: fritz.box
00:00:00.123167 nspr-2     search string 1: fritz.box
00:00:00.129524 nspr-2   VD: VDInit finished with VINF_SUCCESS
00:00:00.138850 nspr-2   Loading settings file "/home/virtualbox-drives/Windows95/Windows95.vbox" with version "1.17-linux"
00:00:00.140472 nspr-2   Loading settings file "/home/virtualbox-drives/Win7Profess_x64/Win7Profess_x64.vbox" with version "1.17-linux"
00:00:00.142358 nspr-2   OCI: Local config file '/home/foobar/.config/VirtualBox/oci_config' does not exist
00:00:00.142393 nspr-2   OCI: Original config file '/home/foobar/.oci/config' does not exist
00:00:00.142402 nspr-2   OCI: Reading profiles finished with status NS_OK
00:00:00.142416 nspr-2   ExtPack: Created cloud provider 'OCI' (hrc=NS_OK)
00:00:00.142442 nspr-2   VirtualBox: object created
00:00:03.974135 nspr-2   Launched VM: 3691786416 pid: 31706 (0x7bda) frontend: GUI/Qt name: Windows95
00:00:04.475104 Watcher  ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={85632c68-b5bb-4316-a900-5eb28d3413df} aComponent={MachineWrap} aText={The virtual machine 'Windows95' has terminated unexpectedly during startup with exit code 1 (0x1)}, preserve=false aResultDetail=0
00:05:37.728208 nspr-3   Saving settings file "/home/foobar/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:05:38.155244 nspr-3   Saving settings file "/home/foobar/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:05:43.875699 main     VirtualBox: object deletion starts
00:05:43.875793 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/home/virtualbox-drives/Windows95/Windows95.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:05:43.876092 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/home/virtualbox-drives/Win7Profess_x64/Win7Profess_x64.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:05:43.876725 main     HostDnsMonitor: shutting down ...
00:05:43.877326 main     HostDnsMonitor: shut down
00:05:44.074226 Watcher  ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={d0a0163f-e254-4e5b-a1f2-011cf991c38d} aComponent={VirtualBoxWrap} aText={The object is not ready}, preserve=false aResultDetail=0
00:05:48.881439 main     {00007fb7dc0194d0} HostPowerServiceLinux::~HostPowerServiceLinux: RTThreadWait() for 5000 ms failed with VERR_TIMEOUT
00:05:48.882440 main     VirtualBox: object deleted

Totalvirtual
Posts: 4
Joined: 18. Apr 2019, 04:20
Primary OS: openSUSE
VBox Version: OSE other
Guest OSses: Windows

Re: VBox 6.1 cannot start any VM (WORKAROUND available)

Post by Totalvirtual »

I have now found a workaround

Root of the problem is, VirtualBox from Oracle is being installed suidroot.
The following commands set the permissions in a way, VBox can start and run.
These commands may have to be executed every time the computer starts and VBox is being updated. Best create a script for it.

Code: Select all

Do it as root

cd /usr/lib/virtualbox/
chmod 0755 {VBox{Headless,Net{AdpCtl,DHCP,NAT},SDL,VolInfo},VirtualBox}
chmod 4755 {VBox{Headless,Net{AdpCtl,DHCP,NAT},SDL,VolInfo},VirtualBoxVM}

This way VBox can now run my VMs again.
Post Reply