13.1-STABLE vritualbox-ose-kmod panic

[Tomek CEDRO]

Hello world :-)

I did upgrade world and kernel today.. still I cannot kldload
virtualbox modules (modules are built from ports, vbox from package)..
that renders VirtualBox useless because it cannot start any virtual
machine due to missing driver error.

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?

Do I need to rebuild both virtualbox-ose and virtualbox-ose-kmod from ports?

Do I have to wait with virtualbox-ose-kmod until STABLE gets in align
with RELEASE?

Any hints welcome :-)
Tomek

% uname -a
FreeBSD octagon 13.1-STABLE FreeBSD 13.1-STABLE #4
stable/13-n253680-16ae7b665c7e: Tue Jan 24 07:20:27 CET 2023
root@octagon:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64

% pkg info virtualbox-ose
virtualbox-ose-6.1.36
Name : virtualbox-ose
Version : 6.1.36
Installed on : Sat Jan 7 06:50:23 2023 CET
Origin : emulators/virtualbox-ose
Architecture : FreeBSD:13:amd64
Prefix : /usr/local
Categories : emulators
Licenses : GPLv2
Maintainer : vb...@FreeBSD.org
WWW : https://www.virtualbox.org/
Comment : General-purpose full virtualizer for x86 hardware
Options :
AIO : on
ALSA : off
DBUS : on
DEBUG : off
GUESTADDITIONS : off
MANUAL : off
NLS : on
OPUS : off
PYTHON : off
QT5 : on
R0LOGGING : off
UDPTUNNEL : on
VDE : off
VNC : on
VPX : off
WEBSERVICE : on
X11 : on
Shared Libs required:
libxml2.so.2
libxcb.so.1
libvncserver.so.1
libpng16.so.16
libcurl.so.4
libXt.so.6
libXext.so.6
libXcursor.so.1
libX11.so.6
libSDL-1.2.so.0
libQt5X11Extras.so.5
libQt5Widgets.so.5
libQt5PrintSupport.so.5
libQt5OpenGL.so.5
libQt5Gui.so.5
libQt5Core.so.5
libGL.so.1
Annotations :
FreeBSD_version: 1301000
cpe : cpe:2.3:a:oracle:vm_virtualbox:6.1.36:::::freebsd13:x64
repo_type : binary
repository : FreeBSD
Flat size : 164MiB
Description :
Oracle VM VirtualBox is a hosted hypervisor for x86 virtualisation.
Supported guests include BSD, Haiku, Linux, OS/2, ReactOS, Solaris and
Windows.

Guest Additions are available from: emulators/virtualbox-ose-additions

For the Extension Pack: FreeBSD is not a supported host platform.
Installation of the Pack will not extend the feature set.

WWW: https://www.virtualbox.org/


% pkg info virtualbox-ose-kmod
virtualbox-ose-kmod-6.1.36
Name : virtualbox-ose-kmod
Version : 6.1.36
Installed on : Tue Jan 24 21:05:52 2023 CET
Origin : emulators/virtualbox-ose-kmod
Architecture : FreeBSD:13:amd64
Prefix : /usr/local
Categories : kld emulators
Licenses : GPLv2
Maintainer : vb...@FreeBSD.org
WWW : https://www.virtualbox.org/
Comment : VirtualBox kernel module for FreeBSD
Options :
DEBUG : on
VIMAGE : on
Annotations :
FreeBSD_version: 1301511
cpe : cpe:2.3:a:oracle:vm_virtualbox:6.1.36:::::freebsd13:x64
Flat size : 3.92MiB
Description :
VirtualBox is a family of powerful x86 virtualization products for
enterprise as well as home use. Not only is VirtualBox an extremely
feature rich, high performance product for enterprise customers, it
is also the only professional solution that is freely available as
Open Source Software under the terms of the GNU General Public License.

WWW: https://www.virtualbox.org/


--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info

[Graham Perrin]

FAO maintainer (omitted from the original email).

Adding freebsd-vir...@freebsd.org, dropping
freebsd-...@freebsd.org (we should address no more than two lists).

[Graham Perrin]

On 24/01/2023 23:07, Graham Perrin wrote:

On 24/01/2023 22:06, Tomek CEDRO wrote:

… 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? …

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.

[Dale Scott]

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.

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 incompatibitliy. You'll get the same error if you attempt to load the kmod manually.

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 always build the kmod from ports when updating.

---

[Dale Scott]

On 24/01/2023 23:07, Graham Perrin wrote:

On 24/01/2023 22:06, Tomek CEDRO wrote:

… 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?

Sorry, please ignore my incredible lack of respect by accidentially top-posting in my previous reply ;-)

There is a period of time in the release engineering cycle when the version of virtualbox-ose-kmod in pkg will work, but most 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 loaded due to a version incompatibitliy. You'll get the same error if you attempt to load the kmod manually.

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 always build the kmod from ports when updating.

Feel free to forward this to the virtualbox and virtualization lists as I'm not subscribed.

Cheers,

Dale

[Tomek CEDRO]

On Wed, Jan 25, 2023 at 12:14 AM Graham Perrin wrote:
> On 24/01/2023 22:06, Tomek CEDRO wrote:
>
> … 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.

Hmm I guess it works on RELEASE and CURRENT.. why it kernel panics STABLE? o_O

> Do I need to rebuild both virtualbox-ose and virtualbox-ose-kmod from ports? …
> 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.

fresh git pull of the ports tree, port built and reinstalled from ports.

:-(

[Amar Takhar]

On 2023-01-25 02:38 +0100, Tomek CEDRO wrote:
<snip>

> fresh git pull of the ports tree, port built and reinstalled from ports.

Did you remember to unload the old kernel module? Also be sure you're using the
same kernel source as your running kernel I take the hash from a uname -a just
to be sure.

Both of these have tripped me up in the past. :)


Amar.

[Tomek CEDRO]

On Wed, Jan 25, 2023 at 2:42 AM Amar Takhar wrote:
> Did you remember to unload the old kernel module? Also be sure you're using the
> same kernel source as your running kernel I take the hash from a uname -a just
> to be sure.

yes sir :-)

[Tomek CEDRO]

On Wed, Jan 25, 2023 at 4:19 AM Ka Ho Ng wrote:
> virtualbox-ose-kmod uses non-public kernel interfaces, thus requires rebuild after kernel buildkernel (in this case -STABLE). It is simply irrelevant whether it works on -RELEASE / -CURRENT.
>
> Further triage is needed only if the virtualbox-ose-kmod after rebuild still panics the kernel.

This seems the case o_O

service vboxguest onestart <- this one works

service vboxservice onestart <- kernel panic here

kldload vboxdrv <- kernel panic here

I had to disable all vbox stuff in /boot/loader.conf and /etc/rc.conf
otherwise boot loop.

No dump is stored in /var/crash I only got this picture:

https://ibb.co/D51Q1xm

Will have to debug it somehow :-)

[Tomek CEDRO]

Well, maybe its time to give bhyve a try after alll these vbox
problems for years ;-)

Is it possible to run macOS with graphics on bhyve? :-P

[Mario Lobo]

Been using Vbox for years without ANY problems.

I have 13.1 STABLE an even bumped the port version to 6.1.42.

Rule of thumb. Always compiled both ports. Never used pkg.

[Amar Takhar]

On 2023-01-25 04:21 +0100, Tomek CEDRO wrote:
> On Wed, Jan 25, 2023 at 2:42 AM Amar Takhar wrote:
> > Did you remember to unload the old kernel module? Also be sure you're using the
> > same kernel source as your running kernel I take the hash from a uname -a just
> > to be sure.
>
> yes sir :-)

Anytime I have issues with VirtualBox I delete all the packages unload the kmods
and check for anything dangling in /usr/local/ and remove that as well.

I know you're having panics I've had the boot loop issue before just last year
after updating from 13-RELEASE to 13.1-RELEASE instant panic with no dumps.
Just last week I was having issues with VMs not booting after a Qt update
rebuilding all the ports fixed the issue. I always rebuild every port and never
use packages VirtualBox can be really touchy but once it's running it's rock
solid,

I would try to go and carefully check everything again and do a rebuild from
ports no packages at all and see what happens. For good measure before
rebuilding make sure you update all your packages.


Amar.

[Tomek CEDRO]

On Tue, Jan 24, 2023 at 11:06 PM Tomek CEDRO wrote:
> I did upgrade world and kernel today.. still I cannot kldload
> virtualbox modules (modules are built from ports, vbox from package)..
> that renders VirtualBox useless because it cannot start any virtual
> machine due to missing driver error.
>

> % uname -a
> FreeBSD octagon 13.1-STABLE FreeBSD 13.1-STABLE #4
> stable/13-n253680-16ae7b665c7e: Tue Jan 24 07:20:27 CET 2023
> root@octagon:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64

I have downgraded to a RELEASE problem solved ;-)

Too many crashes on STABLE probably caused RAIDZ2 failures.. I hoped
it will be more failure resistant :-(