-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add back in Hyper-V provider #74
Comments
We've confirmed in the past that we will add a Hyper-V image but it isn't something we're working on just now. |
Windos
added a commit
to Windos/chocolatey-test-environment
that referenced
this issue
Jun 17, 2024
The hyper-v box can potentially have the max memory set lower than the desired amount of memory in the test environment Vagrantfile. Overring the max memory with `nil` enables any memory amount to be used. In testing, it also took longer than expected to for the box to get an IP address, and so the IP Address Timeout has been increased to give more time for this step to complete.
Windos
added a commit
to Windos/chocolatey-test-environment
that referenced
this issue
Jun 17, 2024
Add a section on using Hyper-V instead of VirtualBox, including a recommendation to prefer VirtualBox and linking to known limitations. This also updates the table of contents to include the newly added section as well as two sections added in a previous commit that were not added to the list.
Windos
added a commit
to Windos/chocolatey-test-environment
that referenced
this issue
Jun 17, 2024
The hyper-v box can potentially have the max memory set lower than the desired amount of memory in the test environment Vagrantfile. Overring the max memory with `nil` enables any memory amount to be used. In testing, it also took longer than expected to for the box to get an IP address, and so the IP Address Timeout has been increased to give more time for this step to complete.
Windos
added a commit
to Windos/chocolatey-test-environment
that referenced
this issue
Jun 17, 2024
Add a section on using Hyper-V instead of VirtualBox, including a recommendation to prefer VirtualBox and linking to known limitations. This also updates the table of contents to include the newly added section as well as two sections added in a previous commit that were not added to the list.
10 tasks
Windos
added a commit
to Windos/chocolatey-test-environment
that referenced
this issue
Jun 17, 2024
Add a section on using Hyper-V instead of VirtualBox, including a recommendation to prefer VirtualBox and linking to known limitations. This also updates the table of contents to include the newly added section as well as two sections added in a previous commit that were not added to the list.
pauby
pushed a commit
to Windos/chocolatey-test-environment
that referenced
this issue
Jun 20, 2024
Add a section on using Hyper-V instead of VirtualBox, including a recommendation to prefer VirtualBox and linking to known limitations. This also updates the table of contents to include the newly added section as well as two sections added in a previous commit that were not added to the list.
pauby
added a commit
that referenced
this issue
Jun 20, 2024
(#74)(ENGTASKS-3605) Update ReadMe and Vagrantfile in preperation for release of new box version with Hyper-V provider
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As of v3.0.0, the Hyper-V box was removed, so the Hyper-V provider no longer works as is.
Converting the Virtualbox image to Hyper-V is possible, but is an undocumented, potentially painful process.
Given that Virtualbox does not fully work when Hyper-V is enabled (which includes WSL 2, Windows Sandbox, and Credential/Device Guard), having a Hyper-V box would be useful and would reduce testing friction for some maintainers.
The text was updated successfully, but these errors were encountered: