Ticket #6009 (closed defect: fixed)
Faulty teleportation configuration leaves half-open VBox
|Reported by:||bauer40||Owned by:|
I know that what I've done is not allowed, but it should be handled correctly...
If you configure teleportation on a port which is in use, and start up VBoxHeadless, the VM is being shut down but the state of the VM is only "stopping", not "powered off".
To reproduce, create two vms, and issue:
VBoxManage modifyvm testvm1 --teleporter on --teleporterport 6000
VBoxManage modifyvm testvm2 --teleporter on --teleporterport 6000 <- that's the problem
nohup VBoxHeadless -s testvm1 <- testvm waits for teleportation
VBoxheadless -s testvm2 <- This one is terminated
When you look on the VBox GUI, the state of testvm2 is "stopping", which is wrong. Furthermore, you can no longer start/stop testvm2.