From owner-freebsd-virtualization@freebsd.org Fri Mar 18 11:39:16 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1E594AD5F67 for ; Fri, 18 Mar 2016 11:39:16 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id DA4651D0B for ; Fri, 18 Mar 2016 11:39:15 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id C0F254F57A; Fri, 18 Mar 2016 11:39:08 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id u2IBd7pO037796; Fri, 18 Mar 2016 11:39:07 GMT (envelope-from phk@phk.freebsd.dk) To: Neel Natu cc: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= , "freebsd-virtualization@freebsd.org" Subject: Re: -current host, 10.1 client loops In-reply-to: From: "Poul-Henning Kamp" References: <20918.1458052609@critter.freebsd.dk> <23329.1458077441@critter.freebsd.dk> <28223.1458163559@critter.freebsd.dk> <30597.1458200333@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <37794.1458301147.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Fri, 18 Mar 2016 11:39:07 +0000 Message-ID: <37795.1458301147@critter.freebsd.dk> X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 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: Fri, 18 Mar 2016 11:39:16 -0000 -------- In message , Neel Natu writes: >https://www.freebsd.org/releases/10.1R/errata.html#open-issues > >Can you try to reproduce after setting 'vfs.unmapped_buf_allowed=3D0' at >the guest loader prompt? > >The issue doesn't mention bhyve specifically but given that it's a >simple workaround it should be worth a try. That may have helped, at least I got all the way through a nanobsd build this time. -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= .