I cannot seem to get my VM to run anymore and am at a loss for things to investigate.
Any help appreciated.
When trying to run an existing Windows 10 VM on Gentoo Linux using the GUI, I get the following error:
Code:
Select all
Het is niet gelukt een sessie te openen voor virtuele machine Windows 10 for Teams.
The virtual machine 'Windows 10 for Teams' has terminated unexpectedly during startup with exit code 1 (0x1).
Resultaatcode: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
I've added the corresponding logs I see in the ~/.VirtualBox folder. There is no VBox.log generated (last one is from Feb. 4th, I guess when I last successfully ran the VM, I've attached that one).
Some more info:
I've successfully run this VM before on the same machine, with the same kernel (I've tried two, actually, 5.15.12 and 5.15.19 the logs are from the newer kernel; both kernels give the same result)
I've tested with reinstalled versions and tried with both Virtualbox 6.1.28 (last version when it worked) and 6.1.32
I've looked at the kernel modules and /dev file and they are loaded/they currently have the correct permissions (see below)
My user is in the vboxusers group
I've created a new (Windows) VM, but when I try to run it, it gives the same error
Code:
Select all
# lsmod | grep vbox
vboxnetflt 28672 0
vboxnetadp 24576 0
vboxdrv 401408 2 vboxnetadp,vboxnetflt
# ls -al vbox*
crw-rw---- 1 root vboxusers 10, 125 2022-02-07 21:16 vboxdrv
crw-rw---- 1 root vboxusers 10, 124 2022-02-07 21:16 vboxdrvu
crw-rw---- 1 root vboxusers 10, 123 2022-02-07 21:16 vboxnetctl
vboxusb:
total 0
drwxrwx--- 6 root vboxusers 120 2022-02-07 21:16 .
drwxr-xr-x 20 root root 3640 2022-02-07 21:17 ..
drwxr-x--- 2 root vboxusers 60 2022-02-07 21:16 002
drwxr-x--- 2 root vboxusers 140 2022-02-07 21:16 004
drwxr-x--- 2 root vboxusers 80 2022-02-07 21:16 005
drwxr-x--- 2 root vboxusers 80 2022-02-07 21:16 006
The only thing that changed AFAICT is some software updates.
mpack wrote:
Post a VM log. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.
I've edited my original post to add such a log. Do note that this is from the last successful run and no such log is generated when I now try to run my VM.
The log shows that you are not using VirtualBox.
00:00:01.163642 VirtualBox VM
6.1.28_Gentoo
r147628 linux.amd64 (Jan 29 2022 21:40:04) release log
It shows instead that you are using a third party build by the Gentoo people, from the VBox open source code.
Please purge that version and install the official version from the
Downloads
area of this site, then lets see if you still have a problem. If you want to continue using the Gentoo version then you need to get support from them as well.
I'll give you one tip that "terminated during startup with exit code 1" on a Linux host usually means some kind of conflict with KVM.
Please try to start the VM from within a terminal, which usually gives a more detailed error message:
Code:
Select all
VirtualBoxVM --startvm "Windows 10 for Teams"
fth0 wrote:
Please try to start the VM from within a terminal, which usually gives a more detailed error message:
Code:
Select all
VirtualBoxVM --startvm "Windows 10 for Teams"
Thanks for the tip. I get
Code:
Select all
$ VirtualBoxVM --startvm "Windows 10 for Teams"
VirtualBoxVM: Error -610 in supR3HardenedMainInitRuntime!
VirtualBoxVM: dlopen("/usr/lib64/virtualbox/VBoxRT.so",) failed: <NULL>
VirtualBoxVM: Tip! It may help to reinstall VirtualBox.
Reinstalling VirtualBox did not change this.
But: I found (sorry, do not have rights to post links…)
www . virtualbox . org ticket 16759
forums . virtualbox . org topic 88900
These pages suggest that a wrong (non-root) ownership of anything in the path of /usr/lib64/virtualbox/VBoxRT.so could be to blame. And indeed it was! (I know what mistake I made
.) Now my VM runs again.
Many thanks!
fth0 wrote:
If you'd tell us what you did, it could help others in the same situation ...
I use a non-root user to build my kernels. For convenience, I make the whole of /usr/src owned by that user. Every time my package manager installs a new kernel source, it does so in a folder with root as the user, so I repeat this from time to time. I must have chown'ed /usr itself as well at some point, by invoking ‘chown kbuilder:kbuilder .*’ in /usr/src, where the ‘.*’ also matches ‘..’.
