Opened 7 years ago
Closed 5 years ago
#17653 closed defect (obsolete)
VERR_NO_LOW_MEMORY
| Reported by: | Stephen Rondeau | Owned by: | |
|---|---|---|---|
| Component: | VMM | Version: | VirtualBox 5.2.8 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | other |
Description
# VBoxManage startvm win10a --type headless Waiting for VM "win10a" to power on... VBoxManage: error: VM creation failed (GVMM) (VERR_NO_LOW_MEMORY) VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole
This message has been appearing for the first time, perhaps since an upgrade to 5.2.8.
There are 16 running VMs on other login accounts. Total virtual RAM allocated to VMs is no more than 64GB of 256GB physical RAM.
Attachments (1)
Change History (5)
by , 7 years ago
comment:1 by , 7 years ago
Since opening this ticket, I:
- killed VMs that had problem (seen in their VBox.log file, as attached)
- saved the state of remaining running VMs
- noted that VMs were running as processes that "VBoxManage list runningvms" for the owning user did not show
- updated the host OS (was Linux 4.15.10-200.fc26.x86_64, now 4.15.12-201.fc26.x86_64)
- restarted host OS
- started the previously-running VMs
- did not detect any further VERR_NO_LOW_MEMORY issues in the new VBox.log files
follow-up: 3 comment:2 by , 7 years ago
So, this ticket can now be closed? Probably as "WorksForMe"?
comment:3 by , 7 years ago
No. It re-appeared later. Could you please tell me what this means so I can check various places and configuration files? Is lack of adequate swap space an issue, even though there is plenty of RAM in the system?
comment:4 by , 5 years ago
| Resolution: | → obsolete |
|---|---|
| Status: | new → closed |
Please reopen if still an issue with a recent VirtualBox release.
VBox.log