VirtualBox

Ticket #10745 (reopened defect)

Opened 3 years ago

Last modified 10 months ago

Guru Meditation 1103 (VINF_EM_DBG_HYPER_ASSERTION), error -1701 (VERR_MM_HYPER_NO_MEMORY)

Reported by: John Watson Owned by:
Priority: major Component: other
Version: VirtualBox 4.1.18 Keywords: Guru Meditation 1103
Cc: Guest type: Linux
Host type: Linux

Description

Using VB 4.1.18. Host is OEL5.6 x86_64, guests are OEL5.7 x86. Not using 64bit guests because CPUs are the older AMD Opteron 248 that don't have hardware virtualization. I have told VB not to use HW virtualization, see "Hardw. virt.ext: off" in the attached showvminfo.txt file. I have three VMs: oel57net has 500M RAM, this never fails. It doesn't do much: acts as a DHCP and DNS and NFS server for the other two. oel57a and oel57b have 1500M RAM and fail regularly but unpredictably with a Guru Mediatation 1103. They never last more 15 minutes, they usually last at least 5 minutes. I had thought that the problem was to do with the software I am running (I'm building a Oracle 11.2 cluster) but I do not believe this: the failures sometimes occur before starting the clusterware daemons. I previously raised this issue on the forum when I was using VB release 4.1.12 this is the link tio the post  https://forums.virtualbox.org/viewtopic.php?f=7&t=49184&p=223700&hilit=guru+meditation+1103#p223700 which includes more examples of the problem. Please tell me any other information I can provide, and thank you for any assistance.

Attachments

oel57b-2012-07-09-20-42-12.log Download (425.4 KB) - added by John Watson 3 years ago.
VM logfile
oel57a-2012-07-09-20-42-10.log Download (428.4 KB) - added by John Watson 3 years ago.
VM logfile
showvminfo.txt Download (3.5 KB) - added by John Watson 3 years ago.
outout of VBoxManage showvminfo oel57a
oel57a-2012-07-10-10-37-11.log Download (424.3 KB) - added by John Watson 3 years ago.
oel57b-2012-07-10-10-48-03.log Download (420.1 KB) - added by John Watson 3 years ago.

Change History

Changed 3 years ago by John Watson

VM logfile

Changed 3 years ago by John Watson

VM logfile

Changed 3 years ago by John Watson

outout of VBoxManage showvminfo oel57a

comment:1 Changed 3 years ago by John Watson

And to complete the example, another log file: no activity on the VM, booted it and left it alone. And by the way, sorry about my typo in the original post: host OS is OEL 5.5, not OEL 5.6.

Changed 3 years ago by John Watson

Changed 3 years ago by John Watson

comment:2 Changed 3 years ago by John Watson

As well as setting

Hardw. virt.ext: off

I have also tried

Page Fusion: off Hardw. virt.ext exclusive: off Nested Paging: off VT-x VPID: off

and there is no memory balloon. The 1500M VMs still fail unpredicatably after a few minutes.

comment:3 Changed 3 years ago by ramshankar

This looks like you're running out of hyperheap memory. Could you try bumping the HyperHeap size from the default 1.25 MiB to say 3 MiB?

  1. Poweroff the VM.
  2. Enter the command:
    VBoxManage setextradata <VMname> "VBoxInternal/MM/cbHyperHeap" "3145728"
    

Note: the value you specify is in bytes (here, 3145728 bytes = 3 MiB). If you continue to get this guru, try bumping this value even higher. The MMHyper code rounds this to 4096 bytes boundaries.

Version 0, edited 3 years ago by ramshankar (next)

comment:4 Changed 3 years ago by frank

  • Summary changed from Guru Meditation 1103 (VINF_EM_DBG_HYPER_ASSERTION) to Guru Meditation 1103 (VINF_EM_DBG_HYPER_ASSERTION), error -1701 (VERR_MM_HYPER_NO_MEMORY)

comment:5 Changed 3 years ago by John Watson

Thank you for your advice, ramshankar, it looks good. I am using the value you suggested, and the VMs have been running for a couple of hours no problem. Please close the ticket. I could only try it today, because I've been on a different job for the last two weeks.

comment:6 Changed 2 years ago by frank

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

comment:7 Changed 10 months ago by frank

  • Status changed from closed to reopened
  • Resolution worksforme deleted

comment:8 Changed 10 months ago by frank

Better use

VBoxManage setextradata VM_NAME "VBoxInternal/MM/CanUseLargerHeap" 1

We should add some heuristics to VBox to set this option automatically.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use