From nobody Sun Sep 8 01:01:02 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4X1Wqk4nbkz5VFxd for ; Sun, 08 Sep 2024 01:01:06 +0000 (UTC) (envelope-from void@f-m.fm) Received: from fhigh4-smtp.messagingengine.com (fhigh4-smtp.messagingengine.com [103.168.172.155]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4X1Wqk05wxz4WvB for ; Sun, 8 Sep 2024 01:01:05 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm1 header.b=VUpMeqJo; dkim=pass header.d=messagingengine.com header.s=fm1 header.b="PRlU/ftr"; dmarc=pass (policy=none) header.from=f-m.fm; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 103.168.172.155 as permitted sender) smtp.mailfrom=void@f-m.fm Received: from phl-compute-07.internal (phl-compute-07.phl.internal [10.202.2.47]) by mailfhigh.phl.internal (Postfix) with ESMTP id 9DE08114018B for ; Sat, 7 Sep 2024 21:01:04 -0400 (EDT) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-07.internal (MEProxy); Sat, 07 Sep 2024 21:01:04 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm1; t=1725757264; x=1725843664; bh=QXL1XjSYAi DuhtRy+Oj792v7Bv999oWdCw1PlJNcDgw=; b=VUpMeqJoSaQ9TGXKpg3tVkNARm 4OB5zeL5xHZCaXfLoQnDJ0gIVxRYUoGiSvaKa81zlZYJ8xLzWtkdULANL9Ebeq4G Q6s3imbD2HP/ZyaiAGvuqVJ3zRxQsA6jPj5yR2YzapSw/25iKZZNkpYc9VOA1JWw 3llIDK7yLOBXLFtFZIOujFZtrc66KurbB0HNy19mVli/ErccnDr0TxmmrQxB7mL9 nf1wU8azVw3dsg0a8V/W8HQ6NwK/7Lxmxq+jtyKMUkbRWmrcuXN4n9z2e7RQ+8f3 /ElIzejWXesy8+U60NRPfo1O/q8Tv8Gb8clL1zDPHsopBBUVGRD29fazkuiA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1725757264; x=1725843664; bh=QXL1XjSYAiDuhtRy+Oj792v7Bv99 9oWdCw1PlJNcDgw=; b=PRlU/ftrLcfVp6qsflIz9M7zTZbyxb6xOr3FFo/jg4e1 Ny3OzmSOQ7bbBL491UodByAllj/hmZy7DpzfqDuogmH88WBMVLtRcYOGqE+dn0wX VUSxvEjhzi9j/QMcNaTf9cYVwfKsTzRB/831QyhQ+CyhlDDptLcgcUXveHtovu14 OXaBZHZtsAyhXsmE0/koqCPojpDyD4tH6ESV2uL9MQIeE9H1jrnMaNitsOQguwi2 I8OZ5vDRECHcXoAMQls44qQ6T1y4qwUdBhmXVbU4vUgvXlyDsK5M1Y27DU3iHznJ dxlXwXafFoCdfnZfDsJ5/jud3+FXWSFIQ1zeUc2UHA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrudeigedggedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuf fkfhggtggujgesthdtredttddtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhm rdhfmheqnecuggftrfgrthhtvghrnhepkeeluddvlefhieelfefggffhffektdehleelgf dugfdvgeekjeejuddtheehgfeunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghm pehmrghilhhfrhhomhepvhhoihgusehfqdhmrdhfmhdpnhgspghrtghpthhtohepuddpmh houggvpehsmhhtphhouhhtpdhrtghpthhtohepfhhrvggvsghsugdqtghurhhrvghnthes fhhrvggvsghsugdrohhrgh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Sat, 7 Sep 2024 21:01:04 -0400 (EDT) Date: Sun, 8 Sep 2024 02:01:02 +0100 From: void To: freebsd-current@freebsd.org Subject: Re: Loader needs to be updated message Message-ID: Mail-Followup-To: freebsd-current@freebsd.org References: <9494862A-E445-43AC-8887-FACC84A74435.ref@yahoo.com> <9494862A-E445-43AC-8887-FACC84A74435@yahoo.com> <20240908092302.caa9f655693f71e03ee6b030@dec.sakura.ne.jp> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20240908092302.caa9f655693f71e03ee6b030@dec.sakura.ne.jp> X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.59 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.79)[-0.792]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; MID_RHS_NOT_FQDN(0.50)[]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm1,messagingengine.com:s=fm1]; RWL_MAILSPIKE_VERYGOOD(-0.20)[103.168.172.155:from]; R_SPF_ALLOW(-0.20)[+ip4:103.168.172.128/27]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[103.168.172.155:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FREEMAIL_FROM(0.00)[f-m.fm]; RCVD_COUNT_THREE(0.00)[3]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; ASN(0.00)[asn:209242, ipnet:103.168.172.0/24, country:US]; RCVD_VIA_SMTP_AUTH(0.00)[]; MISSING_XM_UA(0.00)[]; DWL_DNSWL_NONE(0.00)[messagingengine.com:dkim] X-Rspamd-Queue-Id: 4X1Wqk05wxz4WvB On Sun, Sep 08, 2024 at 09:23:02AM +0900, Tomoaki AOKI wrote: >Can it be in reverse? > >I've not read (even if it's already provided somewhere or attached) the >vmrun.sh script, but isn't there any possibility that it somehow >uses loader on bare-metal (regardless on /boot/ or on ESP) to kick the >guests? >If so, version mismatch happenes, but newer kicks older. >But yes, usually it is not at all the problem, as newer loader codes in >same interpreter (lua/4th) is keeping backward compatibilities, I guess. > >Another case is that void already stated that > >>>In such a case, you might need something like: >>> >>># cp -a /boot/loader.efi /boot/efi/efi/BOOT/bootx64.efi >> >>and the error is gone!!! TYVM > >in another mail in this thread [1]. I should have made it clearer, in that other case, i did # cp -a /boot/loader.efi /boot/efi/efi/BOOT/bootaa64.efi as it was an arm64 context >This could mean that efi/freebsd/loader.efi in ESP is not called by >the UEFI firmware and efi/BOOT/efi/bootx64.efi is used instead. In *this* amd64 case, neither the -current server running bhyve nor the 13.4-stable guest have bootx64.efi present. /boot/efi is empty on both the server and the guest. --