VirtualBox

Ticket #7586 (closed defect: fixed)

Opened 4 years ago

Last modified 3 years ago

ubuntu 10.10 crashes with memory > 4G (out of hypervisor heap guru) -> fixed in SVN

Reported by: tommy Owned by:
Priority: critical Component: VMM/HWACCM
Version: VirtualBox 3.2.10 Keywords:
Cc: Guest type: Linux
Host type: Windows

Description

Hello experts,

i run ubuntu 10.10-64 (desktop) as guest on a Win7-64 (Mem: 12GB) Host

The guest can be started, but after login (when starting the user session) the system crashes, but only when main memory is more than 4G. Worked fine with VB 3.2.8!

Attachments

Ubuntu64-2010-10-15-09-36-55.zip Download (63.5 KB) - added by tommy 4 years ago.
Ubuntu64-2010-10-18-10-30.zip Download (63.5 KB) - added by tommy 3 years ago.
vbox-log after setting extradata
Ubuntu64-2010-10-18-10-30.2.zip Download (63.5 KB) - added by tommy 3 years ago.
vbox-log after setting extradata
Ubuntu64-2010-10-18-10-44-42.zip Download (63.3 KB) - added by tommy 3 years ago.
Vbox log testbuild 3.2.11
Ubuntu64-2010-10-19-09-24-17.zip Download (5.7 KB) - added by tommy 3 years ago.

Change History

Changed 4 years ago by tommy

comment:1 Changed 4 years ago by tommy

the ubuntu guest system crashes, not the host! sorry!

comment:2 Changed 4 years ago by sandervl73

You can work around it by changing an internal config value:

VBoxManage setextradata "VM name" "VBoxInternal/PGM/Pool/MaxPhysExts" 2048

If that doesn't help, then please upload another log file (so I can check you did it correctly).

comment:3 Changed 4 years ago by sandervl73

  • Component changed from other to VMM/HWACCM
  • Summary changed from ubuntu 10.10 crashes with memory > 4G to ubuntu 10.10 crashes with memory > 4G (out of hypervisor heap guru)

Changed 3 years ago by tommy

vbox-log after setting extradata

Changed 3 years ago by tommy

vbox-log after setting extradata

comment:5 Changed 3 years ago by tommy

Hello sandervl73,

setting the extradata did not help. I send you the logfile.

I will try out the testbuild.

Thanks!

regards

tommy

comment:6 Changed 3 years ago by tommy

hello sandervl73,

the testbuild also does not work with mem >4G :-(( I attach the new log.

But i recognized a difference between startup with <=4G and > 4G:

When starting up with more than 4G there is an info in the window that does not appear when starting with <= 4G:

modprobe: FATAL could not load /lib/modules/2.6.35-22 generic/modules.dep No such file or directory

Googleing around i found some tips but no working solution.

regards

tommy

Changed 3 years ago by tommy

Vbox log testbuild 3.2.11

comment:7 Changed 3 years ago by frank

Well, you still get a Guru Meditation.

comment:8 Changed 3 years ago by sandervl73

Could you try  this build?

comment:9 Changed 3 years ago by tommy

with this build (r66734) it is not possible to start at all. A messagebox appears: "VirtualBox GUI funktioniert nicht mehr" (in english: Virtualbox GUI does not work anymore)

one more log attached ;-)

tommy

Changed 3 years ago by tommy

comment:10 Changed 3 years ago by tommy

i have to correct me: the client starts up with memory up to 3575MB.

comment:11 Changed 3 years ago by frank

Please test  this build, the VM should now start with more than 3575MB RAM.

comment:12 Changed 3 years ago by tommy

This build (66799) works fine now with more than 4G! (though the modprobe error is still appearing) and i can start my application that needs a lot of main memory without problems.

thanx for your help!

comment:13 follow-up: ↓ 15 Changed 3 years ago by frank

Regarding the modprobe error: Did do depmod -a in your guest?

comment:14 Changed 3 years ago by sandervl73

  • Summary changed from ubuntu 10.10 crashes with memory > 4G (out of hypervisor heap guru) to ubuntu 10.10 crashes with memory > 4G (out of hypervisor heap guru) -> fixed in SVN

comment:15 in reply to: ↑ 13 Changed 3 years ago by tommy

Replying to frank:

Regarding the modprobe error: Did do depmod -a in your guest?

sorry for my late answer:

Restarting after running 'depmod -a' did not show the message. But after a next restart it is shown again.

comment:16 follow-up: ↓ 17 Changed 3 years ago by frank

tommy, in that case make sure that you rebuild the initram disk. Do

depmod -a
update-initramfs -c -k $(uname -r)

comment:17 in reply to: ↑ 16 Changed 3 years ago by tommy

Replying to frank:

tommy, in that case make sure that you rebuild the initram disk. Do

depmod -a
update-initramfs -c -k $(uname -r)

didn't help :-((

comment:18 Changed 3 years ago by frank

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

Your problem is something else.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use