From nobody Sun Dec 25 23:55:30 2022 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 4NgHqP5sn4z1Lknk for ; Sun, 25 Dec 2022 23:55:45 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4NgHqP11Dzz4PwJ for ; Sun, 25 Dec 2022 23:55:45 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x531.google.com with SMTP id u28so9085792edd.10 for ; Sun, 25 Dec 2022 15:55:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ddq7biMjkEHbjOp/GIOt3/6DEeCXpL+Kl8dJdU9OZ2w=; b=gFnVHtY6EQRvgQNSmGCzsV/zZKsi9U2kBulTG7V7Y82bB2Vzzv/RjNT6xbM/I5CjpD Wya5+jXaSdjmyHpSlV/erT70UmfiQN0dYNhcPzTPV9I5PsWAIGOh2RobrlqPSW70/+ti G1tecD7K2icqIUW7MeZHxV7TNza2OS/c6IQ4lpYSo7g4ROKeBsjHhO6tTttP+rFDPysm /yZ+TGuRZHtbMaLCIATq/oC7FILmMLCdPG+8+bWURYf7/BwPNbIJxDwgrx3Q60qCTIiW fCv6ZD0AWOREwF4KcRxOrrKZsoOmrXFD38+8g/p6LmijrCpazeJuVJAFmPLmjmFZbARV IsQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ddq7biMjkEHbjOp/GIOt3/6DEeCXpL+Kl8dJdU9OZ2w=; b=DMljlWUhljkjWsrHB5hzhbtc7xy3LyQCV1GJHZ3vUcyxb7X2U/39U7fPnNDIKom4Mj A61Yfl1+US3BNARw1k6+IrPTkRCVkksKKhuMZS3c/IQHy6XjEcxt1mrVzpzHVHCV29J/ 9xn1nVvykCM/57iaWMViJZ+aoJ810nw7Eu+OGuP/hDjePPdZo2jyOckAVZMgABqt/tCa PV67rmW1AkZ7BKt8TMceYq2szcg69JJcg8oFqC0Ih/X/YBNBUEHKYLirbfTPSMe9Mmne rJwFEyiRGhz2bgXgvxSH9lcvc5CwS+igPLA+HgTWzfL32tLkHEKnKZXiq/PNQoBGIbM2 Cxzg== X-Gm-Message-State: AFqh2kqKWoZlf09p6TujkEkKOd526AmOrhrZKWTVxOgtSpqJhuEsj3wA daXPczuVeXDSNyUjNuBNSPgsMjFmKtpERx77AmzbPxe81/ca2A== X-Google-Smtp-Source: AMrXdXv2QLNj++QRh+gYtQhGNy1sMjIFJB+7IZyROcf7mEU2qB+dwiNBvRZbKcUJ1PRjDLzARsFhYW+DYj8tWlLT0w0= X-Received: by 2002:a05:6402:3205:b0:469:f59f:352e with SMTP id g5-20020a056402320500b00469f59f352emr1321136eda.241.1672012541474; Sun, 25 Dec 2022 15:55:41 -0800 (PST) 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 References: In-Reply-To: From: Warner Losh Date: Sun, 25 Dec 2022 16:55:30 -0700 Message-ID: Subject: Re: snapshot 1st aarcch64 boot got devd error message: "sh: /usr/libexec/hyperv/hyperv_vfattach: not found" To: Mark Millard Cc: freebsd-current , freebsd-arm Content-Type: multipart/alternative; boundary="000000000000984fc105f0afc157" X-Rspamd-Queue-Id: 4NgHqP11Dzz4PwJ X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000984fc105f0afc157 Content-Type: text/plain; charset="UTF-8" Most likely MK_HYPERV is defaulting to no for aarch64? Or there is a bogus if MACHINE_ARCH == "amd64" somewhere. Warner On Sun, Dec 25, 2022, 4:28 PM Mark Millard wrote: > From the Dec 24 main [so: 14] snaphot for an aarch64 RPi* > system: > > . . . > Starting devd. > genet0: link state changed to UP > sh: /usr/libexec/hyperv/hyperv_vfattach: not found > Starting dhclient. > . . . > > This seems to be from /etc/devd/hyperv.conf : > > notify 10 { > match "system" "ETHERNET"; > match "type" "IFATTACH"; > action "/usr/libexec/hyperv/hyperv_vfattach $subsystem 0"; > }; > > For reference: > > # ls -Tla /usr/libexec/hyperv/ > total 8 > drwxr-xr-x 2 root wheel 512 Dec 24 06:30:06 2022 . > drwxr-xr-x 10 root wheel 1536 Dec 24 06:49:40 2022 .. > > I do not know if the error might have lead to skipping some > other activities or not. > > Note: > > This is from a test where I'd 1st side stepped a syntax problem > in /etc/rc.d/growfs in the snapshot to try to see if the growfs > otherwise worked. > > # uname -apKU # long output line split for reability > FreeBSD generic 14.0-CURRENT FreeBSD 14.0-CURRENT #0 > main-n259842-c89209c674f2: Sat Dec 24 05:52:28 UTC 2022 > root@releng1.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC > arm64 aarch64 1400076 1400076 > > === > Mark Millard > marklmi at yahoo.com > > > --000000000000984fc105f0afc157 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Most likely MK_HYPERV is defaulting to no for aarch64? Or= there is a bogus if MACHINE_ARCH =3D=3D "amd64" somewhere.

Warner

On Sun, Dec 25, 2022, 4= :28 PM Mark Millard <marklmi@yahoo.= com> wrote:
From the Dec 24 = main [so: 14] snaphot for an aarch64 RPi*
system:

. . .
Starting devd.
genet0: link state changed to UP
sh: /usr/libexec/hyperv/hyperv_vfattach: not found
Starting dhclient.
. . .

This seems to be from /etc/devd/hyperv.conf :

notify 10 {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 match "system"=C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 "ETHERNET";
=C2=A0 =C2=A0 =C2=A0 =C2=A0 match "type"=C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 "IFATTACH";
=C2=A0 =C2=A0 =C2=A0 =C2=A0 action "/usr/libexec/hyperv/hyperv_vfattac= h $subsystem 0";
};

For reference:

# ls -Tla /usr/libexec/hyperv/
total 8
drwxr-xr-x=C2=A0 =C2=A02 root=C2=A0 wheel=C2=A0 =C2=A0512 Dec 24 06:30:06 2= 022 .
drwxr-xr-x=C2=A0 10 root=C2=A0 wheel=C2=A0 1536 Dec 24 06:49:40 2022 ..

I do not know if the error might have lead to skipping some
other activities or not.

Note:

This is from a test where I'd 1st side stepped a syntax problem
in /etc/rc.d/growfs in the snapshot to try to see if the growfs
otherwise worked.

# uname -apKU=C2=A0 # long output line split for reability
FreeBSD generic 14.0-CURRENT FreeBSD 14.0-CURRENT #0
main-n259842-c89209c674f2: Sat Dec 24 05:52:28 UTC 2022
root@releng1.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC
arm64 aarch64 1400076 1400076

=3D=3D=3D
Mark Millard
marklmi at yahoo.com


--000000000000984fc105f0afc157--