Ticket #14318 (closed defect: obsolete)

Opened 5 years ago

Last modified 4 hours ago

Ubuntu 14.04 Host and Guest Error involving 'rc=VERR_NO_MEM' (235GB guest RAM)

Reported by: boring Owned by:
Component: other Version: VirtualBox 5.0.0
Keywords: Cc:
Guest type: Linux Host type: Linux



As the title suggests, I'm running ubuntu 14.04 as both the host and guest. My guest keeps being aborted with the following in the log: 01:11:53.814786 VGA Sequencer (3C5): SR index 3C4:04 01:11:53.814788 SR00:03 SR01:00 SR02:0F SR03:00 SR04:0A 01:11:53.814798 !! 01:11:53.814798 !! {vgatext} 01:11:53.814799 !! 01:11:53.814801 Not in text mode! 01:11:53.814802 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 01:11:53.814840 emR3Debug: rc=VERR_NO_MEMORY 01:11:54.815637 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION' 01:11:54.815673 Console: Machine state changed to 'GuruMeditation' 01:15:54.310203 Console: Machine state changed to 'Stopping'

When running rsync to download data from a remote server to the VM, it has consistently aborted, however, leaving the VM open and doing nothing, it has been up for 48 hr plus now.

I have 235 GB of memory devoted to the Linux guest, leaving 16+ GB for the host. The reason why is the following:

I deal with bioinformatics programs that can use all the resources they can get. I also deal with very large databases. Configuration for a specific workflow pipeline is a problem, since configurations between workflow pipelines can conflict with each other, and in some cases, threaten the OS integrity. I was interested in creating an image with all the databases needed and with a clean OS, then converting it to a multiattach-moded image and using that image as a base for each VM dedicated to each pipeline.

I opened a forum thread about this, and it was suggested I post this here. Here's a link to the forum thread:

Thank you!



VBox.log.txt.gz Download (52.9 KB) - added by boring 5 years ago.
log file

Change History

Changed 5 years ago by boring

log file

comment:1 Changed 5 years ago by frank

  • Summary changed from Ubuntu 14.04 Host and Guest Error involving 'rc=VERR_NO_MEM' to Ubuntu 14.04 Host and Guest Error involving 'rc=VERR_NO_MEM' (235GB guest RAM)

VBox does currently not support such configurations. I guess a sane maximum for the amount of guest RAM would be less than 128G.

comment:2 Changed 4 years ago by sillyjims

Same problem Host win10 Guest: Mac OS X

comment:3 Changed 4 years ago by frank

sillyjims, your problem is NOT the same. Sorry, we don't support configurations like yours for legal reasons. Mac OS X guests are only allowed to run on Apple hardware.

comment:4 Changed 4 years ago by HugeMemory

The situation is confirmed with the following configuration:

Host: Oracle Linux 7, with 256 GB RAM Guest: Oracle Linux 6, 220 GB RAM

After making some memory fill-up tests, it seems that guest defined with more that 128 GB will halt execution, becoming unresponsive and "guru meditation" state.

53:38:25.385396 -------------------------------------------------------------------------------- 53:38:25.385447 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 53:38:25.385486 emR3Debug: rc=VERR_NO_MEMORY 53:38:26.245962 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago

In "online" documentation there is no reference to the memory limit.

comment:5 Changed 4 hours ago by aeichner

  • Status changed from new to closed
  • Resolution set to obsolete
Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use