Errm, I don't know what to say. Today I rebooted and tried again... and it worked. o.O
``` $ VBoxManage startvm 92522455-ebd0-4a67-8a38-4ba05ca3fc00 Waiting for VM "92522455-ebd0-4a67-8a38-4ba05ca3fc00" to power on... VM "92522455-ebd0-4a67-8a38-4ba05ca3fc00" has been successfully started. ``` I did not reinstall Virtualbox. Just an ordinary regular apt update && apt upgrade today. Hm, what remains is my sticky bit for /usr/share/virtualbox/VirtualBoxVM: ``` $ find /usr/lib/virtualbox/ -type f -executable | xargs ls -l | grep rws -rwsr-xr-x 1 root root 166208 Jun 22 09:15 /usr/lib/virtualbox/VirtualBoxVM ``` I don't know why it works today, despite my tries yesterday... maybe the virtual box kernel modules have some magic residing in memory and thus ignoring my attempts until a reboot. See myself puzzled... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935856 Title: Virtualbox encounters 'Effective UID is not root' when starting a VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1935856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
