New comment by AngryPhantom on void-packages repository

https://github.com/void-linux/void-packages/issues/38116#issuecomment-1237955145

Comment:
The bug is still here with version 6.1.36. It is even NOT fixed in 6.1.38. And it's not the Void's fault.
The problem is that no one can confirm this since the virtual machine **had to be created several versions ago**. And after that, upon upgrading VirtualBox itself, the issue appears. There is **no problem** if you create a **new virtual machine** with a **new version of VB**.