Try checking login.conf(5), specifically your default limits. ksh(1) shows these via 'ulimit -a'.
Penned by David Cantrell on 20110821 21:09.30, we have: | I am unable to start a qemu guest with more than 256M of memory, | despite having 4G in my system. I get ENOMEM and qemu exits. Using | 256M or less works just fine. | | After some debugging, I see that qemu uses valloc(), which then uses | malloc() and that's preventing anything larger than 256M. | | Out of curiosity, I wrote a simple test program that used valloc() to | ask for 256M. Then I tried 512M, and got the failure I expected. | Debugging passed NKMEMPAGES in front of my eyes and I was curious | what changing that would have. I built a kernel with: | | option NKMEMPAGES=131072 | | My test program was able to request 536678400 bytes and no more, | short of 512M by 192512 bytes, or 47 pages on my system. | | Despite that test, qemu still wouldn't have any of it and refused to | start guests with more than 256M. I really am at a loss. Anyone | have any suggestions? | | I am back to running GENERIC.MP unmodified on OpenBSD 4.9. | | Thanks, | | -- | David Cantrell <david.l.cantr...@gmail.com> | WH6DSN | http://blog.burdell.org/ -- Todd Fries .. t...@fries.net _____________________________________________ | \ 1.636.410.0632 (voice) | Free Daemon Consulting, LLC \ 1.405.227.9094 (voice) | http://FreeDaemonConsulting.com \ 1.866.792.3418 (FAX) | 2525 NW Expy #525, Oklahoma City, OK 73112 \ sip:freedae...@ekiga.net | "..in support of free software solutions." \ sip:4052279...@ekiga.net \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ 37E7 D3EB 74D0 8D66 A68D B866 0326 204E 3F42 004A http://todd.fries.net/pgp.txt
