Opened 8 years ago
#15883 new defect
Slashes are not converted to underscores when a VM is part of a group
| Reported by: | trondfsi | Owned by: | |
|---|---|---|---|
| Component: | GUI | Version: | VirtualBox 5.1.4 |
| Keywords: | SessionMachine | Cc: | |
| Guest type: | all | Host type: | Windows |
Description
Before placing my VMs into groups, I had no trouble naming my VMs as "FreeBSD/amd64 stable/10 ZFS". The XML file was magically saved as "FreeBSD_amd64 stable_10 ZFS.vbox" upon initial creation. I was happy, and VBox was happy. I could change the configuration of my VMs; the VMs would still have names like "FreeBSD/amd64 stable/10 ZFS", and the XML file would still be named "FreeBSD_amd64 stable_10 ZFS.vbox".
Enter the use of groups. Shock and horror ensues!
I can no longer give my VMs names such as "FreeBSD/amd64 stable/11 BIOS ZFS". Somehow the magic sanitation of file names is put aside.
Here's an example of a VM currently named "FreeBSD_amd64 stable_11 BIOS ZFS", and as appropriate, the XML file is named "FreeBSD_amd64 stable_11 BIOS ZFS.vbox". Everyone are happy, except me.
Now, I attempt to change the name of the VM from "FreeBSD_amd64 stable_11 BIOS ZFS" to "FreeBSD/amd64 stable/11 BIOS ZFS".
VBox makes noises such as "Failed to save the setting of the virtual machine FreeBSD/amd64 stable/11 BIOS ZFS to D:\Users\trond\Documents\VirtualBox VMs\FreeBSD\FreeBSD_amd64 stable_11 BIOS ZFS\FreeBSD_amd64 stable_11 BIOS ZFS.vbox".
Details: Could not rename the settings file 'D:\Users\trond\Documents\VirtualBox VMs\FreeBSD\FreeBSD\amd64 stable\11 BIOS ZFS\FreeBSD_amd64 stable_11 BIOS ZFS.vbox' to 'D:\Users\trond\Documents\VirtualBox VMs\FreeBSD\FreeBSD\amd64 stable\11 BIOS ZFS\FreeBSD/amd64 stable/11 BIOS ZFS.vbox' (VERR_PATH_NOT_FOUND).
Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
Had I refrained from creating groups, none of the above would have happened, and I would not be the one who created this bug report.
A workaround is to stop the VBox GUI, manually edit the XML file, give the VM whatever name I desire, and launch the GUI once more. In the long run, this is not acceptable.
