Version

7.1.12

Host OS Type

Linux

Host OS name + version

Linux 6.12.39-1-MANJARO (x86_64) on BTRFS

Host Architecture

x86

Guest OS Type

all

Guest Architecture

x86

Guest OS name + version

bug happens on all guest OS

Component

Other

What happened?

The bug happens on a fresh installed Manjaro. No errors in dmesg or other diagnostic tools. BIOS virtualization is on, group and membership of vboxusers is set correctly, all relevant directories do have read/write access for the user and for VBox. Default pathes and default names are used for VBox.

VirtualBox Manager freezes, if a new VM should be created or if an existing VM, which is running smoothly on another Laptop, should be added.
VirtualBox Manager cannot work with any VM, but will generate the usual files in the directories "VirtualBox VMs" and "./config/VirtualBox"
VirtualBox Manager can only started again, when the directory "./config/VirtualBox" is cleaned up before.

This issue has been already extensively but unsuccessfully discussed in Manjaro forum here:

and in the Oracle VirtualBox forum here:

When trying to create an "empty" new VM, VBoxSVC.log error lines say, that the VM cannot be closed, because it is still attached to another VM.
When trying to add an already existing VM, VBoxSVC.log error lines say, that the VM cannot be found and later it says, that the VM cannot be closed, because it is still attached to another VM.

VBoxSVC.log.zip
VirtualBox.xml.zip
VirtualBox.xml-prev.zip
test.vbox.zip

How can we reproduce this?

Create a Manjaro-Linux 6.12 host system on a btrfs formatted nvme drive (COW=active, compression=on, space_cache=v2, no encryption).

Create an ext4 partition on the same nvme drive. (no compression, no encryption, just default) in order to circumvent VBox problems with COW of btrfs.

Install VirtualBox 7.1.12r1 main and kernel component from Manjaro official repo.

Create symlinks for the directories "VirtualBox VMs" and "./config/VirtualBox" leading to folders with same name on the ext4 partition.

Start VirtualBox Manager (GUI) and create a new "empty" VM (empty=no OS, no harddrive, no optical drive, no ISO attached)
Click "finish" and VirtualBox Manager immediately freezes.
All files, which VirtualBox Manager usually will generate, are stored correctly in the folders on the ext4 drive.
VirtualBox Manager can only started again, when the directory "./config/VirtualBox" is cleaned up before.

see attached *.vbox, VBoxSVC.log, VirtualBox.xml-prev and VirtualBox.xml
These files were the result of trying to create an "empty" VM as described above.

Did you upload all of your necessary log files, screenshots, etc.?

• Yes, I've uploaded all pertinent files to this issue.