Between May/August of 2025, Ceres upgraded virtualbox from 7.0.20-dfsg-1.2 to 7.1.12-dfsg-2+b1. I think it was after the 7.1.10-dfsg-1 upgrade in June when VBox failed to start. Was odd because it was just an update. Did lsmod | grep vbox and in addition to vboxdrv not loaded, got this:

libkmod: ERROR: conf_files_filter_out: Directories inside directories are not supported: /etc/modprobe.d/virtualbox-dkms.conf

The error? Inside /etc/modprobe.d, VBox created the directory virtualbox-dkms.conf and inside it was the file virtualbox-dkms.modprobe.conf. I moved the directory out of /etc/modprobe.d and started the VBox modules: no more lsmod errors and VBox worked.

A search found bug report 1105784 filed in May. The patch to fix it was in July and noted:

Why? Blacklisting the kvm module was required because it conflicted with VBox's modules.

The full VBox suite, upgraded to 7.1.12-dfsg-2+b1 two weeks ago, is in Ceres contrib and works without issue.

Original:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<CodeBlocks_project_file>
    <FileVersion major="1" minor="6" />
    <Project>
        <Option title="theapp" />
        <Option pch_mode="2" />
        <Option compiler="gcc" />
        <Build>
            <Target title="English-GUI-Debug">
(... rest good ..)

Now the modified file:

: rtl-sdr
Multi-Arch: same
Tag: role::shared-lib
Section: libs
Priority: optional
Filename: pool/DEBIAN/main/r/rtl-sdr/librtlsdr0_0.6.0-3_i386.deb
Size: 33188
MD5sum: d5799384f8cd3990d7f4188e018b3d19
SHA256: 356e865c0b811314001bc2bb4fcb31f5b52eae6b4a16d77c8ee048dea0b50251

Package: librtmidi-dev
Version: 4.0.0-1
Installed-Size: 185
Maintainer: Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>
Architecture: i386
Depends: libasound2-dev, libjack-dev, librtaudio-dev, librtmidi5 (= 4.0.0-1)
Homepage: https://www.music.mcgill.ca/~gary/rtmidi/
Description: C++ library for realtime MIDI input/ouput (development files)
Description-md5: 54fd0b82fc9ca8bd591d66ee5342b772
Source: rtmidi
(... and on and on .. )

There were two modified files, the 2 project files (.cbp) I updated (If I update any other file, they will corrupt too).   It uses shared folders to a drive that is a DriveCrypt container.   This setup has been this way for years, debian first, then on to Devuan which is what I currently use.

I'm currently using VirtualBox 7.1.10 x64 on Win10 x64 Pro.  Latest extensions are installed (I didn't have to reinstall after the upgrade).

So something in the update is causing issues, I couldn't tell you what update I'm on other than Devuan Chimaera.

So I guess I'm stuck.  I now will restore those project files and the .vmdk file and I'll be able to work just fine, but those 400+ updates I don't dare do.

Thanks.

That is not (and should not be) a problem for anyone taking the time to reply to as request for support here at Dev1.

ie: You do what you can, when you can and if you can.

My apologies if my text sounded like anything else.

Time is, indisputably, the most valuable thing anyone has.
And to dedicate a part of it, however small, to help someone is the right thing to do.

It is part of what I refer to as the 'pay it forward system'.
It goes around and (eventually) will come back to you.

Best,

A.

Let's see ...

Registered:
2025-01-27
Posted:
2025-01-28

Received answers:
2025-01-28 x1
2025-01-30 x1
---
A long awkward silence ensues ...
eg: crickets
---
20250504 x 2  <- valiant effort from Devarch and Rolfie ...

When I see this sort of attitude from members (most if not all, new ones) seeking help, it really makes me wonder ...

.
A.

Well, I am on Daedalus now, VBox is installed from the .deb from virtualbox.org, I am currently on 7.0.22. Got two older Win VMs running using shared folders. Never had any issues. The XP VM was generated about 2012, the Win7 VM around 2017. Have been pulled up through several releases of Debian/Devuan.

Now to your problem: what is host, what is guest? Are you running Win10 as host and Chimaera as guest in a VM? Is that right? Have you got dkms and the linux headers installed in the VM? Guest additions are uptodate, you use the ones from 7.0.20?

I run VirtualBox to host WinXP with a CAD program I cannot replace, as well as Devuan derivatives and other distros. I rarely use a shared folder and whether enabled/disabled, never had a problem.

Don't have a suggestion other than, have you tried a Devuan update with the shared folder/s disabled?

Welcome to Dev1.

You run a Win10 box + VirtualBox 7.0 to run Devuan Chimaera VM?

It is not quite clear to me where the problem lies but it would seem that it is with VirtualBox.
If the issues are indeed with VirtualBox, I'd say that it is something to ask about either in a Win10 or VBox forum.

That said, you may want to consider running a Devuan box + VirtualBox and then drop in whatever VM you want to run.
I would not trust any MSOS box to run my VMs in, but maybe that's just me getting old. 8^°

As always, YMMV.

I have been running VirtualBox in my Devuan installations to host three VMs since Devuan ascii: W98 for a pair of applications I cannot replace and two Devuan Linux, one to run a PiHole+ a recursive DNS and another for testing purposes and such.

Never had any problems.

Best,

A.

Edit: do take 5' to read this article.

Any ideas or known issue fixed with latest updates?