Vagrant 2.2.9 on Windows 10 performance

mrx · August 12, 2020, 7:40am

Hi there,

i’m new to vagrant so i do not have any experience and therefore asking if what i am seeing on my box is normal behaviour or if i have some issue with my setup i can work on.
I am using the latest vagrant release on a Windows 10 (2004) box with VirtualBox.
If i type in any vagrant command, it takes almost 3 minutes until anything happens.

May it be a vagrant init, up, or even just “vagrant” without any parameters, it takes 3 minutes to get any output.

I am not sure if this is normal behaviour, as it doesn’t seem so to me at first sight and i just need to be patient, or if this is an issue and if so, if there are any steps i can take to find out what is happening and preventing vagrant from performing faster.
The host box itself has quite some CPU cores as well as 32 gig of memory, all being idle and waiting for action so that should definitely not being an issue with hardware performance.

mrx · August 12, 2020, 2:17pm

Ok,

i found about the vagrant log levels and i see that various powershell commands are being run that take a lot of time, like finding out if the user is in the administrators role and getting the users groups.
I don’t know why they take so long, but it is definitely not normal. Being started in. privileged powershell vagrant up takes only a few seconds to respond.

elico · October 31, 2020, 4:16am

What powershell comands take so long?
I have had such an issue but not 3 minutes. I have had a scenario which at my LAN it takes a really short time while on a workplace it took at-least 5+ seconds to start showing that something is moving.

I located and found this bug report:

github.com/hashicorp/vagrant

Windows 10 vagrant is spending time in powershell doing something before actually doing anything useful

opened 10:48PM - 27 Oct 19 UTC

closed 09:22PM - 21 Apr 20 UTC

kozmaz87

host/windows needs-debug-gist

### Vagrant version PS C:\Users\Ubul> vagrant -v Vagrant 2.2.6 ### Host ope…rating system Windows 10 ### Guest operating system N/A ### Output ```ruby PS C:\Users\Ubul> Measure-Command {C:\HashiCorp\Vagrant\bin\vagrant.exe status} A Vagrant environment or target machine is required to run this command. Run `vagrant init` to create a new Vagrant environment. Or, get an ID of a target machine from `vagrant global-status` to run this command on. A final option is to change to a directory with a Vagrantfile and to try again. Days : 0 Hours : 0 Minutes : 0 Seconds : 9 Milliseconds : 750 Ticks : 97501033 TotalDays : 0.000112848417824074 TotalHours : 0.00270836202777778 TotalMinutes : 0.162501721666667 TotalSeconds : 9.7501033 TotalMilliseconds : 9750.1033 ``` ### Expected behavior immediate response with the help page ### Actual behavior 10 seconds just to get a help message ### Steps to reproduce 1. type vagrant On inspection it seems that vagrant is launching the ruby interpreter which keeps idling while the CPU is spending 100% in Powershell for seconds until vagrant finally executes. Same behaviour was observed during installation. It took forever to copy files.... Nothing else is slow on this machine. It has an NVME SSD and performs well otherwise.

And my current idea for a solution would be to change the dns client at:

github.com

hashicorp/vagrant/blob/74570802f326418f62442090dea9ad8377b052f3/lib/vagrant/util/platform.rb#L127


      
              admin_group = groups.detect do |g|
                g["Value"].to_s == "S-1-5-32-578" ||
                  (g["Value"].start_with?("S-1-5-21") && g["Value"].to_s.end_with?("-512"))
              end
          
              if admin_group
                return @_windows_hyperv_admin = true
              end
            end
          
            ps_cmd = "$x = (Get-VMHost).Name; if($x -eq [System.Net.Dns]::GetHostName()){ Write-Output 'true'}"
            output = Vagrant::Util::PowerShell.execute_cmd(ps_cmd)
            result = output == "true"
          
            return @_windows_hyperv_admin = result
          end
          
          # Checks if Hyper-V is enabled on the host system and returns true
          # if enabled.
          #
          # @return [Boolean]

to a an async one using this:
$x = (Get-VMHost).Name; if($x -eq [System.Net.Dns]::GetHostEntryAsync($x).Result.HostName){ Write-Output 'true'}

To debug it I have used the next powershell commands since the example in the mentioned bug report is not for powershell cli:

$env:VAGRANT_LOG="debug" 
$env:VAGRANT_LOG_TIMESTAMP="1"
vagrant status
Remove-Item Env:\VAGRANT_LOG
Remove-Item Env:\VAGRANT_LOG_TIMESTAMP