Opened 9 years ago
Closed 8 years ago
#14892 closed defect (fixed)
ERROR_MAX_THRDS_REACHED / unable to shutdown
Reported by: | A_User_Called_M | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 5.0.10 |
Keywords: | Cc: | ||
Guest type: | BSD | Host type: | Windows |
Description
the ERROR_MAX_THRDS_REACHED was displayed when attempting to open the main vbox app (where I can see and control all VM that I have.
I then also got an error:
Failed to stop the virtual machine Freebsd10A. Invalid machine state Paused when checking if the guest entered the ACPI mode). Callee RC: E_FAIL (0x80004005)
When I tried to "close" the machine (after shutting down the OS inside)
More details:
Host Windows Vista Guest Freebsd / several network interfaces
The guest has been running for a long time (over a week, maybe 2 or 3). The host was up all the time too, neither host nor guest where suspended at any time.
I first noted that the guest could no longer connect to the public internet. Yet the guest still had network to the host (I was connected via ssh, and the ssh session was as old as the guests uptime)
I then attempted to start the vbox control center (see above) and got the ERROR_MAX_THRDS_REACHED. Clicking ok, got me to start the control center.
Then I shutdown (via ssh) the freebsd inside the VM, after that I went to the VM window (in which I can see the fbsd console), and attempted to close / power off the machine. I get the above error. I was not able to resume it.
Attempting several times I eventually got "the instruction 0x598878e0 referenced memory at 0x00000010 the memory could not be read"
Attachments (4)
Change History (6)
by , 9 years ago
Attachment: | Freebsd10A-2015-12-03-19-16-05__.log added |
---|
by , 9 years ago
Attachment: | Freebsd10A-2015-12-03-18-53-57.log added |
---|
log created slightly earlier, while still running, attempting to close
by , 9 years ago
Attachment: | Freebsd10A-2015-12-03-19-17-48_hardwar.zip added |
---|
log from tab "hardware log"
comment:1 by , 8 years ago
I believe the error no longer exists.
Please close the ticket.
I am not sure at which version it went away (I am now at 5.1.14). But the error has not happen in over 4 month (or even longer). And it used to happen every 2 or 3 weeks. So for me, the problem no longer exists.
log created after final crash