Date: Sat, 22 Nov 2014 22:30:04 -0500 From: Shawn Webb <lattera@gmail.com> To: Peter Grehan <grehan@freebsd.org> Cc: freebsd-virtualization@freebsd.org Subject: Re: bhyve cannot allocate memory Message-ID: <CADt0fhxFzqKbw7kndeUVQaVeJ_jj=-yNUgvD6ntn7hM3YGqCLA@mail.gmail.com> In-Reply-To: <54715438.3090905@freebsd.org> References: <20141122215245.d9380cc4e43cb5e60d479009@gmail.com> <20141122220202.09523b0ae828993174af05d8@gmail.com> <5471513C.6040400@freebsd.org> <CADt0fhxEavv5e6tbmORxUZgPNGQNZiu2O=PtO6aKhW%2B_fkRSZQ@mail.gmail.com> <54715438.3090905@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 22, 2014 10:27 PM, "Peter Grehan" <grehan@freebsd.org> wrote: > > Hi Shawn, > > >> It's hardenedBSD. I'll try a stock build tomorrow. The only change we >> have that could affect bhyve is the removal of map_at_zero. > > > This may be the issue. bhyve creates a kernel-use-only vmspace that represents guest memory (starting at 0), and is used to allow the VM system to manage the EPT paging structures (full details in the AsiaBSDcon paper at http://people.freebsd.org/~neel/bhyve/bhyve_nested_paging.pdf). > > Is there a way to bypass the map-at-zero check for this usage in HardenedBSD ? > > later, > > Peter. > There isn't. map_at_zero was fully removed. I can revert that change, though. Or is there a way to make bhyve work with out it (with a patch)?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADt0fhxFzqKbw7kndeUVQaVeJ_jj=-yNUgvD6ntn7hM3YGqCLA>