Feature Request to hyper-v builder: add the ability to build VMs against a remote hyper-v host/cluster

[ghost]

This issue was originally opened by @giordyb as hashicorp/packer#5200. It was migrated here as a result of the Packer plugin split. The original body of the issue is below.

---

It would be really useful to have packer connect to a remote hyper-v host/cluster to provision virtual machines (like the vmware builder already does).

I think that this could be done relatively easily either by

• adding the "-ComputerName" parameter to the various cmdlets that are called to build the VM

• using invoke-command (with the relevant connection parameters) instead of running the powershell scripts locally. An added bonus to this would be that it would enable the Linux version of packer to provision against hyper-v by using the Linux version of powershell.

[tps125]

Mostly managing on-site infrastructure; this would be quite helpful.

[rismoney]

This issue has been lurking for years. Is there anyone who can help get this to the finish line?

[danonh]

Really appreciate if someone could take a look on this. The lack of this option does not allow us perform our CD process efficiently. Thanks.

[mikepayne02]

Really wish we could have a working solution for this. The terraform Hyper-V provider does this well, although there are definitely hurdles when it comes to SSL encryption.

[dataenligne]

I agree with the comments above.. this would be really useful, especially from a CD process perspective.

[andrew-jones-transvault]

I have several years experience with automted provisioning but I'm relatively new to the Packer and Vagrant. They appeared to be an ideal solution to providing the outcome we desired. However, in my ideal sceanrio I would prefer to use Packer, Vagrant and Ansible in containers on a separate Docker host (not hosted in WSL).

As Packer can provision VMs using WinRM, it seems a small step to allow it to control a remote Hyper-V hypervisor using the same technology.

So this get's my vote too.