I have several VMs saved which I can access from either my Windows boot or a Linux boot.
I have no issue with any of them apart from a WindowsXP VM. That probably isn't relevant with this error.
It's been a while since I have used VirtualBox from any boot but they all work apart from WindowsXP. I've changed some drives around and had to re-register the VMs in the VB Manager.
I will try to upload a screenshot.
What I'd like to know is if it is possible to fix this error? The VM does not appear in the VB Manager so I can't see any way to access it to delete the offending drive(s).
I have looked through the VB manage documents but couldn't find a command that will do this but I am not familiar with the tool.
I have searched this forum but it is difficult to know what phrase to search for. I failed to find any reference to this error.
A Google search did come up with a few hits on this error message but none relevant to my situation.
If it cannot be fixed then I will just delete the VM and create a new one but I'd like to 'rescue' this one if possible.
Probably not relevant but here are my specs: HP Z420 E1660v2 3.70GHz x 6 Nvidia GTx 1650 32GB ram Win10, Fedora 35, Mint 20.1 VirtualBox 6.1 on all systems.
Thanks
Colin
[Solved] VM fails to start due to drive conflicts
[Solved] VM fails to start due to drive conflicts
- Attachments
-
- VBoxerror.png (56.97 KiB) Viewed 1623 times
-
- Volunteer
- Posts: 5104
- Joined: 19. Sep 2009, 04:44
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows 10,7 and earlier
- Location: Sydney, Australia
Re: VM fails to start due to drive conflicts
From the VM VirtualBox Manager window select File then Virtual Media Manager, select Optical Disks and remove VBoxGuestAdditions.iso .
When you start your vm it is trying to register a file which already is registered.
When you start your vm it is trying to register a file which already is registered.
Bill
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: VM fails to start due to drive conflicts
The problem is caused because for some reason in the past you downloaded another copy of an ISO that is bundled with VirtualBox. Some VMs have the bundled ISO still mounted, and the new VM tries to reference the downloaded copy. VirtualBox does not allow two copies of the same virtual drive file to be registered.
Re: VM fails to start due to drive conflicts
mpack, yes, I realized that it was something I'd done in the past but I couldn't find how to get it sorted out.mpack wrote:The problem is caused because for some reason in the past you downloaded another copy of an ISO that is bundled with VirtualBox. Some VMs have the bundled ISO still mounted, and the new VM tries to reference the downloaded copy. VirtualBox does not allow two copies of the same virtual drive file to be registered.
Solved now, thanks to Bill's suggestion.
Re: VM fails to start due to drive conflicts
Thanks, that worked. I had quite a few unattached ISOs as well.BillG wrote:From the VM VirtualBox Manager window select File then Virtual Media Manager, select Optical Disks and remove VBoxGuestAdditions.iso .
When you start your vm it is trying to register a file which already is registered.
Everything is working now.
Colin