[VirtualBox] ne peut pas accéder au pilote du noyau
Solved
nono313
Posted messages
196
Status
Member
-
coggia -
coggia -
Hello,
after installing version 2.2.2 of VirtualBox, I launched the software.
When I click on a virtual machine to start it, I get a message:
I have a window with a progress bar "Spawning session" that stays at 0.
When I click on the "Abort" button of the first window, I get this message displayed:
I want to clarify that the error occurs with all my virtual machines.
I tried to create a new virtual machine from version 2.2.2 but I get the same error message.
after installing version 2.2.2 of VirtualBox, I launched the software.
When I click on a virtual machine to start it, I get a message:
cannot access the kernel driver! make sure the kernel module has been loaded successfully.
I have a window with a progress bar "Spawning session" that stays at 0.
When I click on the "Abort" button of the first window, I get this message displayed:
Result code: E_FAIL (0x80004005 Component: Machine Interface: IMachine {13420cbb-175a-4456-85d0-301126dfdec7} I want to clarify that the error occurs with all my virtual machines.
I tried to create a new virtual machine from version 2.2.2 but I get the same error message.
Configuration: Windows Vista Firefox 3.5
11 answers
-
Hello,
I know it's been years since you solved your problem, but guess what, the bug is still present.
For those interested, I had VirtualBox version 4.1.12 and I encountered a problem where my computer suddenly shut down while my VM was running, anyway.
Upon restarting, I tried to start my VM, and here I am with the error
"make sure the kernel module has been loaded successfully." blablabla
I searched for a solution for a few minutes before stumbling upon yours, which involves installing a version of VirtualBox higher than the one currently installed... and miracle... my VM starts without issue with VirtualBox version 4.2.12.
So where did the problem come from exactly? Maybe some sort of "cache" of VirtualBox that wasn't cleared or something...
Anyway, if you ever run into this problem, you know what to do ;)
And thanks, nono313. -
-
I solved my problem by installing version 2.2.4 of VirtualBox, which was released on May 29.
-
-
-
-
-
-
-
-