Open masifpak opened 6 years ago
vSphere machinery (vsphere.conf) uses the vSphere API directly to communicate with vCenter/ESXi. ESX machinery (esx.conf) uses the libvirt abstraction layer. Use the vSphere machinery if you want to talk to vCenter.
I did but facing some problem like could not find host system. What user privilege should be? Did you try this? Can you share the configs. I used only these parameters. host = 10.0.0.1 port = 443 user = username_goes_here pwd = password_goes_here
What's the exact error you are getting?
2017-07-21 14:52:20,972 [lib.cuckoo.core.scheduler] INFO: Using "vsphere" machine manager with max_analysis_count=0, max_machines_count=0, and max_vmstartup_count=10 2017-07-21 14:52:21,095 [root] CRITICAL: CuckooCriticalError: Couldn't connect to vSphere host itsec@SNGPL-MAE:/opt/cuckoo$
If you are sure that the connectivity to the server is ok, and you have the correct username and password, then you can try to uncomment the unverified_ssl=on in vsphere.conf
The main difference in term of features is the possibility to use full memory dump with vsphere config, which is not the case with esx conf.
About the config file, I can confirm it works for me. You should uncomment unverified_ssl = on and check if the specified account has appropriate rights.
Thanks Yes it is working.
We have a scenario where we have deployed vcenter server to manage multiple ESX servers. To enjoy the independence of ESX server (What ever ESX server our Cuckoo and analysis machine is hosted), can we use user name and password of vcenter server for launching and stopping analysis machine.