Hi,
I'm under XP SP3 and I want to start a VM using XP SP3 too.
When I start the VM, I have this error message : "Cannot access the kernel driver."
Have you got answers ?
Impossible to start a VM XP SP3
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Impossible to start a VM XP SP3
This usually means that you have not installed the software properly, e.g. in admin mode (not the same as the admin account) using the proper installer and for the current user (you).
Also see Minimum information needed for assistance.
Also see Minimum information needed for assistance.
Re: Impossible to start a VM XP SP3
Sorry.
I use VirtualBox 4.2.6 and my OS and the VM are on a 32 bits architecture. I have just installed VirtualBox in admin mode but it's the same.
I use VirtualBox 4.2.6 and my OS and the VM are on a 32 bits architecture. I have just installed VirtualBox in admin mode but it's the same.
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Impossible to start a VM XP SP3
I suggest uninstalling, then install again inside your normal user account, using "Run as administrator" on the installer to ensure that device drivers are installed.
If the problem persists after that then post the installer log file (as a .zip). See here for how to enable msi installer logging.
If the problem persists after that then post the installer log file (as a .zip). See here for how to enable msi installer logging.
Re: Impossible to start a VM XP SP3
This is the file log.
- Attachments
-
- MSI6e811.rar
- (37.65 KiB) Downloaded 5 times
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Impossible to start a VM XP SP3
I'm afraid I'm going to have to pass on this one. I see an error associated with "VBoxDrv" in the msi install log, however I don't know why that would happen or if it is relevant. Perhaps you should raise a BugTracker ticket for it. And, if you are aware of anything unusual about the host then better mention it.