Ticket #10759 (reopened defect)
Can't kill Virtualbox.exe process
| Reported by: | speedkills20 | Owned by: | |
|---|---|---|---|
| Priority: | major | Component: | other |
| Version: | VirtualBox 4.1.18 | Keywords: | |
| Cc: | Guest type: | Linux | |
| Host type: | Windows |
Description
Windows 7 64 bit Host. Ubuntu 11.10. OS will lock when running certain programs and the virtualbox.exe process will keep running at 25% cpu. Can't kill it in the command line or in task Manager. Only option is to reboot the host Windows 7.
Attachments
-
ScreenHunter_39 Jul. 13 13.30.jpg
(360.6 KB) -
added by speedkills20 5 years ago.
- Virtualbox UI that's up is completely frozen. Can't kill virtualbox.exe process.
-
ScreenHunter_40 Jul. 13 13.33.jpg
(313.2 KB) -
added by speedkills20 5 years ago.
-
VBox.log
(103.8 KB) -
added by ipatrol 23 months ago.
- Log for Ubuntu machine
-
VBox.log.1
(76.8 KB) -
added by ipatrol 23 months ago.
- Additional log for Ubuntu machine
-
VBoxHardening.log
(351.8 KB) -
added by ipatrol 23 months ago.
- Hardening log for Ubuntu
-
VBoxSVC.log
(4.2 KB) -
added by ipatrol 23 months ago.
- VBoxSVC log
-
VBoxSVC.log.1
(11.1 KB) -
added by ipatrol 23 months ago.
- Additional VBoxSVC log
Change History
Changed 5 years ago by speedkills20
-
attachment
ScreenHunter_39 Jul. 13 13.30.jpg
added
comment:1 Changed 5 years ago by Hachiman
Could you please attach the Log file of such session? and what kind of programs and where (host? or guest?) are you running?
comment:2 Changed 5 years ago by frank
- Status changed from new to closed
- Resolution set to worksforme
No response, closing.
comment:3 Changed 23 months ago by ipatrol
- Status changed from closed to reopened
- Resolution worksforme deleted
Since I seem to also have this problem, I've decided to reopen this bug with my own logs. The setup is the same: 64bit Win7 host, 64bit Ubuntu guest. I could kill everything except the process holding the VM itself. My other VM, a 64bit Debian guest, has never given me this problem. Also, when this happens, all networking ceases to function.
A little background research suggests this probably means a hung call to the NT kernel, a very old bug first noticed by Mark Russinovich back in 2005 (see https://blogs.technet.microsoft.com/markrussinovich/2005/08/17/unkillable-processes/). Combined with the coincident loss of networking, that might suggest the problem lies in VirtualBox's networking driver, though I don't know enough yet to be sure.
I will keep you posted on anything else I uncover. My logs are posted above, and they seem to have some sort of unhandled exception at the end that's probably worth looking into.
Have fun, folks! ;-)
Virtualbox UI that's up is completely frozen. Can't kill virtualbox.exe process.