Please add Hyper-V configuration versions information in box.xml during vagrant post processor. about packer-plugin-vagrant HOT 4 OPEN

@fsdrw08
I am facing the same issue and I found a trace to what we could do, but I cant get past it.

On some builds it will create a Box which will start as configuration version 8.0 and some will start as 9.0.
I found that the information about which configuration version Hyper-V should use is only in the *.vmcx files.
On 'vagrant up', Vagrant searches for any configuration files in the 'Virtual Machines' folder. It will stop on the first valid one (no matter if it is a box.xml or *.vmcx).
https://github.com/hashicorp/vagrant/blob/5b501a3fb05ed0ab16cf10991b3df9d231edb5cf/plugins/providers/hyperv/action/import.rb#L31

*.vmcx are named after the UUID of the VM, which is randomly generated.
So: Some builds from packer create a Box with a structure inside the 'Virtual Machines' Folder like this:

• 'box.xml'
• 'F1C7C5C3-F7EA-45CA-8B87-119864E08A35.vmcx'
• 'F1C7C5C3-F7EA-45CA-8B87-119864E08A35.vmrs'

And some will be like this:

• '29A77F80-839B-488E-8233-9F2E16FE4E86.vmcx'
• '29A77F80-839B-488E-8233-9F2E16FE4E86.vmrs'
• 'box.xml'

Notice that some vmcx files start with a number and will be further up in a Folder listing.

Packer will read all artifact names inside the builder plugin and will return a list of files for the post-processors.
(https://github.com/hashicorp/packer-plugin-hyperv/blob/main/builder/hyperv/common/artifact.go#L27)
This means, renaming the VMCX files to start with a number or '_' in a post-processing step wont work, because packer already knows which files need to be exported.
The only thing left would be to set the range of the UUIDs which Hyper-V creates and let it only create ones that start with a number. And that's where I am stuck ...

from packer-plugin-vagrant.

@fsdrw08
I am facing the same issue and I found a trace to what we could do, but I cant get past it.

On some builds it will create a Box which will start as configuration version 8.0 and some will start as 9.0.
I found that the information about which configuration version Hyper-V should use is only in the *.vmcx files.
On 'vagrant up', Vagrant searches for any configuration files in the 'Virtual Machines' folder. It will stop on the first valid one (no matter if it is a box.xml or *.vmcx).
https://github.com/hashicorp/vagrant/blob/5b501a3fb05ed0ab16cf10991b3df9d231edb5cf/plugins/providers/hyperv/action/import.rb#L31

*.vmcx are named after the UUID of the VM, which is randomly generated.
So: Some builds from packer create a Box with a structure inside the 'Virtual Machines' Folder like this:

• 'box.xml'
• 'F1C7C5C3-F7EA-45CA-8B87-119864E08A35.vmcx'
• 'F1C7C5C3-F7EA-45CA-8B87-119864E08A35.vmrs'

And some will be like this:

• '29A77F80-839B-488E-8233-9F2E16FE4E86.vmcx'
• '29A77F80-839B-488E-8233-9F2E16FE4E86.vmrs'
• 'box.xml'

Notice that some vmcx files start with a number and will be further up in a Folder listing.

Packer will read all artifact names inside the builder plugin and will return a list of files for the post-processors.
(https://github.com/hashicorp/packer-plugin-hyperv/blob/main/builder/hyperv/common/artifact.go#L27)
This means, renaming the VMCX files to start with a number or '_' in a post-processing step wont work, because packer already knows which files need to be exported.
The only thing left would be to set the range of the UUIDs which Hyper-V creates and let it only create ones that start with a number. And that's where I am stuck ...

I notice this issue in these days too, I think it should make a improvement in vagrant side, vagrant should take vmcx config file as primary than the box.xml file

from packer-plugin-vagrant.

Hi, any update on this topic?

from packer-plugin-vagrant.

now I use terraform hyperv provider instead of Vagrant, Vagrant is dead

from packer-plugin-vagrant.