Opened 4 years ago
Last modified 4 years ago
#19816 new defect
VirtualBox not able to power-off any (currently-running) machines
| Reported by: | soutsos | Owned by: | |
|---|---|---|---|
| Component: | VM control | Version: | VirtualBox 5.2.42 |
| Keywords: | poweroff | Cc: | |
| Guest type: | Windows | Host type: | Linux |
Description
I am using cuckoo sandbox (version 2.0.7) to perform batch dynamic analysis on windows malware. My host system is Ubuntu 18.04 and I am running 10 Windows 7 VMs on parallel (headless).
The Cuckoo Sandbox application will stop a VM when it is done analysing a binary and will restore the specified snapshot. It will then power up the machine to start a new analysis.
After prolonged usage (around 4+ hours), one or more of the running VMs will become unresponsive and will not poweroff. The only solution I have is to restart the computer, as the virtualbox services will fail to reload. (If I quit the cuckoo sandbox when one of the machines deadlocks, then all of the running machines will become unresponsive and keep running endlessly).
I am attaching the log of the VM that caused the issue most recently
Attachments (5)
Change History (8)
by , 4 years ago
| Attachment: | cuckoo10-2020-08-16-20-20-40.log added |
|---|
comment:1 by , 4 years ago
attachment cuckoo10-2020-08-16-20-20-40.3.log (VBox.log.2) is a duplicate of VBox.log.1, but I couldn't find an option to remove it from the submission.
comment:2 by , 4 years ago
It is not after prolonged usage. Total time running turns out to be irrelevant to the issue
comment:3 by , 4 years ago
I'm not a dev, but out of curiosity, how does the Cuckoo Sandbox application handles the VM shutdown?
VBox.log