| View previous topic :: View next topic |
| Author |
Message |
pablo_supertux
Advocate
Joined: 25 Jan 2004
Posts: 2961
Location: Somewhere between reality and Middle-Earth and in Freiburg (Germany)
|
 Posted: Thu Jan 30, 2025 10:43 am Post subject: Virtualbox cannot start my VMs |
 |
|
Hi
Recently app-emulation/virtualbox got updated to 7.1.4 (I think I had 7.0.22) and since then I cannot any of my virtual machines anymore.
I've removed the modules with depmod -r, I recompiled then, inserted them again with depmod and yet all I get is
| Code: |
Result Code:
NS_ERROR_FAILURE (0x80004005)
|
on all VMs
In dmesg all I can see is this
| Code: |
[ 4893.378288] VirtualBoxVM[21455]: segfault at 0 ip 00007f902df3665d sp 00007ffc13e56548 error 4 in libc.so.6[7f902de66000+f5000] likely on CPU 12 (core 4, socket 0)
[ 4893.378302] Code: 00 00 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 00 <c5> fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66
|
In ~/.VirtualBox/VBoxSVC.log I can see
| Code: |
00:06:58.387297 DCon17 Launched VM: 486141856 pid: 21581 (0x544d) frontend: GUI/Qt name: Windows 10 (Viega)
00:06:58.417397 DCon16 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={5bfd8965-b81b-469f-8649-f717ce97a5d5} aComponent={NvramStoreWrap} aText={The UEFI NVRAM file is not existing for this machine}, preserve=false aResultDetail=0
00:06:58.418728 DCon16 Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE
00:06:58.430433 DCon16 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={e36a5081-a82a-40bd-9e4e-42a44d6ce50f} aComponent={MachineWrap} aText={The machine is not mutable, saved or running (state is PoweredOff)}, preserve=false aResultDetail=0
00:06:58.887942 Watcher ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={e36a5081-a82a-40bd-9e4e-42a44d6ce50f} aComponent={MachineWrap} aText={The virtual machine 'Windows 10 (Viega)' has terminated unexpectedly during startup because of signal 11}, preserve=false aResultDetail=0
00:06:58.942521 DCon22 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={5bfd8965-b81b-469f-8649-f717ce97a5d5} aComponent={NvramStoreWrap} aText={The UEFI NVRAM file is not existing for this machine}, preserve=false aResultDetail=0
00:06:58.943821 DCon22 Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE
00:06:58.955441 DCon22 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={e36a5081-a82a-40bd-9e4e-42a44d6ce50f} aComponent={MachineWrap} aText={The machine is not mutable, saved or running (state is PoweredOff)}, preserve=false aResultDetail=0
|
The Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE" is interessting.
| Code: |
ls -alh /dev/vboxdrvu
crw------- 1 root root 10, 123 Jan 30 11:26 /dev/vboxdrvu
|
So this dev device is only accessible for root (which is strange). I tried
| Code: |
chgrp vboxusers /dev/vboxdrvu
chmod 660 /dev/vboxdrvu
|
but I'm keep getting the same error. In VBoxSVC.log I get the same entries minus the "Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE"
Does anybody know what is going on?
_________________
A! Elbereth Gilthoniel!
silivren penna míriel
o menel aglar elenath,
Gilthoniel, A! Elbereth! |
|
| Back to top |
|
 |
pablo_supertux
Advocate
Joined: 25 Jan 2004
Posts: 2961
Location: Somewhere between reality and Middle-Earth and in Freiburg (Germany)
|
| Posted: Thu Jan 30, 2025 11:06 am Post subject: |
|
|
It seems an error on 7.1.4. I downgraded to 7.0.22 and now everything is working again.
I will create a bug report
_________________
A! Elbereth Gilthoniel!
silivren penna míriel
o menel aglar elenath,
Gilthoniel, A! Elbereth! |
|
| Back to top |
|
|
pablo_supertux
Advocate
Joined: 25 Jan 2004
Posts: 2961
Location: Somewhere between reality and Middle-Earth and in Freiburg (Germany)
|
|
| Back to top |
|
|
OldTango
l33t
Joined: 21 Feb 2004
Posts: 732
|
| Posted: Wed Feb 19, 2025 10:10 pm Post subject: Re: Virtualbox cannot start my VMs |
|
|
| pablo_supertux wrote: | Hi
Recently app-emulation/virtualbox got updated to 7.1.4 (I think I had 7.0.22) and since then I cannot any of my virtual machines anymore.
I've removed the modules with depmod -r, I recompiled then, inserted them again with depmod and yet all I get is
| Code: |
Result Code:
NS_ERROR_FAILURE (0x80004005)
|
on all VMs
|
Had the same issue here until I realized I had forgotten to load the correct modules. I just did a system reboot. Solved the problem.
| pablo_supertux wrote: |
In ~/.VirtualBox/VBoxSVC.log I can see
| Code: |
00:06:58.387297 DCon17 Launched VM: 486141856 pid: 21581 (0x544d) frontend: GUI/Qt name: Windows 10 (Viega)
00:06:58.417397 DCon16 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={5bfd8965-b81b-469f-8649-f717ce97a5d5} aComponent={NvramStoreWrap} aText={The UEFI NVRAM file is not existing for this machine}, preserve=false aResultDetail=0
00:06:58.418728 DCon16 Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE
00:06:58.430433 DCon16 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={e36a5081-a82a-40bd-9e4e-42a44d6ce50f} aComponent={MachineWrap} aText={The machine is not mutable, saved or running (state is PoweredOff)}, preserve=false aResultDetail=0
00:06:58.887942 Watcher ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={e36a5081-a82a-40bd-9e4e-42a44d6ce50f} aComponent={MachineWrap} aText={The virtual machine 'Windows 10 (Viega)' has terminated unexpectedly during startup because of signal 11}, preserve=false aResultDetail=0
00:06:58.942521 DCon22 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={5bfd8965-b81b-469f-8649-f717ce97a5d5} aComponent={NvramStoreWrap} aText={The UEFI NVRAM file is not existing for this machine}, preserve=false aResultDetail=0
00:06:58.943821 DCon22 Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE
00:06:58.955441 DCon22 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={e36a5081-a82a-40bd-9e4e-42a44d6ce50f} aComponent={MachineWrap} aText={The machine is not mutable, saved or running (state is PoweredOff)}, preserve=false aResultDetail=0
|
The Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE" is interessting.
but I'm keep getting the same error. In VBoxSVC.log I get the same entries minus the "Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE"
|
I am getting the exact same errors in my logs as well, even after my VM's start and run. They don't seem to be causing me any issues.
Have you confirmed you have the correct modules loaded and you built them for the kernel you are running. |
|
| Back to top |
|
|
figueroa
Advocate
Joined: 14 Aug 2005
Posts: 3020
Location: Edge of marsh USA
|
| Posted: Thu May 15, 2025 5:28 pm Post subject: |
|
|
Over the last couple of months I've upgraded and then downgraded repeatedly to 7.0.22. I'm happy with 7.0.22, but I don't understand why 7.1.4-r1 continues to be "stable."
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi
Last edited by figueroa on Thu May 15, 2025 7:30 pm; edited 1 time in total |
|
| Back to top |
|
|
apiaio
Guru
Joined: 04 Dec 2008
Posts: 429
|
| Posted: Thu May 15, 2025 7:15 pm Post subject: |
|
|
| app-emulation/virtualbox-7.1.4-r1 works perfectly for my virtual machines |
|
| Back to top |
|
|
figueroa
Advocate
Joined: 14 Aug 2005
Posts: 3020
Location: Edge of marsh USA
|
| Posted: Thu May 15, 2025 7:30 pm Post subject: |
|
|
Thanks, apiaio. That's hopeful. It's clearly a mixed experience for users on Gentoo and other distributions. I've tried the various tricks found on the web, different VM settings, clearing kernel cashes via echoing a 3 into /proc/sys/vm/drop_caches. All I got for my troubles was slower performance until those caches are rebuilt through use. Happily, 7.0.22-r1 has been working flawlessly.
My hope is that someone will encounter this thread who has had and then blazed the way forward for we "problem users."
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
| Back to top |
|
|
OldTango
l33t
Joined: 21 Feb 2004
Posts: 732
|
| Posted: Thu May 15, 2025 8:59 pm Post subject: |
|
|
Works and performs very well for me also.
| Code: | | [ebuild R ] app-emulation/virtualbox-7.1.4-r1:0/7.1::gentoo USE="alsa dbus gui java nls opengl pam pulseaudio sdk sdl udev vmmraw -debug -doc -dtrace -lvm (-pch) -python -test -vboxwebsrv -vde -vnc" PYTHON_SINGLE_TARGET="python3_11" 0 KiB |
|
|
| Back to top |
|
|
figueroa
Advocate
Joined: 14 Aug 2005
Posts: 3020
Location: Edge of marsh USA
|
| Posted: Mon Jun 09, 2025 5:00 am Post subject: |
|
|
Actually solved, but I didn't start the thread. Andy, hopefully this isn't considered a zombie post.
VirtualBox-7.0.22 is no longer in the repository, so I was forced to upgrade to stable version 7.1.8, which gave me the same problem of not being able to start any virtual machine. I found the solution at https://www.virtualbox.org/ticket/22193
In short, as root, I did the following:
| Code: | cd /usr/lib64/virtualbox
ln -s libpthread.so /lib64/libpthread.so.0
ln -s /lib64/libpthread.so.0 libpthread.so |
After creating the two symlinks, my virtual machines start just fine. Why didn't the ebuild or source code do this for me?
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
| Back to top |
|
|
rab0171610
Guru
Joined: 24 Dec 2022
Posts: 532
|
| Posted: Mon Jun 09, 2025 8:40 am Post subject: |
|
|
| figueroa wrote: | Actually solved, but I didn't start the thread. Andy, hopefully this isn't considered a zombie post.
VirtualBox-7.0.22 is no longer in the repository, so I was forced to upgrade to stable version 7.1.8, which gave me the same problem of not being able to start any virtual machine. I found the solution at https://www.virtualbox.org/ticket/22193
In short, as root, I did the following:
| Code: | cd /usr/lib64/virtualbox
ln -s libpthread.so /lib64/libpthread.so.0
ln -s /lib64/libpthread.so.0 libpthread.so |
After creating the two symlinks, my virtual machines start just fine. Why didn't the ebuild or source code do this for me? |
I think that is a workaround and not a solution. The last two posts you link to explain:
| Code: | "The symbolic-link workaround is not needed for fresh VirtualBox configurations, but only for configurations inherited from an older version of VirtualBox.
This insight prompted me to look for references to the suspicious dynamic libraries in my VirtualBox configuration. And I found this:
~/.config/VirtualBox> grep libdl *
compreg.dat:rel:VBoxXPCOMIPCC.so,1182466622000,VBoxXPCOM.so libpthread.so libdl.so
Looks like compreg.dat is caching some dynamic loader configuration.
Removing this file resolved the issue for me. " |
I do not have older VM's laying around and I cannot replicate the issue. I think it is affecting a limited subset of users. I don't imagine that an ebuild would generally create symlinks in the system that aren't necessary and link to extinct file names from libraries that were absorbed into libc years ago.
The last post goes on to explain:
| Code: | problem *seems* to affect really long time users of VBox where compreg.dat contains an outdated entry for the VBoxXPCOMIPCC.so component (above example is dated 2007-06-22). For various reasons, the entry for that component wasn't ever updated as new versions of VBox shipped. So, when we disabled the bogus generating of dependencies (VBoxXPCOM.so libpthread.so libdl.so) in 2008, the list for the VBoxXPCOMIPCC.so entry was carried along
. . .
the issue is fixed in SVN and backported to 7.1. Test builds with revision r168606 or later should include the fix.
Just deleting the compreg.dat file will fix the issue as well. It will automatically be re-generated, so this is perfectly safe. |
So if it turns out the problem is due to a corrupt entry in a VBox config file located in the user's home directory, deleting the file would be the real solution and not creating bogus symlinks. |
|
| Back to top |
|
|
figueroa
Advocate
Joined: 14 Aug 2005
Posts: 3020
Location: Edge of marsh USA
|
| Posted: Mon Jun 09, 2025 4:46 pm Post subject: |
|
|
Thank you very much rab0171610. That nailed it. REALLY solved for me now. You explained the rest of the story very well.
My original ancient installation was such that I didn't even have a VirtualBox file or directory in ~/.config. I have a ~/.VirtualBox directory containing configuration files and even some virtual machines.
To cut to the chase, I moved compreg.dat into old_compreg.dat_bak and removed the two symlink work arounds, and now VirtualBox runs and launches virtual machines as it should. compreg.dat was recreated without the problem entry:
Old compreg.dat with the problematic line: "rel:VBoxXPCOMIPCC.so,1196266671000,VBoxXPCOM.so libpthread.so libdl.so"
| Code: | cat .VirtualBox/old_compreg.dat_bak
Generated File. Do not edit.
[HEADER]
Version,0,5
[COMPONENTS]
rel:VBoxSVCM.so,1749442381119
rel:VBoxC.so,1749442381150
rel:VBoxXPCOMIPCC.so,1196266671000,VBoxXPCOM.so libpthread.so libdl.so
[CLASSIDS]
{d9e56bf8-e32e-4b6d-87f1-06d73b0ce7ca},,,,rel:VBoxXPCOMIPCC.so
{1403adf4-94d1-4c67-a8ae-d9f86972d378},,,,rel:VBoxXPCOMIPCC.so
{9f12676a-5168-4a08-beb8-edf8a593a1ca},,,,rel:VBoxXPCOMIPCC.so
{b1a7a4f2-47b9-4a1e-82b2-07ccd5323c3f},,,,rel:VBoxSVCM.so
{3c02f46d-c9d2-4f11-a384-53f0cf917214},,,,rel:VBoxC.so
{49ee8561-5563-4715-b18c-a4b1a490dafe},,,,rel:VBoxC.so
{dd3fc71d-26c0-4fe1-bf6f-67f633265bba},,,,rel:VBoxC.so
{63a5d9dc-4828-425a-bd50-bd10a4b26f2c},@mozilla.org/ipc/dconnect-service;1,,ipcDConnectService,rel:VBoxXPCOMIPCC.so
[CONTRACTIDS]
@virtualbox.org/Session;1,{3c02f46d-c9d2-4f11-a384-53f0cf917214}
@virtualbox.org/VirtualBoxClient;1,{dd3fc71d-26c0-4fe1-bf6f-67f633265bba}
@mozilla.org/ipc/lock-service;1,{d9e56bf8-e32e-4b6d-87f1-06d73b0ce7ca}
@mozilla.org/ipc/service;1,{9f12676a-5168-4a08-beb8-edf8a593a1ca}
@virtualbox.org/CallbackWrapper;1,{49ee8561-5563-4715-b18c-a4b1a490dafe}
@virtualbox.org/VirtualBox;1,{b1a7a4f2-47b9-4a1e-82b2-07ccd5323c3f}
@mozilla.org/ipc/dconnect-service;1,{63a5d9dc-4828-425a-bd50-bd10a4b26f2c}
@mozilla.org/ipc/transaction-service;1,{1403adf4-94d1-4c67-a8ae-d9f86972d378}
[CATEGORIES]
xpcom-startup,ipcDConnectService,@mozilla.org/ipc/dconnect-service;1 |
New created compreg.dat
| Code: | cat .VirtualBox/compreg.dat
Generated File. Do not edit.
[HEADER]
Version,0,5
[COMPONENTS]
rel:VBoxSVCM.so,1749442381119
rel:VBoxC.so,1749442381150
rel:VBoxXPCOMIPCC.so,1749442381120
[CLASSIDS]
{9f12676a-5168-4a08-beb8-edf8a593a1ca},,,,rel:VBoxXPCOMIPCC.so
{b1a7a4f2-47b9-4a1e-82b2-07ccd5323c3f},,,,rel:VBoxSVCM.so
{3c02f46d-c9d2-4f11-a384-53f0cf917214},,,,rel:VBoxC.so
{dd3fc71d-26c0-4fe1-bf6f-67f633265bba},,,,rel:VBoxC.so
{63a5d9dc-4828-425a-bd50-bd10a4b26f2c},,,,rel:VBoxXPCOMIPCC.so
[CONTRACTIDS]
@virtualbox.org/Session;1,{3c02f46d-c9d2-4f11-a384-53f0cf917214}
@virtualbox.org/VirtualBoxClient;1,{dd3fc71d-26c0-4fe1-bf6f-67f633265bba}
@mozilla.org/ipc/service;1,{9f12676a-5168-4a08-beb8-edf8a593a1ca}
@virtualbox.org/VirtualBox;1,{b1a7a4f2-47b9-4a1e-82b2-07ccd5323c3f}
@mozilla.org/ipc/dconnect-service;1,{63a5d9dc-4828-425a-bd50-bd10a4b26f2c}
[CATEGORIES]
xpcom-startup,ipcDConnectService,@mozilla.org/ipc/dconnect-service;1 |
By the way, I had earlier tried virtualbox-7.0.26, but it did not provide a desktop file in /usr/share/applications/ and there was no VirtualBox sysmlink in /usr/bin, so I quickly gave up on it, figuring I'd have to sink or swim with 7.1.8. I seem to be swimming OK now.
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
| 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
|
|
Portage & Programming
