| View previous topic :: View next topic |
| Author |
Message |
Lori
Guru
Joined: 30 Mar 2004
Posts: 338
Location: Barcelona, Spain
|
 Posted: Tue Sep 22, 2020 1:43 pm Post subject: [SOLVED] Switching from virtualbox-bin to virtualbox (6.1.x) |
 |
|
I have been using virtualbox-bin until yesterday, when it was removed from the tree and I was forced to switch to virtualbox from source. I'm using ~amd64, so version 6.1.14a. I can no longer start my existing VMs, I get this error:
| Code: | The virtual machine 'VM' has terminated unexpectedly during startup with exit code 1 (0x1).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df} |
Digging a bit further, I see this in ~/.VirtualBox/VBoxSVC.log
| Code: | ...
00:00:00.129199 nspr-2 Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE
00:00:00.208743 nspr-2 VD: VDInit finished with VINF_SUCCESS
00:00:00.209891 nspr-2 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={027bc463-929c-40e8-bf16-fea557cd8e7e} aComponent={SystemPropertiesWrap} aText={Cannot determine default Guest Additions ISO location. Most likely they are not available}, preserve=false aResultDetail=0
... |
Permissions on those files:
| Code: | > ls -la /dev/vbox*
crw------- 1 root root 10, 60 Sep 22 2020 /dev/vboxdrv
crw------- 1 root root 10, 59 Sep 22 2020 /dev/vboxdrvu
crw------- 1 root root 10, 58 Sep 22 2020 /dev/vboxnetctl |
I think these were the permissions previously as well, and virtualbox-bin was still working, but to see if it helps, I change ownership to my user. That solves the access issue to /dev/vboxdrvu, but then this happens:
| Code: | 00:00:00.141930 nspr-2 failed to create vboxnet0, error (0x80004005)
00:00:00.144688 nspr-2 failed to create vboxnet1, error (0x80004005)
00:00:00.147383 nspr-2 failed to create vboxnet2, error (0x80004005)
00:00:00.150141 nspr-2 failed to create vboxnet3, error (0x80004005)
00:00:00.152906 nspr-2 failed to create vboxnet4, error (0x80004005)
00:00:00.155705 nspr-2 failed to create vboxnet5, error (0x80004005)
00:00:00.158442 nspr-2 failed to create vboxnet6, error (0x80004005)
00:00:00.161316 nspr-2 failed to create vboxnet7, error (0x80004005)
00:00:00.164146 nspr-2 failed to create vboxnet8, error (0x80004005)
00:00:00.166783 nspr-2 failed to create vboxnet9, error (0x80004005)
00:00:00.166977 nspr-2 VD: VDInit finished with VINF_SUCCESS
00:00:00.167053 nspr-2 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={027bc463-929c-40e8-bf16-fea557cd8e7e} aComponent={SystemPropertiesWrap} aText={Cannot determine default Guest Additions ISO location. Most likely they are not available}, preserve=false aResultDetail=0
|
What's the RightWay(TM) to get virtualbox working...?!
_________________
"The hunt is sweeter then the kill."
Registered Linux User #176911
Last edited by Lori on Mon Nov 30, 2020 7:55 pm; edited 1 time in total |
|
| Back to top |
|
 |
alamahant
Advocate
Joined: 23 Mar 2019
Posts: 3879
|
| Posted: Tue Sep 22, 2020 3:56 pm Post subject: |
|
|
Hi maybe you need to install
| Code: |
app-emulation/virtualbox-extpack-oracle
|
 |
|
| Back to top |
|
|
Lori
Guru
Joined: 30 Mar 2004
Posts: 338
Location: Barcelona, Spain
|
| Posted: Tue Sep 22, 2020 4:03 pm Post subject: |
|
|
Thanks for the suggestion, I just tried it, but unfortunately it didn't help... 
_________________
"The hunt is sweeter then the kill."
Registered Linux User #176911 |
|
| Back to top |
|
|
alamahant
Advocate
Joined: 23 Mar 2019
Posts: 3879
|
| Posted: Tue Sep 22, 2020 5:22 pm Post subject: |
|
|
virtualbox must have automatically pulled the virtuabox-modules
Try please running
| Code: |
modprobe vboxdrv vboxnetadp vboxnetflt
|
And start Vm.
|
|
| Back to top |
|
|
Lori
Guru
Joined: 30 Mar 2004
Posts: 338
Location: Barcelona, Spain
|
| Posted: Tue Sep 22, 2020 6:38 pm Post subject: |
|
|
I did that too, both manually, and then with a reboot (they're configured to be auto-loaded). I also checked the output of dmesg and the modules are loaded correctly... It's something else... I have seen SUID root binaries mentioned on some virtualbox forums I think, but I haven't looked into that...
_________________
"The hunt is sweeter then the kill."
Registered Linux User #176911 |
|
| Back to top |
|
|
halcon
l33t
Joined: 15 Dec 2019
Posts: 629
|
| Posted: Tue Sep 22, 2020 7:05 pm Post subject: Re: Switching from virtualbox-bin to virtualbox (6.1.14a) |
|
|
| Lori wrote: | 00:00:00.167053 nspr-2 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={027bc463-929c-40e8-bf16-fea557cd8e7e} aComponent={SystemPropertiesWrap} aText={Cannot determine default Guest Additions ISO location. Most likely they are not available}, preserve=false aResultDetail=0
|
Well... Do you have virtualbox-guest-additions installed? Despite of I remember messages in elog that extpack should replace additions, they are still un use, and in the tree, and I have it installed, only not *guest*, but usual one.
| Code: | # emerge -s app-emulation/virtualbox-additions
[ Results for search key : app-emulation/virtualbox-additions ]
Searching...
* app-emulation/virtualbox-additions
Latest version available: 6.1.14
Latest version installed: 6.1.14
Size of files: 59 552 KiB
Homepage: https://www.virtualbox.org/
Description: CD image containing guest additions for VirtualBox
License: GPL-2+ LGPL-2.1+ MIT SGI-B-2.0 CDDL
* app-emulation/virtualbox-guest-additions
Latest version available: 6.0.24-r1
Latest version installed: [ Not Installed ]
Size of files: 156 092 KiB
Homepage: https://www.virtualbox.org/
Description: VirtualBox kernel modules and user-space tools for Gentoo guests
License: GPL-2
[ Applications found : 2 ] |
EDIT: Latest version available: 6.0.24-r1 - It seems there is no one for 6.1.14a...
EDIT2: No, there is, I just didn't keyword them because I don't need them. |
|
| Back to top |
|
|
fedeliallalinea
Administrator
Joined: 08 Mar 2003
Posts: 30915
Location: here
|
|
| Back to top |
|
|
Lori
Guru
Joined: 30 Mar 2004
Posts: 338
Location: Barcelona, Spain
|
| Posted: Wed Sep 23, 2020 3:41 pm Post subject: |
|
|
Yeah, I've seen the first before posting, but it doesn't really have a resolution, other than saying that it works well with virtualbox-bin, which it did for me too. However, that package has been removed from the tree, and while I could revive it and continue using it, I would like to use the currently supported build.
The second links talks about permissions, using udev. Before going the udev route, and before posting, I tried manually changing the permissions. That solved the error about /dev/vboxdrvu, so I will probably implement the suggested udev configuration, but other network driver related errors persist, see last code snippet from my original post. My guess is that some binary from the virtualbox-bin package had SetUID permissions, which was necessary on startup and then dropped privileges (it worked with the driver /dev entries being accessible by root only), but I may be wrong.
_________________
"The hunt is sweeter then the kill."
Registered Linux User #176911 |
|
| Back to top |
|
|
Lori
Guru
Joined: 30 Mar 2004
Posts: 338
Location: Barcelona, Spain
|
| Posted: Wed Sep 23, 2020 3:56 pm Post subject: |
|
|
Actually, there are a few binaries with SUID bit set:
| Code: | -rws--x--- 1 root vboxusers 162176 Sep 21 22:41 VBoxHeadless
-rws--x--- 1 root vboxusers 31112 Sep 21 22:41 VBoxNetAdpCtl
-rws--x--- 1 root vboxusers 162176 Sep 21 22:41 VBoxNetDHCP
-rws--x--- 1 root vboxusers 162176 Sep 21 22:41 VBoxNetNAT
-rws--x--- 1 root vboxusers 162176 Sep 21 22:41 VBoxSDL
-rws--x--- 1 root vboxusers 162176 Sep 21 22:41 VirtualBoxVM |
_________________
"The hunt is sweeter then the kill."
Registered Linux User #176911 |
|
| Back to top |
|
|
Tony0945
Watchman
Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA
|
| Posted: Wed Sep 23, 2020 3:58 pm Post subject: |
|
|
| Code: | tony@MSI ~ $ ls -l /dev/vbox*
crw-rw---- 1 root root 10, 61 Sep 21 09:42 /dev/vboxdrv
crw-rw---- 1 root root 10, 60 Sep 21 09:42 /dev/vboxdrvu
crw-rw---- 1 root root 10, 59 Sep 21 09:42 /dev/vboxnetctl
|
Works well. You shouldn't have to change permissions.
| Code: | tony@MSI ~ $ grep vbox /etc/group
vboxguest:x:992:tony,root
vboxusers:x:304:tony,root |
Are you in the right groups?
I didn't even know there was a virtualbox-bin. I've been compiled virtualbox right from the start.
Every time you build or rebuild your kernel, you must run "emerge @module-rebuild".
My packages and use flags:
| Code: | tony@MSI ~ $ grep virtualbox /var/lib/portage/world
app-emulation/virtualbox
app-emulation/virtualbox-additions
app-emulation/virtualbox-extpack-oracle
tony@MSI ~ $ emerge -pv virtualbox
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ~] app-emulation/virtualbox-6.1.14a::gentoo USE="alsa opengl opus qt5 sdk udev vnc -debug -doc -dtrace -headless -java -libressl -lvm -pam -pax_kernel -pulseaudio -python -vboxwebsrv" PYTHON_SINGLE_TARGET="python3_8 -python3_6 -python3_7" 0 KiB
|
|
|
| Back to top |
|
|
Lori
Guru
Joined: 30 Mar 2004
Posts: 338
Location: Barcelona, Spain
|
| Posted: Wed Sep 23, 2020 5:03 pm Post subject: |
|
|
Regarding groups, I don't have a vboxguest group on my system, but I'm already in the vboxusers group:
| Code: | > grep vbox /etc/group
vboxusers:x:999:moriarty |
I started out compilig virtualbox as well, I don't remember why I switched to the binary package. I think I wanted to be on the bleeding edge versions without managing to many unstable dependencies.
I do rebuild modules every time a build a new kernel, so I don't think that's an issue. I fact, I just switched to 5.4.66-gentoo yesterday, will all the required rebuilds. I didn't have app-emulation/virtualbox-additions installed, I just did to see if that helps, but I didn't really expect it to, and it didn't.
Here are my USE flags:
| Code: | | [ebuild R ~] app-emulation/virtualbox-6.1.14a::gentoo USE="alsa java opengl opus pam pulseaudio qt5 sdk udev vnc -debug -doc -dtrace -headless -libressl -lvm -pax_kernel -python -vboxwebsrv" PYTHON_SINGLE_TARGET="python3_7 -python3_6 -python3_8" 0 KiB |
I have java, pam, pulseaudio, as extras. I can try removing them, although I don't think that will help. Can you list your SUID binaries if you have a working config?
| Code: | > ls -la /usr/lib64/virtualbox | grep rws
-rws--x--- 1 root vboxusers 162176 Sep 21 22:41 VBoxHeadless
-rws--x--- 1 root vboxusers 31112 Sep 21 22:41 VBoxNetAdpCtl
-rws--x--- 1 root vboxusers 162176 Sep 21 22:41 VBoxNetDHCP
-rws--x--- 1 root vboxusers 162176 Sep 21 22:41 VBoxNetNAT
-rws--x--- 1 root vboxusers 162176 Sep 21 22:41 VBoxSDL
-rws--x--- 1 root vboxusers 162176 Sep 21 22:41 VirtualBoxVM |
Looking at the list of binaries above, I just tried executing VBoxHeadless. I get a different error:
| Code: | > VBoxHeadless
VBoxHeadless: Error -610 in supR3HardenedMainInitRuntime!
VBoxHeadless: dlopen("/usr/lib64/virtualbox/VBoxRT.so",) failed: <NULL>
VBoxHeadless: Tip! It may help to reinstall VirtualBox. |
I don't run a hardened profile! Not sure what that's about either... I will try the tip, but I don't expect much...
_________________
"The hunt is sweeter then the kill."
Registered Linux User #176911 |
|
| Back to top |
|
|
Tony0945
Watchman
Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA
|
| Posted: Wed Sep 23, 2020 5:54 pm Post subject: |
|
|
| Code: | -rws--x--- 1 root vboxusers 166264 Sep 10 17:01 VBoxHeadless
-rws--x--- 1 root vboxusers 31104 Sep 10 17:01 VBoxNetAdpCtl
-rws--x--- 1 root vboxusers 166264 Sep 10 17:01 VBoxNetDHCP
-rws--x--- 1 root vboxusers 166264 Sep 10 17:01 VBoxNetNAT
-rws--x--- 1 root vboxusers 166264 Sep 10 17:01 VBoxSDL
-rws--x--- 1 root vboxusers 166264 Sep 10 17:01 VirtualBoxVM
|
Actual line from package.use: | Code: | | app-emulation/virtualbox qt5 -java udev vnc -headless python_single_target_python3_8 -python_single_target_python3_7 -python_single_target_python3_6 |
Don't know why I have a VBoxHeadless.
Every time I update I have to execute VBox-Additions on first virtual boot. Then it's fine until the next update.
I mostly run Windows as virtual machines. I've tried some Linices but prefer my customized Gentoo. |
|
| Back to top |
|
|
Lori
Guru
Joined: 30 Mar 2004
Posts: 338
Location: Barcelona, Spain
|
| Posted: Wed Sep 23, 2020 7:35 pm Post subject: |
|
|
| Tony0945 wrote: | Actual line from package.use:
| Code: | | app-emulation/virtualbox qt5 -java udev vnc -headless python_single_target_python3_8 -python_single_target_python3_7 -python_single_target_python3_6 |
Don't know why I have a VBoxHeadless. |
It is always installed. The headless USE flag is useful on servers to avoid dependencies on X libraries, because ONLY the headless part is installed, so you can use virtualbox as a hypervisor from the CLI.
_________________
"The hunt is sweeter then the kill."
Registered Linux User #176911 |
|
| Back to top |
|
|
Lori
Guru
Joined: 30 Mar 2004
Posts: 338
Location: Barcelona, Spain
|
| Posted: Fri Sep 25, 2020 9:41 am Post subject: |
|
|
| Lori wrote: | Looking at the list of binaries above, I just tried executing VBoxHeadless. I get a different error:
| Code: | > VBoxHeadless
VBoxHeadless: Error -610 in supR3HardenedMainInitRuntime!
VBoxHeadless: dlopen("/usr/lib64/virtualbox/VBoxRT.so",) failed: <NULL>
VBoxHeadless: Tip! It may help to reinstall VirtualBox. |
I don't run a hardened profile! Not sure what that's about either... I will try the tip, but I don't expect much... |
I did reinstall virtualbox, and I disabled the java and pam USE flags, to no avail...
_________________
"The hunt is sweeter then the kill."
Registered Linux User #176911 |
|
| Back to top |
|
|
Tony0945
Watchman
Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA
|
| Posted: Fri Sep 25, 2020 1:12 pm Post subject: |
|
|
Do your errors occur when launching the Virtualbox application? Or When launching a particular guest from the virtualbox GUI?
Are you using the Virtualbox GUI? (It's all I've every used) |
|
| Back to top |
|
|
Lori
Guru
Joined: 30 Mar 2004
Posts: 338
Location: Barcelona, Spain
|
| Posted: Fri Sep 25, 2020 6:43 pm Post subject: |
|
|
The error happens when I launch the GUI application, independent of a particular VM. I checked the headless binary just out of curiosity.
_________________
"The hunt is sweeter then the kill."
Registered Linux User #176911 |
|
| Back to top |
|
|
gorbag
n00b
Joined: 29 Apr 2004
Posts: 19
|
| Posted: Mon Sep 28, 2020 9:24 am Post subject: |
|
|
I had a similar problem moving from virtualbox-bin to virtualbox. The problem for me was the config files in .config/VirtualBox. Removing that directory solved it for me.
Examining the old config files in that directory showed that xpti.dat contained references to /opt/VirtualBox which is the install location used by virtualbox-bin. virtualbox installs instead to /usr/lib64, which is probably the cause of the problem, but I have not confirmed that. |
|
| Back to top |
|
|
Lori
Guru
Joined: 30 Mar 2004
Posts: 338
Location: Barcelona, Spain
|
| Posted: Mon Sep 28, 2020 9:57 am Post subject: |
|
|
| gorbag wrote: | | I had a similar problem moving from virtualbox-bin to virtualbox. The problem for me was the config files in .config/VirtualBox. Removing that directory solved it for me. |
Thanks for the suggestion. I didn't even have a ~/.config/VirtualBox directory, I guess I started using VirtualBox when they used ~/.VirtualBox as the config and log location. I removed that directory, and on next restart it created the newer .config/VirtualBox location. However, that didn't help, the issues are still somehow permissions related.
_________________
"The hunt is sweeter then the kill."
Registered Linux User #176911 |
|
| Back to top |
|
|
Tony0945
Watchman
Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA
|
| Posted: Mon Sep 28, 2020 3:00 pm Post subject: |
|
|
This is what gets executed when you click the desktop icon: | Code: | ls -l /usr/lib64/virtualbox/VBox
-rwxr-x--- 1 root vboxusers 3570 Sep 10 17:01 /usr/lib64/virtualbox/VBox |
When I execute by clicking the icon, it runs by my membership in vboxusers.
| Code: | l $ groups tony
tty lp wheel mail cron audio cdrom tape video cdrw usb users scanner lpadmin locate git portage plugdev vboxguest vboxusers wireshark |
I am not in the root group so the program must be suid. I'm on hazy ground here, but perhaps an suid program executes as a member of group "root" instead of user "root"? That's the difference that I see between my /dev listing from yours.
All old troubleshooting maxim goes "If you don't know what is wrong but you see that something seemingly unrelated is wrong, fix that and often it will fix the original problem." Why are your devices not executable by group root?
| Code: | tony@MSI ~ $ equery f virtualbox|grep etc
/etc
/etc/env.d
/etc/env.d/90virtualbox
/etc/vbox
/etc/vbox/vbox.cfg
tony@MSI ~ $ cat /etc/env.d/90virtualbox
VBOX_APP_HOME=/usr/lib64/virtualboxtony@MSI ~ $
tony@MSI ~ $ cat /etc/vbox/vbox.cfg
INSTALL_DIR=/usr/lib64/virtualbox
|
Anything leap out there? Why is udev (I assume you are running udev, I'm not) failing to give permissions to group "root" and only to user "root"?
What happens if you run "chmod 0660 /dev/vbox*" ? If it starts working or you get a little farther, start looking at udev. |
|
| Back to top |
|
|
Lori
Guru
Joined: 30 Mar 2004
Posts: 338
Location: Barcelona, Spain
|
| Posted: Mon Sep 28, 2020 3:38 pm Post subject: |
|
|
| Tony0945 wrote: | | What happens if you run "chmod 0660 /dev/vbox*" ? |
I just tried that, and I get the exact same result. I also checked what udev related files is the ebuild instaling:
| Code: | ~> equery f app-emulation/virtualbox | grep udev
/lib/udev
/lib/udev/VBoxCreateUSBNode.sh
/lib/udev/rules.d
/lib/udev/rules.d/10-virtualbox.rules |
These are only related with USB stuff, not the other drivers, so no default udev rules from the ebuild.
I think I will restore the virtualbox-bin ebuild from portage git history, see if any of the files installed by it gives me a hint as to what's wrong, and if I'm unable to fix it, I will just keep using and updating that...
_________________
"The hunt is sweeter then the kill."
Registered Linux User #176911 |
|
| Back to top |
|
|
OldTango
l33t
Joined: 21 Feb 2004
Posts: 718
|
| Posted: Mon Sep 28, 2020 7:10 pm Post subject: |
|
|
| Lori wrote: | | I think I will restore the virtualbox-bin ebuild from portage git history, see if any of the files installed by it gives me a hint as to what's wrong, and if I'm unable to fix it, I will just keep using and updating that... |
That might prove to be more trouble than it's worth. You should be able to get VirtualBox up and running.
I was also forced to move from virtualbox-bin to virtualbox but I also needed to do a kernel upgrade as well. I did the kernel upgrade to gentoo-sources-5.4.66 first making sure the minimum requirements for virtualbox were met. | Code: |
[*] Enable loadable module support --->
[ ] Trim unused exported kernel symbols
[*] Virtualization ---> |
After rebooting into the new kernel I uninstalled virtualbox-bin along with 3 other applications that were removed from portage due to a lack of python-3 support as well. I also removed all the ~/.VirtualBox items in my home directory, except my VM's. Emerged the latest stable virtualbox-6.0.24 using default USE flags. That process pulled in about 13 new packages but failed to complete due to dev-util/kbuild errors. After keywording dev-util/kbuild-0.1.9998.3407 ~amd64 the emerge process completed successfully. I completed the process by emerging app-emulation/virtualbox-additions and app-emulation/virtualbox-extpack-oracle and modprobing, vboxdrv, vboxnetflt, vboxnetadp.
I started the VirtualBox-GUI and got a COM error and the GUI terminated. The error made no sense to me and googling it led nowhere. Rebuilding several packages also did not solve the issue. After checking all the possible causes without any solution, I decided to reboot the system and allow th init process to do the module loading normally. For whatever reason the GUI started and I was able to select my VM's and run them without issue. When starting WinXP VirtualBox informed me I was using the incorrect VGA driver with 3D acceleration enabled. After fixing the issue the warning went away.
After I was able to successfully start the GUI and my VM's. Many of the ERRORS you are reporting appear in my logs but don't seem to affect the application from working properly. Here is my complete ~/.config/VirtualBox/VBoxSVC.log after a secessful startup. | Code: |
00:00:00.000166 main VirtualBox XPCOM Server 6.0.24_Gentoo r139119 linux.amd64 (Sep 27 2020 18:41:05) release log
00:00:00.000167 main Log opened 2020-09-28T17:21:11.166796000Z
00:00:00.000168 main Build Type: release
00:00:00.000171 main OS Product: Linux
00:00:00.000171 main OS Release: 5.4.66-gentoo
00:00:00.000172 main OS Version: #2 SMP PREEMPT Sun Sep 27 17:32:26 MDT 2020
00:00:00.000195 main DMI Product Name: To Be Filled By O.E.M.
00:00:00.000200 main DMI Product Version: To Be Filled By O.E.M.
00:00:00.000233 main Host RAM: 128779MB (125.7GB) total, 127524MB (124.5GB) available
00:00:00.000236 main Executable: /usr/lib64/virtualbox/VBoxSVC
00:00:00.000236 main Process ID: 6277
00:00:00.000237 main Package type: LINUX_64BITS_GENERIC (OSE)
00:00:00.001753 main IPC socket path: /tmp/.vbox-michael-ipc/ipcd
00:00:00.103742 nspr-2 VirtualBox: object creation starts
00:00:00.103827 nspr-2 Home directory: '/home/michael/.config/VirtualBox'
00:00:00.103990 nspr-2 Loading settings file "/home/michael/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:00:00.104807 nspr-2 Successfully initialised host USB using sysfs
00:00:00.107792 nspr-2 HostDnsMonitor: initializing
00:00:00.108048 nspr-2 NAT: resolv.conf: nameserver 192.168.0.1
00:00:00.108059 nspr-2 HostDnsMonitor: updating information
00:00:00.108067 nspr-2 HostDnsMonitor: old information
00:00:00.108069 nspr-2 no server entries
00:00:00.108071 nspr-2 no domain set
00:00:00.108072 nspr-2 no search string entries
00:00:00.108074 nspr-2 HostDnsMonitor: new information
00:00:00.108075 nspr-2 server 1: 192.168.0.1
00:00:00.108077 nspr-2 no domain set
00:00:00.108079 nspr-2 no search string entries
00:00:00.108102 nspr-2 Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE
00:00:00.108769 nspr-2 VD: VDInit finished with VINF_SUCCESS
00:00:00.113369 nspr-2 Loading settings file "/home/michael/VirtualBox VMs/Windows XP Pro/Windows XP Pro.vbox" with version "1.15-linux"
00:00:00.113854 nspr-2 Loading settings file "/home/michael/VirtualBox VMs/Windows 10 Pro/Windows 10 Pro.vbox" with version "1.14-linux"
00:00:00.114343 nspr-2 OCI: Local config file '/home/michael/.config/VirtualBox/oci_config' does not exist
00:00:00.114350 nspr-2 OCI: Original config file '/home/michael/.oci/config' does not exist
00:00:00.114352 nspr-2 OCI: Reading profiles finished with status NS_OK
00:00:00.114360 nspr-2 ExtPack: Created cloud provider 'OCI' (hrc=NS_OK)
00:00:00.114371 nspr-2 VirtualBox: object created
00:00:00.482670 nspr-3 Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE
00:00:08.356988 nspr-3 Saving settings file "/home/michael/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:00:08.415633 nspr-3 Saving settings file "/home/michael/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:00:13.949864 main VirtualBox: object deletion starts
00:00:13.949915 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/home/michael/VirtualBox VMs/Windows XP Pro/Windows XP Pro.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:13.950065 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/home/michael/VirtualBox VMs/Windows 10 Pro/Windows 10 Build 10130.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:13.950327 main HostDnsMonitor: shutting down ...
00:00:13.953897 main HostDnsMonitor: shut down
00:00:13.957124 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:00:13.957223 main VirtualBox: object deleted |
The things I would look into are:
Is it possible you have a Kernel Version, VirtualBox Version compatibility issue? It seems I read somewhere that VirtualBox has problems with Kernels >5.4 but I run mostly stable systems so there is no way for me to rule this out.
Also check the ~/.config/VirtualBox/xpti.dat file and if it looks like this | Code: |
# Generated file. ** DO NOT EDIT! **
[Header,2]
0,Version,2,0
1,AppDir,/opt/VirtualBox
[Directories,2]
0,/opt/VirtualBox/components
1,/home/michael/components
[Files,0]
[ArchiveItems,0]
[Interfaces,0] |
I would delete it and try again.
I did not have to mess around with any file permissions or udev rules to get VirtualBox up and running.
Best Tango.....  |
|
| Back to top |
|
|
Lori
Guru
Joined: 30 Mar 2004
Posts: 338
Location: Barcelona, Spain
|
| Posted: Tue Sep 29, 2020 2:16 pm Post subject: |
|
|
OldTango many thanks for sharing your switching experience with steps, very helpful!
| OldTango wrote: | | Lori wrote: | | I think I will restore the virtualbox-bin ebuild from portage git history, see if any of the files installed by it gives me a hint as to what's wrong, and if I'm unable to fix it, I will just keep using and updating that... |
That might prove to be more trouble than it's worth. You should be able to get VirtualBox up and running. |
I already managed to do it before I read your post, not at all complicated for the short term, but obviously not a solution for the long term, as I would like to get rid of Python 2 dependencies too, and virtualbox-bin does depend on Python 2.
| OldTango wrote: | | I was also forced to move from virtualbox-bin to virtualbox but I also needed to do a kernel upgrade as well. I did the kernel upgrade to gentoo-sources-5.4.66 first making sure the minimum requirements for virtualbox were met. |
I'm running the exact same kernel version, and I do have the necessary support, AFAIK.
| OldTango wrote: | | I also removed all the ~/.VirtualBox items in my home directory, except my VM's. Emerged the latest stable virtualbox-6.0.24 using default USE flags. |
Yes, I tried completely removing ~/.VirtualBox, a new fresh configuration was created under ~/.config/VirtualBox, but that didn't solve the issue either. The main difference I see from your setup is the VirtualBox version itself. I was using 6.1.12 before the switch, so I kept using ~amd64 and built 6.1.14a. I will test if downgrading to 6.0.24 helps, but I'd rather avoid that.
| OldTango wrote: | | I started the VirtualBox-GUI and got a COM error and the GUI terminated. |
I never had that issue. The GUI always came on, no error dialog boxes, only the errors I reported in the log file. But no matter if I tried starting my existing VMs, or created new VM and tried starting that, I got the error dialog box mentioned in the original post.
| OldTango wrote: | After I was able to successfully start the GUI and my VM's. Many of the ERRORS you are reporting appear in my logs but don't seem to affect the application from working properly. Here is my complete ~/.config/VirtualBox/VBoxSVC.log after a secessful startup. | Code: |
00:00:00.000166 main VirtualBox XPCOM Server 6.0.24_Gentoo r139119 linux.amd64 (Sep 27 2020 18:41:05) release log
00:00:00.000167 main Log opened 2020-09-28T17:21:11.166796000Z
00:00:00.000168 main Build Type: release
00:00:00.000171 main OS Product: Linux
00:00:00.000171 main OS Release: 5.4.66-gentoo
00:00:00.000172 main OS Version: #2 SMP PREEMPT Sun Sep 27 17:32:26 MDT 2020
00:00:00.000195 main DMI Product Name: To Be Filled By O.E.M.
00:00:00.000200 main DMI Product Version: To Be Filled By O.E.M.
00:00:00.000233 main Host RAM: 128779MB (125.7GB) total, 127524MB (124.5GB) available
00:00:00.000236 main Executable: /usr/lib64/virtualbox/VBoxSVC
00:00:00.000236 main Process ID: 6277
00:00:00.000237 main Package type: LINUX_64BITS_GENERIC (OSE)
00:00:00.001753 main IPC socket path: /tmp/.vbox-michael-ipc/ipcd
00:00:00.103742 nspr-2 VirtualBox: object creation starts
00:00:00.103827 nspr-2 Home directory: '/home/michael/.config/VirtualBox'
00:00:00.103990 nspr-2 Loading settings file "/home/michael/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:00:00.104807 nspr-2 Successfully initialised host USB using sysfs
00:00:00.107792 nspr-2 HostDnsMonitor: initializing
00:00:00.108048 nspr-2 NAT: resolv.conf: nameserver 192.168.0.1
00:00:00.108059 nspr-2 HostDnsMonitor: updating information
00:00:00.108067 nspr-2 HostDnsMonitor: old information
00:00:00.108069 nspr-2 no server entries
00:00:00.108071 nspr-2 no domain set
00:00:00.108072 nspr-2 no search string entries
00:00:00.108074 nspr-2 HostDnsMonitor: new information
00:00:00.108075 nspr-2 server 1: 192.168.0.1
00:00:00.108077 nspr-2 no domain set
00:00:00.108079 nspr-2 no search string entries
00:00:00.108102 nspr-2 Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE
00:00:00.108769 nspr-2 VD: VDInit finished with VINF_SUCCESS
00:00:00.113369 nspr-2 Loading settings file "/home/michael/VirtualBox VMs/Windows XP Pro/Windows XP Pro.vbox" with version "1.15-linux"
00:00:00.113854 nspr-2 Loading settings file "/home/michael/VirtualBox VMs/Windows 10 Pro/Windows 10 Pro.vbox" with version "1.14-linux"
00:00:00.114343 nspr-2 OCI: Local config file '/home/michael/.config/VirtualBox/oci_config' does not exist
00:00:00.114350 nspr-2 OCI: Original config file '/home/michael/.oci/config' does not exist
00:00:00.114352 nspr-2 OCI: Reading profiles finished with status NS_OK
00:00:00.114360 nspr-2 ExtPack: Created cloud provider 'OCI' (hrc=NS_OK)
00:00:00.114371 nspr-2 VirtualBox: object created
00:00:00.482670 nspr-3 Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE
00:00:08.356988 nspr-3 Saving settings file "/home/michael/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:00:08.415633 nspr-3 Saving settings file "/home/michael/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:00:13.949864 main VirtualBox: object deletion starts
00:00:13.949915 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/home/michael/VirtualBox VMs/Windows XP Pro/Windows XP Pro.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:13.950065 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/home/michael/VirtualBox VMs/Windows 10 Pro/Windows 10 Build 10130.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:13.950327 main HostDnsMonitor: shutting down ...
00:00:13.953897 main HostDnsMonitor: shut down
00:00:13.957124 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:00:13.957223 main VirtualBox: object deleted |
|
This looks quite similar to mine, so I guess the permissions on the /dev files are not the problem.
| OldTango wrote: | The things I would look into are:
Is it possible you have a Kernel Version, VirtualBox Version compatibility issue? It seems I read somewhere that VirtualBox has problems with Kernels >5.4 but I run mostly stable systems so there is no way for me to rule this out. |
I have to test VirtualBox 6.0.x too...
| OldTango wrote: | Also check the ~/.config/VirtualBox/xpti.dat file and if it looks like this | Code: |
# Generated file. ** DO NOT EDIT! **
[Header,2]
0,Version,2,0
1,AppDir,/opt/VirtualBox
[Directories,2]
0,/opt/VirtualBox/components
1,/home/michael/components
[Files,0]
[ArchiveItems,0]
[Interfaces,0] |
I would delete it and try again. |
Yeah, that shouldn't be an issue, since I also tried with a clean config...
| OldTango wrote: | | I did not have to mess around with any file permissions or udev rules to get VirtualBox up and running. |
That's useful info, I know what I shouldn't waste my time on...
_________________
"The hunt is sweeter then the kill."
Registered Linux User #176911
Last edited by Lori on Tue Sep 29, 2020 3:09 pm; edited 2 times in total |
|
| Back to top |
|
|
Tony0945
Watchman
Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA
|
| Posted: Tue Sep 29, 2020 3:06 pm Post subject: |
|
|
I also am on 5.4.66 like Old Tango. Now on 5.4.66
Running Virtualbox 6.1.14a
Are you sure you cleaned out everything from virtualbox-bin ? Since it installs into /opt, something left over may be trying to access /opt files that are no longer there as was the case for Old Tango. Using gcc 9.3.0 NOT gcc 10. I found Gcc 10 gave me problems (not specifically with virtualbox) and reinstalled a stable toolchain.
I would suggest trying to install a new VM, but you can't even get the application to start. |
|
| Back to top |
|
|
OldTango
l33t
Joined: 21 Feb 2004
Posts: 718
|
| Posted: Tue Sep 29, 2020 6:00 pm Post subject: |
|
|
Are you 100% sure you built the virtualbox-modules for the kernel version you are booting into and they are properly loaded. When we run/test more than one kernel and many of us do , it is easy to forget we also need to build all out of kernel modules against every kernel we intend to boot. The way I do it is to use | Code: | eselect kernel list
and
eselect kernel set |
to list and select the kernel I want modules built for. Once I am sure I have the proper kernel set I rebuild the virtualbox-modules package. I would do this for every kernel I plan on booting.
I use openrc and /etc/conf.d/modules to tell the kernel what modules to load. | Code: | | modules="nvidia vboxdrv vboxnetflt vboxnetadp |
If this isn't done the VM's won't start due to a module version mismatch.
Best Tango.... |
|
| Back to top |
|
|
Lori
Guru
Joined: 30 Mar 2004
Posts: 338
Location: Barcelona, Spain
|
| Posted: Tue Sep 29, 2020 7:53 pm Post subject: |
|
|
Thanks Tony0945 and OldTango for the suggestions.
I use gcc 9.3.0 too. And I did clean everything. Also, I can get the application to start, I can even create a new VM from scratch, but I can't start the VM.
Regarding kernel compilation, the modules work perfectly with virtualbox-bin, on the exact same kernel, so they are definitely not the issue. I haven't had a chance to switch back to the stable version 6.0.24 yet, to see if that helps, but if 6.1.14a works for Tony0945, that's probably not the issue either. I wish the error message thrown was more helpful...
_________________
"The hunt is sweeter then the kill."
Registered Linux User #176911 |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
