Do I have to be root?

Fjatle · Post by **Fjatle** » 29. May 2007, 18:38

Hi!

To run VirtualBox, I cannot just click the launcher. I get the message
that I do not have the administrative rights to run a guest OS.
So I have to: sudo VirtualBox to run the program..

Is there any easyer way I can execute the program?

And even better, is it possible to make a launcher to run run a guest OS straight from the Launcher?? That would have been cool.. !

Post by **bodhi.zazen** » 29. May 2007, 18:49

You have to add your user to the vboxusers group

Fjatle · Post by **Fjatle** » 29. May 2007, 20:49

I did that, but it didn't help.

Is it a problem that i added myself as a user AFTER I installed a Viritual machine?

Post by **bodhi.zazen** » 29. May 2007, 21:29

Just curious, you did not state your guest OS or version of VirtualBox.

If you still have permissions problems, set the permissions of /dev/vboxdrv:

Code: Select all

chmod 660 /dev/vboxdrv
chgrp vboxusers /dev/vboxdrv

You may need to edit /etc/udev/rules.d/40-permissions.rules The exact location and file name will vary with distro (the one above is for Ubuntu).

and change this line to

KERNEL=="vboxdrv", GROUP="vboxusers", MODE="0660"

To keep the permissions /dev/vboxdrv from reverting when you re-boot.

Fjatle · Post by **Fjatle** » 30. May 2007, 00:37

First of, Guest OS is Win XP Pro.
VB version is 1.3.8

Uhhm, I couldn't edit vboxdrv.
I got the following error messgage (translated from norwegian): It's not an usual file... wtf?? It didn't say anything else..
Well, the terminal told me this:

(gedit:23581): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
root@atle-laptop:~#

---------------------------------

You may need to edit /etc/udev/rules.d/40-permissions.rules The exact location and file name will vary with distro (the one above is for Ubuntu).

and change this line to
KERNEL=="vboxdrv", GROUP="vboxusers", MODE="0660"

I couldn't find any line to CHANGE, so I added the line..

Post by **bodhi.zazen** » 30. May 2007, 01:12

Hmm ...

No need to edit the vboxdrv directly

Code: Select all

sudo chown root:vboxusers /dev/vboxdrv

Then log-out and back in and re-try VirtualBox

If that fails, reboot.

Fjatle · Post by **Fjatle** » 30. May 2007, 16:39

Ok, now I did what you said. Even rebooted.. But still no sucsess..

Here is the error message:

Could not load the settings file '/home/atle/.VirtualBox/Machines/Xp/Xp.xml' (VERR_OPEN_FAILED).
FATAL ERROR: An exception occurred! Type:RuntimeException, Message:The primary document entity could not be opened. Id=/home/atle/.VirtualBox/Machines/Xp/Xp.xml
Location: '', line 0, column 0.

Result Code:
0x80004005
Component:
Machine
Interface:
IMachine {fd443ec1-0009-4f5b-9282-d72760a66916}

---------------------------------------------

any ideas?[/img]

Post by **bodhi.zazen** » 30. May 2007, 17:03

Who owns /home/atle/.VirtualBox/Machines/Xp/Xp.xml ?

Since you haev been running as root, perhaps you now have to change permissions of that file to your user :

Code: Select all

sudo chown atle:atle /home/atle/.VirtualBox/Machines/Xp/Xp.xml

Fjatle · Post by **Fjatle** » 30. May 2007, 18:09

Arrgh! Not even that did work

If this tells you anything, here is the first errormessage I get when I launch VB:

One oer more of the registered virtual hard disk, CD/DVD or floppy media are not currently accessible. As a result, you will not be able to operate virtual machines that use these media until they have becom accessible late.

Press OK to open the Virtual Disk Manager window and see what media are inaccessible, or press Ignore to ignore this message

Post by **bodhi.zazen** » 30. May 2007, 20:30

LOL

Well, click OK and lets see what disk/iso is not available

Did you move or delete something ? Rename a vdi ? move an iso ? ???

Fjatle · Post by **Fjatle** » 31. May 2007, 00:20

Yeah, when I click OK, it tells m it's the disk (vdi) wich my Guest OS is installed..
About deleting, renaming:

I did first install with a license that came with the computer (of course that didn't work since it detected too much new hardware (and did not allow me to activate))...
Anyhow, after that install, I left my computer without pluggin in the powercable (yeah, its a laptop), and it got shut down because of low battery.
When I then started VB, it had forgot all about my installation, even the virtual Harddrive it created.. But after a reinstallation (with another license of MS), and a properly shutdown of the physic computer, it has remembered my guest OS.... Ok, that was maybe a long useless story, but now you know

But still, what can make me access without the sudo VirtualBox (ohh, no errormessages when launching as sudo by the way)??