-
Good day to my new favorite customer support service :-) My VirtualBox VMs are stored at Following the logic of default profiles, I blacklisted /vbox/VMs folder for any app using Firejail in disable-common.local: And then did the opposite for VirtualBox itself in virtualbox.local:
When I start VirtualBox, there are lots of errors about access to /sys/module/* in output:
VirtualBox GUI works, but VM fails to start:
Unfortunately, I do not know much about filtering VMs logs from particular sessions (since there are several files), nor if them apply for immediately aborted start. If providing those will help troubleshoot, please let me know. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Firejail protects some /proc and /sys paths by default: Lines 739 to 745 in ab70db5 Try adding |
Beta Was this translation helpful? Give feedback.
-
I finally discovered what caused this issue! Firejail profile is fine, it's due to my specific configuration. To make it work, I had to allow write access to
Now VMs successfully start with this
Without |
Beta Was this translation helpful? Give feedback.
I finally discovered what caused this issue! Firejail profile is fine, it's due to my specific configuration.
As mentioned before, I use custom
/vbox/VMs
folder for storing my VMs instead of default one~/VirtualBox VMs
.To make it work, I had to allow write access to
/vbox
directory in Firejail's AppArmor profile by adding the following line to/etc/apparmor.d/local/firejail-default
file:/{,run/firejail/mnt/oroot/}vbox/** w,
Now VMs successfully start with this
virtualbox.local
: