| View previous topic :: View next topic |
| Author |
Message |
pablo_supertux
Advocate
Joined: 25 Jan 2004
Posts: 2953
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: 2953
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: 2953
Location: Somewhere between reality and Middle-Earth and in Freiburg (Germany)
|
|
| Back to top |
|
|
OldTango
l33t
Joined: 21 Feb 2004
Posts: 719
|
| 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 |
|
|
|
|
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
