Opened 13 years ago
Closed 13 years ago
#10214 closed defect (duplicate)
HostMemoryLow and VERR_UNRESOLVED_ERROR or VERR_NO_MEMORY errors on previously working VMs
| Reported by: | eteq | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.1.8 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Windows |
Description
This may be related to #10121 or #10205, but it seems to be slightly different symptoms (particularly, there is no GURU_MEDIATION), so I'm reporting it separately.
Basically, on two separate VMs (on the same host), I suddenly started getting various memory-related errors from VirtualBox that kill the VMs. In one case, it triggered a BSOD on the host. I'm attaching two vbox.log files attached for each of the VMs.
The Host is Windows 7 with 8GB physical RAM - both VMs were set to 2048MB of memory, and there was quite a bit more than that much free on the host when I ran them.
There have been 4 windows updates that might be the culprit (e.g. it was working before then and not after): KB2585542 (this was the most recent, and I saw on a forum post that someone else thought this was the only possible culprit), KB2631813, KB2644615, and KB2584146
Attachments (2)
Change History (5)
by , 13 years ago
comment:1 by , 13 years ago
Oh, forgot to say: Host is 64bit Win7, VMs were both different versions of 64bit ubuntu.
comment:2 by , 13 years ago
try the resolution here: https://www.virtualbox.org/ticket/10219 it worked for me! Almost the same setup.
comment:3 by , 13 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Please continue the discussion at #10219.
VM#1 (64bit Ubuntu)