Hi; I have noticed what appears to be a bug in VirtualBox.
VirtualBox 4.3.24 r98716 Mac Book Pro running Yosemite and Mac Book Air running Yosemite Guest OS are several different instances of Ubuntu 14.04 LTS (server). Situation A. 1. VirtualBox GUI is up; 2. No Guest OS; 3. Guest OS is imported via VBoxManage; 4. Guest OS appears in the GUI as expected; 5. Guest OS (optionally) is started (with or without UI); 6. Guest OS status changes as expected; 7. Guest OS is shutdown via VBoxManage (if it was powered up); 8. Guest OS changes as expected; 9. Guest OS is removed (using VBoxManage closemedium --delete and VBoxManage unregistervm); 10; Guest OS completely vanishes from GUI (as expected); Situation B; The difference between Situation A and Situation B is that one or more Guest OS vms exist prior to the Guest OS in question is imported, powered up, shutdown and deleted. Situation C: In Situation C, the Guest OS that will be deleted occurs first in order (in time) where there are one or more Guest OS vms that have been imported (or created freshly) afterwards. In this case, the Guest OS removal causes the GUI to display the disk of the Guest OS for the other remaining Guest OS vms and the VIrtualBox GUI will spin until terminated with force. It appears that after the VirtualBox GUI has been terminated with extreme prejudice :-) that rstarting the VirtualBox GUI, that the disk images of the remaining Guest OS's are correctly displayed. I have been able to reproduce this consistently. What I have not exhaustively determined is if the buggy behavior only happens if the Guest OS to be removed is the oldest one. I have seen instances where the Guest OS that will be removed is somewhere in the middle (not the first and not the last) that the bug does not appear, but I have not exhaustively tested this scenario. A similar problem is more persistent. If one runs VBoxManage unregistervm prior to VBoxManage closemedium (lesson learneed the hard way; don't do this!), then the disk disassociation can occur even after all Guest OS's have been removed and the directories and files under ~/VIrtualBox VMs have been removed. The only way to prevent the disk disassociation from occurring again was to cpompletely deinstall VirtualBox (using the provided tool) and reinstall VirtualBox. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:[email protected]?subject=unsubscribe
