Date: Fri, 16 Aug 2019 12:00:37 -0700 (PDT) From: Sean Eric Fagan <sef@kithrup.com> To: freebsd-current@freebsd.org, jhb@FreeBSD.org Subject: Re: Can't boot current under bhyve on current Message-ID: <20190816190037.D88D41B84A@kithrup.com> In-Reply-To: <9933e6ab-63e9-c2ad-94eb-c8654d75ae99@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190816190037.D88D41B84A>