VirtualBox

Ticket #7941 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

VM Portability/XML: Shared folder path is not absolute => Fixed in SVN

Reported by: Technologov Owned by:
Priority: major Component: other
Version: VirtualBox 4.0.0 Keywords:
Cc: Guest type: other
Host type: other

Description

I am pushing the new v4.0 architecture to the limits.

Hosts: WinXP --> RHEL5 x64, VBox v4.0.0

VM cannot be moved from Windows to Linux host due to shared folders.

VirtualBox ERROR:

Failed to open virtual machine located in /home/alexey/Windows XP Unattended3/Windows XP Unattended3.vbox.

Shared folder path 'E:\' is not absolute.

VM cannot be imported.

Workaround: Manually Remove Shared Folders from XML.

-Technologov, 29.12.2010.

Attachments

Windows XP Unattended3.vbox Download (30.2 KB) - added by Technologov 3 years ago.
VBox VM XML

Change History

Changed 3 years ago by Technologov

VBox VM XML

comment:1 Changed 3 years ago by Technologov

It would be nice if VirtualBox reduces the importance of this issue from Error to Warning.

-Technologov

comment:2 Changed 3 years ago by patrick.steiner

I can confirm this bug on a OS X Host

comment:3 Changed 3 years ago by bhamail

comment:4 Changed 3 years ago by frank

  • Summary changed from VM Portability/XML: Shared folder path is not absolute to VM Portability/XML: Shared folder path is not absolute => Fixed in SVN

This will be fixed in the next maintenance release.

comment:5 Changed 3 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

comment:6 Changed 3 years ago by Technologov

  • Status changed from closed to reopened
  • Resolution fixed deleted

Reopened. Still broken in 4.0.6.

comment:7 Changed 3 years ago by Technologov

IMO, on VM import (Machine->Add) it should warn user about existing incompatible shared folders, and offer the user to delete them. (from all snapshots)

-Technologov

comment:8 Changed 3 years ago by jackyyaplt

Just tried on V4.0.8, still outstanding, guess has to modify the xml manually...

comment:9 Changed 3 years ago by burnchar

I don't think this was fixed in a maintenance release. If it was, it's regressed. Still a problem in 4.1

comment:10 Changed 3 years ago by sentin3l

Confirmation - still a problem in 4.1.
IMHO: If detected, Import-Dialog should ask for valid path and/or deletion of shared folder.

comment:11 Changed 3 years ago by poetzsch

Fixed in SVN. The fix will be included in the next minor version.

comment:12 Changed 3 years ago by ailie

Same problem on VirtualBox 4.1.2

I need to import a VM with shared folders already set, but because I do not have that folders (I don't have D: on linux), the import fails:

WinXP host (with shared folders) --> WinXP guest --> Linux host

possible dup: Ticket #7001

comment:13 Changed 3 years ago by rivimey

Just experienced this problem on 4.1.2... not easy to workaround when all you have is an .ova file.

I looked at the trunk svn for vboxmanage and could find no evidence of change there of the sort I would expect -- which is "import" commands to ignore shared folder specs (as for e.g. a floppy) and dry-run check that the shared folder is ok.

I agree that, from the GUI, it would be nice to have a prompt for the updated folders.

My variant of the problem was exporting a Debian VM from Win7 and importing on an Ubuntu machine. I'd just updated the Ubuntu vb to 4.1.2 (why is "natty" still 4.0.4). My workaround was to use "sed" on the .ova file to edit the bad path to one in /tmp that had the same number of characters.

comment:14 Changed 3 years ago by frank

  • Status changed from reopened to closed
  • Resolution set to fixed

VBox 4.1.4 contains the fix.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use