Ticket #1397 (new defect) — at Version 4

Opened 11 years ago

Last modified 2 years ago

Overcommitting of memory (swap in/out)

Reported by: IuK Owned by:
Priority: major Component: VMM
Version: VirtualBox 1.5.6 Keywords:
Cc: Guest type: other
Host type: Windows

Description (last modified by frank) (diff)

I always get HostMemoryLow e.g. Knoppix 5.2. VMware and Microsoft Virtual PC work on this PC (IBM Thinkpad T40, 512 Mb RAM). I have enclosed the Logfile. How can I help?

Change History

Changed 11 years ago by IuK

comment:1 Changed 11 years ago by sandervl73

  • Priority changed from blocker to major
  • Summary changed from HostMemoryLow to Overcommitting of memory (swap in/out)

You don't have enough memory in your machine. Reduce the ram size of the VM to 128 MB or less. VMWare and VPC swap memory in and out; VBox currently doesn't.

comment:2 Changed 11 years ago by Ralf_W

There seems to be another reason for the HostMemoryLow error:

I have 3Gb of memory on my XP host, 2Gb assigned to my ubuntu guest. It's possible to work for hours, but suddenly the machine is halted with

00:14:54.616 NAT: DHCP offered IP address
09:47:58.916 NAT: DHCP offered IP address
09:48:29.243 pgmr3PhysGrowRange: out of memory. pause until the user resumes execution.
09:48:29.243 Changing the VM state from 'RUNNING' to 'SUSPENDED'.
09:48:29.887 Console: VM runtime error: fatal=false, errorID=HostMemoryLow message="Unable to allocate and lock memory. The virtual machine will be paused. Please close applications to free up memory or close the VM."

The host had still about 700k of free memory. The guest-machine really posessed 2Gb, cause memory usage was 2.3Gb when the SUSPEND occurred and after closing the VM, memory usage was at 330k.

I'll attach the complete log.

Changed 11 years ago by Ralf_W

comment:3 Changed 11 years ago by Ralf_W

Since my last visit I've increased host memory to 4Gb (resulting in ~3.5 Gb usable memory under XP).

  • When giving 2 Gb to the virtual machine, the HostMemoryLow error continues to happen.
  • After reducing VM memory to 1.5 Gb (=less than half of my usable memory) the problem did not occur for serveral days.

Does VirtualBox perform something like a realloc?
If so, could you provide an option to allocate all memory at startup and avoid reallocation?

comment:4 Changed 10 years ago by frank

  • Description modified (diff)
Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use