VirtualBox

Ticket #10121 (closed defect: duplicate) — at Version 13

Opened 7 years ago

Last modified 4 years ago

Guru Meditation (HostMemoryLow) when low memory

Reported by: wacher Owned by:
Component: other Version: VirtualBox 4.1.8
Keywords: memory low, resume, guru mediation Cc:
Guest type: Windows Host type: Windows

Description (last modified by frank) (diff)

I've resumed a virtual machine, but memory low. Expected result is a Paused VM state, but the VirtualBox simple crashed with guru mediation. (First occurence was founded in unofficial test build 4.1.7, see comment #9 of ticket #7929

Change History

Changed 7 years ago by wacher

Guru mediation when memory low

comment:1 Changed 7 years ago by wacher

Sorry, I don't know why I wrote 'VERR_MAP_FAILED' in title. (I've checked #7929 previously, maybe this 'typo' came from there via copy+paste...) So, I would like to change title to GURU_MEDITATION

comment:2 Changed 7 years ago by frank

  • Summary changed from VERR_MAP_FAILED when memory low to Guru Meditation (HostMemoryLow) when low memory

Changed 7 years ago by sanchox

comment:3 Changed 7 years ago by sanchox

Same thing on Win 7 x64 as host when try to install CentOS as guest. VM just crashes when something whith memory.

Changed 7 years ago by gwaddell

Zipped VM Log

comment:4 Changed 7 years ago by gwaddell

I'm getting the same behaviour with VirtualBox 4.1.8r75467 running on a Windows 7 64 bit Host with 6 GB RAM, I've three guests set up on the machine, one with Windows 7 and the rest with Windows Server 2003.

If I try and run any (single) guest with over 1 GB RAM, I get the following error at "boot up"

Error ID: HostMemoryLow, Severity: Non-Fatal Error

The host machine then pauses and wont restart and I have to switch it off and take the RAM down to 1GB.

Also, if I'm running a 1GB RAM guest, and start another one to run concurrently, I get the same error on the second machine. Is there some sort of size limit set at 1GB RAM?

Host Details: windows 7 Professional 64 bit Service Pack 1, 6 GB Ram, Intel core i7-2620M CPU @ 2.7GHz Example Guest Details: windows 7 Professional 32bit Service Pack 1, 2048 MB Ram

Task Manager while Guest is running: CPU Usuage 1-3%, RAM 3.02GB used

I've attached a log file

comment:5 follow-up: ↓ 6 Changed 7 years ago by wacher

The problem still exists in 4.1.9r75927. (Yes, I know that this is not an official release... but it is very annoying)

comment:6 in reply to: ↑ 5 Changed 7 years ago by gwaddell

Replying to wacher:

The problem still exists in 4.1.9r75927. (Yes, I know that this is not an official release... but it is very annoying)

Hi, I have a solution, well it worked for me....

I had read other forum posts about ensuring hardware virtualisation was enabled and I checked on my machine and it was. BUT I went back into the BIOS and double checked and although it was enabled, it was only enabled for something called VT-A I changed this setting to one that said VT-A & VT-D supported and now not only can I run over a 1 GB Ram guest, I can run a 2GB ram guest and a 1GB ram guest concurrently too.

comment:7 Changed 7 years ago by Plazgoth

I am seeing similar issue as well.

I have 8GB physical memory with 6.5 GB free when I try to start the VM with base memory set to 3584MB it fails.

Both the Guest and Host OS are Win 7 64Bit.

This VM has been working for the past few months with base memory set to 4096MB. Not sure what changed but I just started seeing this error tonight. Reducing the base memory to 3072MB gets it to boot.

The VirtualBox version I am using is 4.1.8 r75467

And I have checked in BIOS and VT-x is enabled.

Changed 7 years ago by Plazgoth

Changed 7 years ago by markusk

comment:8 Changed 7 years ago by markusk

Same issue with my System.

Host OS is Win 7 Ent 64Bit. Guest OS are Linux Mint 12 and Ubuntu Linux 10.04. Both 64 Bit.

The VM worked without any problems for the last couple of months. The problem appeared 2 days ago.

I was using version 4.1.8 r75467 and tried 4.0.16 yesterday. Unfortunatly i ran into the same problem.

Changed 7 years ago by roygbiv

comment:9 Changed 7 years ago by roygbiv

Same problem. Host Os is Win 7 64 bit with the last updates (genuie). Guest OS is Windows 2008 R2 64bit. Worked well 3 months, until last week, when it crashed with 2048MB and above of RAM (only 1024 works), when it's 6GB total in system, and almost 5 are free. Log attached. 1GB is not acceptable at all for my purposes - can't start Oracle and other apps.

Thanks in advance for support and solution.

VirtualBox's version is 4.1.8 r75467

Last edited 7 years ago by roygbiv (previous) (diff)

comment:10 Changed 7 years ago by froling

O my.. I thought it was my computer hardware that has been broken. I have run all kind of memory checks and did not find anything wrong with my laptop. The reason that I suspected hardware errors is because of the fact that the screen start to flicker when the memory consumption begin to reach its limit of 8GB. I suspected that is could be Virtual Box release, the problems started when I updated the Oracle VM VirtualBox Extention Pack to version 4.1.8r75467 but I was not sure. It could be some windows update that could caused my flickering screen and virtual instances limitation of memory consumption. I'm still not sure of this, who am I going to blame, Microsoft or Oracle? No offense I like both of them. I deeply depending on them both. I uninstalled VirtualBox and downloaded an older version of VirtualBox, to my surprise it did not solve the problem, so it could be Microsoft that has released a Windows patch that has broken a feature in windows that VirtualBox depend upon. I could also be VirtualBox that don't revert all parts when I downgraded to it's previous version.

I sincerely hope that this is solved swiftly. I which I can contribute, but I lack the skill of programming OS or Viritualization software.

Host: Win7 64bit with 8GB mem, running several different guests (win 2008 r2, win 2008 32bit, win 2003, Ubunut 10.10, ...)

Last edited 7 years ago by froling (previous) (diff)

comment:11 follow-up: ↓ 12 Changed 7 years ago by cmkim

Same problem. Host: Win7 64bit with 6GB mem, running single guest. a lot of available memory. Guest: Ubuntu 10.10

Changed 7 years ago by cmkim

comment:12 in reply to: ↑ 11 Changed 7 years ago by c_lize

Same issue here: Host Windows 7 64bit guest: Centos 5, w2k3... Using the resource monitor on the host, I can see that Virtualbox is unable to get the memory from the standby memory... Hope this help.

comment:13 Changed 7 years ago by frank

  • Status changed from new to closed
  • Resolution set to duplicate
  • Description modified (diff)

Looks like a duplicate of #10219.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use