8000 Fix hyperv import failure due to lack of resources by chrisroberts · Pull Request #13670 · hashicorp/vagrant · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Fix hyperv import failure due to lack of resources #13670

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
May 21, 2025
Merged

Fix hyperv import failure due to lack of resources #13670

merged 1 commit into from
May 21, 2025

Conversation

chrisroberts
Copy link
Member

When importing a box that was built with more resources than is
available on the current system, import would fail. If the memory
and/or cpu values are set in the Vagrantfile configuration, provide
them when importing the guest. This allows the values to be modified
prior to registering the new guest preventing a resource unavailability
error.

Fixes #12180

@chrisroberts
Fix hyperv import failure due to lack of resources
6a0f875 
When importing a box that was built with more resources than is
available on the current system, import would fail. If the memory
and/or cpu values are set in the Vagrantfile configuration, provide
them when importing the guest. This allows the values to be modified
prior to registering the new guest preventing a resource unavailability
error.

Fixes #12180
@chrisroberts chrisroberts requested a review from a team as a code owner May 21, 2025 01:11
@chrisroberts chrisroberts merged commit 849591b into main May 21, 2025
10 checks passed
@chrisroberts chrisroberts deleted the fix-hyperv-diff-import branch May 21, 2025 16:25
@zhindes
Copy link
zhindes commented May 22, 2025

@chrisroberts - this seems to have broken hyperv xml import because New-VagrantVM forwards to New-VagrantVMXML using @PSBoundParameters, but your new parameters ($Memory etc) weren't added to the XML-specific version of the function.

@chrisroberts chrisroberts mentioned this pull request May 22, 2025
Merged
@smbd smbd mentioned this pull request May 27, 2025
Open
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 22, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

vagrant up with Hyper-V fails when box was packaged from a VM that has more resources than available on current Machine.
2 participants
@chrisroberts @zhindes
0