Opened 7 years ago
#16359 new defect
VBOX XML files are not locked by VBOX Manager instances
| Reported by: | Z6543 | Owned by: | |
|---|---|---|---|
| Component: | VM control | Version: | VirtualBox 5.1.4 |
| Keywords: | Cc: | ||
| Guest type: | all | Host type: | Windows |
Description
We have lost snapshots recently because the .vbox XML files are not locked by the Virtualbox Manager.
Steps to reproduce:
- Create a new VM in User1 Windows account.
- Don't quit from the Virtualbox Manager GUI.
- Switch to Windows user account User2.
- Open the same VM in the Virtualbox Manager.
- Create a new snapshot (Snapshot 1).
- Close the Virtualbox Manager in User2 account, logoff from User2.
- Switch back to User1. Snapshot 1 is not listed.
- Close the Virtualbox Manager.
- Start the Virtualbox Manager. Snapshot 1 is not listed.
Expected result: When the User2 opens the VM in the Virtualbox Manager, it should raise an error that this VM is locked by another user.
These errors never happen intentionally, so it would be great if the Virtualbox Manager could lock the vbox files.
Sometimes we can recover the snapshots by manually recreating the snapshot entries in the vbox XML file, but this is not optimal.
Thank you for your help
Note:
See TracTickets
for help on using tickets.
