From owner-freebsd-virtualization@FreeBSD.ORG  Wed Dec  4 20:00:13 2013
Return-Path: <owner-freebsd-virtualization@FreeBSD.ORG>
Delivered-To: freebsd-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 ESMTPS id 664E6E28
 for <freebsd-virtualization@freebsd.org>; Wed,  4 Dec 2013 20:00:13 +0000 (UTC)
Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12])
 by mx1.freebsd.org (Postfix) with ESMTP id 26AA41C86
 for <freebsd-virtualization@freebsd.org>; Wed,  4 Dec 2013 20:00:12 +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 154B012393;
 Thu,  5 Dec 2013 06:00:11 +1000 (EST)
Received: from Peter-Grehans-MacBook-Pro-2.local ([64.245.0.210])
 by dommail.onthenet.com.au (MOS 4.2.4-GA)
 with ESMTP id BQN79973 (AUTH peterg@ptree32.com.au);
 Thu, 5 Dec 2013 06:00:10 +1000
Message-ID: <529F89C7.6070909@freebsd.org>
Date: Wed, 04 Dec 2013 12:00:07 -0800
From: Peter Grehan <grehan@freebsd.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6;
 rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: Michael Dexter <editor@callfortesting.org>
Subject: Re: Upcoming FreeBSD 10.x + bhyve ...
References: <56DEE328-7C96-4AC9-BF87-2C41D4C7949F@hub.org>
 <529D210C.9020801@freebsd.org> <70B115D9-436C-45EC-8F2E-CEBB2A48A9A5@hub.org>
 <529F8656.7000408@callfortesting.org>
In-Reply-To: <529F8656.7000408@callfortesting.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-virtualization@freebsd.org
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Dec 2013 20:00:13 -0000

Hi Michael,

> In short:
>
> -S 31,uart,stdio
>
> Becomes:
>
> -S 31,uart,/dev/nmdm0A

  This will continue to work, though the preferred way of setting up a 
console port is to use the PCI-ISA (aka LPC) bridge

  -s N,lpc

  (N can be any slot number on bus 0, usually 1..31)

  There are 2 serial ports behind the LPC bridge, com1 and com2. These 
can have backends assigned to them in the same way as PCI devices, but 
use the "-l" option for configuration since they are 'lpc' devices e.g.

  -l com1,stdio

  -l com2,/dev/nmdm9B

  The advantage of using the LPC serial ports is that they will show up 
on the expected tty devices - com1 will be /dev/ttyu0 on FreeBSD as 
opposed to /dev/ttyu2 for the uart PCI device.

  So: "-S 31,uart/dev/nmdm0A" becomes "-s 31,lpc -l com1,nmdm0A"

  ... and change the guest's /etc/ttys file to set up a getty on ttyu0

later,

Peter.