Date: Tue, 17 Sep 2019 08:47:03 +0300 From: Toomas Soome <tsoome@me.com> To: KIRIYAMA Kazuhiko <kiri@truefc.org> Cc: "freebsd-current@freebsd.org" <freebsd-current@FreeBSD.org> Subject: Re: r352368 can't boot Message-ID: <5E929415-319A-490D-AB9A-2F8259391B13@me.com> In-Reply-To: <201909170530.x8H5UGxo012419@kx.truefc.org> References: <201909170530.x8H5UGxo012419@kx.truefc.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 17 Sep 2019, at 08:30, KIRIYAMA Kazuhiko <kiri@truefc.org> wrote: >=20 > Hi,all >=20 > Yesterday I've updated latest head (r352368) and rebuild > 13.0-CURRENT. All went fine, but when I boot, it's stopped > at boot stage. Then I typed `boot', booted normally and put > login prompt and login go ahead. But `shutdown -r now', > stopped at loader prompt same as login case. What happened? > All I've done is whithin bhyve VM. >=20 >=20 > Consoles: userboot =20 >=20 > FreeBSD/amd64 User boot, Revision 1.1 > (Mon Jun 18 16:11:55 UTC 2018 root@releng3.nyi.freebsd.org) > Loading /boot/defaults/loader.conf > xemit not found > Error while including /boot/frames.4th, in the line: > h_el @ xemit >=20 > can't load 'kernel' >=20 > Type '?' for a list of commands, 'help' for more detailed help. > OK=20 >=20 This is unfortunate case where the guest image has more recent boot = scripts than hosts /boot/userboot.so has. I did push the fix for that = issue to stable/11 and stable/12. The patch does introduce xemit word. Such situation is unfortunate, but accident waiting to happen with this = method where we are attempting to use bootloader (userboot.so) from = older system to load guest vm.=20 rgds, toomas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5E929415-319A-490D-AB9A-2F8259391B13>