After updating to newest version, i now recieve an error when trying to start my VM
Failed to load R0 module D:\/VMMR0.r0: The path is not clean of leading double slashes: 'D:\/VMMR0.r0' (VERR_SUPLIB_PATH_NOT_CLEAN).
Failed to load VMMR0.r0 (VERR_SUPLIB_PATH_NOT_CLEAN).
Can someone help me plz
Ive uploaded the VB.log file
New Version error
New Version error
- Attachments
-
ParrotOS-2021-03-10-09-35-01.log- (2.56 KiB) Downloaded 7 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: New Version error
I've never heard of anything called "newest version."
Seriously, please always be explicit what software you are talking about, and what version.
If the software is VirtualBox, then the truncated log you provided says 6.1.8, which is far from being the newest version: in fact there have been 5 new releases since then, the current version is 6.1.18.
The only thing your problem reminds me of: do not install VMs in the root folder of a drive.
Seriously, please always be explicit what software you are talking about, and what version.
If the software is VirtualBox, then the truncated log you provided says 6.1.8, which is far from being the newest version: in fact there have been 5 new releases since then, the current version is 6.1.18.
The only thing your problem reminds me of: do not install VMs in the root folder of a drive.
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: New Version error
orbit4l wrote:D:\/VMMR0.r0
Virtualbox itself is installed in the root of the D drive, which is definitely not going to fly.orbit4l's log wrote:00:00:05.072081 Executable: D:\VirtualBoxVM.exe
Uninstall Virtualbox, and reinstall in C:\Program Files, where the default is.
Re: New Version error
My apologies mate, bit of a noob.. thanks for the info. I wanted to preserve what little drive room i have left on C:/ so i attempted to install it to a second ssd drive. I will reinstall on C drive, thank you.mpack wrote:I've never heard of anything called "newest version."
Seriously, please always be explicit what software you are talking about, and what version.
If the software is VirtualBox, then truncated log you provided says 6.1.8, which is far from being the newest version: in fact there have been 5 new releases since then, the current version is 6.1.18.
The only thing your problem reminds me of: do not install VMs in the root folder of a drive.
-
BillG
- Volunteer
- Posts: 5106
- Joined: 19. Sep 2009, 04:44
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows 10,7 and earlier
- Location: Sydney, Australia
Re: New Version error
If you are short of disk space, or any other resource, you should not be thinking about running vms. A vm is a way of using spare resources on your PC. Everything the vm uses is a cost to the host system.
Bill
-
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: New Version error
The software size is miniscule, and installing it on D: will not change where your data is located - which will still be on C:. And your data is definitely NOT miniscule.orbit4l wrote: I wanted to preserve what little drive room i have left on C:/ so i attempted to install it to a second ssd drive.
Uninstall VirtualBox, then reinstall without changing any of the install wizard defaults (unless it defaults to the same as you did before).
Then when you run the software for the first time, before creating any VMs, you can go into File|Preferences and set the folder to use for future VMs. That folder can be on the D: drive if it is suitable (basically it needs to be fast and huge). A USB flash drive is a no-no, a VM will destroy that. USB2 mechanical drives will be usable but slow. USB3 begins to be usable, but you must be very careful not to unplug a drive while the VM is running - and never ever use the VHD image format.
If you already have a VM and want to move it to a new drive then right click it in the manager and choose Move...