From owner-freebsd-virtualization@FreeBSD.ORG Wed Dec 3 03:27:33 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D3F1A81B for ; Wed, 3 Dec 2014 03:27:33 +0000 (UTC) Received: from alto.onthenet.com.au (alto2.onthenet.com.au [203.13.68.14]) by mx1.freebsd.org (Postfix) with ESMTP id 979BCD2 for ; Wed, 3 Dec 2014 03:27:32 +0000 (UTC) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by alto.onthenet.com.au (Postfix) with ESMTP id 5130312648; Wed, 3 Dec 2014 13:27:25 +1000 (EST) Received: from Peters-MacBook-Pro.local ([64.245.0.210]) by dommail.onthenet.com.au (MOS 4.4.4-GA) with ESMTP id CAF10028 (AUTH peterg@ptree32.com.au); Wed, 3 Dec 2014 13:27:24 +1000 Message-ID: <547E8319.9070509@freebsd.org> Date: Tue, 02 Dec 2014 19:27:21 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: John-Mark Gurney , freebsd-virtualization@freebsd.org Subject: Re: FreeBSD i386 guest doesn't see console... References: <20141203024112.GF99957@funkthat.com> In-Reply-To: <20141203024112.GF99957@funkthat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 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: Wed, 03 Dec 2014 03:27:33 -0000 Hi John-Mark, > This is w/ a resonably recent current i386 kernel (r275062) I verified the r274463 i386 snapshot boots fine. That's not quite as recent, but: >... Any suggestions? > uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 on acpi0 ... > uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > uart0: console (9600,n,8,1) The "flags 0x10" text isn't being displayed in the i386 dmesg. This is derived from /boot/device.hints i.e. ... hint.uart.0.flags=0x10 ... You can see this from bhyveload by issuing a 'show' command to dump all the environment, including what was read in from device.hints by the loader, or "more /boot/device.hints". It may be possible that this file isn't being populated in your image, or being read in by bhyveload. later, Peter.