virtualbox.org

I had some machines on an old vm, haven't accessed them in some months, so I tried today and I got the following errors, attached below. I would appreciate if someone could help me out here on what could possibly the problem and how to go about fixing it.

Cannot register the hard disk 'Y:\vm\Hifi\Hifi.vdi' {82b1d5ab-3423-47f5-a507-b6d1da6593bc} because a hard disk 'Y:\vm\Hifi\Hifi.vdi' with UUID {e0a76a67-4c04-4612-ba61-58ea6a7c8180} already exists.

Result Code:
E_INVALIDARG (0x80070057)
Component:
VirtualBoxWrap
Interface:
IVirtualBox {0169423f-46b4-cde9-91af-1e9d5b6cd945}

Start tag expected, '<' not found.
Location: 'Y:\vm\mypc\mypc.vbox', line 1 (0), column 1.
F:\tinderbox\win-5.1\src\VBox\Main\src-server\MachineImpl.cpp[485] (long __cdecl Machine::initFromSettings(class VirtualBox *,const class com::Utf8Str &,const class com::Guid *)).

Result Code:
E_FAIL (0x80004005)
Component:
MachineWrap
Interface:
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
Callee:
IVirtualBox {0169423f-46b4-cde9-91af-1e9d5b6cd945}

Start tag expected, '<' not found.
Location: 'Y:\vm\USA\USA\USA.vbox', line 1 (0), column 1.
F:\tinderbox\win-5.1\src\VBox\Main\src-server\MachineImpl.cpp[485] (long __cdecl Machine::initFromSettings(class VirtualBox *,const class com::Utf8Str &,const class com::Guid *)).

Result Code:
E_FAIL (0x80004005)
Component:
MachineWrap
Interface:
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
Callee:
IVirtualBox {0169423f-46b4-cde9-91af-1e9d5b6cd945}

The virtual machine 'Win7' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'Y:\vm\Win7\Logs\VBoxHardening.log'.

Result Code:
E_FAIL (0x80004005)
Component:
MachineWrap
Interface:
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

The virtual machine 'winnie' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'Y:\vm\winnie\Logs\VBoxHardening.log'.

Result Code:
E_FAIL (0x80004005)
Component:
MachineWrap
Interface:
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

The virtual machine 'X' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'Y:\vm\X\Logs\VBoxHardening.log'.

Result Code:
E_FAIL (0x80004005)
Component:
MachineWrap
Interface:
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

Got a good list of errors, there!

Disks can't be registered twice:

stan here wrote:Cannot register the hard disk 'Y:\vm\Hifi\Hifi.vdi' {82b1d5ab-3423-47f5-a507-b6d1da6593bc} because a hard disk 'Y:\vm\Hifi\Hifi.vdi' with UUID {e0a76a67-4c04-4612-ba61-58ea6a7c8180} already exists

VM's can't be registered twice either. One does not need to register a VM to just run it if it is already registered. Is there more to your procedure besides just running a VM you haven't used in a while?

*******************************

stan here wrote:Start tag expected, '<' not found.
Location: 'Y:\vm\mypc\mypc.vbox', line 1 (0), column 1.

For the VMs having this error:
Reboot the host so no Virtualbox processes are running.
Rename the existing "vm name.vbox" file to "vm name.vbox-bad"
Rename the existing "vm name.vbox-prev" file to "vm name.vbox"
Try the VM.

*******************************

stan here wrote:The virtual machine 'Win7' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'Y:\vm\Win7\Logs\VBoxHardening.log'.

Zip the reported hardening log, and post the zip file, using the forum's Upload Attachment tab.

scottgus1 wrote:Disks can't be registered twice:
stan here wrote:Cannot register the hard disk 'Y:\vm\Hifi\Hifi.vdi' {82b1d5ab-3423-47f5-a507-b6d1da6593bc} because a hard disk 'Y:\vm\Hifi\Hifi.vdi' with UUID {e0a76a67-4c04-4612-ba61-58ea6a7c8180} already exists

VM's can't be registered twice either. One does not need to register a VM to just run it if it is already registered. Is there more to your procedure besides just running a VM you haven't used in a while?

I am not exactly sure I understand what you mean by VM's cant vbe registered twice, its not registered to the vm I am trying to run it on, all I am trying to do is run the vm as I haven't done that in months.

*******************************

scottgus1 wrote:
stan here wrote:Start tag expected, '<' not found.
Location: 'Y:\vm\mypc\mypc.vbox', line 1 (0), column 1.
For the VMs having this error:
Reboot the host so no Virtualbox processes are running.
Rename the existing "vm name.vbox" file to "vm name.vbox-bad"
Rename the existing "vm name.vbox-prev" file to "vm name.vbox"
Try the VM.

For this here, I can't find a vm name.vbox, I can only see the vm name.vox-prev file. Here is a screenshot of the folder and the content in it

: MYPC vm.JPG (22.73 KiB) Viewed 4652 times

*******************************

scottgus1 wrote:
stan here wrote:The virtual machine 'Win7' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'Y:\vm\Win7\Logs\VBoxHardening.log'.
Zip the reported hardening log, and post the zip file, using the forum's Upload Attachment tab.

I have attached the hardening log

The hardening log now shows a different error, indicating that Virtualbox may not be installed, or some security software on your PC is really interfering. You have Avast and Malwarebytes installed. Please uninstall (not just disable) these, as a test. Also, if you have Trusteer Rapport or HP ProtectTools installed, uninstall these too. Then do these things, please follow these instructions exactly:

Reboot the PC.
Re-install Virtualbox by right-clicking the Virtualbox installer and choose Run As Administrator.
Reboot the host again.
Open Virtualbox. Don't try the old VMs yet.
Make a new VM using an Ubuntu ISO, see if it runs OK. The Ubuntu VM will confirm if Virtualbox is out of the hardening problems.

*********************************

stan here wrote:I can't find a vm name.vbox

Web-search how to show all extensions on your Windows host, then you'll find it. (Of course, "vm name" should be replaced by the actual name of the VM, example, in your screenshot it would be "mypc.vbox". I had one lubbox say "I can't find a "vm name.vbox" and was actually looking for a file called exactly "vm name.vbox"

)

*********************************

stan here wrote: its not registered to the vm I am trying to run it on,

The VM is the virtual machine, also called the "guest". The computer running the VM is the "host". So this would be:

stan here wrote: its not registered to the host I am trying to run it on,

You have to have the VM registered on the host in order to run it. "Registering" means to have the VM showing up in the main Virtualbox window's list of VMs. Disks have to be "registered" by showing up in the main Virtualbox window's Virtual Media Manager (found under the File menu.

The error "already exists" occurs because the disk file is already registered in the Virtual Media Manager, and something you're doing is trying to register it again.

From the unusual use of terminology and other indications I do not fully understand what you're doing. Clicking "start" on a VM you have not used in a while would not cause a re-register of an already-registered disk file. Please explain exactly, step-by-step, what you're doing that causes these errors.

scottgus1 wrote: Web-search how to show all extensions on your Windows host, then you'll find it. (Of course, "vm name" should be replaced by the actual name of the VM, example, in your screenshot it would be "mypc.vbox". I had one lubbox say "I can't find a "vm name.vbox" and was actually looking for a file called exactly "vm name.vbox" )
.

I did this, renamed the first one to .vbox-bad and renamed the .vbox-prev file to .vbox, and then i got this error

Implementation of the USB 2.0 controller not found!
Because the USB 2.0 controller state is part of the saved VM state, the VM cannot be started. To fix this problem, either install the 'Oracle VM VirtualBox Extension Pack' or disable USB 2.0 support in the VM settings.
Note! This error could also mean that an incompatible version of the 'Oracle VM VirtualBox Extension Pack' is installed (VERR_NOT_FOUND).

Result Code:
E_FAIL (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Check your Extension Pack version. It may be missing or the wrong version. Virtualbox version and Extension Pack version must match exactly.

scottgus1 wrote:Check your Extension Pack version. It may be missing or the wrong version. Virtualbox version and Extension Pack version must match exactly.

How do I Check for this? I can;t find it inside the folder of the virtualbox, the virtualbox I use shows as version 5.1.22r115126

Reboot the host PC so no Virtualbox processes are running.
Right-click the Virtualbox icon and choose Run As Administrator.
File menu, Preferences, Extensions, will show the Extension Pack installed.
Virtualbox must be running As Administrator to have permissions to change the Extension Pack.

After changing the Extension Pack, close Virtualbox and wait one minute for the background service to disappear. Virtualbox should not run VMs while running as admin, except in special circumstances like running a Raw Disk Access VM. Running as Admin enables greater permissions, which malware can use to get deeper into a host PC.

scottgus1 wrote:Reboot the host PC so no Virtualbox processes are running.
Right-click the Virtualbox icon and choose Run As Administrator.
File menu, Preferences, Extensions, will show the Extension Pack installed.
Virtualbox must be running As Administrator to have permissions to change the Extension Pack.

After changing the Extension Pack, close Virtualbox and wait one minute for the background service to disappear. Virtualbox should not run VMs while running as admin, except in special circumstances like running a Raw Disk Access VM. Running as Admin enables greater permissions, which malware can use to get deeper into a host PC.

So I did as you told me to and I got this, seems no extension found

: vm1.JPG (65.33 KiB) Viewed 4561 times

Ok, this error could also mean that the VM is trying to use USB 2 or 3 and the Extension Pack is not loaded. Get the matching EP and install it.

scottgus1 wrote:Ok, this error could also mean that the VM is trying to use USB 2 or 3 and the Extension Pack is not loaded. Get the matching EP and install it.

Some good news, after installing the extension 2 machines now work. However 2 wouldn't run and another 2 wouldn't attach.

Here are the errors

Cannot register the hard disk 'Y:\vm\Hifi\Hifi.vdi' {82b1d5ab-3423-47f5-a507-b6d1da6593bc} because a hard disk 'Y:\vm\Hifi\Hifi.vdi' with UUID {e0a76a67-4c04-4612-ba61-58ea6a7c8180} already exists.

Result Code:
E_INVALIDARG (0x80070057)
Component:
VirtualBoxWrap
Interface:
IVirtualBox {d0a0163f-e254-4e5b-a1f2-011cf991c38d}

**********************************************************************************************************************************************************************************************************************

Failed to open virtual machine located in Y:/vm/USA/USA/USA.vbox.

Start tag expected, '<' not found.

Location: 'Y:\vm\USA\USA\USA.vbox', line 1 (0), column 1.

F:\tinderbox\win-6.1\src\VBox\Main\src-server\MachineImpl.cpp[499] (long __cdecl Machine::initFromSettings(class VirtualBox *,const class com::Utf8Str &,const class com::Guid *)).

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
Callee: IVirtualBox {d0a0163f-e254-4e5b-a1f2-011cf991c38d}

**********************************************************************************************************************************************************************************************************************

Could not open the medium 'Y:\vm\winnie\winnie.vdi'.
VD: error VERR_FILE_NOT_FOUND opening image file 'Y:\vm\winnie\winnie.vdi' (VERR_FILE_NOT_FOUND).

Result Code:
E_FAIL (0x80004005)
Component:
MediumWrap
Interface:
IMedium {ad47ad09-787b-44ab-b343-a082a3f2dfb1}

**********************************************************************************************************************************************************************************************************************

Could not open the medium 'G:\vm\pcx2\pcx2.vdi'.
VD: error VERR_PATH_NOT_FOUND opening image file 'G:\vm\pcx2\pcx2.vdi' (VERR_PATH_NOT_FOUND).

Result Code:
E_FAIL (0x80004005)
Component:
MediumWrap
Interface:
IMedium {ad47ad09-787b-44ab-b343-a082a3f2dfb1}

Read the errors, they are clear what the problem is. Two of them were covered already: one you should recognize right away, one will be familiar if you note that < is the < symbol.

scottgus1 wrote:Read the errors, they are clear what the problem is. Two of them were covered already: one you should recognize right away, one will be familiar if you note that < is the < symbol.

I know I am asking what could be the possible solution to fixing these errors

stan here wrote: I know I am asking what could be the possible solution to fixing these errors

Obviously the drive letter changed. Change it back or unregister the VM then re-register from the new location.

I'll add that a clear problem has a clear solution, Stan. It is beneficial for you to try to come up with a solution based on the clear problem. You asked about the 'already exists' and '< not found' errors before: Repeat the suggested solution given before. As for 'file/path not found'? Find them. Mpack has given you a very big clue on where to search.

I already gave you a fish. Now I'm trying to teach you to fish.

virtualbox.org

Errors while trying to attach my machines

Errors while trying to attach my machines

Re: Errors while trying to attach my machines

Re: Errors while trying to attach my machines

Re: Errors while trying to attach my machines

Re: Errors while trying to attach my machines

Re: Errors while trying to attach my machines

Re: Errors while trying to attach my machines

Re: Errors while trying to attach my machines

Re: Errors while trying to attach my machines

Re: Errors while trying to attach my machines

Re: Errors while trying to attach my machines

Re: Errors while trying to attach my machines

Re: Errors while trying to attach my machines

Re: Errors while trying to attach my machines

Re: Errors while trying to attach my machines