I went ahead and tried installing the latest avaiable from their repository.

groucho@devuan:~$ vboxmanage --version
6.1.28r147628
groucho@devuan:~$ 

After all the vm only runs Pie-hole and Unbound.

The line in dmesg for the guest is still there:

groucho@dev-pihole:~$ sudo dmesg | grep -i error
--- snip ---
[   16.458606] 00:00:00.178288 vminfo   Error: Unable to connect to system D-Bus (1/3): Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
--- snip ---
groucho@dev-pihole:~$ 

I now get the kernel traps for vboxsvc and vboxheadless but can see no problem/effects.

That said, it seems that a newer version for Buster/Beowulf has been released after we last wrote:

https://download.virtualbox.org/virtual … _amd64.deb

I'll try it and see if things improve.

Thanks for your input.

Best,

A.

Have you tried the latest one from the virtual box repository or was that the one that locked up?

No, not yet. I am reluctant to do so since I don't have much hope that it will work, and since what I have now is working, I really don't want to mess with it. I probably won't try it until after I upgrade to Chimaera.

My experience has been that VirtualBox 6.1 is messed up and doesn't work right on Beowulf. I had VMs completely lock up, multiple times. The latest version that has been working reliably for me is 6.1.22 r144080 (Qt5.6.1). And in case it matters, I am also using a kernel (and headers) from backports (on the host system). Hopefully this problem will disappear when I upgrade to Chimaera.

Just thought I'd pass along this information in case it's helpful.

Very helpful... that was my experience on Ceres with VBox 6.1.28-dfsg-1+b1 and kernel/headers 5.14.0-3. Appreciate the info. I'll try an earlier VBox and see how it goes.

I have not had any of the problems you mention.
Only the ones mentioned (kernel error in host at shutdown and guest's dmesg) but they don't seem to cause any malfunction, at least one that I can see or notice.

But then I am not doing anything to tax the installation, my guest just runs a recursive DNA server (unbound) and Pi-hole on the host.

It seems from what I have read in the Virtualbox support forum that they balk at use of Linux distribution versions of VBox.
They insist on their version being used, not targeted at any specific distribution, just at any version that is not theirs.

If not their version, admin says no to any support.

Like I mentioned I am running 6.1.18-142142 but the virtualbox version for Debian Buster/Devuan Beowulf available at download.virtualbox.org is 6.1.28-147628.

Have you tried the latest one from the virtual box repository or was that the one that locked up?

Thanks for your input.

A.

Just thought I'd pass along this information in case it's helpful.

Good to know.
Thanks.

The daemon(s) run in the guest, yes?

Lets see:
I boot the host and it autostarts the guest (headless) at some point in the boot process.
I can eventually login to the guest's desktop via the VirtualBox manager, but I am slowly getting used to doing most things via cmd line.  =^)

I log in to the host as soon as I get SLiM on screen and right upon getting the desktop, I load Pegasus Mail and Pale Moon.
But unless I wait a few seconds, I cannot get anything from either because there is no net connection available at that point.

I expect this is because Unbound and Pi-hole are not up and running yet.
Not because of the guest machine not being up yet.

Sound plausible?

Thanks for your input.

Best,

A.

I added the -o to the command to show the owner and group data:

groucho@dev-pihole:~$ sudo namei -l -o /var/run/dbus/system_bus_socket
f: /var/run/dbus/system_bus_socket
drwxr-xr-x root       root         /
drwxr-xr-x root       root         var
lrwxrwxrwx root       root         run -> /run
drwxr-xr-x root       root         /
drwxr-xr-x root       root         run
drwxr-xr-x messagebus messagebus   dbus
srwxrwxrwx root       root         system_bus_socket

I'm afraid this is rather out of my depth. 8^|
Have to read the manfile a few more times to interpret this properly.

Does it look right to you?

The only thing that seems strange (to me) is that everything is owned by root.

Thanks for your input.

Best,

A.

On a whim, I added the vboxusers group to the guest machine and my userid to the group:

groucho@dev-pihole:~$ groups
groucho adm disk mail cdrom tape sudo backup plugdev users vboxsf vboxusers
groucho@dev-pihole:~$ 

groucho@dev-pihole:~$ cat /etc/group | grep vbox
vboxsf:x:999:groucho
vboxusers:x:1001:groucho
groucho@dev-pihole:~$ 

Unfortunately, the error in dmesg persists:

groucho@dev-pihole:~$ sudo dmesg | grep -i error
[   17.507723] 00:00:00.118675 vminfo   Error: Unable to connect to system D-Bus (1/3): Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
groucho@dev-pihole:~$

There are two instances of system_bus_socket.

1. In /var/run/dbus

groucho@dev-pihole:~$ ls /var/run/dbus
pid  system_bus_socket
groucho@dev-pihole:~$ 

2. In /run/dbus

groucho@dev-pihole:/run/dbus$ ls
pid  system_bus_socket
groucho@dev-pihole:/run/dbus$ 

This would be correct as they are linked:

groucho@dev-pihole:~$ ls -ald /run /var/run /var/lock /run/lock
drwxr-xr-x 21 root root 920 Nov 20 16:26 /run
drwxrwxrwt  2 root root  80 Nov 20 16:27 /run/lock
lrwxrwxrwx  1 root root   9 Jun  6  2018 /var/lock -> /run/lock
lrwxrwxrwx  1 root root   4 Jun  6  2018 /var/run -> /run
groucho@dev-pihole:~$ 

So ...
Why doesn't vm find it?

I wonder where it is you have to tell it where to find it ...
Some *.conf file?

Best,

A.

Ja bin ich  =^)

My userid is the same in both the host and the guest.

In the host:

groucho@devuan:~$ groups
groucho adm lp mail dialout fax cdrom floppy tape sudo audio dip www-data backup video plugdev staff users crontab netdev lpadmin scanner saned vboxusers fuse powerdev debian-exim
debian-eximgroucho@devuan:~$

groucho@devuan:~$ cat /etc/group | grep vbox
vboxusers:x:124:groucho
groucho@devuan:~$ 

In the guest, my user is a member of vboxsf:

groucho@dev-pihole:~$ groups
groucho adm disk mail cdrom tape sudo backup plugdev users vboxsf
groucho@dev-pihole:~$ 

groucho@dev-pihole:~$ cat /etc/group | grep vbox
vboxsf:x:999:groucho
groucho@dev-pihole:~$ 

There does not seem to be a vboxusers group available in the guest machine.

Danke schön,

A.

Sorry, I neglected to mention it.  8^/

My host runs on Beowulf:

groucho@devuan:~$ uname -a
Linux devuan 5.10.0-0.bpo.3-amd64 #1 SMP Debian 5.10.13-1~bpo10+1 (2021-02-11) x86_64 GNU/Linux
groucho@devuan:~$ 

It runs VBox 6.1:

groucho@devuan:~$ vboxmanage --version
6.1.18r142142
groucho@devuan:~$ 

The guest runs on ascii:

groucho@dev-pihole:~$ uname -a
Linux dev-pihole 4.9.0-16-amd64 #1 SMP Debian 4.9.272-2 (2021-07-19) x86_64 GNU/Linux
groucho@dev-pihole:~$ 

I thought something like that would happen.
Mix & Match is usually not a good idea.
Unless backports?

So, I get this error in my guest's dmesg:
ie: when booting.

groucho@dev-pihole:/var/log$ sudo dmesg | grep -i error
[   18.005937] 00:00:00.181397 vminfo   Error: Unable to connect to system D-Bus (1/3): Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
groucho@dev-pihole:/var/log$ 

This seems to be related to VBox and dbus.

But ...
I also get this on the screen when I shutdown the host, found it in /var/log/messages:

groucho@devuan:/var/log$ cat messages | grep -i error
--- snip ---
Nov 19 22:38:23 localhost kernel: [21254.843754] traps: VBoxSVC[2451] trap int3 ip:7fa545efcddc sp:7ffe92195e50 error:0 in VBoxXPCOMIPCC.so[7fa545ef8000+f000]
--- snip ---
groucho@devuan:/var/log$

It seems to be related to VBox, just like the error in the guest.

Could these be related? Dumb question.  8^|

No problem.
It's the effort that counts. 8^)

Thanks for your input.

Best,

A.

$ apt-cache depends dbus
dbus
  PreDepends: init-system-helpers
  Depends: lsb-base
  Depends: dbus-bin
  Depends: dbus-daemon
  Depends: dbus-system-bus-common
  Depends: libc6
  Depends: libdbus-1-3
  Depends: libexpat1
 |Suggests: <default-dbus-session-bus>
    dbus-x11
  Suggests: <dbus-session-bus>
    dbus-x11

$ find /run/dbus -name system_bus_socket
/run/dbus/system_bus_socket

Assuming Ascii's your host system, hard to say what'll work. Trying to bring in Ceres' dbus-system-bus-common for VBox will break dbus if older than 1.12.20-3~, and upgrading dbus will also require upgrading libc6, creating a mess. Maybe download an older version of VBox from their site?

Sorry but I don't know what to suggest.

My VBox Devuan machine is ascii:

groucho@dev-pihole:~$ uname -a
Linux dev-pihole 4.9.0-16-amd64 #1 SMP Debian 4.9.272-2 (2021-07-19) x86_64 GNU/Linux
groucho@dev-pihole:~$ 

And these are the dependencies listed for dbus:

groucho@dev-pihole:~$ apt-cache depends dbus
dbus
  Depends: adduser
  Depends: init-system-helpers
  Depends: lsb-base
  Depends: libapparmor1
  Depends: libaudit1
  Depends: libc6
  Depends: libcap-ng0
  Depends: libdbus-1-3
  Depends: libexpat1
  Depends: libselinux1
| Suggests: <default-dbus-session-bus>
  Suggests: <dbus-session-bus>
    dbus-x11
groucho@dev-pihole:~$ 

default-dbus-session-bus and dbus-session-bus are not installed.  (see OP)

But dbus-system-bus-common is not listed.

In any case, default-dbus-session-bus and dbus-session-bus can't be installed.
Apt selects dbus-x11 but it is already installed.

Can dbus-system-bus-common from experimental be installed in ascii?

Thanks for your input.

Best,

A.