From owner-freebsd-current@freebsd.org Fri Aug 16 22:16:59 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A9C4DB130A for ; Fri, 16 Aug 2019 22:16:59 +0000 (UTC) (envelope-from sef@kithrup.com) Received: from kithrup.com (kithrup.com [96.79.110.97]) by mx1.freebsd.org (Postfix) with ESMTP id 469Hjk65DWz4rBH; Fri, 16 Aug 2019 22:16:58 +0000 (UTC) (envelope-from sef@kithrup.com) Received: by kithrup.com (Postfix, from userid 1001) id 5B4B61B8A4; Fri, 16 Aug 2019 15:16:57 -0700 (PDT) To: freebsd-current@freebsd.org, jhb@FreeBSD.org Subject: Re: Can't boot current under bhyve on current Message-Id: <20190816221657.5B4B61B8A4@kithrup.com> Date: Fri, 16 Aug 2019 15:16:57 -0700 (PDT) From: Sean Eric Fagan X-Rspamd-Queue-Id: 469Hjk65DWz4rBH X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of sef@kithrup.com designates 96.79.110.97 as permitted sender) smtp.mailfrom=sef@kithrup.com X-Spamd-Result: default: False [-4.32 / 15.00]; ARC_NA(0.00)[]; FAKE_REPLY(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+a]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[kithrup.com]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE(-2.04)[ip: (-7.38), ipnet: 96.64.0.0/11(-3.62), asn: 7922(0.85), country: US(-0.05)]; NEURAL_HAM_SHORT(-0.98)[-0.981,0]; RCPT_COUNT_TWO(0.00)[2]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7922, ipnet:96.64.0.0/11, country:US]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 16 Aug 2019 22:16:59 -0000 Ok, if I run the bhyve commands manually, then I get a serial console. So something is just borked with vm-bhyve and its use of tmux. Whew. (Now I don't know *what*, but that's at least progress in my diagnosis!)