Re: [vagrant-up] Windows 2012 R2

2020-02-24 Thread Rock Ade
Os it seems like vagrant is not compatible with Windows 2012 R2 Hyper as Vagrant requires Nested Virtualization and thats only available in Windows Server 2016 - https://github.com/hashicorp/vagrant/issues/11409 Is there a work around for this? On Tue, Feb 25, 2020 at 2:46 PM Rock Ade wrote:

Re: [vagrant-up] Windows 2012 R2

2020-02-24 Thread Rock Ade
Hi All Here is the Debug output, does vagrant work on Hyper-v on Windows 2012 R2? https://github.com/hashicorp/vagrant/issues/11409 On Tuesday, 25 February 2020 04:10:00 UTC+11, JP Toto wrote: > > Rock, > > Can you see the actual error that Powershell is throwing? More than likely > you're

Re: [vagrant-up] Windows 2012 R2

2020-02-24 Thread JP Toto
Rock, Can you see the actual error that Powershell is throwing? More than likely you're running into a privilege escalation issue. You can elevate your PowerShell scripts by passing the proper options: something.vm.provision "shell", privileged: "true", powershell_elevated_interactive: "true",

Re: [vagrant-up] Global triggers to run once in multi-machine setup

2020-02-24 Thread Andrii Senkovych
Hi, Brian Thanks, after setting VAGRANT_EXPERIMENTAL=typed_triggers your snippet worked! вт, 18 лют. 2020 о 19:12 Brian Cain пише: > > Hey there - > > You will need to make your trigger a command trigger. By default, globally > defined triggers run for each guest. If you wish for them to run