appliance import error

Discussions about using Windows guests in VirtualBox.
Post Reply
OCR14a
Posts: 10
Joined: 14. Oct 2009, 16:45
Primary OS: Ubuntu 8.04
VBox Version: OSE Debian
Guest OSses: none yet

appliance import error

Post by OCR14a »

Host: Windows 7 Enterprise 64 bit
Guest: Windows 7 Enterprise 32 bit

I built the VM within VB on my Mac.
Then imported it into VB on another Mac, and had no problem (well....not this problem anyway).

Now, I'm trying to import it into VB on another Windows machine, and I got this error...

VirtualBox - Error
Failed to import appliance %path.ova%

Shared folder path
%path% is not absolute.

[I tried to copy the other info at the bottom of the error box, but doing so hung the whole program, and I had to kill it]


I understand part of what's going on.....in the original VM, at one time, I connected an SD card to my Mac, and connected it to the VM as a shared folder.
However, when I imported this same VM into VB on my Mac, it did not choke like this.....once imported, I simply disconnected it and another shared folder, and went on my way.

Any idea why it would do this?
Any way around it, or do I have to re-export the image and make sure to not have any shared folders connected?

Thanks.
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: appliance import error

Post by Perryg »

Any way around it, or do I have to re-export the image and make sure to not have any shared folders connected?
I believe you have answered your own question. AFAIK this is the only way to get it to work (at this time). I believe the DEVs are working on this so things may change soon.
OCR14a
Posts: 10
Joined: 14. Oct 2009, 16:45
Primary OS: Ubuntu 8.04
VBox Version: OSE Debian
Guest OSses: none yet

Re: appliance import error

Post by OCR14a »

OK, cool.
I don't have a problem with that....I totally understand that free magical software can't do everything perfectly :)

It's just odd that it doesn't give me trouble on the same issue when I import this same, exact VM into VB running on a Mac.
Oh well, I will just make the appropriate adjustments and re-export.

Thanks.
Post Reply