When attempting to start Virtual Box, i receive an error:
Failed to load VMMR0.r0
(VERR_SUPLIB_OWNER_NOT_ROOT).
Any ideas?
Please, this is a very, very short explanation about what you have (openSUSE, some version, something else?), what you are doing, what you expected to happen and what happened instead.
Also it seamns to be about virtualization. And we have a Virtualization forum. Maybe the people there hve a better idea about what you mean with those few lines of information.
Sorry- here is version info:
NAME=openSUSE
VERSION=“13.1 (Bottle)”
VERSION_ID=“13.1”
PRETTY_NAME=“openSUSE 13.1 (Bottle) (x86_64)”
ID=opensuse
ANSI_COLOR=“0;32”
CPE_NAME=“cpe:/o:opensuse:opensuse:13.1”
BUG_REPORT_URL=“https://bugs.opensuse.org”
HOME_URL=“https://opensuse.org/”
ID_LIKE=“suse”
I am attempting to install Oracle Virtual Box. I’m not really having a virtualization problem, but an application problem. The application installs correctly, and will allow creation of a new “machine.” However, when attempting to start the new “machine” the permissions error posted to start this thread occur.
Failed to load VMMR0.r0 (VERR_SUPLIB_OWNER_NOT_ROOT).
additional error detail:
| Result Code:
|
| NS_ERROR_FAILURE (0x80004005)
|
| Component:
| Console
|
| Interface:
| IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}
|
I have searched Virtual Box forums for similar error, but have mainly found users solutions for Ubuntu.
And how are you attempting to install it?
Use the supplied RPMs (either the ones included in openSUSE, or the one you can download at virtualbox.org) to install it, and it should work.
Failed to load VMMR0.r0 (VERR_SUPLIB_OWNER_NOT_ROOT).
Well, that message means that the file VMMR0.r0 is not owned by root although it should be.
You probably compiled it yourself, right?
Did you actually install it?
Probably with “sudo make install”.
But as I said, better just use the RPM packages to install it.
Sounds like a common permissions issue…
You probably tried to launch or run VBox as a normal User…
Although there are ways to modify permissions to allow this (I see this all over the place), I really have a serious mis-giving about modifying this standard setup that requires root permissions to launch, shutdown and otherwise manage whole machines (even Guests). Is akin to giving a regular User root permissions.
I’d ask how you’re launching VBox.
If you’re launching VBox using a shortcut, you should modify the shortcut to prompt you for elevated permissions.
If you’re launching from the command line, I’d recommend requiring and using sudo or su.
TSU
Well, how else would you run it?
I’d ask how you’re launching VBox.
If you’re launching VBox using a shortcut, you should modify the shortcut to prompt you for elevated permissions.
If you’re launching from the command line, I’d recommend requiring and using sudo or su.
NO!
You should NOT run VirtualBox as root.
sudo won’t work anyway as VirtualBox wouldn’t even be able to open its GUI… 
Ah,
Someone else who believes that managing virtualized Guests should be something ordinary Users can do…
Really, think about that a sec… If we believe that ordinary Users should not have the same permissions as root, why would you allow those same Users to launch and manage something with root permissions (within the Guest)?
That nearly guarantees root permissions of a node on the network (assuming the Guest has networking capability) and potentially could also compromise the Host. At the very least you’re granting permissions to a very low level of the operating system, possibly even below the operating system.
Note I’m not saying that Virtualbox should be running as the actual root user, but that access to management functions should require root access.
TSU
Yes. And I’m using VirtualBox for years (as normal user).
That said, you do have to be part of the group “vboxusers” to be able to do that (with the openSUSE packages at least, I’m not sure about Oracle’s or a self-compiled version).
But if you are not, you get a different error message.
Really, think about that a sec… If we believe that ordinary Users should not have the same permissions as root, why would you allow those same Users to launch and manage something with root permissions (within the Guest)?
That nearly guarantees root permissions of a node on the network (assuming the Guest has networking capability) and potentially could also compromise the Host. At the very least you’re granting permissions to a very low level of the operating system, possibly even below the operating system.
What are you talking about?
Aren’t you suggesting to run the VM as root?
The OP wanted to start a VirtualBox VM, but cannot.
And again, you do not need root permissions for running a VirtualBox VM.
Why would you run VirtualBox as root? And what does this have to do with root access in the guest?
Note I’m not saying that Virtualbox should be running as the actual root user, but that access to management functions should require root access.
???
What else does sudo or su achieve?
Running Virtualbox with su or sudo WILL run it as the actual root user.