virtualbox.org

After reinstalling win 7 host on my pc, I would already have backed up all what the .Virtualbox folder has so that I may not have to re-config everything from the beginning. I have 2 guests -> Debian running fine but Win Xp is now (inaccessible, normal). Am still using the same version I was running but had been updating by over-writting older ver and still worked fine back then until now

When I try to run it I get:

DV: error VERR_PATH_NOT_FOUND openning image file C:\blah\blah (VERR_PATH_NOT_FOUND)

details:

When I try to register it through the Virtual media manager I get this error: It also has a yellow exclamation mark in the media manager. I really want to save this Xp as it has my project work and havent backed it up anywhere else

First my global translator has died and blah blah blah does not translate anymore.
Next do/did you have snapshots.
Finally tells us exactly how you saved and moved the original files?
Remember details!

Perryg wrote:....global translator....

hahaha that would be c:\HardDisks\WinXp.vdi

Since the whole process worked once without a snapshot unfortunately from then on, I never bothered to snapshot it at all. Been like 4 times now without a snapshot.
Save process was a copy past the whole .Virtualbox folder to a backup folder, then after the new os is in. I would install virtualbox, make sure its runnning then close all its processes then over-write the backup .Virtualbox onto the one created by virtualbox the app, then everything would work like nothing ever happened.

I have just tried editting the path on a hunch, but now I get:

VD: error VERR_VD_VDI_INVALID_HEADER opening image file C:\Users\k74zrx\.VirtualBox\HardDisks\WinXp.vdi (VERR_VD_VDI_INVALID_HEADER)

C:\Users\k74zrx\.VirtualBox\HardDisks\WinXp.vdi (VERR_VD_VDI_INVALID_HEADER)

I am guessing that the location is different on this install then the last one, correct?
You need to check the VirtualBox.xml as well as the machine xml files to make sure that the paths are the same and that they are absolute and exact.
One other thing that I found out the hard way. You should use the same version of Virtualbox when you do this. Not the new on on the new install. You can upgrade it after you get it working, but somewhere in the xml files it gets confused anymore. ALFM

Perryg wrote: I am guessing that the location is different on this install then the last one, correct?
You need to check the VirtualBox.xml as well as the machine xml files to make sure that the paths are the same and that they are absolute and exact.
One other thing that I found out the hard way. You should use the same version of Virtualbox when you do this. Not the new on on the new install. You can upgrade it after you get it working, but somewhere in the xml files it gets confused anymore. ALFM

The installation procedure for the Host and virtual box are exactly the same in all cases making the paths all the same, why it fail this time round, I dont know. I kind of saw that coming, I looked at the WinXp log folder and it shows 2 upgrade log changes then I just out of another hunch downloaded ver 3.1.6 before u mentioned it, which is what i started with, the reason I upgraded is because it would cause the pc to freeze whenever a usb thumbdrive was inserted. I havent looked at the machine xml files though

Still cant get it to work even after ver 3.1.6. Same error

Well since you have the vdi files and do not have snapshots, the easiest thing would be to delete the VM in the Main VBox GUI and then create it again.
You may need to remove it from the media manager but when asked if you want to delete it say no.
Then create the VM and when asked to create a new one, select an existing drive. Click the folder icon and add it back to the media manager and well there you have it.
If you selected the defaults for the original then it will be the same. If not you may need to tweak the settings to get it to work.

Now I get a (VERR_NOT_SUPPORTED) error when trying to use it as an already existing vdi.

Details: Just to see whether it really works I also deleted the debian and followed as you have instructed. The debian works but not Xp where all my important stuff is.

Look at the storage settings and see if the Windows guest is on the IDE or SATA chain. Make sure it is on the chain that it was on. By default it should be on the IDE unless you installed the SATA drivers in it.
Also try changing the controller to PIIX3 or PIIX4 All of mine say PIIX4 but I have heard of some that were setup in PIIX3.

I still get the same error over and over again "(VERR_NOT_SUPPORTED)" even with the version that run it last 3.1.8

What about the VT-x/AMD-v switch? Have you tried with it off?

Since I don't know anything about your setup you will need to try tweaking the settings.

You could also try opening the VDI using CloneVDI. If CloneVDI won't open it either then the VDI file is corrupted, and can only be restored from a backup.

Perryg wrote:What about the VT-x/AMD-v switch? Have you tried with it off?

Since I don't know anything about your setup you will need to try tweaking the settings.

I remember seeing that somewhere and you would need to check it's box to turn it on right? If thats the case it always has been off. Am not very sure what settings to try tweaking

mpack wrote:You could also try opening the VDI using CloneVDI. If CloneVDI won't open it either then the VDI file is corrupted, and can only be restored from a backup.

Where should I get it? I cant seem to see it hosted anywhere like cnet or filehippo

Takayuki wrote:Where should I get it?

I gave you a link (in fact you included the link in your quote of my msg). The zipped executable is there as an attachment to the linked message.