LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 05-18-2014, 02:38 AM   #1
Don Graham
Member
 
Registered: Apr 2014
Location: Bangsaen Beach, Thailand
Distribution: Ubuntu 15.04 & Mint 17.1
Posts: 125

Rep: Reputation: Disabled
VMbox


I am trying to run a newly installed Window 7. When I click start I get this window:

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing

'/etc/init.d/vboxdrv setup'

as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.

Because I am so new to Ubuntu 14.04 or anything Linux. I have no idea what to type into my terminal to make the corrections needed. Please help!
 
Old 05-18-2014, 07:42 AM   #2
273
LQ Addict
 
Registered: Dec 2011
Location: UK
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 6,734

Rep: Reputation: 1918Reputation: 1918Reputation: 1918Reputation: 1918Reputation: 1918Reputation: 1918Reputation: 1918Reputation: 1918Reputation: 1918Reputation: 1918Reputation: 1918
You could try running:
Code:
sudo apt-get install virtualbox-dkms
 
Old 05-18-2014, 10:10 AM   #3
Don Graham
Member
 
Registered: Apr 2014
Location: Bangsaen Beach, Thailand
Distribution: Ubuntu 15.04 & Mint 17.1
Posts: 125

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by 273 View Post
You could try running:
Code:
sudo apt-get install virtualbox-dkms
The results:

don@don-CQ1270L:~$ sudo apt-get install virtualbox-dkms
[sudo] password for don:
Reading package lists... Done
Building dependency tree
Reading state information... Done
virtualbox-dkms is already the newest version.
virtualbox-dkms set to manually installed.
The following packages were automatically installed and are no longer required:
firefox-locale-th kde-l10n-engb kde-l10n-th libappindicator1 libgnome-menu2
libindicator7 linux-headers-generic linux-image-generic python-appindicator
python-gmenu
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
don@don-CQ1270L:~$
 
Old 05-18-2014, 10:16 AM   #4
273
LQ Addict
 
Registered: Dec 2011
Location: UK
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 6,734

Rep: Reputation: 1918Reputation: 1918Reputation: 1918Reputation: 1918Reputation: 1918Reputation: 1918Reputation: 1918Reputation: 1918Reputation: 1918Reputation: 1918Reputation: 1918
You could try:
Code:
sudo apt-get install --reinstall virtualbox-dkms
Or, failing that you could run the command suggested in the error:
Code:
sudo /etc/init.d/vboxdrv setup
DKMS ought to take care of things but I have known things to go awry and having to manually run the latter command to get VirtualBox working.
 
Old 05-18-2014, 02:00 PM   #5
dijetlo
Senior Member
 
Registered: Jan 2009
Location: RHELtopia....
Distribution: Solaris 11.2/Slackware/RHEL/
Posts: 1,491
Blog Entries: 2

Rep: Reputation: Disabled
Quote:
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem
Code:
 lsmod | grep -i vboxdrv
If the output includes vboxdrv, it's loaded.

If it's loaded, and you think it's a permission problem, you can always check the module directory which on my machine is in /proc/modules (sorry, /usr/lib/3.xx.xx/kernel/drivers/firmware/*.ko) and see if the permissions are significantly different than say, button or microcode. If it is, **back a copy of the existing module out to an alternative location preserving file permissions**

Unload the module with modprobe.
Change the vboxsdrv's file permissions (the original, not the copy). Reload the module, praying fervently for mercy because when things go bad down at the kernel.... it's a kind of bad that you probably have never experienced.
Let's just say, you should have your install disks handy when you do this....or at least the rescue thumb drive..
Didn't make a rescue thumb drive?
Do that before you even read the man page for lsmod.

If it's not loaded, you can fix that with modprobe to, but in the interest of not having someone say to themselves " I can just swap around kernel modules whenever I feel like it! Kewl!" and the inevitable "why did you tell me to brick my laptop!!!" recriminations, let's hold off on a deeper exploration of that, for the moment.

FYI, if it's there, it's probably not the file permissions, those are set automatically at install.

A final note: It would seem to me that if the kernel were to load a virtual driver module, it wouldn't be at boot, it would be at the instantiation of vbox (otherwise it's just chugging along in the kernel, gumming up the works). You might try to find out how and where vbox makes the modprobe call and make sure that it's righteous voodoo for your distro.

Last edited by dijetlo; 05-18-2014 at 02:24 PM. Reason: Accuracy
 
Old 05-18-2014, 08:22 PM   #6
Don Graham
Member
 
Registered: Apr 2014
Location: Bangsaen Beach, Thailand
Distribution: Ubuntu 15.04 & Mint 17.1
Posts: 125

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by 273 View Post
You could try:
Code:
sudo apt-get install --reinstall virtualbox-dkms
Or, failing that you could run the command suggested in the error:
Code:
sudo /etc/init.d/vboxdrv setup
DKMS ought to take care of things but I have known things to go awry and having to manually run the latter command to get VirtualBox working.
The re-install seemed to work. When I tried to install windows 7-32 I was told I need to install some driver. What drivers? I am installing off a Microsoft install disk. When I tried to install window 7-64 I get this:

Failed to open a session for the virtual machine Don's 64bit OS.
VT-x is disabled in the BIOS. (VERR_VMX_MSR_VMXON_DISABLED).

Well it looks like VM is not fix. It is lock up (frozen). Can not close or do anything.
 
Old 05-18-2014, 09:10 PM   #7
dijetlo
Senior Member
 
Registered: Jan 2009
Location: RHELtopia....
Distribution: Solaris 11.2/Slackware/RHEL/
Posts: 1,491
Blog Entries: 2

Rep: Reputation: Disabled
Quote:
VT-x is disabled in the BIOS.
Turn on hardware virtualization in your bios settings. You're trying to run a 64 bit OS and it looks like virtualbox needs the accelerator.
A good test would be to load the 32 bit version and see if it works.

Last edited by dijetlo; 05-18-2014 at 09:15 PM.
 
Old 05-18-2014, 10:58 PM   #8
Don Graham
Member
 
Registered: Apr 2014
Location: Bangsaen Beach, Thailand
Distribution: Ubuntu 15.04 & Mint 17.1
Posts: 125

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by dijetlo View Post
Turn on hardware virtualization in your bios settings. You're trying to run a 64 bit OS and it looks like virtualbox needs the accelerator.
A good test would be to load the 32 bit version and see if it works.
Well, I have installed windows 7 32 bit and 64 bit and I also installed Zorin 8 Ult on the VM. None of them will start. My desktop has Ubuntu 14 and Zorin Lite installed on it. Thinking like a windows user. I concluded that my be my VMbox is crouped? In the world of windows. I would dump the bad program and install a new one. I tried that using the Ubuntu software center. The results turned out to be, nothing changed. It was as if I had done nothing at all. Then I booted into Zorin and then did the same operation. Nothing changed. Then it dawned on me that both systems are using a common resource (one partition hold files that support both OS)Daaaaa! So the question is. How do I delete VMbox from my computer and re-install a new and clean VMbox. I am taking about removing any and all trace of VMbox. And then doing a new INTERNET download into the Ubuntu software center, and re-installing from there. If it can not be done that way. Then I guess I am going to do it from my Terminal. Which of course I have no idea how to do. LOL!!!
 
Old 05-19-2014, 01:02 AM   #9
dijetlo
Senior Member
 
Registered: Jan 2009
Location: RHELtopia....
Distribution: Solaris 11.2/Slackware/RHEL/
Posts: 1,491
Blog Entries: 2

Rep: Reputation: Disabled
A couple of thoughts, Don.

While I definitely use the uninstall/reinstall strategy with Microsoft, because it works, it doesn't seem to pay the same dividends in the Linux world.
I don't mean to start a flame war, but the first thing I'd do is open a terminal (Pfft, who am I kidding? I'm a Slackhead Zombie I've always got an open terminal) and type
Code:
virtualbox
What's going to happen is that terminal is going to try to instantiate your virtualbox app, and as it does so it's going to capture system messages. If you've got a bad install... you'll probably get to read about it in the terminal. Often, if the install is fine but the app is mis-configured, you'll see the app searching for things it can't find. In any case we'll know more than we know now and all you gotta do is open a terminal and call the app.
(Edit: I have no idea how to open a terminal in gnome. The Benevolent Dictator for Life issued his famous "No Consorting with Garden Statuary" fatwa several years ago and the entire Slackhead Zombie Nation went KDE or some variety of openbox. I don't even use it on my RHEL boxes, it's unclean.)
Assuming it spawns the vbox app without totally freaking out, the next thing I'd do is open a second terminal, su to root and run that command I showed you up above ( I would then immediately exit the root account). That will let us know if the modules loaded.
If the terminal tells us the app instantiates without disabling the functionality you need and the appropriate libraries and module are loaded, then I'd try to load an image through the GUI. The little terminal that you called the application from originally will just keep capturing system messages, so you can watch what kind of breakdown virtualbox is having over loading something easy (go 32 bit to start with, 16 bit if you can find a known good image, we just want the bear to dance a little, he don't gotta waltz right out of the box.)
If you can capture the data and post it, that'd be a real help.
We know Ubuntu can run this stuff 'cause other Ubuntunites report they're running it and they can't all be lyin' (that Distro bigotry thing is foolishness) so we're probably just a library or configuration setting or two away from you playing the latest sega games from the late 1990s.
Progress!
(kidding, virtualization is something everybody should be thinking about/looking at, it looks like it's going to be a big part of our future, think of the trouble your having now as a learning experience that will make you all the more valuable later... because it's true)

Last edited by dijetlo; 05-19-2014 at 02:00 AM.
 
Old 05-19-2014, 01:48 AM   #10
Don Graham
Member
 
Registered: Apr 2014
Location: Bangsaen Beach, Thailand
Distribution: Ubuntu 15.04 & Mint 17.1
Posts: 125

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by dijetlo View Post
A couple of thoughts, Don.

While I definitely use the uninstall/reinstall strategy with Microsoft, because it works, it doesn't seem to pay the same dividends in the Linux world.
I don't mean to start a flame war, but the first thing I'd do is open a terminal (In truth, I'm a slackhead Zombie I've always got an open terminal) and type
Code:
virtualbox
What's going to happen is that terminal is going to try to instantiate your virtualbox app, and as it does so it's going to capture system messages. If you've got a bad install... you'll probably get to read about it in the terminal. Often, if the install is fine but the app is mis-configured, you'll see the app searching for things it can't find. In any case we'll know more than we know now and all you gotta do is open a terminal and call the app.
(Edit: I have no idea how to open a terminal in gnome. The Benevolent Dictator for Life issued his famous "No Consorting with Garden Statuary" fatwa several years ago and the entire Slackhead Zombie Nation went KDE or some variety of openbox. I don't even use it on my RHEL boxes, it's unclean.)
Assuming it spawns the vbox app without totally freaking out, the next thing I'd do is open a second terminal, su to root and run that command I showed you up above ( I would then immediately exit the root account). That will let us know if the modules loaded.
If the terminal tells us the app instantiates without disabling the functionality you need and the appropriate libraries and module are loaded, then I'd try to load an image through the GUI. The little terminal that you called the application from originally will just keep capturing system messages, so you can watch what kind of breakdown virtualbox is having over loading something easy (go 32 bit to start with, 16 bit if you can find a known good image, we just want the bear to dance a little, he don't gotta waltz right out of the box.)
If you can capture the data and post it, that'd be a real help.
We know Ubuntu can run this stuff 'cause other Ubuntunites report they're running it and they can't all be lyin' (that Distro bigotry thing is foolishness) so we're probably just a library or configuration setting or two away from you playing the latest sega games from the late 1990s.
Progress!
(kidding, virtualization is something everybody should be thinking about/looking at, it looks like it's going to be a big part of our future, think of the trouble your having now as a learning experience that will make you all the more valuable later... because it's true)
Here is what I het when I try to open any of the OS's i have installed in my VMbox:

Failed to open a session for the virtual machine Zorin Ult.
VT-x is disabled in the BIOS. (VERR_VMX_MSR_VMXON_DISABLED).

Failed to open a session for the virtual machine Don's 64bit OS.
VT-x is disabled in the BIOS. (VERR_VMX_MSR_VMXON_DISABLED).

Windows 7-32 opens to a black screen and says it has no boot able source. Here is something strange, In my VM list of installed OS's. Now there is windows XP on the list. I have know idea were that came from. I do have an XP disk but I have not used it in six years.

This is what was in the Terminal:

don@don-CQ1270L:~$ virtualbox
Qt WARNING: void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "S&tart" under id 16
Qt WARNING: void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "&Pause" under id 17
Qt WARNING: void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "&Reset" under id 18
Qt WARNING: void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "D&iscard saved state..." under id 24
Qt WARNING: void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "Re&fresh..." under id 25
Qt WARNING: void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "Show in File Manager" under id 27
Qt WARNING: void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "Create Shortcut on Desktop" under id 28
don@don-CQ1270L:~$ open
Couldn't get a file descriptor referring to the console
don@don-CQ1270L:~$

Last edited by Don Graham; 05-19-2014 at 02:02 AM.
 
Old 05-19-2014, 02:50 AM   #11
dijetlo
Senior Member
 
Registered: Jan 2009
Location: RHELtopia....
Distribution: Solaris 11.2/Slackware/RHEL/
Posts: 1,491
Blog Entries: 2

Rep: Reputation: Disabled
Quote:
VT-x is disabled in the BIOS. (VERR_VMX_MSR_VMXON_DISABLED).
Did you go into the bios and change the settings to enable hardware acceleration?
EDIT: Trusted execution set to off and TPM set to on (virtual box appears to have determined the fix for this issue 3 years ago, I do love a good mailing list...)
Did you shut the machine down (power off/cold boot) and restart it after making the change?
IF so, in the vbox gui go to System->acceleration-> look for something that reads like VtxAmdV. If the checkbox is checked, un-check it and restart.

Quote:
Qt WARNING: void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "Create Shortcut on Desktop" under id 28
That's just QT whining, nothing to be concerned about unless it starts in about the database. The good news is no system messages suggests there are no major problems with your virtualbox install, other than the bios setting.
Quote:
I have know idea were that came from. I do have an XP disk but I have not used it in six years.
It's probably just confused about what it's looking at in the repository. If, in fact it is windows XP, you'll be famous for having discovered how to install virtual images via osmosis.
Edit: Most likely though, that problem will go away when we get the settings and bios config right.
Quote:
Couldn't get a file descriptor referring to the console
I just use a redirect or pipe it into cat and toss it in a text file.

Edit: because you seem interested
Code:
 virtualbox > vlog 2>&1

Last edited by dijetlo; 05-19-2014 at 03:29 AM.
 
Old 05-19-2014, 04:36 AM   #12
Don Graham
Member
 
Registered: Apr 2014
Location: Bangsaen Beach, Thailand
Distribution: Ubuntu 15.04 & Mint 17.1
Posts: 125

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by dijetlo View Post
Did you go into the bios and change the settings to enable hardware acceleration?
EDIT: Trusted execution set to off and TPM set to on (virtual box appears to have determined the fix for this issue 3 years ago, I do love a good mailing list...)
Did you shut the machine down (power off/cold boot) and restart it after making the change?
IF so, in the vbox gui go to System->acceleration-> look for something that reads like VtxAmdV. If the checkbox is checked, un-check it and restart.


That's just QT whining, nothing to be concerned about unless it starts in about the database. The good news is no system messages suggests there are no major problems with your virtualbox install, other than the bios setting.

It's probably just confused about what it's looking at in the repository. If, in fact it is windows XP, you'll be famous for having discovered how to install virtual images via osmosis.
Edit: Most likely though, that problem will go away when we get the settings and bios config right.
I just use a redirect or pipe it into cat and toss it in a text file.

Edit: because you seem interested
Code:
 virtualbox > vlog 2>&1
"Did you go into the bios and change the settings to enable hardware acceleration?"

I have no idea how to access Basic Input / Output System (BIOS) to make the recommended changes.

"in the vbox gui go to System->acceleration-> look for something that reads like VtxAmdV."

I do not know how to do this ether,I am starting to feel really stupid. LOL!!!...unedgeamcated

I have removed all the OS's I had in my vbox. So nothing will foil up any changes we might make. I will put some back latter.

Last edited by Don Graham; 05-19-2014 at 04:40 AM.
 
Old 05-19-2014, 05:15 AM   #13
dijetlo
Senior Member
 
Registered: Jan 2009
Location: RHELtopia....
Distribution: Solaris 11.2/Slackware/RHEL/
Posts: 1,491
Blog Entries: 2

Rep: Reputation: Disabled
Hey Don,

Quote:
have no idea how to access Basic Input / Output System (BIOS)
Let's begin by figuring out which bios you have, after I know that, I can probably give you accurate instructions on how to get into it.
EDIT:
Mad props to Soadyheid for the correction, Thanks for the save, dude!

As root:
Code:
dmidecode | grep -A 35 -i "bios inf"
#or if you want to save a copy of the bios information to your home directory
dmidecode | grep -A 35 -i "bios inf" > $HOME/bios.txt
EDIT
Quote:
have removed all the OS's I had in my vbox. So nothing will foil up any changes we might make. I will put some back latter.
Good thinking, if I'd a thought of it, I'd a told you to do just that.
BTW, there is nothing dumb about not knowing something, it's only dumb if you don't ask. The only test in linux (not counting the RHEL) is did you get it done?

Last edited by dijetlo; 05-19-2014 at 07:12 PM.
 
Old 05-19-2014, 05:34 AM   #14
Don Graham
Member
 
Registered: Apr 2014
Location: Bangsaen Beach, Thailand
Distribution: Ubuntu 15.04 & Mint 17.1
Posts: 125

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by dijetlo View Post
Hey Don,


Let's begin by figuring out which bios you have, after I know that, I can probably give you accurate instructions on how to get into it.
As root:
Code:
dmicode | grep -A 35 -i "bios inf"
#or if you want to save a copy of the bios information to your home directory
dmicode | grep -A 35 -i "bios inf" > $HOME/bios.txt
BTW, there is nothing dumb about not knowing something, it's only dumb if you don't ask. The only test in linux (not counting the RHEL BS) is did you get it done?
As you can see I tried different combos, but end up with zip:

don@don-CQ1270L:~$ dmicode | grep -A 35 -i "bios inf"
dmicode: command not found
don@don-CQ1270L:~$ open
Couldn't get a file descriptor referring to the console
don@don-CQ1270L:~$ dmicode | grep -A 35 -i "bios inf" > $HOME/bios.txt
dmicode: command not found
don@don-CQ1270L:~$ dmicode | grep -A 35 -i "bios inf"
dmicode: command not found
don@don-CQ1270L:~$ #or if you want to save a copy of the bios information to your home directory
don@don-CQ1270L:~$ dmicode | grep -A 35 -i "bios inf" > $HOME/bios.txt
dmicode: command not found
don@don-CQ1270L:~$

Last edited by Don Graham; 05-19-2014 at 05:35 AM. Reason: spelling
 
Old 05-19-2014, 05:47 AM   #15
dijetlo
Senior Member
 
Registered: Jan 2009
Location: RHELtopia....
Distribution: Solaris 11.2/Slackware/RHEL/
Posts: 1,491
Blog Entries: 2

Rep: Reputation: Disabled
Are you logged in on your system as the superuser? Root?

Only his chi-kung is mighty enough to weild that ancient voodoo.....

Correction: We got voodoo for every chi-kung around here....
It's just not every chi-kung can command every piece of voodoo, and when you make a system call that's beyond your users normal rights, the shell plays dumb and says "Command Not Found".

Last edited by dijetlo; 05-19-2014 at 05:58 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Oracle vmbox no VBoxManage on host windows 7 sehgalnamit Linux - Virtualization and Cloud 1 02-18-2011 07:58 PM
VMBox Locks Up wsduvall Linux - Software 8 03-28-2009 01:30 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 11:08 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration