clong / DetectionLab

Automate the creation of a lab environment complete with security tooling and logging best practices
MIT License
4.6k stars 980 forks source link

Issue while deploying Windows based Virtual Machines. #758

Closed kunalzs closed 2 years ago

kunalzs commented 2 years ago

Please verify that you are building from an updated Master branch before filing an issue : CONFIRMED

While deploying the Windows-based Virtual Machines I am getting the below error: I do not face any issues while deploying the logger VM.

PS D:\VM\DetectionLab\Vagrant>
PS D:\VM\DetectionLab\Vagrant> vagrant up dc
Bringing machine 'dc' up with 'vmware_desktop' provider...
==> dc: Cloning VMware VM: 'detectionlab/win2016'. This can take some time...
==> dc: Checking if box 'detectionlab/win2016' version '1.9' is up to date...
==> dc: Verifying vmnet devices are healthy...
==> dc: Preparing network adapters...
WARNING: The VMX file for this box contains a setting that is automatically overwritten by Vagrant
WARNING: when started. Vagrant will stop overwriting this setting in an upcoming release which may
WARNING: prevent proper networking setup. Below is the detected VMX setting:
WARNING:
WARNING:   ethernet0.pcislotnumber = "33"
WARNING:
WARNING: If networking fails to properly configure, it may require this VMX setting. It can be manually
WARNING: applied via the Vagrantfile:
WARNING:
WARNING:   Vagrant.configure(2) do |config|
WARNING:     config.vm.provider :vmware_desktop do |vmware|
WARNING:       vmware.vmx["ethernet0.pcislotnumber"] = "33"
WARNING:     end
WARNING:   end
WARNING:
WARNING: For more information: https://www.vagrantup.com/docs/vmware/boxes.html#vmx-allowlisting
==> dc: Starting the VMware VM...
An error occurred while executing `vmrun`, a utility for controlling
VMware machines. The command and output are below:

Command: ["start", "D:\\VM\\DetectionLab\\Vagrant\\.vagrant\\machines\\dc\\vmware_desktop\\4e9f8ed4-a4b1-4896-9db1-1fb9f987fe3d\\WindowsServer2016.vmx", "gui", {:notify=>[:stdout, :stderr], :timeout=>45}]

Stdout: Error: Unknown error

Stderr:

To fix the issue I used whitelisting option of the Vagrantfile (D:\VM\DetectionLab\Vagrant\Vagrantfile), re-installed Vmware workstation, Vagrant and all its dependencies but the error still persists. https://www.vagrantup.com/docs/providers/vmware/boxes#vmx-whitelisting

kunalzs commented 2 years ago

I want to update, that today I deployed the lab without any issue with Virtualbox.