2 days ago I installed a clean 13.2 x64 with VirtualBox from the default repo.
Today I ran it and it told me I must be member of vboxusers. Fair enough - I added my user to the group.
But then when I attempt to start VirtualBox again I get a message box:
Effective UID is not root (euid=1000 egid=100 uid=1000 gid=100) (rc=-10)
Please try reinstalling VirtualBox.
I uninstalled the virtualbox-* packages and rebooted.
Installed them and rebooted again.
Again trying to run VirtualBox gives the same error.
The permissions of the file are the same before and after reinstall:
-rwxr-xr-x 1 root vboxusers 35384 Oct 1 15:55 /usr/lib/virtualbox/VirtualBox*
On this forum I read that changing the rwx to rws solves the problem for some people. However I am being cautious with that because afaik s means executing the process as the owner (root). Is it really necessary this process to be run as root?
I also wonder if it should have been s - why is it x? I was also thinking - ok, say I change it to s and it works, what happens after an update? I suppose the permissions might be reset to the default again as it seems they are the same after reinstall?
Anyone having seen that? Perhaps a clean solution?
So to add yourself, you did the following steps:
Open YaST.
Enter password.
Choose Security and Users
User and Group Management
Choose your user, then select “Edit”.
Go to Details tab, then in “Additional Groups” put a check by “vboxusers”.
Then say “OK”, “OK”, then close YaST and re-login.
When you install packages, the configuration files aren’t always removed (I don’t know the VBox uninstall behavior).
The way to ensure a completely clean <default> install is to force re-install, eg
zypper in -f virtualbox
If you prefer to use YAST, you’ll find a similar selection.
You might also doublecheck your User membership in the vboxusers group by inspecting the members of that group (don’t just check from your User which groups it’s a member of).
The install is completely clean because the whole openSUSE installation is. No VMs have been configured, nothing yet. Anyway I have re-installed it one more time as you suggested and of course the groups have been N-times checked. The result is the same however
On 10/27/2015 04:36 AM, heyjoe wrote:
>
> 2 days ago I installed a clean 13.2 x64 with VirtualBox from the default
> repo.
>
> Today I ran it and it told me I must be member of vboxusers. Fair enough
> - I added my user to the group.
>
> But then when I attempt to start VirtualBox again I get a message box:
>
>
> Code:
> --------------------
> Effective UID is not root (euid=1000 egid=100 uid=1000 gid=100) (rc=-10)
>
> Please try reinstalling VirtualBox.
> --------------------
Hate to be ‘that guy’ but is there a reason you need VBox? I find that
on Linux KVM/virt-manager work great, even for windows VMs. At the
moment I am running a 2012R2 and Windows 7 VM and they perform fine.
Just speaking from personal experience, VBox is always trouble for me on
linux while KVM/virt-manager work fine so whenever I have the choice I
avoid VBox.
I need a solution that allows me to run the same guest in both Linux and Windows host. Can you suggest anything more suitable than VirtualBox?
Just speaking from personal experience, VBox is always trouble for me on
linux while KVM/virt-manager work fine so whenever I have the choice I
avoid VBox.
Is it possible to run a VBox guest in KVM, then reboot in Windows 7 and run the same guest on VirtualBox for Windows? Then boot back in Linux and continue running the same guest in KVM etc.
Technically QEMU supports VBox disk format, but the problem is devices that are emulated by each one. I suppose it would be possible to carefully select physical devices to be emulated, but at least with QEMU my experience is, that it becomes painfully slow. And of course VB guest additions won’t work in QEMU, different video acceleration etc.
Nowadays many virtualization technologies support “non-native” disk formats.
Or, you can choose a virtualization that runs on both Windows and Linux.
Runs on both Windows and Linux…
Virtualbox
VMware
I don’t know if anyone is maintaining a matrix of supported disk formats, but in general VBox supports practically everything I’ve run across and you can list all supported KVM disk formats with the following command
qemu-img -h
Note that because of qemu-kvm integration, KVM supports all QEMU disk formats without the penalties associated with full virtualization.
So, you have many choices if you run VBox (or VMware) on Windows and KVM (or VMware) on Linux.
