Windows 10: Virtualbox not closing on shutdown


Advanced search

Message boards : Number crunching : Windows 10: Virtualbox not closing on shutdown

Author Message
Profile Scalextrix[Gridcoin]
Send message
Joined: 17 Dec 14
Posts: 11
Credit: 1,209,253
RAC: 0
    
Message 5886 - Posted: 27 Dec 2016, 18:46:23 UTC

Its more of an annoyance, but since updating to the later VirtualBox versions on Win 10 I get a notification on shutdown that there are still active connections. Windows does not seem able to close them and returns to desktop after a couple of minutes.

Anyone found a solution for that?

Profile Jim1348
Send message
Joined: 15 Nov 14
Posts: 111
Credit: 1,319,885
RAC: 0
    
Message 5887 - Posted: 28 Dec 2016, 1:37:42 UTC - in response to Message 5886.

Good question. I have found the same thing on Win7 64-bit while running any VirtualBox project (Cosmology, ATLAS, etc.). I get the message "VirtualBox Interface has active connections", and I can not shut down the PC without risk of corrupting the disk drive. I have to first stop "VBoxSVC.exe" in Task Manager before I can reboot without problems, so I just don't run VirtualBox projects on this PC anymore.

It may have to do with hardware incompatibility or software, but I have tried shutting down programs before rebooting and have not found a fix.

Jesse Viviano
Send message
Joined: 20 Dec 15
Posts: 16
Credit: 328,453
RAC: 0
    
Message 5888 - Posted: 28 Dec 2016, 3:10:17 UTC - in response to Message 5886.

This is because ATLAS@home requires a constant connection to the Internet while it computes, and it constantly generates traffic to the ATLAS@home servers. You should set "No new tasks" on ATLAS@home, LHC@home, and vLHC@home while you are at it; and suspend any not-yet-started tasks on these three projects when you plan on rebooting to let the work units drain out before the reboot and allow these connections to gracefully close.

Profile Jim1348
Send message
Joined: 15 Nov 14
Posts: 111
Credit: 1,319,885
RAC: 0
    
Message 5889 - Posted: 28 Dec 2016, 11:54:21 UTC - in response to Message 5888.
Last modified: 28 Dec 2016, 12:53:06 UTC

OK, that may be it. But I don't recall that in earlier versions of VirtualBox (before 5.1, or maybe it was 4.xx). Also, I can reboot my Linux (Ubuntu 16.10) machine without any delay or hangs when running ATLAS and CMS or Theory using VirtualBox 5.1.6. So I think something changed in the Windows version at some point, but maybe it is beyond our control. Thanks for the input.

Crystal Pellet
Send message
Joined: 25 Jun 14
Posts: 39
Credit: 59,718
RAC: 0
    
Message 5891 - Posted: 29 Dec 2016, 11:10:48 UTC - in response to Message 5886.

Its more of an annoyance, but since updating to the later VirtualBox versions on Win 10 I get a notification on shutdown that there are still active connections. Windows does not seem able to close them and returns to desktop after a couple of minutes.

Anyone found a solution for that?

After the last virtualbox.exe and vboxheadless.exe's are terminated, VBoxSVC.exe still remains active for several minutes.
Terminating the first two mentioned processes is done by suspending the VM-tasks in BOINC Manager with 'Leave applications in memory' set to off and/or stopping the BOINC-client.

When the mentioned processes are gone it's save to reboot and ignoring the 'active connections' message or kill VBoxSVC.exe with Task Manager as Jim wrote.

Message boards : Number crunching : Windows 10: Virtualbox not closing on shutdown