From owner-freebsd-virtualization@FreeBSD.ORG Fri Oct 25 15:30:35 2013 Return-Path: Delivered-To: virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A1D97AC2 for ; Fri, 25 Oct 2013 15:30:35 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 665492DF1 for ; Fri, 25 Oct 2013 15:30:35 +0000 (UTC) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by alto.onthenet.com.au (Postfix) with ESMTPS id 8B3AA123FA; Sat, 26 Oct 2013 01:30:33 +1000 (EST) Received: from Peters-MacBook-Pro.local (c-67-161-27-37.hsd1.ca.comcast.net [67.161.27.37]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BPK76968 (AUTH peterg@ptree32.com.au); Sat, 26 Oct 2013 01:30:32 +1000 Message-ID: <526A8E95.7090808@freebsd.org> Date: Fri, 25 Oct 2013 08:30:29 -0700 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: symbolics@gmx.com Subject: Re: Three observations on Bhyve References: <20131025143341.GC26481@lemon> In-Reply-To: <20131025143341.GC26481@lemon> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: virtualization@freebsd.org 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 15:30:35 -0000 > (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.