Date: Sun, 19 Aug 2012 23:11:29 +0400 From: Roman Bogorodskiy <novel@FreeBSD.org> To: freebsd-virtualization@freebsd.org Subject: Re: BHyVe: vm_setup_memory(highmem): Cannot allocate memory Message-ID: <20120819191127.GA1733@kloomba> In-Reply-To: <20120815155222.GA46502@kloomba> References: <20120815155222.GA46502@kloomba>
next in thread | previous in thread | raw e-mail | index | archive | help
--YiEDa0DAkWCtVeE4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Roman Bogorodskiy wrote: > Hi, >=20 > I'm running into a problem. I did a fresh checkout of 'bhyve' branch > from svn and followed the instruction here: >=20 > http://people.freebsd.org/~neel/bhyve/bhyve_instructions.txt >=20 > In my /boot/loader.conf I have: >=20 > debug.witness.watch=3D"0" > hw.physmem=3D"0x180000000" >=20 > and dmesg says: >=20 > real memory =3D 8589934592 (8192 MB) > avail memory =3D 5643694080 (5382 MB) >=20 > When I try to start a VM I get this error: >=20 > (19:46) novel@kloomba:~/bhyve/vm1 %> sudo ./vmrun.sh -m 256 vm1 > Launching virtual machine "vm1" with 256MB memory below 4GB and 2048MB me= mory above 4GB ... > vm_setup_memory(highmem): Cannot allocate memory > (19:46) novel@kloomba:~/bhyve/vm1 %>=20 >=20 > This page: >=20 > http://callfortesting.org/bhyve/ >=20 > describes that reloading 'vmm' would help, but doing it changes nothing. >=20 > Any ideas what's wrong with that? Also, I am curious, what do these > numbers mean: >=20 > "256MB memory below 4GB and 2048MB memory above 4GB". I get that 256 is > the amount of mem to give to VM, but what do 4GB and 2048MB stand for? I have managed to boot a VM. The 4GB thing is hardcoded in the vmrun.sh script: 110 echo "Launching virtual machine \"$vmname\" with ${lowmem}MB memory below 4GB and ${highmem}MB memory above 4GB ..." Also, it seems it's hardcoded in bhyveload.c: if (highmem !=3D 0) { error =3D vm_setup_memory(ctx, 4 * GB, highmem, NULL); <---= here if (error) { perror("vm_setup_memory(highmem)"); exit(1); } } I used './vmrun.sh -m 512 -M 0 vm1' which sets highmem =3D=3D 0 to avoid th= is call. Roman Bogorodskiy --YiEDa0DAkWCtVeE4 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iQEcBAEBAgAGBQJQMTpfAAoJEMltX/4IwiJq+h8H/iMnDW4eR/DftPkdFIzVIzWe ywfxlBHlL+nreFUvZGYttUOTxHiHCJTGpGsmFlIzdvApxDosiUxaBiSygBl7oB3P +og8Yp8RZK07W1QhSa3hECwK4o14q5HgG23FKl5Oufl/HjzKJclvLYelHxnIpZop NdwLJGRsIyCFK8Bg1pUuJX2f7YdjrhMV/OaG2U6ygJ/FMh9SxMoZQe+ziqbbfz85 hRBC3CTS0w6h/E/xAUU/loK8ESa2ceZaXkiruIENwfN1XqQF+c6jiEXNviJ3xBgO T++bOfiMDP5ebsSjJox4epbp1TP+2ipVAvdUJ+6sau4uoHkmSJ9BbEDoJACKhnQ= =6VdT -----END PGP SIGNATURE----- --YiEDa0DAkWCtVeE4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120819191127.GA1733>