Context Navigation

Changes between Initial Version and Version 1 of Ticket #12241, comment 4

initial	v1
1		I have found that this problem (at least in my case) is caused by the host-only interface ("vboxnet0" on my machine). If I don't have a host-only interface active on a given VM, it will stop cleanly. If one ''is'' active, the "stuck" behavior will be exhibited, ~~unable to be Force Quit and preventing shutdown or reboot from the GUI. The machine can be rebooted or shut down from the command line via "sudo reboot" or "sudo shutdown -h now"~~.
	1	I have found that this problem (at least in my case) is caused by the host-only interface ("vboxnet0" on my machine). If I don't have a host-only interface active on a given VM, it will stop cleanly. If one ''is'' active, the "stuck" behavior will be exhibited, the VM will be unable to be Force Quit and will prevent shutdown or reboot from the GUI. The machine can, however, be rebooted or shut down from the command line via "sudo reboot" or "sudo shutdown -h now", although there is a significant delay before the actual reboot/shutdown occurs (up to a minute).
2	2
3	3	I have also found that removing the host-only interface via "VBoxManage hostonlyif remove vboxnet0" will clear the condition and allow the stuck VM to finish its shutdown and disappear from the Dock.