Ticket #10214 (closed defect: duplicate)

Opened 6 years ago

Last modified 6 years ago

HostMemoryLow and VERR_UNRESOLVED_ERROR or VERR_NO_MEMORY errors on previously working VMs

Reported by: eteq Owned by:
Priority: major Component: other
Version: VirtualBox 4.1.8 Keywords:
Cc: Guest type: Linux
Host type: Windows


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


VBox.log Download (67.4 KB) - added by eteq 6 years ago.
VM#1 (64bit Ubuntu)
VBox2.log Download (99.5 KB) - added by eteq 6 years ago.
VM#2 (older 64bit Ubuntu)

Change History

Changed 6 years ago by eteq

VM#1 (64bit Ubuntu)

Changed 6 years ago by eteq

VM#2 (older 64bit Ubuntu)

comment:1 Changed 6 years ago by eteq

Oh, forgot to say: Host is 64bit Win7, VMs were both different versions of 64bit ubuntu.

comment:2 Changed 6 years ago by idanciu

try the resolution here: it worked for me! Almost the same setup.

comment:3 Changed 6 years ago by frank

  • Status changed from new to closed
  • Resolution set to duplicate

Please continue the discussion at #10219.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use