Changes between Initial Version and Version 1 of Ticket #19508, comment 14
- Timestamp:
- Jun 16, 2020 7:46:12 PM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #19508, comment 14
initial v1 1 1 I am not sure whether or not the scenario described below is related to the original error or not. Maybe a separate ticket needs to be opened - maybe not. Perhaps someone can indicate that? 2 2 3 If the VBox Manager Window is closed while one or more VMs are running and then the VBox Manager is started again, the still running VMs are shown in the VBox Manager window as 'Powered Off'. Is this corrector not?3 If the VBox Manager Window is closed while one or more VMs are running and then the VBox Manager is started again, the still running VMs are shown in the VBox Manager window as 'Powered Off'. Is this a bug or not? 4 4 5 5 The problem is: The VBox Manager then allows a VM to be started again, although it it still running. This of course causes data corruption on the virtual disks. I think that it should not be allowed to start a VM that is already running. Is there some mechanism implemented that is supposed to suppress such an action? If yes, why does it not work in this case - and is this then maybe related to the original error?
