Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: rbowman <bowman@montana.com>
Newsgroups: comp.os.linux.misc
Subject: Re: Virtualbox on Debian Trixie,
Date: 25 Feb 2026 19:59:00 GMT
Lines: 14
Message-ID: <n092k4F5ca9U2@mid.individual.net>
References: <10nmp1b$n560$6@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net iM7Pah83TjT/3RCWTRUsbA0/G++HmmyZgQuLsz3o/lIEQwz0QC
Cancel-Lock: sha1:6JxLvWE0S7o4EvbhMILSkubhHNw= sha256:uEN0wbJ4FlBJoIFU9ocwN6pSEia0sereWeOLhJO8jcQ=
User-Agent: Pan/0.162 (Pokrosvk)
Xref: csiph.com comp.os.linux.misc:82264

On Wed, 25 Feb 2026 12:13:31 +0000, The Natural Philosopher wrote:

> I did some research. There are known issues that prevent this working
> out of the box..
> 
> They seem to be due to Trixie having dropped some libraries that the
> current vbox needs and a need to remove the kvm nodule,
> 
> Whose 'fault' this is is a worm can I will refrain from opening...

https://forums.virtualbox.org/viewtopic.php?t=113902

Yeah, it does seems to be a deeper problem than the unloading the kvm 
module that worked for people on other distros.