VirtualBox problem

jonaskellens · 11-29-2008, 02:24 PM

[root@localhost Download]# rpm -iv VirtualBox-2.0.6_39765_fedora9-1.i386.rpm
Preparing packages for installation...
VirtualBox-2.0.6_39765_fedora9-1
chcon: can't apply partial context to unlabeled file `/usr/lib/virtualbox/VirtualBox'
chcon: can't apply partial context to unlabeled file `/usr/lib/virtualbox/VBoxSDL'
chcon: can't apply partial context to unlabeled file `/usr/lib/virtualbox/VBoxHeadless'
chcon: can't apply partial context to unlabeled file `/usr/lib/virtualbox/vboxwebsrv'

Creating group 'vboxusers'. VM users must be member of that group!

My 'normal' user jonas is member of the group vboxusers.

[jonas@localhost Download]$ VirtualBox
Wrong owner (0) of '/tmp/.vbox-jonas-ipc'.
Wrong owner (0) of '/tmp/.vbox-jonas-ipc'.
[jonas@localhost Download]$ su
Password:
[root@localhost Download]# VirtualBox
Qt WARNING: Qt: Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed

When I want to start VirtualBox via Applications>System Tools>VirtualBox I get :

Callee RC:
NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154)

Installation of the rpm should be very easy. I already succesfully installed VirtualBox 2.0.4. But when I install this newer version of VirtualBox I encounter many problems as posted above on my Fedora 9.

knudfl · 11-30-2008, 03:46 AM

I have errors too from version 2.0.6, different errors,
may be why I used "rpm -U" ( U = update, replace )

Code:

[root@localhost 1-download]# rpm -Uvh VirtualBox-2.0.6_39765_fedora9-1.i386.rpm
Forbereder...               ########################################### [100%]
   1:VirtualBox             ########################################### [100%]

Creating group 'vboxusers'. VM users must be member of that group!

No precompiled module for this kernel found -- trying to build one. Messages
emitted during module compilation will be logged to /var/log/vbox-install.log.

Success!

Stopping VirtualBox kernel module [     O.k.    ]

Code:

[knudfl@localhost ~]$ VirtualBox
VirtualBox: supR3HardenedMainGetTrustedMain: dlopen
("/usr/lib/virtualbox/VirtualBox.so",) failed: 
/usr/lib/virtualbox/VirtualBox.so: undefined symbol:
 _ZN7QRegionpLERK5QRect

So I just replaced it with my previous version, 2.0.2

( Kernel version = 2.6.25-14.fc9.i686 )
...

astrogeek · 12-01-2008, 02:53 AM

Quote:

Originally Posted by jonaskellens

[I][root@localhost Download]
[jonas@localhost Download]$ VirtualBox
Wrong owner (0) of '/tmp/.vbox-jonas-ipc'.
Wrong owner (0) of '/tmp/.vbox-jonas-ipc'.

When I want to start VirtualBox via Applications>System Tools>VirtualBox I get :
Callee RC: NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154)

I was having the same problem with VB 2.0.6 and Slackware, and found the solution as posted here.

Hope this helps.

jonaskellens · 12-01-2008, 04:40 AM

Quote:

Originally Posted by astrogeek

I was having the same problem with VB 2.0.6 and Slackware, and found the solution as posted here.

Hope this helps.

What I did till now : I changed the owner of the file /tmp/.vbox-jonas-ipc (as the error stated that there was an owner-problem).
Root was owner of that file and now jonas is.
I am now able to start up VirtualBox, but starting up a VM gives an error.

I will check out your solution !

EDIT :

I did not delete the file as said in the post, but I just changed group of the file :
[jonas@localhost ~]$ chgrp -R vboxusers .vbox-jonas-ipc/

This also helped and I am now able to start up via Applications>System Tools>VirtualBox

astrogeek · 12-02-2008, 01:14 AM

Quote:

Originally Posted by jonaskellens

I did not delete the file as said in the post, but I just changed group of the file :
[jonas@localhost ~]$ chgrp -R vboxusers .vbox-jonas-ipc/
This also helped and I am now able to start up via Applications>System Tools>VirtualBox

Excellent! Deleting it forces it to be re-created the next time you start VB as that user, with proper permissions, group and ownership - the same thing you did by directly changing ownership and groups - so I guess we arrived at the same end point.

This thread was one of few hints I found when looking for my own solution so thought I'd let you know what I found. Glad you have it going, enjoy!

[EDIT] After submitting above post I realized that you said that you could start from the menu but not that you could actually run a VM. I too hit that intermediate state because I had not restarted the daemons.

If you still cannot start a VM be sure to start vboxdrv and vboxnet scripts - probably under /etc/init.d in FC, probably want to add them to the boot tasks (/etc/rc.d/rc5.d/ maybe?). Good luck!
[/EDIT]

jonaskellens · 12-02-2008, 04:35 AM

Running a VM is no problem anymore also. So by changing the group of that directory and all what's in it, VirtualBox runs under normal user account and I can create and run VM's.

Just having some trouble with my host network card. But therefore I need to check the manual first.

Thanks for your reply !

himuinkol · 12-24-2008, 10:02 PM

Just delete the .vbox-youruserid-ipc directory within /tmp and then launched VirtualBox. It will run fine.

REF:

link - forums.virtualbox.org/viewtopic.php?p=43023&sid=0b137f0c952b145f81982f666948e557

Thanks
Himadri/APT/KOLKATA/INDIA