Date: Tue, 24 Jan 2023 17:40:58 -0700 (MST) From: Dale Scott <dalescott@shaw.ca> To: Graham Perrin <grahamperrin@freebsd.org> Cc: FreeBSD questions <freebsd-questions@freebsd.org>, VirtualBox on FreeBSD team <vbox@freebsd.org>, Virtualisation on FreeBSD <freebsd-virtualization@freebsd.org> Subject: Re: 13.1-STABLE vritualbox-ose-kmod panic Message-ID: <271536304.16750316.1674607258015.JavaMail.zimbra@shaw.ca> In-Reply-To: <7fe27024-d794-d808-c2f4-371c533eb2e4@freebsd.org> References: <CAFYkXjkwYJBx=naj75WbKAGbZv2f-9fVeWu5Bd2bRtpp9W=45A@mail.gmail.com> <3d8f8238-020b-0706-1c48-b17db12891f1@freebsd.org> <7fe27024-d794-d808-c2f4-371c533eb2e4@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--=_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" <grahamperrin@freebsd.org>
> To: "FreeBSD questions" <freebsd-questions@freebsd.org>
> Cc: "VirtualBox on FreeBSD team" <vbox@freebsd.org>, "Virtualisation on F=
reeBSD"
> <freebsd-virtualization@freebsd.org>
> 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
<html><body><div style=3D"font-family: arial, helvetica, sans-serif; font-s=
ize: 10pt; color: #000000"><div>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.</div><div><br da=
ta-mce-bogus=3D"1"></div><div>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><div><br data-mce-bogus=3D"1"></div><=
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.</div><div><br data-mce-bogu=
s=3D"1"></div><div><br data-mce-bogus=3D"1"></div><hr id=3D"zwchr" data-mar=
ker=3D"__DIVIDER__"><div data-marker=3D"__HEADERS__"><blockquote style=3D"b=
order-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;fo=
nt-weight:normal;font-style:normal;text-decoration:none;font-family:Helveti=
ca,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Graham Perrin" <graha=
mperrin@freebsd.org><br><b>To: </b>"FreeBSD questions" <freebsd-quest=
ions@freebsd.org><br><b>Cc: </b>"VirtualBox on FreeBSD team" <vbox@fr=
eebsd.org>, "Virtualisation on FreeBSD" <freebsd-virtualization@freeb=
sd.org><br><b>Sent: </b>Tuesday, January 24, 2023 4:13:54 PM<br><b>Subje=
ct: </b>Re: 13.1-STABLE vritualbox-ose-kmod panic<br></blockquote></div><di=
v data-marker=3D"__QUOTED_TEXT__"><blockquote style=3D"border-left:2px soli=
d #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;fo=
nt-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif=
;font-size:12pt;">
<div class=3D"moz-cite-prefix">On 24/01/2023 23:07, Graham Perrin
wrote:<br>
</div>
<blockquote>On
24/01/2023 22:06, Tomek CEDRO wrote:
<br>
<blockquote>=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.
<br>
<br>
How can I make things work again?
<br>
<br>
Will virtualbox-ose-kmod work only with a RELEASE and not with
STABLE?
<br>
</blockquote>
</blockquote>
It works here with CURRENT. <br>
<blockquote>
<blockquote>
<br>
Do I need to rebuild both virtualbox-ose and virtualbox-ose-kmod
from ports?
=E2=80=A6<br>
</blockquote>
</blockquote>
<p>Tomek, please check that your copy of the ports tree is
up-to-date. <br>
</p>
<p>If you build from source, build (and install) the kernel module
alone. <br>
</p><br></blockquote></div></div></body></html>
--=_ac82ec49-8f38-4172-94e3-fc491780ec5d--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?271536304.16750316.1674607258015.JavaMail.zimbra>