From owner-freebsd-current@freebsd.org Wed Sep 18 06:37:48 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 EC2BAF32CD for ; Wed, 18 Sep 2019 06:37:48 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv50p00im-zteg10011401.me.com (pv50p00im-zteg10011401.me.com [17.58.6.41]) (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 46Y9Jr0lQKz3Pm5 for ; Wed, 18 Sep 2019 06:37:47 +0000 (UTC) (envelope-from tsoome@me.com) Received: from nazgul.lan (148-52-235-80.sta.estpak.ee [80.235.52.148]) by pv50p00im-zteg10011401.me.com (Postfix) with ESMTPSA id 3066D900D01; Wed, 18 Sep 2019 06:37:43 +0000 (UTC) From: Toomas Soome Message-Id: Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: r352368 can't boot Date: Wed, 18 Sep 2019 09:37:39 +0300 In-Reply-To: Cc: KIRIYAMA Kazuhiko , FreeBSD Current To: Warner Losh References: <201909170530.x8H5UGxo012419@kx.truefc.org> <5E929415-319A-490D-AB9A-2F8259391B13@me.com> <8A9627B9-8190-490C-8D76-6F2A9D00E059@me.com> X-Mailer: Apple Mail (2.3445.104.11) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-09-18_04:, , signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1909180070 X-Rspamd-Queue-Id: 46Y9Jr0lQKz3Pm5 X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.20 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:17.58.0.0/16]; FREEMAIL_FROM(0.00)[me.com]; MV_CASE(0.50)[]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; URI_COUNT_ODD(1.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[me.com:+]; RCVD_IN_DNSWL_MED(-0.20)[41.6.58.17.list.dnswl.org : 127.0.5.2]; DMARC_POLICY_ALLOW(-0.50)[me.com,quarantine]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (-6.07), ipnet: 17.58.0.0/20(-3.36), asn: 714(-2.91), country: US(-0.05)]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[me.com]; ASN(0.00)[asn:714, ipnet:17.58.0.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[me.com:s=1a1hai]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE_FREEMAIL(0.00)[]; DWL_DNSWL_LOW(-1.00)[me.com.dwl.dnswl.org : 127.0.5.1]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: Wed, 18 Sep 2019 06:37:49 -0000 > On 17 Sep 2019, at 14:21, Warner Losh wrote: >=20 >=20 >=20 > On Tue, Sep 17, 2019, 11:24 AM Toomas Soome > wrote: >=20 >=20 >> On 17 Sep 2019, at 13:09, Warner Losh > wrote: >>=20 >>=20 >>=20 >> On Tue, Sep 17, 2019, 6:47 AM Toomas Soome > wrote: >>=20 >>=20 >> > On 17 Sep 2019, at 08:30, KIRIYAMA Kazuhiko > 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 >>=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 >>=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. >>=20 >> 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 >>=20 >> Can we provide a fallback to xemit builtin for old systems without = it? I believe we did this for other things as a transition. Forth has a = way to do this, though we need to make sure we properly constrain what = we pass to emit... >>=20 >> Warner >>=20 >> P.s. I'm at legoland this week, so I can't look at it for a bit. >>=20 >=20 > Well, the only way to avoid such issue is to make sure the guest = environment is providing all the needed bits, but since we do have = interpreter inside the userboot.so and userboot.so is in host, this does = set rather unfortunate limits what we can do. >=20 > Yes. I understand that we are limited in our scripts to somehow = testing if xemit is a forth word and if not providing a fallback = implementation of it in forth using emit. >=20 >=20 done:) rgds, toomas