From owner-freebsd-virtualization@FreeBSD.ORG  Sun Apr 28 18:26:08 2013
Return-Path: <owner-freebsd-virtualization@FreeBSD.ORG>
Delivered-To: freebsd-virtualization@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 284F7EA1;
 Sun, 28 Apr 2013 18:26:08 +0000 (UTC)
 (envelope-from mack@macktronics.com)
Received: from coco.macktronics.com (coco.macktronics.com [209.181.253.65])
 by mx1.freebsd.org (Postfix) with ESMTP id 076BD1091;
 Sun, 28 Apr 2013 18:26:07 +0000 (UTC)
Received: from coco.macktronics.com (coco.macktronics.com [209.181.253.65])
 by coco.macktronics.com (Postfix) with ESMTP id 090D04AC41;
 Sun, 28 Apr 2013 13:26:07 -0500 (CDT)
Date: Sun, 28 Apr 2013 13:26:06 -0500 (CDT)
From: Dan Mack <mack@macktronics.com>
To: Peter Grehan <grehan@freebsd.org>
Subject: Re: bhyve console question
In-Reply-To: <517D5F9F.6030809@freebsd.org>
Message-ID: <20130428124802.K97174@coco.macktronics.com>
References: <20130427154625.X29498@coco.macktronics.com>
 <517C4F9C.9020200@freebsd.org>
 <20130428083458.S95875@coco.macktronics.com> <517D5F9F.6030809@freebsd.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: freebsd-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."
 <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: Sun, 28 Apr 2013 18:26:08 -0000

Ahh, cool.   I wasn't paying attention I guess:

  uart2: <16550 or compatible> port 0x3f8-0x3ff irq 4 at device 31.0 on pci0
  uart2: console (9600,n,8,1)

which maps to the bhyve argument given:  '-S 31,uart,stdio'

and subsequently the serial console getty on ttyu2.  Nice.   Thank you,

It would be kind of cool to bind a guest's serial port to a named pipe on 
the host system (I think virtual box lets you do this too - an option when 
creating a guest serial port).

This would make it easy to have each bhyve guest with serial console 
attached to a list of device files upon which we could attach a screen 
session to later if we wanted to login or look at the console.

For now, I'll just spin up each vm guest within a separate screen window.

Take care,

Dan


On Sun, 28 Apr 2013, Peter Grehan wrote:

> HI Dan,
>
>> Yes, the current bhyve-manual has that as a step in the configuration
>> (http://bhyve.org/bhyve-manual.txt) which I guess is the culprit. I
>> guess I just didn't expect that side effect but admit to not spending
>> much time thinking about it first :-)
>
> I think it was done that way since /dev/console will always work, whereas 
> the tty line to use changed at one point when we cut over from the ISA uart 
> device to the PCI uart device resulting in a different tty device being used. 
> However, it looks like we may switch back to using a PCI-ISA bridge device 
> and that will change things again :(
>
> For now, you can edit the stock /etc/ttys as follows:
>
> -ttyu2  "/usr/libexec/getty std.9600"   dialup  off secure
> +ttyu2   "/usr/libexec/getty std.9600"   vt100   on  secure
>
> later,
>
> Peter.
>