last day (14 days later) » 

2:21 PM
0
Q: vboxmanage works only with sudo

Heihachii cant list all vms without sudo: vboxmanage list vms Shows nothing, but when i try this: sudo vboxmanage list vms It shows all vms. I've installed virtualbox with following command: sudo apt-get install virtualbox Is that normal behavior?

 
Probably not, especially if you created the VMs under your own user account (you didn't launch VirtualBox with sudo) and the VMs are in your VirtualBox VMs folder.
 
my VirtualBox VMs folder is under: /root/VirtualBox VMs
 
That's the problem. That folder is owned by root and you need sudo to see anything in the folder.
 
How can i install virtualbox as non-root user?
 
That's not the issue. The issue is that you likely used sudo virtualbox to launch VirtualBox, and so the VMs are in the root's home folder. Also, just to check, what user are you logged in as?
 
2:21 PM
yes, i've used sudo virtualbox because if i run just: virtualbox - when i close virtualbox it throws many errors in CLI. And i am logged as "alexander" (that's my username)
Hello, thanks for helping me
 
You're welcome
What are the errors when you run virtualbox under your username?
 
let me install it again 1 minute
* Stopping VirtualBox kernel modules [ OK ]
* Starting VirtualBox kernel modules * No suitable module for running kernel found
[fail]
invoke-rc.d: initscript virtualbox, action "restart" failed.
when i am installing virtualbox i am getting that error
can i ignore that
That's the errors i get after launching virtualbox without sudo: i.snag.gy/M2Q9Z.jpg
 
Those errors are just warnings from Qt, and you can ignore them.
 
what is Qt by the way?
 
As it is, those are related to the GUI side
 
2:27 PM
can't i turn them off?
 
Short version: Qt is a cross-platform GUI (and other things) C++ library.
 
well, but they are very annoying :)
what about: * Starting VirtualBox kernel modules * No suitable module for running kernel found
[fail]
is that ok?
 
You can probably use virtualbox 2&>/dev/null to discard the error output.
For the second error, no, that's not normal
 
can you advice
best method of installation virtualbox on ubuntu 14.04?
i thought one from native repository would be ok
 
There's a command to compile the virtualbox modules, but I don't remember the command. Let me check.
 
2:29 PM
are there any packages ready to use?
 
They should work.
Run sudo service vboxdrv setup.
 
ok let me reinstall everything from the ground
in order to remove everything related to Vbox now
i have to run sudo apt-get remove virtualbox-*
right?
 
If you are using the ones in the main Ubuntu repo, run sudo apt-get remove virtualbox.
 
well
can't you try to install virtualbox from ubuntu repo and see if you get similar errors while installing?
 
I had virtualbox installed some time back, but don't use it much. (I moved to KVM.)
 
2:33 PM
you had virtualbox from ubuntu repo?
 
yes
Just to check do you have linux-headers-generic installed? (Run apt-cache policy linux-headers-generic to find out.)
 
sec
linux-headers-generic:
Installed: 3.13.0.34.40
Candidate: 3.13.0.34.40
Version table:
*** 3.13.0.34.40 0
500 http://mirror.neolabs.kz/ubuntu/ trusty-updates/main amd64 Packages
500 http://mirror.neolabs.kz/ubuntu/ trusty-security/main amd64 Packages
100 /var/lib/dpkg/status
3.13.0.24.28 0
500 http://mirror.neolabs.kz/ubuntu/ trusty/main amd64 Packages
 
ok, looks good
 
can i ignore that error while installing virtualbox?
seems like everything works
 
The invoke-rc.d error?
 
2:40 PM
yes
 
If everything seems to work, then I suppose so, but run sudo service vboxdrv setup just o be sure.
*to
 
let me run it
alexander@SuperPC:~$ sudo service vboxdrv setup
vboxdrv: unrecognized service
 
hang on, I'll be offline for 10 minutes
 
ok
 
2:56 PM
When you were installing virtualbox, was there any output like the following?
vboxdrv:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/3.13.0-34-generic/updates/dkms/

vboxnetadp.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/3.13.0-34-generic/updates/dkms/

vboxnetflt.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
 
yes i had that
 
Then you're fine
The invoke-rc.d fail message is expected since you didn't have the kernel modules yet.
 
nice thanks
post an answer i will accept it
 
3:14 PM
Done
 
thanks, accepted :) bye
 
bye
 

last day (14 days later) »