From owner-freebsd-virtualization@FreeBSD.ORG Mon Oct 28 04:02:06 2013 Return-Path: Delivered-To: freebsd-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 29D673D6; Mon, 28 Oct 2013 04:02:06 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 06F772EFD; Mon, 28 Oct 2013 04:02:05 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 7657C1CEAF; Mon, 28 Oct 2013 04:02:03 +0000 (UTC) Message-ID: <526DE1C1.604@allanjude.com> Date: Mon, 28 Oct 2013 00:02:09 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org Subject: Re: Three observations on Bhyve References: <20131025143341.GC26481@lemon> <526A8E95.7090808@freebsd.org> In-Reply-To: <526A8E95.7090808@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Devin Teske 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 04:02:06 -0000 On 2013-10-25 11:30, 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 :) > > later, > > Peter. > > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to > "freebsd-virtualization-unsubscribe@freebsd.org" > > > Last night Devin made a patch to bsdinstall (at #vBSDCon hacker lounge) to deal with the /etc/ttys issue on the system that bsdinstall installs, but, I wonder what the correct fix is for the livecd environment. During the hacker lounge discussion, we decided it probably wasn't a good idea to enable the serial console by default (bsdinstall only does it if it detects you using the serial console to do the install). I suppose the same logic could be added to the rc.local script in usr/src/release/ maybe, to 'patch' the /etc/ttys file when the serial condition is detected. -- Allan Jude