From owner-freebsd-current@freebsd.org  Thu Aug 27 13:16:58 2015
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@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 876699C4989
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Thu, 27 Aug 2015 13:16:58 +0000 (UTC)
 (envelope-from outbackdingo@gmail.com)
Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com
 [IPv6:2607:f8b0:400c:c05::229])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 43B34115A
 for <freebsd-current@freebsd.org>; Thu, 27 Aug 2015 13:16:58 +0000 (UTC)
 (envelope-from outbackdingo@gmail.com)
Received: by vkm66 with SMTP id 66so8823194vkm.1
 for <freebsd-current@freebsd.org>; Thu, 27 Aug 2015 06:16:57 -0700 (PDT)
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=O56vL9ymZDKut4IKvLoGebWSKCExU20yMVfnuu4qAX4=;
 b=IuWpWHMxX3zDGbWfTVaWcJVjj4+i5v6v/bJSCyLxZ9QRwfEWyyqbg/AqJtoV6h0zEU
 mhzGpNCOwWOKkPQXJ9PCw+x8A3Mm4TySbs7SQ0e6G1zR1iBl5T7oToyKavlZ8G7gwvcM
 kC90R9i/dDIB5NHwWsq313UGpF8wS+XmVgLq5zfJlC/pfxCrvVqnNXyzJHng7Bl5MEke
 nG3ERNXwSH4qkWeaF33nhkwegw1tYReY3MMbPAfwPYOweNsv2BwpxQdBRKbaMCiV10iS
 HqoM4Ngio9ohBoKjjrWnIRbeuK/YEV26QOvod5n+FWgu2pFvtkd4w1cEN78uoYj4c4aP
 x2HA==
MIME-Version: 1.0
X-Received: by 10.52.114.196 with SMTP id ji4mr4813087vdb.24.1440681417308;
 Thu, 27 Aug 2015 06:16:57 -0700 (PDT)
Received: by 10.103.77.221 with HTTP; Thu, 27 Aug 2015 06:16:57 -0700 (PDT)
In-Reply-To: <CABx9NuTcqFR=vSd1DR-SA4-my-avNOF-jDep3fam=EjaSvgsuA@mail.gmail.com>
References: <CABx9NuTcqFR=vSd1DR-SA4-my-avNOF-jDep3fam=EjaSvgsuA@mail.gmail.com>
Date: Thu, 27 Aug 2015 23:16:57 +1000
Message-ID: <CAKYr3zwP=Msu2YcDzv415aZ6excqqiydvyEjs1TEga2Nw2b_+A@mail.gmail.com>
Subject: Re: Is NextBSD safe for bhyve?
From: Outback Dingo <outbackdingo@gmail.com>
To: Russell Haley <russ.haley@gmail.com>
Cc: freebsd-current@freebsd.org
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.20
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Aug 2015 13:16:58 -0000

On Thu, Aug 27, 2015 at 5:15 PM, Russell Haley <russ.haley@gmail.com> wrote:

> Is NextBSD safe for bhyve?
>
> Thanks
>

Consider that everything CURRENT, can be somewhat volatile at times, I
wouldnt recommend it for a production business case.
However that being said I do have XEN/NextBSD running as a dom0 quite well,
iocage, behyve and others are being reveiwed
for use cases, at this state of flux your mileage may vary depending on
exactly what your using it for, localized testing and
running a few vms, Ive accomplished that much with XEN so far. But again,
it is based on CURRENT with alot of additions
being merged in and worked on daily.


>
> Russ
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>