LiviuArln
commented
10 years ago It seems it is a Powershell issue. I have version 2 on my machine and ConvertTo-Json is a version 3 cmdlet (whatever that means). I will press on.
Open LiviuArln opened 10 years ago
LiviuArln
commented
10 years ago It seems it is a Powershell issue. I have version 2 on my machine and ConvertTo-Json is a version 3 cmdlet (whatever that means). I will press on.
Hi guys,
I've been following your instructions on my Windows machine. Something goes wrong and I have "vagrant up" hanging.
These are the last lines in the ouput of "vagrant up --debug" :
INFO host: Detected: windows! INFO runner: Preparing hooks for middleware sequence... INFO runner: 2 hooks defined. INFO runner: Running action: #Vagrant::Action::Builder:0x36f3300 INFO warden: Calling IN action: #VagrantPlugins::HyperV::Action::CheckEnabled:0x27efa30 INFO interface: output: Verifying Hyper-V is enabled... INFO interface: output: ==> default: Verifying Hyper-V is enabled... ==> default: Verifying Hyper-V is enabled... INFO subprocess: Starting process: ["c:\Windows\System32\WindowsPowerShell\v1.0\/powershell.EXE", "-NoProfile", "-ExecutionPolicy", "Bypass", "&('d:\dev\Vagrant\embedded\gems\gems\vagrant-1.6.2\plugins\prov iders\hyperv\scripts\check_hyperv.ps1')", "-ErrorAction", "Stop"] DEBUG subprocess: Selecting on IO DEBUG subprocess: stderr: The term 'ConvertTo-Json' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path i s correct and try again. At D:\dev\Vagrant\embedded\gems\gems\vagrant-1.6.2\plugins\providers\hyperv\scripts\check_hyperv.ps1:10 char:38
DEBUG subprocess: stdout: ===Begin-Output===
===End-Output===
Can you help me make sense of this? Thank you very much.
Regards, Liviu