You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When provisioning the VM from packer cpu_type is not being passed to proxmox resulting in all hosts taking the default value regardless of cpu_type setting. This works in 1.2.1
Suspected Cause
proxmox-api-go defines QemuCPU as
type QemuCPU struct {
Affinity *[]uint `json:"affinity,omitempty"`
Cores *QemuCpuCores `json:"cores,omitempty"` // Required during creation
Flags *CpuFlags `json:"flags,omitempty"`
Limit *CpuLimit `json:"limit,omitempty"`
Numa *bool `json:"numa,omitempty"`
Sockets *QemuCpuSockets `json:"sockets,omitempty"`
Type *CpuType `json:"type,omitempty"`
Units *CpuUnits `json:"units,omitempty"`
VirtualCores *CpuVirtualCores `json:"vcores,omitempty"`
}
In change 75dded5, in step_start_vm.go CpuType is not passed through in the config.
While I can spot the issue, my skills at committing are lacking. Don't blame me, I'm just a sysadmin. :)
Reproduction Steps
Set cpu_type = "x86-64-v3" within proxmox-iso source section. The resulting VM will have type kvm64
Overview of the Issue
When provisioning the VM from packer cpu_type is not being passed to proxmox resulting in all hosts taking the default value regardless of cpu_type setting. This works in 1.2.1
Suspected Cause
proxmox-api-go defines QemuCPU as
In change 75dded5, in step_start_vm.go CpuType is not passed through in the config.
While I can spot the issue, my skills at committing are lacking. Don't blame me, I'm just a sysadmin. :)
Reproduction Steps
Set cpu_type = "x86-64-v3" within proxmox-iso source section. The resulting VM will have type kvm64
Plugin and Packer version
Packer v1.11.2
packer-plugin-proxmox_v1.2.2
Simplified Packer Buildfile
Very simple testing
Operating system and Environment details
Running packer on M1 silicon, MacOS 15.1.1
Log Fragments and crash.log files
No relevant logs
The text was updated successfully, but these errors were encountered: