From owner-freebsd-current@freebsd.org Fri Jun 15 10:35:07 2018 Return-Path: Delivered-To: freebsd-current@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 DD4A91015A8F; Fri, 15 Jun 2018 10:35:06 +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 856A68610A; Fri, 15 Jun 2018 10:35:06 +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 A658D21C10; Fri, 15 Jun 2018 06:35:05 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Fri, 15 Jun 2018 06:35:05 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :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=MbNscTgV6l4FCQBA2jsMgQSw4YK3l DKLURZa8DHqq0A=; b=Dvk4KbRP+VSrkwSjplAA9ONnPRM3tQhKSyHPd2Zksxgnn EGVxsJzWaGeG6AVyFvTDB5V/kPSdeDR8Hr/0165dQDbCf36QvENwGpeJ/s1k4B+g IEhxicfPMzQ1AcpMC6oiRONhBe0rFMzmYgwCFSmev8cooaGYOjX7RDjuPWxC9Ewy R5/qXjtubO6PYhBDpNll3iz0fJa7LKMqnfFkYrnO+RAkBiavyYyRipswpgUsGn4t 3C8zTzD3Zrt2qR0UiWM+cTrl1JYIxp/bjTECazfx8Zi2vblLVNPXbN4+Ry5c0zjz +APqkSNTZW5st3ovwI7COXLjC4I9yUjVZzpuAYvJg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=MbNscT gV6l4FCQBA2jsMgQSw4YK3lDKLURZa8DHqq0A=; b=a81hzbalC6JedLAsbz54pB L+xeNQmN5+7vpC/qQdEHYEwFr3SKzA/3mwxwzwHeIWoIek3hN5h0V5SYMGTlPfJt O9hF6bzOjBgJAmmiQT6dOfSmDqqw01cc29HGbw6k4Wm3d8skZ6kUKtlKfwIWeix6 z+zg2dtkWGnGQQIPZQsPawforT/f1LNuYtp9k8wPEr6Z2YT+iQqULmEorAs1iZdm /zM71U3e6kymoALKiQsdpO2duF0G+1T+KDlPuyz+x7pB2isRayb6hQQYOP5ADI9o +1I6Yhzy7eCxPlmQ3ZInTMFWouJNowxyoxrCfsBl8SPyQdQVY2KziSunlfn+/n5g == 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 C3613E4329; Fri, 15 Jun 2018 06:35:04 -0400 (EDT) Subject: Re: freebsd bhyve instance does not show kernel messages after boot screen To: "David P. Discher" Cc: freebsd-virtualization@freebsd.org, freebsd-current@freebsd.org References: <8fefdd40-5136-3bcd-829e-40f7d20c05e1@zyxst.net> <18BAA9E7-0320-434B-AC7B-F7C09F313F95@dpdtech.com> From: tech-lists Organization: none Message-ID: Date: Fri, 15 Jun 2018 11:35:03 +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: <18BAA9E7-0320-434B-AC7B-F7C09F313F95@dpdtech.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2018 10:35:07 -0000 On 14/06/2018 23:26, David P. Discher wrote: > Try in /boot/loader.conf of the VM : > > console=userboot > > or after beastie drop to loader OK promot  and try : > > set console=userboot > > I think 11.x should fall back to userboot in bhyve if vidconsole of > comconsole were set. > > (This is assuming non-EFI booting - using bhyveloader ). Hi, Thanks for trying to help. I tried it both ways - in loader.conf and from the loader prompt but unfortunately it didn't work. For clarification, here's the exact way I start the VM: 1. $ screen -S fbsd11-vm 2. $ sudo su - 3. # (cd to where vm is) 4. sh /usr/share/examples/bhyve/vmrun.sh -c 4 -m 8192M -t tap3 -d fbsd-guest.img fbsd-guest If I transfer the VM to a freebsd-11 host (r333874) it also happens. So the behaviour is a property of the VM. Unless of course the issue is with bhyve itself on both -stable and -current. A possible clue (but I'm really out of my depth here) is ISTR something like this happening if say the VM is called say fbsd-guest and is then subsequently launched with some other name like fbsd11guest. Any ideas? thanks, -- J.