Opened 12 years ago
Last modified 12 years ago
#10467 closed defect
VBoxManage clonehd placing output file somewhere other than the explicitly specified full path. — at Initial Version
| Reported by: | dakra | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.1.8 |
| Keywords: | VBoxManage clonehd explicit path | Cc: | dakra137@… |
| Guest type: | Windows | Host type: | Linux |
Description
Scenario: VBoxManage clonehd specifying full paths for input and output files enclosed in double quotes on the bash command line. There are spaces in the input file name.
Result: The output file was placed in an odd place on a different device than specified.
This is not the same as:
https://www.virtualbox.org/ticket/3888
https://www.virtualbox.org/ticket/7402
nor as discussed in:
http://muffinresearch.co.uk/archives/2009/07/23/virtualbox-error-cannot-register-the-hard-disk/[[BR]]
Environment: VirtualBox 4.1.8 r75467 running on Ubuntu 10.04 PAE on i7. Real disks are NTFS, as is the VDISK.
Specifics:
Command:
dakra@EVENTEE:/media/Windoze7$ VBoxManage clonehd "/media/Windoze7/Users/dakra/.VirtualBox/Machines/XP 8 Jan 2012 /XP 8 Jan 2012 -disk1.vdi" "/media/SSD88/XPSYSPREPPED.img" --format RAW
Actual Output file:
"/media/Windoze7/ /media/SSD88/XPSYSPREPPED.img"
I cannot prove, but I believe that VBoxManage created the directory hierarchy " /media/SSD88/" on the Windoze7 partition. It appears that the first level is a one character Unicode directory name x'C2A0', which I believe is a non-breaking space.
Once I found where the result went and had cleared enough disk space for it. I could let it go there and then do what I needed with it.
It may be that some of the erroneous "insufficient disk space" messages in other bug reports and the fora may be due to this misplacement of output onto devices with insufficient space, rather than the specified target destination.
