The issue described in bug #259234 has reappeared in VirtualBox 7.2.8. The behaviour is identical to what was reported in the original bug.
The issue seems to have been fixed upstream in a 7.2.9-xxx testbuild: https://github.com/VirtualBox/virtualbox/issues/645#issuecomment-4444394049 https://www.virtualbox.org/wiki/Testbuilds Until a stable release becomes available, the following workaround can be applied: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259234#c5 "Apropos, the creation of those log files can be suppressed by setting VirtualBox env variable "VBOX_LOG_DEST" to "nofile"."
I confirm that in VirtualBox version 7.2.10 the bug has been fixed.