I installed a new system and liked to install VirtualBox again with an existing Windows 10 guest.
I got the error message that the vboxdrv is not loaded or a permission problem with /dev/vboxdrv.
I tried to recompile the kernel:
sudo /sbin/vboxconfig
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.
There were problems setting up VirtualBox. To re-start the set-up process, run
/sbin/vboxconfig
as root.
Any ideas - I checked dmesg but this doesnt mean a lot to me...
Thanks
Last edited by mpack on 2. Feb 2018, 12:38, edited 2 times in total.
Reason:Enclosed the information in [pre] tag for better readability
curano wrote:I checked dmesg but this doesnt mean a lot to me...
You could post it here, someone might know. Otherwise, we'll never know...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Thanks, but no thanks - not going to click on a random link to an external site!
socratis wrote:You could post it here
-Andy
My crystal ball is currently broken. If you want assistance you are going to have to give me all of the necessary information.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
You would need the 'dmesg' output from when you were trying to install the GAs. Not a generic run. There's not a single mention about "vbox", "VirtualBox", "fail" or "error" in what you posted. Unless I'm not reading it right...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Looks like your reading of it is spot on to me. It looks like a fairly bland Linux boot where nothing exciting really happened!
-Andy.
My crystal ball is currently broken. If you want assistance you are going to have to give me all of the necessary information.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
1. Boot the vm
2. Run the /sbin/vboxconfig command as root
3. Cross your fingers and hope it generates the same result as the original post
4. Post the output of dmesg
5. Power off vm
6. Go for coffee
(Steps 5 and 6 are entirely optional)
-Andy.
My crystal ball is currently broken. If you want assistance you are going to have to give me all of the necessary information.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
Kernel driver not installed (rc=-1908)
where sublibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED -The support driver is not installed. On linux, open returned ENOENT.
Additional details:
The virtual machine 'Windows 10' has terminated unexpectedly during startup with exit code 1 (0x1).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}
Sorry, I can't provide another dmesg output.
The last one was directly after booting Fedora 27 and starting VirtualBox.
After the error I executed /sbin/vboxconfig and saved dmesg output into a log file.
It seems that the system will not try to compile and add the driver to the kernel.
All kernel-devel, kernel-debug-level and kernel-headers are here.
gcc and the libraries are installed too.
So what's going wrong?
It was running under Fedora 27 fine. I just installed a new system with Fedora 27...