All,
Probably a FAQ...point me to the resource as appropriate... :-D
I'm finding that more often than not, VBox on Mac will fail to start a
VM and throw "VBox status code: -8 (VERR_NO_MEMORY)" or sometimes "VBox
status code: -32 (VERR_INTERNAL_ERROR)."
I see a ticket, but no information; no resolution... Apparently the
issue happens on windows hosts, as well?
http://www.virtualbox.org/ticket/1325
The behavior is rather frequent (e.g. MOST of the time it will happen
when I try to start a VM)...
Coldstart or resume doesn't seem to matter.
I have a 4 GB machine and generally I'm not using more than 1 GB of
memory outside of VBox.
The particular VM is only requesting 1 GB of memory.
At first I thought perhaps the issue had to do with some kind of memory
fragmentation, but I used the "usual trick" of the following to force
the Mac to drop free pages:
sudo find / -xdev -print > /dev/null
By the time that completes, one can see in the Activity Monitor that the
free pages have actually been dropped.
So can anyone offer any insight as to what is REALLY going on, here?
And is there a recommended "workaround" to insure that VBox gets the
memory it needs, more often than not?
Regards,
\Leon
--
[EMAIL PROTECTED] - Dearborn, Michigan
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
