Date: Sat, 22 Nov 2014 19:57:07 -0800 From: Peter Grehan <grehan@freebsd.org> To: Shawn Webb <lattera@gmail.com> Cc: freebsd-virtualization@freebsd.org Subject: Re: bhyve cannot allocate memory Message-ID: <54715B13.9020303@freebsd.org> In-Reply-To: <CADt0fhxCv3DneeoVewGEz7%2BQ53gqDNENJKD2-CH6Sxz=PFT3ig@mail.gmail.com> References: <20141122215245.d9380cc4e43cb5e60d479009@gmail.com> <20141122220202.09523b0ae828993174af05d8@gmail.com> <5471513C.6040400@freebsd.org> <CADt0fhxEavv5e6tbmORxUZgPNGQNZiu2O=PtO6aKhW%2B_fkRSZQ@mail.gmail.com> <54715438.3090905@freebsd.org> <CADt0fhxFzqKbw7kndeUVQaVeJ_jj=-yNUgvD6ntn7hM3YGqCLA@mail.gmail.com> <54715822.2010309@freebsd.org> <CADt0fhwTSci31wwq8UoN2JpUGHKgLNiDXymZQyeWYFVd4i7PJA@mail.gmail.com> <54715911.1090100@freebsd.org> <CADt0fhxCv3DneeoVewGEz7%2BQ53gqDNENJKD2-CH6Sxz=PFT3ig@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
Hi Shawn, > Interesting. I'll have to do more digging. Because removing map_at_zero > support is the same as keeping it at the default of 0. It's not possible > that our ASLR implementation is affecting bhyve, since our ASLR > implementation is in sys_mmap and the elf image activator. At this > stage, bhyve's vmm.ko is directly accessing vm_map_*, which we haven't > touched. One thing you may be able to try is ktrace the bhyveload process and see which syscall is failing. later, Peter.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54715B13.9020303>