From owner-freebsd-virtualization@FreeBSD.ORG  Sat Apr 27 21:00:01 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])
 by hub.freebsd.org (Postfix) with ESMTP id A8526A51
 for <freebsd-virtualization@freebsd.org>; Sat, 27 Apr 2013 21:00:01 +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 8A4971A6C
 for <freebsd-virtualization@freebsd.org>; Sat, 27 Apr 2013 21:00:01 +0000 (UTC)
Received: from coco.macktronics.com (coco.macktronics.com [209.181.253.65])
 by coco.macktronics.com (Postfix) with ESMTP id A29CA4AC40
 for <freebsd-virtualization@freebsd.org>; Sat, 27 Apr 2013 15:51:52 -0500 (CDT)
Date: Sat, 27 Apr 2013 15:51:52 -0500 (CDT)
From: Dan Mack <mack@macktronics.com>
To: freebsd-virtualization@freebsd.org
Subject: bhyve console question
Message-ID: <20130427154625.X29498@coco.macktronics.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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: Sat, 27 Apr 2013 21:00:01 -0000


For those of you tinkering with bhyve; quick question.  I've noticed that 
everything I type on the console ends up in /var/log/messages on the 
guest.  This includes all shell activity and login stuff.

Is this expected behaviour ?

When following the standard bhyve recipes on the interwebs, it appears as 
if all console activity is categorized as kernel.debug level messages, for 
example:

root@mcp:~ # tail /var/log/messages
Apr 27 15:50:02 mcp kernel: /
Apr 27 15:50:02 mcp kernel: va
Apr 27 15:50:03 mcp kernel: r/
Apr 27 15:50:03 mcp kernel: l
Apr 27 15:50:03 mcp kernel: o
Apr 27 15:50:03 mcp kernel: g
Apr 27 15:50:04 mcp kernel: /m
Apr 27 15:50:04 mcp kernel: e
Apr 27 15:50:04 mcp kernel: s
Apr 27 15:50:04 mcp kernel: sages

root@mcp:~ # echo 'weird, huh?'
weird, huh?
root@mcp:~ # !tail
tail /var/log/messages
Apr 27 15:50:25 mcp kernel: ,
Apr 27 15:50:25 mcp kernel: h
Apr 27 15:50:26 mcp kernel: u
Apr 27 15:50:26 mcp kernel: h
Apr 27 15:50:26 mcp kernel: ?
Apr 27 15:50:27 mcp kernel: '
Apr 27 15:50:27 mcp kernel:
Apr 27 15:50:29 mcp kernel: !
Apr 27 15:50:30 mcp kernel: ta
Apr 27 15:50:30 mcp kernel: il
root@mcp:~ #