From owner-freebsd-current@freebsd.org Fri Aug 16 19:00:45 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 DB09DABD21 for ; Fri, 16 Aug 2019 19:00:45 +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 469CMJ5SQFz4dRQ; Fri, 16 Aug 2019 19:00:44 +0000 (UTC) (envelope-from sef@kithrup.com) Received: by kithrup.com (Postfix, from userid 1001) id D88D41B84A; Fri, 16 Aug 2019 12:00:37 -0700 (PDT) To: freebsd-current@freebsd.org, jhb@FreeBSD.org Subject: Re: Can't boot current under bhyve on current In-Reply-To: <9933e6ab-63e9-c2ad-94eb-c8654d75ae99@FreeBSD.org> Message-Id: <20190816190037.D88D41B84A@kithrup.com> Date: Fri, 16 Aug 2019 12:00:37 -0700 (PDT) From: Sean Eric Fagan X-Rspamd-Queue-Id: 469CMJ5SQFz4dRQ 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 [-5.29 / 15.00]; ARC_NA(0.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.01)[ip: (-7.21), ipnet: 96.64.0.0/11(-3.61), asn: 7922(0.83), country: US(-0.05)]; NEURAL_HAM_SHORT(-0.98)[-0.983,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 19:00:45 -0000 >I think vm-bhyve hides stderr output from bhyve by default, but there might >be a flag to make it display the stderr output. Can you try doing that to see >if bhyve is reporting an error? Alternatively, can you see if the bhyve >process is still running? The log file from it is below. bhyve was still running, looping on vm ioctls, until I killed it. starting bhyve (run 1) bhyve exited with status 1 destroying network device tap1 stopped initialising [loader: bhyveload] [cpu: 1] [memory: 512M] [hostbridge: standard] [com ports: com1] [uuid: ad7532de-bec1-11e9-8a55-d05099c38c95] [utctime: yes] [debug mode: no] [primary disk: disk0.img] [primary disk dev: file] initialising network device tap0 failed to find virtual switch 'public' booting bhyveload -m 512M -e autoboot_delay=3 -d /VMs/VM-TEST/../.iso/FreeBSD-13.0-CURRENT-amd64-20190725-r350322-disc1.iso VM-TEST [bhyve options: -c 1 -m 512M -AHP -U ad7532de-bec1-11e9-8a55-d05099c38c95 -u] [bhyve devices: -s 0,hostbridge -s 31,lpc -s 4:0,virtio-blk,/VMs/VM-TEST/disk0.img -s 5:0,virtio-net,tap0,mac=58:9c:fc:04:34:69] [bhyve console: -l com1,stdio] [bhyve iso device: -s 3:0,ahci-cd,/VMs/VM-TEST/../.iso/FreeBSD-13.0-CURRENT-amd64-20190725-r350322-disc1.iso,ro] starting bhyve (run 1) bhyve exited with status 1 destroying network device tap0 stopped Alan was trying to help me debug this yesterday, and I manually ran bhyve, but had no errors, and it still didn't work. Thanks, Sean.