Ticket #3059 (closed defect: fixed)

Opened 10 years ago

Last modified 10 years ago

HostMemoryLow on Solaris 10 x86 u6, VBox 2.1.0

Reported by: apljavaman Owned by:
Component: host support Version: VirtualBox 2.1.0
Keywords: Memory Cc:
Guest type: Windows Host type: Solaris


We are experiencing a recurring problem on several of our Solaris hosts. We have 64 bit Dell 2950's running Solaris 10 w/ 12 GB of memory on each box. We only have 2-3 VMs running on each box, each with 1 GB of memory assigned. If we try to set the memory of a VM to 2 GB, we get a HostMemoryLow message. This happens even after rebooting the host. ZFS memory usage has been limited to 1 GB, and the host OS shows access to all 12 GB of memory. The VMs are all windows 2003 server. I am unable to provide the VBox.log due to corporate reasons.


vbox.log Download (31.8 KB) - added by apljavaman 10 years ago.
Log of hung VM due to memory problem

Change History

comment:1 Changed 10 years ago by sandervl73

32 or 64 bits Solaris host?

comment:2 Changed 10 years ago by sandervl73

Without a VBox.log there's not much we can do to help. Can't you just filter out any confidential information?

comment:3 Changed 10 years ago by apljavaman

It is a 64 bit Solaris host.

I will have to print out the log and then scan it back in. Is an image acceptable, or do you want me to OCR the scanned log?

comment:4 Changed 10 years ago by sandervl73

Image is fine, but it would be rather big, so OCR would be better unless it's a lot of work for you.

comment:7 Changed 10 years ago by frank

You might have noticed that your previous comment is almost unreadable because your managed it to cut'n'paste the VBox.log file. Please use the Attach button to attach files. And there is a Preview button as well.

Please could you add your comment again but this time without this VBox.log dump. Then attach the VBox.log file to this defect and I will remove your previous comment to make this bug report readable again.

Changed 10 years ago by apljavaman

Log of hung VM due to memory problem

comment:8 Changed 10 years ago by ramshankar

This is due to the double memory accounting bug in Solaris 10 for anonymous memory locking, which the current workaround is to increase swap.

Refer here:

comment:9 Changed 10 years ago by ramshankar

  • Status changed from new to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use