Changes between Version 1 and Version 2 of Ticket #17908, comment 14
- Timestamp:
- Jul 8, 2019 1:29:47 PM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #17908, comment 14
v1 v2 3 3 I'm referring to the comment #7 by @klaus, who mentioned the current situation is only an intermediate step. Preventing data loss (I lost VM settings many times and have backups of all of them, for years) is always important, that has been done. I'll test as soon as I can, but my VBox is usually in use by BOINC. I'm currently using 5.x Testbuilds. 4 4 5 BOINC tasks are what introduced the original issue for me. These tasks are controlled by a wrapper, using VBoxManage to create, update, maintain and, finally, destroy ingVMs on the fly. They usually never shut down and only use Save states. Worst of all, they all leave their copy of the VBoxGuestAdditions ISO attached!5 BOINC tasks are what introduced the original issue for me. These tasks are controlled by a wrapper, using VBoxManage to create, update, maintain and, finally, destroy VMs on the fly. They usually never shut down and only use Save states. Worst of all, they all leave their copy of the VBoxGuestAdditions ISO attached! 6 6 7 7 The problem occurred at first start, after updating VBox. This changes the VBoxGuestAdditions version and often (or always?) assigned a new GUID for the new copy. But the BOINC task's GUIDs still were the old one, left untouched. Old and new GUIDs collided.
