From owner-freebsd-virtualization@freebsd.org Mon Jun 18 05:39: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 6A5151018009 for ; Mon, 18 Jun 2018 05:39:26 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmail03.adl6.internode.on.net (ipmail03.adl6.internode.on.net [150.101.137.143]) by mx1.freebsd.org (Postfix) with ESMTP id 955CF6FA0E for ; Mon, 18 Jun 2018 05:39:25 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ppp118-210-71-37.bras2.adl4.internode.on.net (HELO leader.local) ([118.210.71.37]) by ipmail03.adl6.internode.on.net with ESMTP; 18 Jun 2018 15:09:15 +0930 Subject: Re: freebsd bhyve instance does not show kernel messages after boot screen To: tech-lists , freebsd-virtualization@freebsd.org References: <201806151402.w5FE26Xm050793@pdx.rh.CN85.dnsmgr.net> <714a9e4e-d57e-efc4-eb4b-2ca36def8489@zyxst.net> From: Shane Ambler Message-ID: <5e3c08ad-bf50-a70e-9d4f-0e465d00bfd5@ShaneWare.Biz> Date: Mon, 18 Jun 2018 15:09:13 +0930 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <714a9e4e-d57e-efc4-eb4b-2ca36def8489@zyxst.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-AU 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 05:39:26 -0000 On 17/06/2018 20:26, tech-lists wrote: > On 15/06/2018 15:02, Rodney W. Grimes wrote: >> With the VM shutdown look in /dev/vmm for the same name as the VM, >> if you see it there, make sure you do not have a running instnace >> of it, then do: >> bhyvectl --destroy --name=fbsd11-vm >> >> You may have remanants of a prior/crashed VM hanging around >> causing you issues. > > Unfortunately this made no difference either. > > If someone can tell me what to do to debug [1] this, I'll make a problem > report? > > [1] unfortunately debugging this particular thing is outside of my realm > of expertise. I know how to start/stop bhyve but not much else outside > of that. 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? Is the guest /etc/ttys types set to xterm, vt100 or something else? In the guest, does /var/log/dmesg.today contain the output you expect? 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. 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? -- FreeBSD - the place to B...Sharing Devices Shane Ambler