VirtualBox 3.2.0 not working on 2010.1KDE

[The_Dadu]

Postby alanbcohen » Sun May 23, 2010 3:12 pm on the VirtualBox Forums
I have tried the 'all distributions' version of the 3.2.0 release unsuccessfully on a new install of PCLinuxOS 2010.1 (and all updates performed).
I get no results from selecting the 'Oracle VM VirtualBox' from the menus. When I tried to run it from the console, the old console command 'virtualbox' was not found. After browsing my /usr/bin directory, I found a 'VirtualBox' command and tried that from the concole with the following results:

    [alanbcohen@localhost ~]$ virtualbox
    bash: virtualbox: command not found
    [alanbcohen@localhost ~]$ VirtualBox
    VirtualBox: supR3HardenedVerifyDir: Cannot trust the directory "/opt/VirtualBox/components": group and/or other writable (st_mode=040775)

I need the USB connections into VM's, so the OSE version doesn't meet my needs. Short of reinstalling the previous version of VirtualBox, do you guys have any suggestions for getting the current one working, based on the error message?

[muungwana]

what does this command give you?

ls -dl /opt/VirtualBox/components

[The_Dadu]

[alanbcohen@localhost ~]$ ls -dl /opt/VirtualBox/components
drwxrwxr-x 2 root root 4096 2010-05-23 15:37 /opt/VirtualBox/components/
[alanbcohen@localhost ~]$

[muungwana]

it seem to want the permissions of the folder to be in a certain way but doesnt say which way, while on the terminal, log in as root and then type the following command and try again

chmod 755 /opt/VirtualBox/components/

edit:
looking at the error msg and it seems to require permissions to be 755(no writing permissions to group or other)

[Tuxfriend]

What does PCC (the PCLinuxOS Control Center) say? Is virtualboxusers in the user setup ticked, as in here:

[Old-Polack]

The_Dadu:

It doesn't really help if it does run. It's quite a bit slower than the previous Sun versions, and the USB part seems to be broken. Even thought the USB items are plugged in, turned on, and marked for use for each VM,



When the VM is running the USB devices are grayed out, and can't be selected or used.



This is the same with three VMs created so far. If you really need the USB, as I do for my scanner, (no Linux drivers available) You'd be better off with one of the previous Sun versions.

[Tuxfriend]

Version 3.2.2 is out and still no PCLinuxOS RPM to be seen:
http://www.virtualbox.org/wiki/Linux_Downloads

[DLWood]

Has anyone tried the "Mandriva" package?

[Texstar]

Has anyone tried the "Mandriva" package?

Doesn't work because they have different python and rpm version than PCLinuxOS.


I think we need to do a package like getopenoffice...

#su to root mode
su

# download VirtualBox
wget http://download.virtualbox.org/virtualbox/3.2.2/VirtualBox-3.2.2-62298-Linux_x86.run

#make file executable
chmod a+x VirtualBox-3.2.2-62298-Linux_x86.run

# run the installer
sh VirtualBox-3.2.2-62298-Linux_x86.run


# add users to group vboxusers
SYSUSERS=`cat /etc/passwd | grep "/bin/bash" |grep "[0-9][0-9][0-9]" |cut -d: -f1`
for idx in $SYSUSERS
 do INP1= usermod -a -G vboxusers,usb $idx; done

# create menu entry for PCLinuxOS

[Desktop Entry]
Encoding=UTF-8
Version=1.0
Name=Oracle VM VirtualBox
GenericName=Virtual Machine
Type=Application
Exec=VirtualBox
TryExec=VirtualBox
DocPath=file:///opt/VirtualBox/UserManual.pdf
Icon=VBox
Categories=Emulator;System;X-MandrivaLinux-MoreApplications-Emulators;
Comment=Run several virtual systems on a single host computer

[ceramics]

A package for VirtualBox similar to getopenoffice would be really helpful for those of us that need USB access and are afraid to "break" something with a bad install.  (getopenoffice is marvelous by-the-way!)

[The_Dadu]

Okay, an update for others who may encounter similar problems. I have been able to install VirtualBox 3.2.2 using the .run installer from the vendor's website.  I did have to manually add myself to the virtualboxusers group and use the chmod 755 command on the directories, as others have advised previously in this thread and on the VB forums. I have not gotten USB working on guest systems at all. The work-arounds I am using are:
- Printing; I've defined another system on my network as sharing it's printer and am using it via the Network. I've also attempted to define a PDF printer in each VM, which allows me to create pdf files that I can transfer to another machine for printing.
- USB drives; I've installed Guest Additions in each VM. Then defined my host /media folder as shared to each VM.  For most purposes, this has been sufficient although a nuisance.
- Palm device connectivity; no solution so far.  And since I have not got jpilot working, I am left synching my Palm to my wife's otherwise-no-longer-user netbook.

[menotu]

A package for VirtualBox similar to getopenoffice would be really helpful for those of us that need USB access and are afraid to "break" something with a bad install.  (getopenoffice is marvelous by-the-way!

+1
+1

I have not gotten USB working on guest systems at all.

Ditto re USB.

Apart from that USB issue it seems to be working okay.

Note: I read some of the PCLinuxOS users posts on the VBox forum (including Tex's) and he (VBox guy) suggested that their statistics showed only a few users downloaded the PCLinuxOS version and a decision was made to not have it anymore.

It begs the question, how many is  "only a few users"  as from my reading on this forum lots of people downloaded it (and most likely a fair few others who don't visit the forum very often)

[MCP]

Okay, an update for others who may encounter similar problems. I have been able to install VirtualBox 3.2.2 using the .run installer from the vendor's website.  I did have to manually add myself to the virtualboxusers group and use the chmod 755 command on the directories, as others have advised previously in this thread and on the VB forums. I have not gotten USB working on guest systems at all.

I also tried out the .run file.  However my results tend to be a bit different.  After telling synaptic to remove the previous ver.  I then ran the .run file in a terminal as root.  I did not have to add myself to virtualboxusers group since it was still there from the previous install.  I did not use chmod on the directories and it ran as it should.  I never did get usb to work. It looks like everything is set right but the device icons are all greyed out.  I don't know why my experience is so different from others but I did have the problem of my vm crashing.  Every time I tried to run Autocad it either locked up or caused the vm to abort.  So because of all this I downgraded to 3.1.8 which is very stable.  Could the problems I experienced with 3.2.2 be because of an incorrect install?

Just my 2 cents,
MCP

[robert21]

I followed texstars post and installed vbox fine. To get usb working, I followed the following from gregPCLOS on another post.

 I went through the whole USB thing myself with my printer and webcam a few months ago.  Finally what I discovered was that the usb and the user were not set to the same group.  So:

Go to PCC>System>Mangage users
Go to Options  in the menu at the top and uncheck "Filter system users"
Go to tab "Groups" and find in the list "usb" and right click,  then Edit.
Go to tab "Group users" and check your username to join the group.  Press OK and reboot.

Now the usb device in virtualbox when you start Windows will not be grayed out anymore.

There may be another better way of accomplishing the same, but that one works for me.

[Duvid]

Before I had read the post from gregPCLOS to solve this problem, I solved it another way it this way. I thought the usb was being greyed out due to write permissions. When I looked at virtualbox.desktop in  /opt/VirtualBox I found the permissions were for read only.
 While in  the /opt/VirtualBox directory, as root, in a terminal I typed chmod 666 virtualbox.desktop.This gives read and write permissions to the owner and the group. The greyed out USB devices were now available.