[Solved] "out of memory" with enough memory allocated.

[KL]

Hello,

I am getting an error message of "out of memory" reading a 7 gb db file. The software requires 4 gb RAm only. I am running ubuntu on win7 host and allocated 20gb RAm in virtualbox. How to fix that??

I have log attached. Thanks!

[mpack]

I don't know what "handling a 7gb file" means. What file are you referring to? Can you be clearer about your problem?

Start by posting a VM log file: with the VM fully shut down, right click and choose "Show Log" in the GUI, save "VBox.log" (ONLY) to a zip, and attach the zip here.

[KL]

Thank you. I attached the log file. Basically I am using a program to read a 7 gb db file. System specification from the program was 4 gb rem. And I have 20gb for the VM.

I don't know what "handling a 7gb file" means. What file are you referring to? Can you be clearer about your problem?

Start by posting a VM log file: with the VM fully shut down, right click and choose "Show Log" in the GUI, save "VBox.log" (ONLY) to a zip, and attach the zip here.

[mpack]

My understanding is that VirtualBox requires the allocated RAM to be in one contiguous chunk. You are allocating 19GB to the VM, on a host which only has 28GB available (i.e. not already in use). It is unlikely that such a large allocation is available in one chunk.

Try reducing the VM RAM allocation to 4GB.

The maximum size of file a VM can handle has absolutely nothing to do with how much RAM you give the VM. E.g. a 512MB XP VM can easily handle a 7GB file. The application doesn't load the entire file into memory at once - at least not if the programmer had a brain.

[Perryg]

I looked at the log the OP posted and it does not show an issue. If the contiguous size had been breached I would expect it to show in the VBox log as host memory low. I think the issue is inside the guest. I also noticed that the AMD processor in one place states 8 cores but in the last where it matters it says 2 physical cores. Sine they have assigned 2 cores to the guest I would look into that if it were me. As well as trying what you said of course.

You know back years ago when I actively used Windows I remember seeing these kinds of memory issues ( even on metal ). Turned out to be caused by the swap size and the registry size settings being too low.

[KL]

Hello, No idea now. But after I decreased the memory allocation for ubuntu to 7 gb, everything worked.