Re: virtualbox: out of memory on start [Was: DRI initialiazation fails on 8.0-BETAx/M54]

From: Ivan Voras <ivoras_at_freebsd.org>
Date: Fri, 18 Sep 2009 16:43:04 +0200
2009/9/18 Ivan Voras <ivoras_at_freebsd.org>:
> 2009/9/17 Bernhard Froehlich <decke_at_bluelife.at>:
>
>
>>> Host RAM: 3822MB RAM, available: 30MB
>>> So it seems like it needs Free memory and can not pressure other memory to
>>> get freed or got to swap.
>>
>> I've had a look at the code and found that "available" is interpreted as
>> "free" which is wrong. According to my understanding available RAM means
>> Free + Cached + Inactive so i have created a patch for that and commited
>> it to our svn port as r491.
>>
>> Could you please give it a try? (we have automatically build tar's now :o)
>>
>> http://svn.bluelife.at/nightlies/virtualbox-port.tar.gz
>
> Your interpretation about available memory is correct, but it doesn't
> solve my problem:
>
> 00:00:00.896 VirtualBox 3.0.51_OSE r23006 freebsd.amd64 (Sep 18 2009
> 12:45:43) release log
> 00:00:00.896 Log opened 2009-09-18T11:00:34.205219000Z
> 00:00:00.896 OS Product: FreeBSD
> 00:00:00.896 OS Release: 8.0-BETA2
> 00:00:00.896 OS Version: FreeBSD 8.0-BETA2 #5: Mon Aug 17 11:29:21
> CEST 2009     ivoras_at_lara.cc.fer.hr:/usr/obj/usr/src/sys/LARA
> 00:00:00.896 Host RAM: 3823MB RAM, available: 1248MB
> 00:00:00.896 Executable: /usr/local/lib/virtualbox/VirtualBox
> 00:00:00.896 Process ID: 30904
> 00:00:00.896 Package type: BSD_64BITS_GENERIC (OSE)
> 00:00:00.908 SUP: Opened VMMR0.r0 (/usr/local/lib/virtualbox/VMMR0.r0)
> at 0xffffffff81070080.
> 00:00:00.909 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005)
> aIID={0a51994b-cbc6-4686-94eb-d4e4023280e2} aComponent={Console}
> aText={VM creation failed (GVMM) (VERR_NO_MEMORY).
> 00:00:00.909 Unknown error creating VM (VERR_NO_MEMORY)}
> aWarning=false, preserve=false
> 00:00:01.059 Power up failed (vrc=VERR_NO_MEMORY, rc=NS_ERROR_FAILURE
> (0X80004005))
>
> As before, I have enough "available" memory (though much more than
> before so your patch is very useful) but this doesn't allow my 512 MB
> VM to start.

It looks like it could be something local.

I've rebooted now and I have around 3 GB "available" memory as VBox
sees it, and now I can start machines as usual.
Received on Fri Sep 18 2009 - 12:43:26 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:55 UTC