From owner-freebsd-virtualization@FreeBSD.ORG Sun Nov 23 03:30:06 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D96BBDE0; Sun, 23 Nov 2014 03:30:05 +0000 (UTC) Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A2493BBC; Sun, 23 Nov 2014 03:30:05 +0000 (UTC) Received: by mail-oi0-f44.google.com with SMTP id e131so5384737oig.3 for ; Sat, 22 Nov 2014 19:30:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=lXrrEoFnWT6n67GWLdwV/85L8WVf9jiNpj3tuK10i2U=; b=GQVQpwklxzrB8/xQ6g0FJqLqXs2wxzrGwp9WvVOkRmV/rmEMQFKUlX+VqzAh1zFPcS 3PfPZETYY179EP+eEPpnDbdaKkNeqA43850I3VPYQJwGcnt8K/fL45IGz6/yAUkWeuz6 L2TQbsKqKWn98ajKO+kAu/SGZiP+gHD1qpLODGnemg/Dym9nGKIbln9IF+NKj342ihij m5tNloOsNooz2vSseY5FB3HHoWXMzBngzb8Vfbkkg06TuPmBjNGrORXXhRvDc3HNKyEn wi1W3/Ggqa5fePu2VNYod6zypmGSAPyhfSOvRCSQggQ4akzXGO3J40om3NFNMIt5lZqm 35tg== MIME-Version: 1.0 X-Received: by 10.202.201.77 with SMTP id z74mr6789012oif.70.1416713404994; Sat, 22 Nov 2014 19:30:04 -0800 (PST) Received: by 10.202.184.7 with HTTP; Sat, 22 Nov 2014 19:30:04 -0800 (PST) Received: by 10.202.184.7 with HTTP; Sat, 22 Nov 2014 19:30:04 -0800 (PST) In-Reply-To: <54715438.3090905@freebsd.org> References: <20141122215245.d9380cc4e43cb5e60d479009@gmail.com> <20141122220202.09523b0ae828993174af05d8@gmail.com> <5471513C.6040400@freebsd.org> <54715438.3090905@freebsd.org> Date: Sat, 22 Nov 2014 22:30:04 -0500 Message-ID: Subject: Re: bhyve cannot allocate memory From: Shawn Webb To: Peter Grehan Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Nov 2014 03:30:06 -0000 On Nov 22, 2014 10:27 PM, "Peter Grehan" 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)?