Thanks Klaus for the extensive tips.
It is correct that I pasted the contents of a file that didn't match the given file name, acutally the PIDs do match, of course.
I have checked the environment variables for the vboxheadless processes.
They looked like this:
Code: Select all
MAIL=/var/mail/xxx
USER=jbxs2c
LANGUAGE=en_US:enSHLVL=2
HOME=/home/xxx
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
LOGNAME=xxx
_=/usr/bin/VBoxManage
XDG_SESSION_ID=c3
PATH=/usr/bin:/bin:/usr/sbin:/sbin
INVOCATION_ID=a7907ec0de284288a52fdfe982f2cce0
XDG_RUNTIME_DIR=/run/user/1000
LANG=en_US.UTF-8
SHELL=/bin/bash
PWD=/home/xxx
LOG=/home/xxx/somelog
VBOX_XPCOM_HOME=/usr/lib/virtualbox
I can see some variables here coming from the script that starts the very first VM.
To rule out that this is causing the issue, I stopped all VMs, waited for VBoxSVC to terminate, and then started a VM manually once, which led to more "default" environment variables.
Still the logs are being created.
I then further investigated the log files and noticed that they are solely being created for
Windows 7 VMs (both 32 and 64 bit). We also run Windows 10, Linux and other VMs on this server, but no log files for these.
So I assume it must be something specific in these VMs (in their configuration/vbox file?) triggering the logging.
I checked the
vbox file for ExtraDataItem containing
Dbg or
Debug, but couldn't find anything.
Do you have an idea what's going on and why it may only be happening for W7 VMs?