From nobody Wed Jan 25 00:40:58 2023 X-Original-To: freebsd-questions@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 4P1lPm3H3Qz3b38Y; Wed, 25 Jan 2023 00:41:00 +0000 (UTC) (envelope-from dalescott@shaw.ca) Received: from omta002.cacentral1.a.cloudfilter.net (omta002.cacentral1.a.cloudfilter.net [3.97.99.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P1lPl5t1cz3nN7; Wed, 25 Jan 2023 00:40:59 +0000 (UTC) (envelope-from dalescott@shaw.ca) Authentication-Results: mx1.freebsd.org; none Received: from shw-obgw-4002a.ext.cloudfilter.net ([10.228.9.250]) by cmsmtp with ESMTP id KSDZpUo0Dl2xSKTqUpoSik; Wed, 25 Jan 2023 00:40:58 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=shaw.ca; s=s20180605; t=1674607258; bh=BVYmVinvetsXL9CZ9IzckfeHz2v68tszX0DIX6p98z0=; h=Date:From:To:Cc:In-Reply-To:References:Subject; b=PSPFtrKD8mN+l28JVkadl9+aG/PQPPLHqDLoFWlrObeVXxEQYf5HSDci3WtbYVqSE WUj+0JC9DL45weTlf8jzJk/MFq80MF3lfjB1atvg2w5l17UxT6G+tHmFjBDyHdFPfE q1ttuPxCKDKkARf4gcYQ7zhRK5REHu9ZC3Vhx8fHSoBtMUoNFiaSSqv+2hXGEXzuZS ukhbFWO8+sF/XPpoCGUSIxajIY4ISUx0EuGkbcUj5kP7ckQlBFhEM7KOtAgSRPB+cB zd2iIEepBKuxJYwU1fao9yG0pGgdVid3uv9s4OBEPuILN2Pqs2wCaDMbvjuhJ+VbDs GMbsORZ2wgyqw== Received: from cds220.dcs.int.inet ([64.59.134.6]) by cmsmtp with ESMTP id KTqUpLOwiyAOeKTqUpltcT; Wed, 25 Jan 2023 00:40:58 +0000 X-Authority-Analysis: v=2.4 cv=e5oV9Il/ c=1 sm=1 tr=0 ts=63d07a9a a=9zdlX7M534QhL7mOrorEvQ==:117 a=FKkrIqjQGGEA:10 a=on0NmgUIp3IA:10 a=6I5d2MoRAAAA:8 a=B-BqFc1x7dFnpsHNKbYA:9 a=QEXdDO2ut3YA:10 a=F3CWQ4dY27ArpVMo:21 a=_W_S_7VecoQA:10 a=IjZwj45LgO3ly-622nXo:22 Date: Tue, 24 Jan 2023 17:40:58 -0700 (MST) From: Dale Scott To: Graham Perrin Cc: FreeBSD questions , VirtualBox on FreeBSD team , Virtualisation on FreeBSD Message-ID: <271536304.16750316.1674607258015.JavaMail.zimbra@shaw.ca> In-Reply-To: <7fe27024-d794-d808-c2f4-371c533eb2e4@freebsd.org> References: <3d8f8238-020b-0706-1c48-b17db12891f1@freebsd.org> <7fe27024-d794-d808-c2f4-371c533eb2e4@freebsd.org> Subject: Re: 13.1-STABLE vritualbox-ose-kmod panic List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_ac82ec49-8f38-4172-94e3-fc491780ec5d" X-Originating-IP: [162.223.103.50, 162.223.103.50] X-Mailer: Zimbra 8.8.15_GA_4464 (ZimbraWebClient - GC109 (Win)/8.8.15_GA_4468) Thread-Topic: 13.1-STABLE vritualbox-ose-kmod panic Thread-Index: ZYI104Z1Z92ZYeD5j9rrp679zP1Dcw== X-CMAE-Envelope: MS4xfN+sb3HC+MF4G56DBxeLRvkZGebSstBpx7ZDWwWN9l8vAYzAvhekiJkAiALpE+etuSi5O3OfDZQ+eSzJZGVQTZFs8tYlRb5zAxqd9/2HQHbRKNsuSUkQ TbphiTge7zymAB1OcvJsrRpvsIPqJfV0fh+5caTEn29LUHVcWhOMl6WVOww6nbxoMsl6316iEttQGt/h4Obc49iT9t3r786mr3RvWSfs9P9T2En9UcYGZQDB 3LSBi8LtEZRgi3ISzx6bBucXqoVtLyLB2GqlcX7Y3UWcauEqSBslKUAMXs7E91DlA4v8uzfXSlKgjA71uwAf8A== X-Rspamd-Queue-Id: 4P1lPl5t1cz3nN7 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16509, ipnet:3.96.0.0/15, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --=_ac82ec49-8f38-4172-94e3-fc491780ec5d Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable There is a period of time in the release engineering cycle when the version= of virtualbox-ose-kmod in pkg works, but most of the time it will need to = be compiled from the port.=20 If you look at dmesg if you are rebooting to load the the kmod, you should = see an error message that the kmod could be loaded due to a version incompa= tibitliy. You'll get the same error if you attempt to load the kmod manuall= y.=20 There is at least one relatively recent thread on this in the mailing list = with more explanation, but personally I have found it simplest to just alwa= ys build the kmod from ports when updating.=20 > From: "Graham Perrin" > To: "FreeBSD questions" > Cc: "VirtualBox on FreeBSD team" , "Virtualisation on F= reeBSD" > > Sent: Tuesday, January 24, 2023 4:13:54 PM > Subject: Re: 13.1-STABLE vritualbox-ose-kmod panic > On 24/01/2023 23:07, Graham Perrin wrote: >> On 24/01/2023 22:06, Tomek CEDRO wrote: >>> =E2=80=A6 The first time I noticed that problem was beginning of Januar= y 2023. Before I >>> was able to use virtualbox-ose(-kmod) on STABLE with no problem. >>> How can I make things work again? >>> Will virtualbox-ose-kmod work only with a RELEASE and not with STABLE? > It works here with CURRENT. >>> Do I need to rebuild both virtualbox-ose and virtualbox-ose-kmod from p= orts? =E2=80=A6 > Tomek, please check that your copy of the ports tree is up-to-date. > If you build from source, build (and install) the kernel module alone. --=_ac82ec49-8f38-4172-94e3-fc491780ec5d Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
There is a period of time in the release en= gineering cycle when the version of virtualbox-ose-kmod in pkg works, but m= ost of the time it will need to be compiled from the port.

If you look at dmesg if you are rebooting to = load the the kmod, you should see an error message that the kmod could be l= oaded due to a version incompatibitliy. You'll get the same error if you at= tempt to load the kmod manually.

<= div>There is at least one relatively recent thread on this in the mailing l= ist with more explanation, but personally I have found it simplest to just = always build the kmod from ports when updating.


From: "Graham Perrin" <graha= mperrin@freebsd.org>
To: "FreeBSD questions" <freebsd-quest= ions@freebsd.org>
Cc: "VirtualBox on FreeBSD team" <vbox@fr= eebsd.org>, "Virtualisation on FreeBSD" <freebsd-virtualization@freeb= sd.org>
Sent: Tuesday, January 24, 2023 4:13:54 PM
Subje= ct: Re: 13.1-STABLE vritualbox-ose-kmod panic
On 24/01/2023 23:07, Graham Perrin wrote:
On 24/01/2023 22:06, Tomek CEDRO wrote:
=E2=80=A6 The first time I noticed that problem was beginning of January 2023. Before I was able to use virtualbox-ose(-kmod) on STABLE with no problem.

How can I make things work again?

Will virtualbox-ose-kmod work only with a RELEASE and not with STABLE?
It works here with CURRENT.

Do I need to rebuild both virtualbox-ose and virtualbox-ose-kmod from ports? =E2=80=A6

Tomek, please check that your copy of the ports tree is up-to-date.

If you build from source, build (and install) the kernel module alone.


--=_ac82ec49-8f38-4172-94e3-fc491780ec5d--