Windows 10 guest fails to start in VirtualBox on Fedora 38
I've been struggling to find a way around this..
Attempting to start Windows 10 guest in Virtualbox, I get the following message... Code:
Kernel driver not installed (rc=-1908) Code:
$sudo dnf install akmod-VirtualBox kernel-devel-$(uname -r) Code:
If you installed VirtualBox packages and don't want reboot the system, you may need load the kernel driver, doing as root: akmods; systemctl restart vboxdrv.service Code:
sudo akmods; systemctl restart vboxdrv.service It would seem that there have been a number of calls for help on this or similar issues, the responses to which I have tried to follow to no avail. Anyone have any answers or ideas that might help? Cheers, Terry |
Have you attempted to start up any OTHER operating systems under VB?
IT might help to understand if this is a problem with your VB install, or if it is specific to Windows as a client. |
Quote:
I have two VB guests, Win XP and Win 10. Both throw the same error message. There have been a couple of VB updates since the F38 install, but the behaviour has not changed. There are numerous posts on the web re similar issues. Some have mentioned that Oracle have changed the way keys are handled. My VB is installed from Fedora repos, so I would guess the advice re keys wouldn't apply to VB from Fedora...not sure about that. Cheers, Terry |
Well, for totally different bur distantly related reasons I stopped using Fedora long ago.
And recently I find I prefer QEMU under VirtualMachineManager over VirtualBox. Also I REALLY distrust Oracle! If you have verified that VB on Fedora fails for you (and others), and there does not appear to be a fix or work-around, then do something else. It is not like you are devoid of other options! Part of your problem is that Fedora is unstable and rapidly changing. Perhaps you need something that does not change and break things as often? |
Quote:
Thanks for your comments. Cheers, Terry |
Quote:
Best of luck! |
I finally have a solution...yet to determine if it is permanent solution.
In my case the fix has been to get into the BIOS and disable secure boot. I had seen stories that this was the solution, but looking into BIOS options it looked like secure boot wasn't enabled...finally had another good poke around in BIOS and found it! Cheers, Terry |
All times are GMT -5. The time now is 02:02 AM. |