Date: Mon, 20 Apr 2020 02:32:23 +0300 From: Yuri Pankov <ypankov@fastmail.com> To: Shawn Webb <shawn.webb@hardenedbsd.org>, Conrad Meyer <cem@freebsd.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r359950 - head/usr.sbin/bhyve Message-ID: <58b1d5e0-fa4d-6024-89e9-d8d40d3f7b25@fastmail.com> In-Reply-To: <20200419231353.fkx5uwtqq7h7yolh@mutt-hbsd> References: <202004150200.03F20I3H001953@repo.freebsd.org> <20200419224713.xaxvnuo334v6bhtj@mutt-hbsd> <CAG6CVpUkVPFJLE_4KsQ1-AUG2OATQY45WNu5Fq%2BJDhem0Gd2jQ@mail.gmail.com> <20200419231353.fkx5uwtqq7h7yolh@mutt-hbsd>
next in thread | previous in thread | raw e-mail | index | archive | help
Shawn Webb wrote: > This is the full output from bhyve: > > fbuf frame buffer base: 0x69191a00000 [sz 16777216] > bhyve: bootrom_alloc: vm_mmap_mapseg: No space left on device > bhyve: vmgenc_init: bootrom_alloc I wonder if it's coincidence, and you really didn't have 16G to wire at that moment, and after reverting the commit it was there (reboot?) -- I was getting the same error well before this change when I had almost all of the memory eaten by ZFS ARC, I was looking at r359949 as possible candidate, but limiting that memory hog did make the issue disappear.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?58b1d5e0-fa4d-6024-89e9-d8d40d3f7b25>