From owner-freebsd-virtualization@FreeBSD.ORG Fri Oct 25 22:14:40 2013 Return-Path: Delivered-To: virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9E11347D for ; Fri, 25 Oct 2013 22:14:40 +0000 (UTC) (envelope-from symbolics@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3AB36263D for ; Fri, 25 Oct 2013 22:14:40 +0000 (UTC) Received: from lemon ([80.7.17.14]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MZU7V-1VHKE93d7N-00LCGj for ; Sat, 26 Oct 2013 00:14:32 +0200 Received: by lemon (Postfix, from userid 1001) id 633A4EB3A6; Fri, 25 Oct 2013 23:14:32 +0100 (BST) Date: Fri, 25 Oct 2013 23:14:32 +0100 From: symbolics@gmx.com To: virtualization@freebsd.org Subject: Re: Three observations on Bhyve Message-ID: <20131025221432.GC26814@lemon> References: <20131025143341.GC26481@lemon> <526A8E95.7090808@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <526A8E95.7090808@freebsd.org> X-Provags-ID: V03:K0:Ck6GQXjg4I1z9lXyCkZ0P8NNc4CBbVSzeQFtt/+OW+A7TQu1WrI RKEE/4tZOuM3f+UvVvY6+/L8zx2xFJOuFgHSwd/P3TwhhN7Gz62WofBQ0+aQIYXNhW9e1E0 jyZrurFtD4FjjLfleoscyrfi9HhyQRcdhStc9vGT9GbiltsVo0gYu42W0H6rZ+07RFz/qi9 7kza7MmDManAFhMGBxwbw== X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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, 25 Oct 2013 22:14:40 -0000 On Fri, Oct 25, 2013 at 08:30:29AM -0700, Peter Grehan wrote: > > (1) You can't boot an i386 ISO. It can't load the kernel. I half > > expected this would be the case. It would be nice if this did work. > > The loader work isn't too bad to get this going, but the bhyve work is > quite a bit more effort since the i386 kernel makes a lot more > assumptions about the environment, such as the ability to call back into > BIOS. > > On the TODO list. Great, thank you. > > (2) VirtIO on a raw disc device seems to have some problems. I tried > > installing using the -BETA1 amd64 ISO. The disc particulars seem to be > > detected fine but when I try and commit the partition layout I see: > > > > 5vtbd0: hard error cmd=write 290-305 > > > > The disc is a 640GB WD SATA disc and I used the automatic scheme, if it > > makes any difference. > > That's bhyve colliding with GEOM. There was a thread a while back > about being able to exempt certain block devices from being tasted for > iSCSI LUN usage - bhyve will probably need something similar. Is this different from the kern.geom.notaste sysctl des@ added recently? > > (3) I tried to use the live environment in order to play around with > > (2) a bit more but it lacks the necessary /etc/ttys line. It would be > > great if this wasn't required *somehow*. > > The ttys issue does need to be addressed. This applies for serial > console users as well. Hey, works for Linux :) > > > Should I file PRs for these issues? > > Yes, always file PRs please :) Okay, will set them up tomorrow. Thanks Peter, --sym