Open Wenzel opened 4 years ago
This looks like we are being a bit aggressive with our locking strategy. Ideally we should check the lock based on intention and allow read-only actions to be allowed while preventing modification behaviors until the lock is released.
Is your feature request related to a problem? Please describe. I'm using
vagrant provision
to provision my VMs on Hyper-V, and some tasks are taking a long time to complete. I would like to monitor/interact with the VM in the meantime withvagrant ssh
.However, this isn't possible due to Vagrant locks.
I'm used to this workflow on Linux with the
libvirt
provider, which doesn't have a lock.Describe the solution you'd like Allow multiple
vagrant ssh
connection alongside avagrant provision
process already running on Hyper-V providerDescribe alternatives you've considered None
Additional context
I'm trying to expand a Vagrant project from Linux to Windows support with Hyper-V provider https://github.com/KVM-VMI/kvm-vmi/
Thanks !