virtualbox.org

Perryg wrote:Back it up somewhere else.

ok!

you the gist of this action is to remove the "-prev" file and leave the other in place?

Ok Let me explain a bit more. It looks like either the *.vbox file is corrupt or the .VirtualBox.xml file is. What you are attempting to do is replace the *.vbox file with the *.vbox-prev which is a VBox backup file. Renaming the *.vbox-prev to *.vbox should actually overwrite the original *.vbox. As long as you backup the file/s first it will not make a difference.

If this does not make the guest work then I will need to see the contents of the .VirtualBox.xml file (as an attachment)

in the user/vbox folder I created a new folder.....moved the current *.vbox file into it....and then renamed the *.vbox-previous to just *.vbox

i am not sure what you meant by backing up the file/s.....


anyway I did this and nothing changed. the error (runtime) still exists as above.

there are only 3 files in that folder. the last file is huge. *.vdi

And the .VirtualBox.xml file?
Could you post that as an attachment? (note you may need to change the .xml to .txt not sure)

Perryg wrote:And the .VirtualBox.xml file?
Could you post that as an attachment? (note you may need to change the .xml to .txt not sure)

The only files I can see are the ones in the post @ 1607. would the file be hidden?

This is the error code:
Runtime error opening '/Users/vincedaddy/VirtualBox VMs/GAME BOX/GAME BOX.vbox' for reading: -102 (File not found.).

what else can we try? I don't see anything with .xml here .

It is a hidden file as indicated with the . in front of the file name. It should be in your user folder and .VirtualBox folder
/Users/vincedaddy/.VirtualBox/VirtualBox.xml There should also be one called VirtualBox.xml~ which is a backup file.
Look at the size of both and let me know if there are different and post the actual xml file.

Question: Do you of have you used snapshots with any of these guests?

Perryg wrote:It is a hidden file as indicated with the . in front of the file name. It should be in your user folder and .VirtualBox folder
/Users/vincedaddy/.VirtualBox/VirtualBox.xml There should also be one called VirtualBox.xml~ which is a backup file.
Look at the size of both and let me know if there are different and post the actual xml file.

Question: Do you of have you used snapshots with any of these guests?

Well I told you I am no expert....I was looking in the wrong place: Here is the snap shot....

I found your .xml file.
I will move and rename first in the right directory and report back...I was dinkin around with the files in the VirtualBox VMs folder......

here is the .xml file very small.

Ok the structure looks right and the location of the control file looks good. Although I have not seen the control file *.vbox.

I need answers to my previous quest. Do you use snapshots? http://www.virtualbox.org/manual/ch01.html#snapshots

If all else fails I would download the previous version you had from http://download.virtualbox.org/virtualbox/ and after removing the current version install the previous one.

I assume you have rebooted the host, right?

I just though of something else you can try if you have not gone the last resort.
Let me know and I will post the information.

Perryg wrote:Ok the structure looks right and the location of the control file looks good. Although I have not seen the control file *.vbox.

I need answers to my previous quest. Do you use snapshots? http://www.virtualbox.org/manual/ch01.html#snapshots

If all else fails I would download the previous version you had from http://download.virtualbox.org/virtualbox/ and after removing the current version install the previous one.

I assume you have rebooted the host, right?

Yes: rebooted
No to snapshots but whenever i get going again i will start using snapshot though I didn't know to use this.
So, if I do re-install the previous version, what files are needed to fire up the 3 virtual boxes?;though I will only try restoring 1.
i renamed the xml-previous and the *log-previous and tried to fire up the any of the 3. NO JOY
I refreshed -NO JOY
I have those vboxSVC.logs?

They all still say: runtime error opening *.* for reading -102 (file not found)

All because I updated or installed the new 4.1.18? (VirtualBox-4-1.1.18-78361-OSX.dmg )
All I did was install .

So this is something that never happens? A runtime error opening is a disaster. What could have occurred here? If I had all the installation disks with me I would just create a new box but all that stuff is at home in my office. VIRTUAL BOX is such a great product, I just cannot fathom how by just installing an upgrade can have such a disastrous result/ It usually boils down to user error so what could I have done to screw this up so bad?

viewtopic.php?f=6&t=49524

Perryg wrote:I just though of something else you can try if you have not gone the last resort.
Let me know and I will post the information.

https://www.virtualbox.org/ticket/10324

I found this and they reinstalled the previous version of VB.
THE TICKET SAYS that it will not mess with my VM but how will it know ?

I don't have any idea what happened to your install. But the issue you have is to get it going again. For what ever reason VirtualBox can not see your guests even though it says it is there.

In the VirtualBox main manager, right click on the guest and left click on remove. When asked if you want to delete say NO. This will remove the guest from VirtualBox but leave everything else in tack. Now close VirtualBox and wait about 30 seconds and start the Main manager again. (your guest should be gone from the tree)
Next click on Machine tab and the add icon. Drill to the folder of the guest and find the *.vbox file and click it to see if VirtualBox will add it back to the tree.

Then see if the guest starts normally. If this works do the same thing to the other guests but if not just stop and tell me what exactly happened and the exact error you see.

You really should do this to one guest only and you should backup the entire guest folder that you are going to do this to before you start.

Is that the error you are seeing? It is not what you posted!