Vagrant 2.4.8 - import_vm.ps1 error - Cannot process argument transformation on parameter 'VM' (Hyper-V)

[urbanogilson]

Debug output

Debug Logs: https://gist.github.com/urbanogilson/714258afe608a8cec49767db215e39a0

Expected behavior

Create VM

Actual behavior

An error occurred, and abort VM creation

Reproduction information

Vagrant version

> vagrant -v
Vagrant 2.4.8

Host operating system

> Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsHardwareAbstractionLayer

WindowsProductName WindowsVersion OsHardwareAbstractionLayer
------------------ -------------- --------------------------
Windows 10 Pro     2009           10.0.22621.2506

Steps to reproduce

> vagrant up
Bringing machine 'vm' up with 'hyperv' provider...
==> vm: Verifying Hyper-V is enabled...
==> vm: Verifying Hyper-V is accessible...
==> vm: Importing a Hyper-V instance
    vm: Creating and registering the VM...
An error occurred while executing a PowerShell script. This error
is shown below. Please read the error message and see if this is
a configuration error with your system. If it is not, then please
report a bug.

Script: import_vm.ps1
Error:

Cannot process argument transformation on parameter 'VM'. Cannot convert the "VirtualMachine (Name = 'generic-rhel9-hyperv') [Id = 'e944984f-ae71-4e1f-9d49-11d168b687a6']" value of type "Microsoft.HyperV.PowerShell.VirtualMachine" to type "Microsoft.HyperV.PowerShell.VirtualMachine".

Vagrantfile

Vagrant.configure("2") do |config|
  config.vm.box = "generic/rhel9"
  config.vm.box_version = "4.2.16"
end

[urbanogilson]

Related: #13676 (comment)

[taru-garg-hashicorp]

Hi @urbanogilson,

Thanks for the detailed report on the issue, I tried to reproduce the issue, with the minimal Vagrantfile you provided in the issue, but it seems to be working for me correctly. Though I think it is worth pointing out, I only had access to Windows Server machine and not a Windows 10 Pro.

Thanks

[urbanogilson]

This issue appears to be intermittent and challenging to reproduce consistently. After several retries, it worked successfully once but remains unreliable. Another colleague is using version 2.4.8, and did not encounter this issue.

I’m happy to assist by collecting additional logs and providing further information to help identify the root cause of the problem.

[romdej]

I encountered the same issue with the exact setup (Vagrant 2.4.8 and Hyper-V provider).

After several hours of troubleshooting, I fixed the issue on my machine by reimporting the Hyper-V module in PowerShell using these two commands:

Remove-Module Hyper-V -Force -ErrorAction SilentlyContinue
Import-Module Hyper-V -Force

This resolved the issue for me. I suspect that upgrading PowerShell after installing Vagrant might be the root cause of the problem, as that's what happened in my case. Before that, I had tried several solutions, such as reinstalling Vagrant and restarting my computer, but these had no effect.

[andrew-jones-transvault]

For me, the issue lies in 6 of the functions in VagrantVM.psm1 (Set-VagrantVMMemory, Set-VagrantVMCPUS, Set-VagrantVMVirtExtensions, Set-VagrantVMAutoActions, Set-VagrantVMService and Set-VagrantVMSwitch). They all declare a parameter $VM of type Microsoft.HyperV.PowerShell.VirtualMachine. However, at least on my machine, there may be more than one instance of that type.

The fix for me was to Assembly-Qualify the name by changing it to:

[Microsoft.HyperV.PowerShell.VirtualMachine, Microsoft.HyperV.PowerShell.Objects]$VM

[mdewart-Centre]

For me, the issue lies in 6 of the functions in VagrantVM.psm1 (Set-VagrantVMMemory, Set-VagrantVMCPUS, Set-VagrantVMVirtExtensions, Set-VagrantVMAutoActions, Set-VagrantVMService and Set-VagrantVMSwitch). They all declare a parameter $VM of type Microsoft.HyperV.PowerShell.VirtualMachine. However, at least on my machine, there may be more than one instance of that type.

The fix for me was to Assembly-Qualify the name by changing it to:

[Microsoft.HyperV.PowerShell.VirtualMachine, Microsoft.HyperV.PowerShell.Objects]$VM

This resolved for me too, thanks!