From owner-freebsd-virtualization@FreeBSD.ORG Mon Oct 28 16:11:39 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 B913394A for ; Mon, 28 Oct 2013 16:11:39 +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 56A632A0E for ; Mon, 28 Oct 2013 16:11:39 +0000 (UTC) Received: from lemon ([80.7.17.14]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0LwaQZ-1VkQQu3q19-018Gjc for ; Mon, 28 Oct 2013 17:11:31 +0100 Received: by lemon (Postfix, from userid 1001) id 5B768EB2F2; Mon, 28 Oct 2013 16:11:31 +0000 (GMT) Date: Mon, 28 Oct 2013 16:11:31 +0000 From: symbolics@gmx.com To: virtualization@freebsd.org Subject: Re: Three observations on Bhyve Message-ID: <20131028161131.GA3335@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:VAEqi5ker3fXXqOPGncWY95a5Gbpd0D5rs0Bq+qPzRMs1Fr1y2F ws1Oj4EZCnqMIXGUDAiWJFKu0gir2Cfn6bqU5eOD1c8aBlbiLkQNFGFrHeHtJS93iPbEQH0 jiOtoTy3c3QczfeuHUQvn2bllCdjSW+Ehp/5zw3wBPrKKEvkcP9B19LeGtWrZsEA296Rtqq Bsw5DFTMThoWZZeRewC2Q== 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: Mon, 28 Oct 2013 16:11:39 -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. > > > (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. > > > (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 :) > Hi Peter, Filed as 183400, 183401 and 183408. --sym