search

cuckoosandbox / cuckoo

Cuckoo Sandbox is an automated dynamic malware analysis system
http://www.cuckoosandbox.org
Other
5.55k stars 1.71k forks source link

VBoxManage permission denied error #1148

Closed arulraji closed 7 years ago

arulraji commented 7 years ago

arul-3530@arul-3530:/opt/cuckoo$ python cuckoo.py 

                 _ 
____ _   _  ____| |  _ ___   ___

/ ) | | |/ ) |/ ) \ / _ \ ( (| || ( (| ( || | || | __)__/ ___)| _)_/ _/

Cuckoo Sandbox 2.0-dev www.cuckoosandbox.org Copyright (c) 2010-2015

Checking for updates... You are running a development version! Current stable is 2.0-rc1. 2016-10-31 21:13:43,330 [lib.cuckoo.core.scheduler] INFO: Using "virtualbox" as machine manager 2016-10-31 21:13:43,373 [lib.cuckoo.core.scheduler] INFO: Machinery name : virtualbox 2016-10-31 21:13:43,397 [root] CRITICAL: CuckooCriticalError: Error initializing machines: VBoxManage error listing installed machines: [Errno 13] Permission denied

please help anyone i got stuck with this permission denied error

Ads5740 commented 7 years ago

Is your user part of the VBoxManage group? For example:

_If you’re using VirtualBox, make sure the new user belongs to the “vboxusers” group (or the group you used to run VirtualBox):

$ sudo usermod -a -G vboxusers cuckoo_

gongqihunan commented 7 years ago

I think you should change your cuckoo version fisrtly for 2.0-rc1 have many bugs. 2.0-dev and see the docs

jbremer commented 7 years ago

Did you run any virtualbox-related commands with sudo? If so, you should probably remove all of those and create some new VMs.

arulraji commented 7 years ago

Thanks @Ads5740 & @gongqihunan

Problem solved by changing version from 2.0-dev to 2.0-rc1 and also small VBoxManage configuration mistake in virtualbox.conf file.

jbremer commented 7 years ago

Ok. Although I guess 2.0-dev should work just as fine with the configuration mistake resolved. Closing as resolved.