Opened 16 years ago
Closed 15 years ago
#1810 closed defect (fixed)
Using VBoxManage drive specification
| Reported by: | Jorge Cribb | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 1.6.2 |
| Keywords: | drive VBoxManage VERR_PATH_NOT_FOUND | Cc: | |
| Guest type: | other | Host type: | other |
Description
Problem: Using VBoxManage in drive D:, with clonevdi option, I get the error VERR_PATH_NOT_FOUND.
Procedure:
- The command executed on dir D:\.VirtualBox was:
D:\Software\VirtualBox\VBoxManage.exe clonevdi ReactOS.vdi new.vdi
- The file ReacOS.vdi is located in D:\.VirtualBox
Workaround:
D:\Software\VirtualBox\VBoxManage.exe clonevdi D:ReactOS.vdi new.vdi
I must use the drive D: specification on the ReacOS.vdi path to force to consider the drive D: because the VBoxManage tool search the file on drive C:.
Note:
See TracTickets
for help on using tickets.
Please reopen if this problem persists with the latest release.