Overview of the Issue
When this post processor is used with artifacts from the 'artifice' post processor along with the provider_override="hyperv", the resulting .box output file does not seem to be valid.
Reproduction Steps
Prerequisite:
- following Hyper V vm source files :

- packer with the necessary plugins installed
- Execute : packer build
- Expected behaviour: a working vagrant box (.box file) is generated from the hyperv source files
- Observed behaviour:
-
An incomplete .box file file is generated (see attached file:packer_example_hyperv_amd64.box in the zip file ).
packer_example_hyperv_amd64.zip
-
No Hyper-v VM artifacts are present in the .box file. It only contains the vagrantfile and the metadata.json. Also the input
artifacts are being copied to 'c:\users' folder which was not expected behaviour.
Plugin and Packer version


Simplified Packer Buildfile
file: vagrant_post_processor_hyperv.pkr.hcl
required_plugins {
vagrant = {
version = "~> 1"
source = "github.com/hashicorp/vagrant"
}
}
}
source "null" "example" {
communicator = "none"
}
build {
sources = [
"source.null.example"
]
post-processors {
post-processor "artifice" {
files = [
"output-windows10/Virtual Hard Disks/VnV-W10-001.vhdx",
"output-windows10/Virtual Machines/4643F645-2EDB-4DD5-8E17-18A7DE59893C.vmcx",
"output-windows10/Virtual Machines/4643F645-2EDB-4DD5-8E17-18A7DE59893C.vmgs",
"output-windows10/Virtual Machines/4643F645-2EDB-4DD5-8E17-18A7DE59893C.VMRS",
"output-windows10/Virtual Machines/box.xml"
]
}
post-processor "vagrant" {
keep_input_artifact = true
provider_override = "hyperv"
}
}
}
Operating system and Environment details


Log Fragments and crash.log files
See attached log file from the CMD prompt ( packer_build_logt.txt) for the packer build:
packer_build_logt.txt
Overview of the Issue
When this post processor is used with artifacts from the 'artifice' post processor along with the provider_override="hyperv", the resulting .box output file does not seem to be valid.
Reproduction Steps
Prerequisite:
An incomplete .box file file is generated (see attached file:packer_example_hyperv_amd64.box in the zip file ).
packer_example_hyperv_amd64.zip
No Hyper-v VM artifacts are present in the .box file. It only contains the vagrantfile and the metadata.json. Also the input
artifacts are being copied to 'c:\users' folder which was not expected behaviour.
Plugin and Packer version
Simplified Packer Buildfile
file: vagrant_post_processor_hyperv.pkr.hcl
Operating system and Environment details
Log Fragments and crash.log files
See attached log file from the CMD prompt ( packer_build_logt.txt) for the packer build:
packer_build_logt.txt