I don't think there's going to be any good resolution when using Windows2008r2 as the VM you're trying to spin up. On OsX I get around 3m30s or 4m when starting Windows2008r2, even when I allocate 4 cpus and 8G ram. Windows2012 takes only half the time.
I recommend the following:
- Allocate at least 2 cpus and 4G ram as with the following
--- driver: name: vagrant provider: virtualbox customize: cpus: 2 memory: 4192 provisioner: name: chef_zero verifier: name: pester platforms: - name: opentable/win-2008r2-standard-amd64-nocm os_type: windows transport: name: winrm provisioner: require_chef_omnibus: 12.5.1 - name: opentable/win-2012r2-standard-amd64-nocm os_type: windows transport: name: winrm provisioner: require_chef_omnibus: 12.5.1
kitchen createsparingly. When you have a running TK for your cookbook, keep it running until you've completed most of your cookbook development, using
kitchen converge; kitchen verifyafter your cookbook code updates.
- Comment here, https://github.com/test-kitchen/test-kitchen/issues/350, if you'd like to see a
1kitchen suspendcommand or equivalent
- You may want to investigate reducing 2008r2 boot times. I started to look at resources on that, found these:
The crux of the issue is that 2008r2 is just dog slow on startup in general, and also uses a delayed start to winrm.