I did a system, VirtualBox, Vagrant update, and vagrant box update (which I tend to do quarterly) on our Vagrant machines which perform CI/CD operations. I have been using this particular box for quite some time in this manor with no issues. I have also confirmed the issue arises on a similar machine which uses the libvirt provider instead of virtualbox with a different windows server box that is available for the the libvirt provider. According to #13076, enabling OpenSSL Legacy Providers should resolve the issue as the newer Default Providers do not include MD4. This has been done on both host systems, but the results persist. Below are the full details.
I did a system, VirtualBox, Vagrant update, and vagrant box update (which I tend to do quarterly) on our Vagrant machines which perform CI/CD operations. I have been using this particular box for quite some time in this manor with no issues. I have also confirmed the issue arises on a similar machine which uses the libvirt provider instead of virtualbox with a different windows server box that is available for the the libvirt provider. According to #13076, enabling OpenSSL Legacy Providers should resolve the issue as the newer Default Providers do not include MD4. This has been done on both host systems, but the results persist. Below are the full details.
Debug output
https://gist.github.com/salderma/c56b768868344c27c5e2d930074d224a
Expected behavior
Vagrant should start the VM with out error, and in more complex cases move on to provisioning and such.
Actual behavior
Running
vagrant up
produces the following error after booting the VM:Reproduction information
Vagrant version
2.3.7-1
Vagrant Source:
https://apt.releases.hashicorp.com jammy/main amd64 Packages
VM Provider:
Host operating system
Ubuntu 22.04.2 LTS OpenSSL Providers (per #13076):
Guest operating system
gusztavvargadr/windows-server (v2102.0.2306)
Steps to reproduce
vagrant init gusztavvargadr/windows-server
vagrant up
Vagrantfile