virtual box not starting

[anwar]

i have instaled virtual box in fe 17 iam trying to run from terminal it is showing folowing error how to resolve this

[anwar@localhost ~]$ virtualbox
VirtualBox: supR3HardenedMainGetTrustedMain: dlopen("/usr/lib/virtualbox/VirtualBox.so",) failed: libaudio.so.2: cannot open shared object file: No such file or directory

[Irfan_A]

Hi...
What is the error message if you run VirtualBox by clicking the VirtualBox logo and after clicking "Start" button?

[glennzo]

It appears that you may need to install nas-libs.

[glenn@script-test script>$ yum provides */libaudio.so.2
Loaded plugins: langpacks, presto, refresh-packagekit
nas-libs-1.9.3-2.fc17.i686 : Run-time libraries for NAS
Repo        : fedora
Matched from:
Filename    : /usr/lib/libaudio.so.2



nas-libs-1.9.3-2.fc17.x86_64 : Run-time libraries for NAS
Repo        : fedora
Matched from:
Filename    : /usr/lib64/libaudio.so.2



[glenn@script-test script>$ yum info nas-libs
Loaded plugins: langpacks, presto, refresh-packagekit
Available Packages
Name        : nas-libs
Arch        : i686
Version     : 1.9.3
Release     : 2.fc17
Size        : 76 k
Repo        : fedora
Summary     : Run-time libraries for NAS
URL         : http://radscan.com/nas.html
License     : Public Domain
Description : Run-time libraries for NAS.

Name        : nas-libs
Arch        : x86_64
Version     : 1.9.3
Release     : 2.fc17
Size        : 75 k
Repo        : fedora
Summary     : Run-time libraries for NAS
URL         : http://radscan.com/nas.html
License     : Public Domain
Description : Run-time libraries for NAS.

[glenn@script-test script>$ yum info NAS
Loaded plugins: langpacks, presto, refresh-packagekit
Available Packages
Name        : nas
Arch        : x86_64
Version     : 1.9.3
Release     : 2.fc17
Size        : 194 k
Repo        : fedora
Summary     : The Network Audio System (NAS)
URL         : http://radscan.com/nas.html
License     : Public Domain
Description : In a nutshell, NAS is the audio equivalent of an X display  server.
            : The Network Audio System (NAS) was developed by NCD for playing,
            : recording, and manipulating audio data over a network.  Like the
            : X Window System, it uses the client/server model to separate
            : applications from the specific drivers that control audio input
            : and output devices.
            : Key features of the Network Audio System include:
            :     o  Device-independent audio over the network
            :     o  Lots of audio file and data formats
            :     o  Can store sounds in server for rapid replay
            :     o  Extensive mixing, separating, and manipulation of audio data
            :     o  Simultaneous use of audio devices by multiple applications
            :     o  Use by a growing number of ISVs
            :     o  Small size
            :     o  Free!  No obnoxious licensing terms

Executing

yum provides */libaudio.so.2

reveals that it is part of nas-libs, so to get libaudio.so.2 you will need to install nas-libs

yum install nas-libs

[anwar]

i have instaled the nas-lib package after that i have run vbox in terminal it showing folowing error


VirtualBox: supR3HardenedMainGetTrustedMain: dlopen("/usr/lib/virtualbox/VirtualBox.so",) failed: /lib/libQtOpenGL.so.4: undefined symbol: _ZNK14QWidgetPrivate17hasHeightForWidthEv

[glennzo]

Try running

PHP Code:

/etc/init.d/vboxdrv setup 


and then try starting VirtualBox again.

[stevea]

I don't mean to derail, but I think it's time for Vbox uses to reconsider KVM.
It's free open source, it's supported under Linux and it doesn't bollux up the kernel regularly.

The most recent KVMs use spice/qlx/channel drivers for video, and tho' I haven't run any tests is a LOT better/faster than the older virtual vid implementations. 'virt-manager' isn't fancy, but it's a very functional VM config tool. These address some of the past KVM vs VBox shortcomings. Also sVirt promises to add some really nice inter-VM/Host security.

Obviously there are cases where VBox is still needed & useful - not suggesting otherwise.

[anwar]

i have run /etc/init.d/vboxdrv setup but it showing bash: /etc/init.d/vboxdrv: No such file or directory

can i reinstall programe

[ah7013]

Originally Posted by stevea

I don't mean to derail, but I think it's time for Vbox uses to reconsider KVM.
It's free open source, it's supported under Linux and it doesn't bollux up the kernel regularly.

The most recent KVMs use spice/qlx/channel drivers for video, and tho' I haven't run any tests is a LOT better/faster than the older virtual vid implementations. 'virt-manager' isn't fancy, but it's a very functional VM config tool. These address some of the past KVM vs VBox shortcomings. Also sVirt promises to add some really nice inter-VM/Host security.

Obviously there are cases where VBox is still needed & useful - not suggesting otherwise.

Agreed. Oh and look, my kernel isn't tainted

[andrew@vmhost1 ~]$ /sbin/lsmod | grep kvm
kvm_intel             132417  66 
kvm                   409194  1 kvm_intel
[andrew@vmhost1 ~]$ cat /proc/sys/kernel/tainted 
0

---------- Post added at 01:31 AM ---------- Previous post was at 01:30 AM ----------

Originally Posted by anwar

i have run /etc/init.d/vboxdrv setup but it showing bash: /etc/init.d/vboxdrv: No such file or directory

can i reinstall programe

What method did you use to install virtualbox?

[glennzo]

+1 for stevea's comment. VirtualBox has become a real PITA to maintain. I don't use it anymore.