ERROR "Could not find a hard disk with UUID" after taking snapshot and re-open Portable-VirtualBox.

DarkBlood

Posts: 19

Date of registration: May 31st 2010

Thanks: 45 / 1

1

Monday, May 31st 2010, 7:06am

With Portable-VirtualBox v3.2.0 after taking a snapshot of any virtual machine and then close and open Portable-VirtualBox, it seems to make some error with the ID of the virtual hard disk allocated in those XMLs (VirtualBox.xml, VirtualBox.xml-tmp and VirtualBox.xml-prev).

Source code

Could not find a hard disk with UUID {0b4e9916-451c-440f-a066-d5a8196c40b8}  in the media registry
('D:\Programas\VirtualBox\data\.VirtualBox\VirtualBox.xml').

Result Code:   VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
Component:    VirtualBox
Interface:   IVirtualBox  {3f36e024-7fed-4f20-a02c-9158a82b44e6}

screenshot of the error:

This post has been edited 4 times, last edit by "DarkBlood" (Jun 7th 2010, 7:11am) with the following reason: *moved > "English Support"

1 registered user and 23 guests thanked already.

Users who thanked for this post:

guenter

DarkBlood

Posts: 19

Date of registration: May 31st 2010

Thanks: 45 / 1

2

Monday, June 7th 2010, 7:10am

Portable-VirtualBox v3.2.2 released and still this problem is not solved

I repeat, this problem is exclusively from Portable-VirtualBox and those XMLs.

To reproduce this bug, do this:
1) open Portable-VirtualBox.
2) do any change on the settings of a virtual machine.
3) take a snapshot of that virtual machine (NOT save state).
4) close Portable-VirtualBox.
5) open Portable-VirtualBox.
6) do any change on the settings of the same virtual machine.
7) close Portable-VirtualBox.
8) open Portable-VirtualBox and... BUG DETECTED "hard disk inaccessible" becasuse of those 3 fucking XMLs (VirtualBox.xml, VirtualBox.xml-prev and VirtualBox.xml-tmp).

This post has been edited 1 times, last edit by "DarkBlood" (Jun 7th 2010, 7:12am)

16 guests thanked already.

g-force

Gunnar

Posts: 11,356

Date of registration: Sep 23rd 2008

Thanks: 166 / 162

3

Monday, June 7th 2010, 10:03am

Did you try to backup the XMLs before Screenshot and did you compare them with the XMLs after Screenshot?
Is the direction readable/writeable or is some data set to read-only?

"Von all den Dingen, die mir verloren gegangen sind, habe ich am meisten an meinem Verstand gehangen."

goose

User

Posts: 1

Date of registration: Jun 8th 2010

4

Tuesday, June 8th 2010, 12:23pm

Zunächst erstmal "Hallo" hier im Board! Lese schon über Jahre hier mit, da ich ebensolange überzeugter und dankbarer Nutzer der Portablen-Version von VirtualBox bin! Der aktuelle Fehler seit dem Change auf die Version 3.2.0 (@ DarkBlood exakt beschrieben) hat auch mich getroffen. Allerdings habe ich heute seit Version 3.2.4 einen Workaround gefunden den ich Euch weiterreichen möchte. So habe ich dieses zum Anlass genommen, mich endlich mal zu registrieren ;-)

.

Seit dem Update auf Version 3.2.0 wird im Verzeichnis "Portable-VirtualBox\data\.VirtualBox" beim erstellen eines neuen Sicherungspunktes bzw. beim Rücksetzen auf den letzten Sicherungspunkt der Virtuellen Maschine (bei mir Windows) eine Datei "VirtualBox.xml-tmp" erstellt. Hierin sind u.a. die korrekten Bezeichnungen aller Sicherungspunkte inkl. des zuletzt veränderten (!) hinterlegt.
Beim Neustart von VirtualBox wird allerdings die NICHT aktualiserte Datei "VirtualBox.xml" eingelesen, was dann zum beschriebenen Fehler führt. Um das zu umgehen, braucht vor Start von VirtualBox lediglich die Datei "VirtualBox.xml" gelöscht oder umbenannt UND durch die Datei "VirtualBox.xml-tmp" (die in "VirtualBox.xml" umzubenennen ist) ersetzt zu werden. Damit läßt sich die Virtuelle Maschine wieder problemlos starten!

Since update on version 3.2.0 in the register "Portable-VirtualBox\data\.VirtualBox" when a new snapshot will created or
resetting on the last snapshot of the virtual machine (Windows Seven at me), a file named "VirtualBox.xml-tmp" will save.
Herein are among other items the correct designations of all snapshots inclusive the changed last one(!) deposited.
With the restart of VirtualBox however the UNCHANGED file "VirtualBox.xml" is read in, which causes then the descripted
error. In order to go around, the file "VirtualBox.xml" only needs to be deleted or renamed AND be replaced by the file
"VirtualBox.xml-tmp" (renamed in "VirtualBox.xml") before starting of VirtualBox. Now the virtual machine lets itself
start again without any problem!

Gruß / Greetings
goose

This post has been edited 1 times, last edit by "goose" (Jun 8th 2010, 12:25pm)

g-force

Gunnar

Posts: 11,356

Date of registration: Sep 23rd 2008

Thanks: 166 / 162

5

Tuesday, June 8th 2010, 12:29pm

Welcome @ Win-Lite.de, goose!

Vielen Dank für deinen Workaround und und die engl. Übersetzung! *THUMBS UP*

Thanks a lot for your workaround and your translation! *THUMBS UP*

"Von all den Dingen, die mir verloren gegangen sind, habe ich am meisten an meinem Verstand gehangen."

wolf1

User

Posts: 1

Date of registration: Nov 10th 2008

Thanks: 16 / 0

6

Wednesday, June 9th 2010, 2:18pm

Problem with new VM on Portable Virtualbox V.3.2.4 Laucher V5.0.0

Hy, I'm an happy user of your fantastic software.
I write you this ( sorry for my poor english ), because with the release of virtualbox of "Oracle" I have some problem to make new VM.
When i start the program, it load the old configuration with the machine for example : "xxx" = Xp + "yyy" = Linux.
But when i try to add e new VM at the end of procedure, the system tell me that can't write on "VirtualBox.xml" the data...???

If I stop the procedure, and exit from the program, with the solution that you explain ( delete VirtualBox.xml and rename VirtualBox.xml-temp ), I can start the program, and load the new machine...but this is a complicate solution for ALL the change that I'll can do on a machine.

Please you have to explain another solution or you think so solve in a future launcher V5..... this problem ??

Thank for your job, I wait your answer.
Bye Wolf1

16 guests thanked already.

Hans69

User

Posts: 4

Date of registration: Apr 11th 2010

7

Wednesday, June 9th 2010, 3:31pm

I have the same problem with this version 3.2.4 and 3.2.0
Please help me! :-(

This post has been edited 1 times, last edit by "Hans69" (Jun 9th 2010, 3:35pm)

Zilc_H

User

Posts: 3

Date of registration: Jun 12th 2010

Thanks: 0 / 1

8

Saturday, June 12th 2010, 10:40pm

Loader for Portable Virtualbox V.3.2.4 Laucher V5.0.0

________________
Hallo,
hab eben einen Loader für den Portable-Virtualbox-Laucher V5.0.0 in Autohotkey geschrieben der den von goose erklärten workarround automatisiert.
Die Datei ist angehängt und das ist der Quellcode:

Hi,
i just wrote a loader for the Portable-Virtualbox-Laucher V5.0.0 in Autohotkey which is automatically doing the workarround decribed by goose.
File is attatched and here is the Source:

Source code

; AutoHotkey Version: 1.x
; Language: English
; Platform: Win9x/NT
; Author: ZilcH
;
#SingleInstance Force
#NoTrayIcon
#NoEnv ; Recommended for performance and compatibility with future AutoHotkey releases.
SendMode Input ; Recommended for new scripts due to its superior speed and reliability.
SetWorkingDir %A_ScriptDir% ; Ensures a consistent starting directory.
RunWait, Portable-VirtualBox.exe
Gui +AlwaysOnTop -Caption +ToolWindow
Gui, Font, s12
Gui, Add, Text, vMyText cBlack, Fixing VirtualBox.xml ...
Gui, Show
FileDelete, data\.VirtualBox\VirtualBox.xml
FileCopy, data\.VirtualBox\VirtualBox.xml-tmp, data\.VirtualBox\VirtualBox.xml
Sleep, 2000
ExitApp

Have fun, viel Spass
ZilcH

Edit by [testesser]: Zwecks Übersichtlichkeit in Codebox

gesetzt

Zilc_H has attached the following file:

VirtualboxLoader.zip (205.82 kB - 116 times downloaded - latest: Yesterday, 7:14pm)

This post has been edited 1 times, last edit by "Zilc_H" (Jun 12th 2010, 11:31pm)

Hans69

User

Posts: 4

Date of registration: Apr 11th 2010

9

Sunday, June 13th 2010, 2:18pm

Hello
Zilc_H,
Thanks for your loader, it works very well with the file
virtualbox.xml,
but there is still a problem. You can not
create a new virtual machine. When you
attempt to try to create a new virtual machine, it shows this error:
Sorry for my bad english.
I use google translate

Zilc_H

User

Posts: 3

Date of registration: Jun 12th 2010

Thanks: 0 / 1

10

Sunday, June 13th 2010, 9:01pm

Hi Hans, the little loader i wrote is just doing what goose is describing in his post.
It is not a fix for the Launcher that comes with portable-virtualbox.
It is just a workarround for the "snapshot-problem".
I am not the author of portable-virtualbox.
The error you get when you create a new VM is a different problem which has to be fixed in the Launcher (by the author of portable-virtualbox - i guess).

Anyhow - this is what you can do to create a new VM:
-Create a new VM as usual until you get the error-message from your screenshot
-Shut down portable-virtualbox and fix VirtualBox.xml as decribed by goose if you didnt use my loader
-Start portable-virtualbox again and you will find your new VM on the left - but without a harddisk and a cd-drive.
-Create a new harddrive and a cd-drive for your new VM in the details-screen on the right (IDE Controller)
-done

not very nice - but it will let you work with this great tool until there is a fix.
...hope this helped
cheers
ZilcH

Hans69

User

Posts: 4

Date of registration: Apr 11th 2010

11

Sunday, June 13th 2010, 9:56pm

Hi Zilc_H,
Your way to create a new virtual machine is a good alternative.
However with your loader you solved the problem more annoying.
I wait for that the bug is resolved.
Thank a lot my friend! ;-)

cheers

This post has been edited 2 times, last edit by "Hans69" (Jun 13th 2010, 10:00pm)

DarkBlood

Posts: 19

Date of registration: May 31st 2010

Thanks: 45 / 1

12

Sunday, June 27th 2010, 9:04am

Portable-VirtualBox v3.2.6 and still the problem is not solved.

I think I'm will going crazy... WHY the fuck this script can´t replace this shit of file!!!???

comparing VirtualBox.xml and VirtualBox.xml-tmp.
(after opened Virtualbox, start a machine, then restore to a saved snapshot and closed VirtualBox).

VirtualBox.xml

	Source code
1	<HardDisk uuid="{a32111e2-931c-4083-951f-4287a7ae4d68}" location="Machines\Windows XP para testeos\Snapshots\{a32111e2-931c-4083-951f-4287a7ae4d68}.vdi" format="VDI"/>

VirtualBox.xml-tmp

Source code

<HardDisk uuid="{bb378db4-6490-48d2-92c7-3894e7494fae}" location="D:\Programas\VirtualBox\data\.VirtualBox\Machines\Windows XP para testeos\Snapshots\{bb378db4-6490-48d2-92c7-3894e7494fae}.vdi" format="VDI"/>

This post has been edited 5 times, last edit by "DarkBlood" (Jun 27th 2010, 9:21am)

2 guests thanked already.

g-force

Gunnar

Posts: 11,356

Date of registration: Sep 23rd 2008

Thanks: 166 / 162

13

Sunday, June 27th 2010, 7:23pm

Quoted from "DarkBlood"

I think I'm will going crazy... WHY the fuck this script can´t replace this shit of file!!!???

Best wishes to Argentina - Warning included due to forumrules (diction).

"Von all den Dingen, die mir verloren gegangen sind, habe ich am meisten an meinem Verstand gehangen."

Midseven

User

Posts: 10

Date of registration: Aug 6th 2009

14

Monday, June 28th 2010, 11:46pm

I second DarkBlood totally, how long it's going to take to have a fix on this? When Launcher v5.1.x will come out? By the way, it's not only a snapshot problem... This error appears on various situations (creating/deleting a Machine/HD/CD-DVD...).

Workarounds are interesting but people want this to be fixed on a new release, it's a writing access problem obviously...

This post has been edited 1 times, last edit by "Midseven" (Jun 28th 2010, 11:49pm)

DarkBlood

Posts: 19

Date of registration: May 31st 2010

Thanks: 45 / 1

15

Tuesday, July 6th 2010, 7:00pm

I found and corrected the problem!
michaelm_007 (the autor of Portable-VirtualBox) has been using an old version of AutoIT to compile the source code, you can check in the executable "Portable-VirtualBox.exe" compiled with AutoIT 3.3.2.0 and this is the problem to all of those write access errors, inaccesible disc, etc.! After I re-compile with the latest version of AutoIT 3.3.6.1 all starts to work fine!

Edit:
[PROBLEM SOLVED] Portable-VirtualBox v3.2.6 has been updated with a "Portable-VirtualBox.exe" re-compiled with the latest version of AutoIT, so go and download it!
http://www.vbox.me/

This post has been edited 9 times, last edit by "DarkBlood" (Jul 19th 2010, 10:41pm)

Zilc_H

User

Posts: 3

Date of registration: Jun 12th 2010

Thanks: 0 / 1

16

Monday, July 19th 2010, 4:38pm

Good one ..!
Thanks a lot !!!

g-force

Gunnar

Posts: 11,356

Date of registration: Sep 23rd 2008

Thanks: 166 / 162

17

Monday, July 19th 2010, 5:43pm

Quoted from "DarkBlood"

EDIT:
michaelm_007 has updated all the recent versions of Portable-VirtualBox, so go and download it!

So the problem is solved in the last version of PortableVirtualBox?

"Von all den Dingen, die mir verloren gegangen sind, habe ich am meisten an meinem Verstand gehangen."

DarkBlood

Posts: 19

Date of registration: May 31st 2010

Thanks: 45 / 1

18

Monday, July 19th 2010, 10:36pm

Quoted from "g-force"

So the problem is solved in the last version of PortableVirtualBox?

Yes, all the problems have been corrected with the latest version of Portable-VirtualBox.

I edited all my posts with this:
[PROBLEM SOLVED] Portable-VirtualBox v3.2.6 has been updated with a "Portable-VirtualBox.exe" re-compiled with the latest version of AutoIT, so go and download it!
http://www.vbox.me/

This post has been edited 2 times, last edit by "DarkBlood" (Jul 19th 2010, 10:39pm)

rawhunger

User

Posts: 10

Date of registration: Aug 23rd 2010

19

Monday, August 23rd 2010, 9:14pm

Are you sure this has been fixed? Because I still see the same issue in version 3.2.8 of this software. Am I doing something wrong then? Should I install the 3.2.6 version that DarkBlood indicated instead?

This post has been edited 1 times, last edit by "rawhunger" (Aug 23rd 2010, 9:49pm)

rawhunger

User

Posts: 10

Date of registration: Aug 23rd 2010

20

Monday, August 23rd 2010, 11:11pm

This is really starting to get frustrating...

I don't know if I'm doing something wrong or not, but I've tried all the suggestions on this forum regarding this issue and I still get the error:

Source code

Could not find a CD/DVD image with UUID {f1eac465-460b-4025-b8b5-166bd21058ab} in the media registry ('G:\Portable-VirtualBox\data\.VirtualBox\VirtualBox.xml').

Result Code: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)


Component: VirtualBox


Interface: IVirtualBox {3f36e024-7fed-4f20-a02c-9158a82b44e6}

Anyone else still getting this error?

This post has been edited 1 times, last edit by "rawhunger" (Aug 23rd 2010, 11:13pm)

DarkBlood

Posts: 19

Date of registration: May 31st 2010

Thanks: 45 / 1

21

Monday, August 23rd 2010, 11:56pm

Quoted from "rawhunger"

Are you sure this has been fixed? Because I still see the same issue in version 3.2.8 of this software. Am I doing something wrong then? Should I install the 3.2.6 version that DarkBlood indicated instead?

I'm using the official Portable-VirtualBox v3.2.8 and I had no more problems, I created new virtual machines, hard drives, edited virtual machines and never saw this error again.

I suggest to eliminate your current virtual machines and re-adding again, you will NOT lose the virtual hard drives, only the snapshots and the configuration of the virtual machine, so delete the folder "..\data\.VirtualBox\Machines" and the xmls in "..\data\.VirtualBox\"

rawhunger

User

Posts: 10

Date of registration: Aug 23rd 2010

22

Tuesday, August 24th 2010, 12:21am

Quoted from "DarkBlood"

I'm using the official Portable-VirtualBox v3.2.8 and I had no more problems, I created new virtual machines, hard drives, edited virtual machines and never saw this error again.

I suggest to eliminate your current virtual machines and re-adding again, you will NOT lose the virtual hard drives, only the snapshots and the configuration of the virtual machine, so delete the folder "..\data\.VirtualBox\Machines" and the xmls in "..\data\.VirtualBox\"

So I delete the "Machines" folder and the XML files from the ".VirtualBox" folder, eh? That means I'll have to reinstall the OS that I put on that VM, wouldn't it?

DarkBlood

Posts: 19

Date of registration: May 31st 2010

Thanks: 45 / 1

23

Tuesday, August 24th 2010, 12:27am

Yes do that, but when you are adding a new virtual machine and when it prompts for a new hard drive and size, use the option for "already existing hard drive", they are located in the folder "..\data\.VirtualBox\HardDisks"

This post has been edited 2 times, last edit by "DarkBlood" (Aug 24th 2010, 12:30am)