Or at least, that's my experience. Though it could be different on debian based distros.

If you are interested and want to try it, you will need the following packages:

sudo apt update

sudo apt install qemu-kvm libvirt-clients libvirt-daemon libvirt-daemon-system bridge-utils virtinst virt-manager

In order to manage virtual machines as a regular user, that user needs to be added to the libvirt group:

#adduser youruserrname libvirt
#adduser youruserrname libvirt-qemu

After installing and setting everything up, reboot your computer.

Thanks for that info, food for thought if qemu isn't enough to get the job done.

Still, virt-manager works pretty well too last I checked for Devuan.

It actually worked for 0.3 Hyperbola pretty well, so it mostly DEFINITELY should work well for devuan also, even now.

After posting I realised that support for v6.1 ends December 2023.

Upgraded to 7.0.6:

~$ apt list | grep virtualbox | grep installed
--- snip ---
virtualbox-7.0/unknown,now 7.0.6-155176~Debian~buster amd64 [installed]
~$ 

If needed, the corresponding VBoxGuestAdditions and Extension Pack must also be installed for everything to work properly.

As before, no issues.

Best,

A.

Yes, it does.

I run Virtualxox-6.1 from the official source in my Devuan Beowulf with a backported kernel:

~$ uname -a
Linux devuan 5.10.0-0.deb10.16-amd64 #1 SMP Debian 5.10.127-2~bpo10+1 (2022-07-28) x86_64 GNU/Linux
~$ 

~$ cat /etc/apt/sources.list
--- snip ---
# virtual box repository x installation
deb https://download.virtualbox.org/virtualbox/debian/ buster contrib non-free 
--- snip ---
~$ 

~$ apt list | grep virtualbox | grep installed
--- snip ---
virtualbox-6.1/unknown,now 6.1.42-155177~Debian~buster amd64 [installed]
~$ 

On boot I start a headless Chimaera VM to run PiHole+Unbound.
And every once in a long while, boot an XPSP3 VM to run some odd MS application or test a Linux image.

Have had no issues.

Best,

A.

I don't know if devuan supports virtualbox anyhow.

The official images require systemd last I checked anyhow.

I don't understand why you are so disturbed by it.

Then again, I don't understand why @Ron

Or really anyone still uses virtualbox when virt-manager and qemu are both options.

Even virt-manager is better than virtualbox though and bare in mind, I am aware it relies on qemu but is also more or less developed by redhat. At least that is what I recall anyways...

That being said, Virtualbox is horribly insecure...

It does not get any more "layman's" than that ...
A.

Look above your post, I got it working.

But it looks like crap.

It does not get any more "layman's" than that ...
ie: VT-x --> disabled --> in BIOS

You first have to check your motherboard's BIOS settings and enable VT-x (hardware virtualization), it is usually disabled by default.

1. Reboot your Computer and Press the BIOS Key. ... (key/s used depend on the mobo brand, BIOS brand, etc.)
2. Locate the section for CPU configuration. ...
3. Find the Settings for Virtualization. ...
4. Select the Option for Enabling Virtualization. ...
5. Save the Changes You Have Made. ...
6. Exit Your BIOS and Reboot Your Computer.

If you don't know how to access the BIOS and/or navigate the respective options, first check the mobo's manual.

Best,

A.

VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).
Result Code: NS_ERROR_FAILURE (0X80004005)
Component: ConsoleWrap
Interface: IConsole {6ac83d89-6ee7-4e33-8ae6-b257b2e81be8}

Can anybody tell me what this means in layman's English, and does anybody know what I need to do to fix this? If it matters, I'm trying to run Windows 7 as the guest.

Thanks.