[Issue 307] fix missing CpuType

[maksimsamt]

[Issue 307] fix missing CpuType Related with: https://github.com/hashicorp/packer-plugin-proxmox/issues/307 https://github.com/hashicorp/packer-plugin-proxmox/commit/75dded5bd17410b4e5d4a5624c52621ac9acf370 https://github.com/Telmate/proxmox-api-go/commit/8e6e018c029320fa061bf764b00f15b2256b3d84#diff-bf2ef831782a92e7b5d3898f34e123fea8c1438ad45e4316282192b7af0bdef0R291

[hashicorp-cla-app[bot]]

All committers have signed the CLA.

[anEXPer]

I've been using this fork without issue, just FYI.

[lsampaioweb]

Hi team,

I’m encountering the issue where cpu_type isn’t passed to Proxmox in v1.2.2, causing all my VMs to default regardless of my Packer template settings. Downgrading to 1.2.1 works, but that’s not viable since 1.2.2 includes critical fixes I rely on. I see a fix was committed based on earlier comments—could you please review and approve it for an official release? Currently, I’m manually updating cpu_type on every VM post-provisioning, which is a hassle. Thanks for your time!

[jelly-is-bean]

Finally found this after a weekend troubleshooting. Using 1.2.2 fails to build windows server 2025 due to incompatible cpu_type (as its not being passed to proxmox so default is kvm64). Reverting to 1.2.1 works as expected. Please take this as another vote to release the cpu_type fix.

[anEXPer]

As we celebrate the six month anniversary of this issue having a good fix with no action, we must ask ourselves: what kind of party should we hold?

[cbrherms]

ping @lbajolet-hashicorp

Can someone have a look at this one please as we've been unable to fully automate a lot of different builds due to packer always defaulting to kvm64! it's been 8 months since this issue was introduced now.