Failed to load VMMR0.r0 VERR_NO_MEMORY

[mperu99]

yesterday this was working fine, no issues, today i needed to launch my quest os after working most of the day on the host, and I received the VERR_NO_MEMORY error.

Here is the log:

Code: Select all

00:00:00.255 VirtualBox 4.0.6 r71416 win.x86 (Apr 26 2011 15:09:03) release log
00:00:00.255 Log opened 2011-05-04T20:46:50.405878900Z
00:00:00.255 OS Product: Windows XP Professional
00:00:00.255 OS Release: 5.1.2600
00:00:00.255 OS Service Pack: 2
00:00:00.266 DMI Product Name: Latitude D830                   
00:00:00.270 DMI Product Version: 
00:00:00.272 Host RAM: 3581MB RAM, available: 2915MB
00:00:00.272 Executable: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
00:00:00.272 Process ID: 5244
00:00:00.272 Package type: WINDOWS_32BITS_GENERIC
00:00:00.282 pdmR3LoadR0U: pszName="VMMR0.r0" rc=VERR_NO_MEMORY szErr="supLoadModule returned VERR_NO_MEMORY"
00:00:00.282 VMSetError: D:\tinderbox\win-4.0\src\VBox\VMM\VMMR3\VM.cpp(583) vmR3CreateU; rc=VERR_NO_MEMORY
00:00:00.282 VMSetError: Failed to load VMMR0.r0
00:00:00.282 VMSetError: D:\tinderbox\win-4.0\src\VBox\VMM\VMMR3\VM.cpp(354) VMR3Create; rc=VERR_NO_MEMORY
00:00:00.282 VMSetError: Unknown error creating VM
00:00:00.282 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={515e8e8d-f932-4d8e-9f32-79a52aead882} aComponent={Console} aText={Failed to load VMMR0.r0 (VERR_NO_MEMORY).
00:00:00.282 Unknown error creating VM (VERR_NO_MEMORY)}, preserve=false
00:00:00.346 Power up failed (vrc=VERR_NO_MEMORY, rc=E_FAIL (0X80004005))

i started out with Host RAM: 3581MB RAM, available: 2915MB, guest started at 1512MB
I adjusted it down to 1024MB, did not work, 512MB did not work,
I even adjusted the guest Memory down to 256Meg of ram it still did not work. I rebooted HOST machine, set the guest to 512Meg and it worked.
I shut down the guest re-adjusted the Ram to 1024 and it still worked.
weird, my available RAM is currently less NOW than it was when i tried before the reboot., this must be a leak of some sort. or lockout of some sort.

SPECS: VirtualBox 4.0.6 r71416 win.x86
Host - see log
Guest - windows xp / sp3 / 1024 Meg of Ram.

Shouldn't have to completely reboot the HOST to get my Virtualbox to run.
I have VMWARE on here too, they didnt have any issues. even running 2 at the same time.
Obviously 4.0.6 still has VERR NO MEM issues.

** forgot to mention I did not have this issue with the previous version or with 3.x

[squall leonhart]

are you using Prio or Kaspersky IS?

[blabj]

I ran into the same issue on linux, but it turns out its not specifically a fault of virtualbox.

Sorry, cannot help with Windows host.. but with linux host here is the solution...

Its a shortage of virtual memory in the linux kernel. Default is 128M.

Certain device drivers (modules) - in my case, a video capture card - require chunks of this virtual memory for device mapping.

Virtualbox obviously uses the same mechanism. You can have 16GB of RAM, but if you only have 128M of vm allocated, you are going to run into the same issue.

Solution is to pass the "vmalloc=<size>" parameter to your kernel on boot.

In ubuntu, edit /etc/default/grub, and add "vmalloc=192M" to the GRUB_CMDLINE_LINUX_DEFAULT list.

eg. GRUB_CMDLINE_LINUX_DEFAULT="vmalloc=192M quiet splash"

sudo update-grub

reboot