Date: Sun, 25 Dec 2022 16:55:30 -0700 From: Warner Losh <imp@bsdimp.com> To: Mark Millard <marklmi@yahoo.com> Cc: freebsd-current <freebsd-current@freebsd.org>, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: snapshot 1st aarcch64 boot got devd error message: "sh: /usr/libexec/hyperv/hyperv_vfattach: not found" Message-ID: <CANCZdfp4hpFypTEP-90nF%2BcUWNr=HFLEJ6JZ7OneQKaXmtGE5A@mail.gmail.com> In-Reply-To: <F78DFB62-5BE2-426E-9578-2367D4C508BF@yahoo.com> References: <F78DFB62-5BE2-426E-9578-2367D4C508BF.ref@yahoo.com> <F78DFB62-5BE2-426E-9578-2367D4C508BF@yahoo.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --]
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 <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 {
> 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
>
>
>
[-- Attachment #2 --]
<div dir="auto">Most likely MK_HYPERV is defaulting to no for aarch64? Or there is a bogus if MACHINE_ARCH == "amd64" somewhere.<div dir="auto"><br></div><div dir="auto">Warner</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Dec 25, 2022, 4:28 PM Mark Millard <<a href="mailto:marklmi@yahoo.com">marklmi@yahoo.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">From the Dec 24 main [so: 14] snaphot for an aarch64 RPi*<br>
system:<br>
<br>
. . .<br>
Starting devd.<br>
genet0: link state changed to UP<br>
sh: /usr/libexec/hyperv/hyperv_vfattach: not found<br>
Starting dhclient.<br>
. . .<br>
<br>
This seems to be from /etc/devd/hyperv.conf :<br>
<br>
notify 10 {<br>
match "system" "ETHERNET";<br>
match "type" "IFATTACH";<br>
action "/usr/libexec/hyperv/hyperv_vfattach $subsystem 0";<br>
};<br>
<br>
For reference:<br>
<br>
# ls -Tla /usr/libexec/hyperv/<br>
total 8<br>
drwxr-xr-x 2 root wheel 512 Dec 24 06:30:06 2022 .<br>
drwxr-xr-x 10 root wheel 1536 Dec 24 06:49:40 2022 ..<br>
<br>
I do not know if the error might have lead to skipping some<br>
other activities or not.<br>
<br>
Note:<br>
<br>
This is from a test where I'd 1st side stepped a syntax problem<br>
in /etc/rc.d/growfs in the snapshot to try to see if the growfs<br>
otherwise worked.<br>
<br>
# uname -apKU # long output line split for reability<br>
FreeBSD generic 14.0-CURRENT FreeBSD 14.0-CURRENT #0<br>
main-n259842-c89209c674f2: Sat Dec 24 05:52:28 UTC 2022<br>
root@releng1.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC<br>
arm64 aarch64 1400076 1400076<br>
<br>
===<br>
Mark Millard<br>
marklmi at <a href="http://yahoo.com" rel="noreferrer noreferrer" target="_blank">yahoo.com</a><br>
<br>
<br>
</blockquote></div>
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfp4hpFypTEP-90nF%2BcUWNr=HFLEJ6JZ7OneQKaXmtGE5A>