Problem to import an already set vm

[leopoldo]

I downloaded a virtual image from windows xp from M$ developer site. There I chosed the virtual machine option "IE6 on XP" and the plataform option "virtualBox"

Downloaded it, unpacked an ova file into an ovf and a vmdk. Ignored the ovf file because it would create the virtual hd on a partition that I don't have enough space for the virtual hd. So I created a new virtual machine and selected the vmdk file as an existing hd. After finished the vm I send it to start. But then nothing happens. All I see is a black screen. No output is showed on a terminal. I thought it might be because I didn't loaded the ovf file that had specific settings.
Then I opened the ovf file again and saw that I could change the place of the virtual hd. I did it and then send VirtualBox to start the imported VM. thein received this:

Failed to import appliance /media/a/IE6 - WinXP.ovf.
<vbox:Machine> element in OVF contains a medium attachment for the disk image 0940d99c-c380-48c8-9527-b0c9c4fa20d7 but the OVF describes no such image."

details:

Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Appliance
Interface:
IAppliance {7b148032-4124-4f46-b56a-b48ac1273f5a}

Anyone can confirm if this it is related to the change I did in the place of the virtual hd?
What should I do now? Thanks for the help.

[mpack]

Delete what you created so far.

Use File|Preferences|General|Default Machine Folder to change where the VM will be created.

Use File|Import Appliance to import the OVA. Don't mess with it.

[leopoldo]

Thanks, unfortunately the same problem persists. The same happen with the other virtual machine that I was downloading yesterday.

[mpack]

Do you have a public download link for the OVA?

Failing that, a link to the website which describes the contents?

[leopoldo]

Yes, I wanted to post in the first message but the forum didn't let post at the time. Here it is https://dev.windows.com/en-us/microsoft ... vms/linux/. Just chose the IE6 and then the virtual box options.

[BillG]

Why did you decide to unpack the .ovf file? I agree with mpack. Don't mess with it. Change where you want to store virtual machines and simply import the appliance.

I am not just guessing it will work. I just did it. Works like a charm.

VB XPIE6.PNG

[leopoldo]

Why did you decide to unpack the .ovf file? I agree with mpack. Don't mess with it. Change where you want to store virtual machines and simply import the appliance.

I am not just guessing it will work. I just did it. Works like a charm.

VB XPIE6.PNG

Not sure why you did post that. I didn't unpack an .ovf. I unpacked an .ova. Anyway, doesn't matter if I unpack or not the ova. I already told in my second message that I already did what was recommended.
It's always the same error, no matter what.
The fact it does work for you, doesn't mean it will work for me.
I putted the error message in the first post and the answer is probably lying there.

[socratis]

OK, let's take a look at the facts:
- Fact: You messed up with the .ova. Not sure of your level of expertise.
- Fact: You created a new VM around an existing VMDK. Settings: UNKNOWN.
- Fact: You changed the location of the VMDK. You didn't mention where.
- Fact: Others managed to get it working. As is.

Given the above, I'm inclined to suggest what the two other trusted users have suggested. Do it again from the beginning. If you decide to mess with it, make sure you know what you're doing. If you don't know what you're doing, be as descriptive as possible as to what steps you took to modify the setup. Also, take a look at Moving a VM for the proper way to relocate your VM, if you don't have enough space. Finally, take a look at the VirtualBox settings for the "Default Machine Folder". If you change that and then you import your VM, it will be there.

[BillG]

The whole point of an appliance is that you do not need to know anything about it. Everything is already there. It is designed that way. You just decompress it if it is compressed, then import it. As long as the download was clean you are in business.

If you want to fiddle with it, do it after that step.