Limit Range of UUID for new VMs (Vagrant / Packer)

Question

We use Packer and Vagrant to generate/build our OS VMs.
It is necessary that all the VMs are created with the configuration version 8.0.

In Packer there is a setting available to set the config-version for new VMs. That works and i can see that in the Hyper-V-Manager and the produced .VMCX file.
Here comes the tricky part: Packer/Vagrant use a second config file for the VM metadata besides the .VMCX file: box.xml
That box.xml currently does not support setting the config-version which results in a VM with the default config-version on our build machine --> 9.0
(No, we cannot downgrade the build machine nor upgrade the target host machine of that VM)

There is already an issue for that in Github discussing this issue in the Vagrant plugin inside Packer. (I wrote the explanation for the UUID problem)
https://github.com/hashicorp/packer-plugin-vagrant/issues/23

--> My question resolves around the UUID which Hyper-V sets for a new VM:
Is it possible to limit the Range of UUIDs that the Hyper-V is using?
(I'd need UUIDs starting with numbers only ...)

Answer 1

Hello @Horvath Robert

If you are talking about BIOS uuid, then there are some scripts available from altaro , just make a search in search engine and you will be able to get it.

If the reply was helpful, please don’t forget to upvote or accept as answer.