Virtualbox error after update [reopened]

Message

Tony0945 · Post by **Tony0945** » Mon Feb 08, 2021 5:09 pm

The given path '{94a50a5e-3c17-4856-b3a5-5b35532c137d}' is not fully qualified.


Result Code: 
VBOX_E_FILE_ERROR (0x80BB0004)
Component: 
MediumWrap
Interface: 
IMedium {ad47ad09-787b-44ab-b343-a082a3f2dfb1}
Callee: 
IVirtualBox {d0a0163f-e254-4e5b-a1f2-011cf991c38d}
Callee RC: 
VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)

Worked fine on the previous stable release of Vbox. This was supposed to be a minor stable upgrade. Yes I rebooted after the portage upgrade.
How do I find what file or vitual equipment that UUID refers to?

alamahant · Post by **alamahant** » Mon Feb 08, 2021 5:36 pm

Maybe

Code: Select all

VBoxManage showvminfo 94a50a5e-3c17-4856-b3a5-5b35532c137d

?

Tony0945 · Post by **Tony0945** » Mon Feb 08, 2021 8:12 pm

Code: Select all

~/.VirtualBox $ VBoxManage showvminfo 94a50a5e-3c17-4856-b3a5-5b35532c137d 
VBoxManage: error: Could not find a registered machine with UUID {94a50a5e-3c17-4856-b3a5-5b35532c137d}
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee nsISupports
VBoxManage: error: Context: "FindMachine(Bstr(VMNameOrUuid).raw(), machine.asOutParam())" at line 2714 of file VBoxManageInfo.cpp

saellaven · Post by **saellaven** » Mon Feb 08, 2021 8:17 pm

How about:
VBoxManage list vms

Tony0945 · Post by **Tony0945** » Mon Feb 08, 2021 9:44 pm

saellaven wrote:How about:
VBoxManage list vms

Returns a blank!
But I do have VMs. Win10, WinXP, Devuan, Gentoo, Void Linux and Win7
All open except for Win7 which has the error.
I hate to go through the laborious process of creating new blank vdi's, installing Win7 (does Microsoft even accept new installs?) finding and installing all the software ...

I get a message when trying to launch Win7 "cannot attach medium palemoonbuilddisk.vhd" which is a BIG 124G file containing several version of PaleMoon software, Visual Studio and more.
This is to be Win7's E: drive. Or rather it was Win7's E:drive because Win7 won't even try to launch because of the error. I'm willing to blow it away if I have to. But I don't really want to.

Another VBox message that seems to make some sense!

Code: Select all

The given path '{94a50a5e-3c17-4856-b3a5-5b35532c137d}' is not fully qualified.

7 copies of the message.
Everything worked yesterday before I updated from portage. With virtualbox not running I hasten to add!

saellaven · Post by **saellaven** » Mon Feb 08, 2021 9:56 pm

have you tried downgrading back to 6.1.16-r1 to see if it sees everything again?

I'm on 6.1.18 and haven't had any issues with my virtual machine.

Do you have the gui interface installed? Can that see the VMs and/or get the broken one to launch? Are you doing snapshots/cloning and maybe an uuid got messed up in there?

I don't see anything glaring in the changelog.

saellaven · Post by **saellaven** » Mon Feb 08, 2021 10:05 pm

How about your .VirtualBox/VirtualBox.xml

You should have something equivalent to

Code: Select all

    <MachineRegistry>
      <MachineEntry uuid="{11d666d2-bf20-4a08-b733-fe191cd4c51f}" src="/home/keri/.VirtualBox/Machines/Win10/Win10.vbox"/>
    </MachineRegistry>

In there, listing your fully qualified path

Code: Select all

$ VBoxManage showvminfo Win10
Name:                        Win10
Groups:                      /
Guest OS:                    Windows 10 (64-bit)
UUID:                        11d666d2-bf20-4a08-b733-fe191cd4c51f
Config file:                 /home/keri/.VirtualBox/Machines/Win10/Win10.vbox
Snapshot folder:             /home/keri/.VirtualBox/Machines/Win10/Snapshots
Log folder:                  /home/keri/.VirtualBox/Machines/Win10/Logs
Hardware UUID:               11d666d2-bf20-4a08-b733-fe191cd4c51f
...
...
SATA (0, 0): /home/keri/.VirtualBox/Machines/Win10/Win10.vdi (UUID: 29850167-a677-4c1a-8a63-37b228d6d8ce)

Tony0945 · Post by **Tony0945** » Mon Feb 08, 2021 11:13 pm

saellaven wrote:have you tried downgrading back to 6.1.16-r1 to see if it sees everything again?

I'm on 6.1.18 and haven't had any issues with my virtual machine.

Do you have the gui interface installed? Can that see the VMs and/or get the broken one to launch? Are you doing snapshots/cloning and maybe an uuid got messed up in there?

I don't see anything glaring in the changelog.

No, haven't downgraded.
Yes, I have the GUI
All launch except the broken one.

What I've done is this:
Since I can't launch or even edit any more the old VM,
I created a new VM callling it "Windows-7" I attached the Win7.vdi, this came up and worked!
Next, I added the palemoonbuilddisk.vhd but not as the boot drive. on launch the machine was locked in a boot loop and I had to log out of openbox to stop. Then the WM was inaccessible.
So, I repeated the process and have a Win7 with only a C: drive that boots, runs TurboTax 2019 and VideoRedo v6, both software that I paid for.
I'm not really interested in building palemoon for windows any more, so I think I will forget that vhd and maybe reclaim the disk space. 128G is nothing to sneeze at.

Tony0945 · Post by **Tony0945** » Sat Mar 13, 2021 3:03 pm

So now win7 comes up and says it is not "genuine" and I can't access the LAN anymore. I did get a workaround by attaching a USB stick as a shared folder for file transfer.
Are Win 7 license servers still up?