virtualbox.org

Hello VM guru's,

I am a novice here and I have to make VM's for class.. Prior to this message I was able to run both my windows 7 and windowsxp servicepack3 VM's. I was trying to install device drivers for the WindowsXP "Base System Device" & Video Controller (VGA Compatible) but when I installed the driver for the Video Controller at school on my VM (which said successful but wasn't because I still had yellow ?) and came back home I got this lovely Runtime Error message below.

Host Machine: Windows 7
VM's: Windows 7 and WindowsXP3



Runtime error opening 'F:\VM\VMWare Machines\Aplus Hardware VM\Windows7_Irani\Windows7_Irani.vbox' for reading: -103 (Path not found.).
E:\tinderbox\win-rel\src\VBox\Main\src-server\MachineImpl.cpp[685] (Machine::registeredInit).
Result Code:
E_FAIL (0x80004005)
Component:
VirtualBox
Interface:
IVirtualBox {c28be65f-1a8f-43b4-81f1-eb60cb516e66}


Any help would be greatful as I am new to this. Simple terms would be the best!!

Thanks guys and gals!

You state:
'F:\VM\VMWare Machines\Aplus Hardware VM\Windows7_Irani\Windows7_Irani.vbox'
But the screen shot say G:\ and also says you have something else registered with the same UUID

You need to get your paths set properly and find out why you have a double registered UUID.
Also just so you know, you cannot install graphics drivers or any other type of hardware drivers in the guest. First they will not work and secondly they could leave your guest in a non-bootable state. You need to install the guest additions (in the guest) instead.

Taking a wild guess...

I suspect he has been running VMs from external drives. However Windows drive letters assigned to external drives tend to change, so when that happened he got the VM not found error. Trying to add the machine back from the new drive letter results compounds this with the duplicated UUID error.

@NanoguyVM. You need to unregister the existing VM before adding the new one. Also be careful about how many (and in what order) you plug USB drives into Windows, as that is what causes the drive letters to be reassigned. You might also want to get familar with the drive manager in Windows, that might allow you to correct the drive letters.

Thanks to both of you, I will try to extract what you guys said.

and Attempt it again.. here are some simple questions but helpful..

1) Do I need to remove the OS on the VM to clear up this UUID ( universally unique identifier (UUID) problem and start fresh?

2) Would either of you guys be down for a Team Viewer session... or do you know any good youtube videos explaining what your doing.. Once I see it done one time I'm golden..

Thanks for responding to my post I am going to professor hopefully he will be able to help me solve this issues..

NanoguyVM wrote:1) Do I need to remove the OS on the VM to clear up this UUID ( universally unique identifier (UUID) problem and start fresh?

No, you don't need to reinstall anything, just unregister the old VM: right click on it, choose "Remove", but don't let VirtualBox delete the physical files. Once the old VM is gone the Machine | Add function should work for the new drive letter.

He fixed it, by re opening the Virtual box software and "discarded it" from the top Menu bar. Which then removed it from the Inaccessible state and reloaded it.

Just like stated from mpak

And he fixed the driver problems VGA/ Base System Device by installing guest additions!! It was amazing lol one click and a restart and EASY.

Thanks for everyone who replied .. I will be posting more soon once I get more experience with VM.

Does anyone know any good websites/videos for VM tutorials ?? I checked youtube.. but would prefer better ones