From owner-freebsd-virtualization@freebsd.org Mon Jun 18 15:04:26 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3F719100D1C0 for ; Mon, 18 Jun 2018 15:04:26 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D66EC83553 for ; Mon, 18 Jun 2018 15:04:25 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 7EF7E21FE0 for ; Mon, 18 Jun 2018 11:04:25 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Mon, 18 Jun 2018 11:04:25 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=0mAS3O9kor35yAvpt/LnZ8dLqpKeP xgTF3y7EuBPZyQ=; b=mRrZUGrTDxSbNQQ+m9mO9rqra4tPIKg2VtyZsgoS9OS6G YS0MrHOaFGybLodSiOh/nEbUEp69NtCdAUDUA0KU1DiwRvSJP9rWGXDhU8zR42Be nbd/GMFilUS2cNO9I6YUK52w8ZLo8wCGyy/+GBikC4LeLX9RTGpWhKfDRbo5IAJP 5THEdDoey85mgX1/qkvBBpejEb4Ece0d1xS6JzI19/0CDi82GTIc4mybp3cJtGGl lcZ+cTK/I1SDQoQiVAvNQEUIOi8zLDV/0LTbIyzVTsZeBMkbW9uaXxQP3PpfZWkp 8zyWFNSHQ4d1XiDont2wDiu8mG2v1Ku/4QAG/F37A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=0mAS3O 9kor35yAvpt/LnZ8dLqpKePxgTF3y7EuBPZyQ=; b=Rez0r0JCI1PVJt0fG5x0Kz OJz0VYTwFxwdac0s6oQUkmhgHwdfo2T1PZqbkfGhjzKEeaKSw63Jumm9qqI0ouwC +mTKTAafPquB5ZCq5ND9VAAVqwlLzGG/kP9S5+ae4QavZwL1W4mi5yhv1ibT2YvB r5uVYZIOj3IKP0KtzODE0tM0ASHtSuPmoHE3O1sM26mPuqOsf7jq21th7f8KESph xVZ6y+qQd4UEp0a/dxhIupyPUDRuBPQg82n+XqqhzdXzQiCisaAoqMBOKQ0CDnlM iHf4YdUfKeghpkQw7OrQMhSKDV+3gBdHeM4Re+YQ0XQcNx/cKflwXEtlBJjw91gg == X-ME-Proxy: X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id BF3C4E4076 for ; Mon, 18 Jun 2018 11:04:24 -0400 (EDT) Subject: Re: freebsd bhyve instance does not show kernel messages after boot screen References: <201806151402.w5FE26Xm050793@pdx.rh.CN85.dnsmgr.net> <714a9e4e-d57e-efc4-eb4b-2ca36def8489@zyxst.net> <5e3c08ad-bf50-a70e-9d4f-0e465d00bfd5@ShaneWare.Biz> To: freebsd-virtualization@freebsd.org From: tech-lists Organization: none Message-ID: Date: Mon, 18 Jun 2018 16:04:23 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <5e3c08ad-bf50-a70e-9d4f-0e465d00bfd5@ShaneWare.Biz> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.26 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: Mon, 18 Jun 2018 15:04:26 -0000 On 18/06/2018 06:39, Shane Ambler wrote: > Find out if it's the guest not outputting or the console not receiving. > > On the host run script before starting the bhyve and connecting to its > console, does this record any extra output? unfortunately not > > Is the guest /etc/ttys types set to xterm, vt100 or something else? here's the file contents for the problematic VM console none unknown off secure # ttyv0 "/usr/libexec/getty Pc" xterm onifexists secure # Virtual terminals ttyv1 "/usr/libexec/getty Pc" xterm onifexists secure ttyv2 "/usr/libexec/getty Pc" xterm onifexists secure ttyv3 "/usr/libexec/getty Pc" xterm onifexists secure ttyv4 "/usr/libexec/getty Pc" xterm onifexists secure ttyv5 "/usr/libexec/getty Pc" xterm onifexists secure ttyv6 "/usr/libexec/getty Pc" xterm onifexists secure ttyv7 "/usr/libexec/getty Pc" xterm onifexists secure ttyv8 "/usr/local/bin/xdm -nodaemon" xterm off secure # Serial terminals # The 'dialup' keyword identifies dialin lines to login, fingerd etc. ttyu0 "/usr/libexec/getty 3wire" vt100 onifconsole secure ttyu1 "/usr/libexec/getty 3wire" vt100 onifconsole secure ttyu2 "/usr/libexec/getty 3wire" vt100 onifconsole secure ttyu3 "/usr/libexec/getty 3wire" vt100 onifconsole secure # Dumb console dcons "/usr/libexec/getty std.9600" vt100 off secure ################################################################# Compared to one where the login prompt appears: console none unknown off secure # ttyv0 "/usr/libexec/getty Pc" xterm on secure # Virtual terminals ttyv1 "/usr/libexec/getty Pc" xterm on secure ttyv2 "/usr/libexec/getty Pc" xterm on secure ttyv3 "/usr/libexec/getty Pc" xterm on secure ttyv4 "/usr/libexec/getty Pc" xterm on secure ttyv5 "/usr/libexec/getty Pc" xterm on secure ttyv6 "/usr/libexec/getty Pc" xterm on secure ttyv7 "/usr/libexec/getty Pc" xterm on secure ttyv8 "/usr/local/bin/xdm -nodaemon" xterm off secure # Serial terminals # The 'dialup' keyword identifies dialin lines to login, fingerd etc. ttyu0 "/usr/libexec/getty 3wire" vt100 onifconsole secure ttyu1 "/usr/libexec/getty 3wire" vt100 onifconsole secure ttyu2 "/usr/libexec/getty 3wire" vt100 onifconsole secure ttyu3 "/usr/libexec/getty 3wire" vt100 onifconsole secure # Dumb console dcons "/usr/libexec/getty std.9600" vt100 off secure So I changed onifconsole to on and rebooted, but this had no effect. > In the guest, does /var/log/dmesg.today contain the output you expect? yes > In /etc/syslog.conf there is a commented line for console.info that > saves all console output to a log file, this will be messages after the > kernel has loaded but includes a lot of what you expect during startup. On the host or the guest? I take it you mean the guest. I did this, shut the vm down with poweroff (from the vm as root) and started it again, logged into the guest and the console.log file is blank (and syslogd is running) so I think you might be onto something here. > Maybe one of these logs shows an odd char that the console has an issue > with. Can you find an odd char that doesn't exist in other guest logs? not yet. But there are other guests with console.log enabled and they get written to as you would expect. thanks, -- J.