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 filing a bug, please include the following headings if possible. Any
example text in this template can be deleted.
Overview of the Issue
When attempting to create a virtual machine using aarch64 as the architecture, the packer script fails:
kvm: -device ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2: Bus 'ide.1' not found
TASK ERROR: start failed: QEMU exited with code 1
The same build process works under x86_64. These builds are using the UEFI firmware, not BIOS. It appears for aarch64, there needs to be an option to set the bus for the that device in order to accommodate native, non-x86_64 architectures. This is not using aarch64 emulation under x86_64.
Reproduction Steps
Run packer script on an aarch64 machine (not emulated). The current build is meant to run packer to provision a template and use a kickstart script to install and configure a Rocky Linux 9.3 VM/template.
proxmox-rl9-aarch64.proxmox-iso.rocky9-kickstart: output will be in this color.
==> proxmox-rl9-aarch64.proxmox-iso.rocky9-kickstart: Creating VM
==> proxmox-rl9-aarch64.proxmox-iso.rocky9-kickstart: No VM ID given, getting next free from Proxmox
==> proxmox-rl9-aarch64.proxmox-iso.rocky9-kickstart: Starting VM
==> proxmox-rl9-aarch64.proxmox-iso.rocky9-kickstart: Error starting VM: start failed: QEMU exited with code 1
==> proxmox-rl9-aarch64.proxmox-iso.rocky9-kickstart: Stopping VM
==> proxmox-rl9-aarch64.proxmox-iso.rocky9-kickstart: Deleting VM
Build 'proxmox-rl9-aarch64.proxmox-iso.rocky9-kickstart' errored after 24 seconds 741 milliseconds: Error starting VM: start failed: QEMU exited with code 1
In the proxmox console, the build fails, and shows that the CDROM is trying to be mounted on an ide bus:
kvm: -device ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2: Bus 'ide.1' not found
TASK ERROR: start failed: QEMU exited with code 1
Operating system and Environment details
CPU(s): Cortex-A72 (also tested under ARMv8 (M128-26)) System: SolidRun CEX7 Platform (Also tested on Ampere Altra) Kernel Version: 6.8.9-1.el9.elrepo.aarch64 and Linux 6.1.0-20-arm64 (2024-04-11) Proxmox version: pve-manager/8.1.7/ee1c3736ef6a6541
Log Fragments and crash.log files
Relevant log information:
proxmox-rl9-aarch64.proxmox-iso.rocky9-kickstart: output will be in this color.
2024/05/09 10:17:52 Build debug mode: false
2024/05/09 10:17:52 Force build: false
2024/05/09 10:17:52 On error:
2024/05/09 10:17:52 Waiting on builds to complete...
2024/05/09 10:17:52 Starting build run: proxmox-rl9-aarch64.proxmox-iso.rocky9-kickstart
2024/05/09 10:17:52 Running builder: proxmox-iso
2024/05/09 10:17:52 [INFO] (telemetry) Starting builder proxmox-iso.rocky9-kickstart
2024/05/09 10:17:52 packer-plugin-proxmox_v1.1.7_x5.0_darwin_amd64 plugin: 2024/05/09 10:17:52 using password auth
2024/05/09 10:17:52 packer-plugin-proxmox_v1.1.7_x5.0_darwin_amd64 plugin: 2024/05/09 10:17:52 No URLs were provided to Step Download. Continuing...
==> proxmox-rl9-aarch64.proxmox-iso.rocky9-kickstart: Creating VM
==> proxmox-rl9-aarch64.proxmox-iso.rocky9-kickstart: No VM ID given, getting next free from Proxmox
==> proxmox-rl9-aarch64.proxmox-iso.rocky9-kickstart: Starting VM
==> proxmox-rl9-aarch64.proxmox-iso.rocky9-kickstart: Error starting VM: start failed: QEMU exited with code 1
==> proxmox-rl9-aarch64.proxmox-iso.rocky9-kickstart: Stopping VM
==> proxmox-rl9-aarch64.proxmox-iso.rocky9-kickstart: Deleting VM
2024/05/09 10:18:15 [INFO] (telemetry) ending proxmox-iso.rocky9-kickstart
Build 'proxmox-rl9-aarch64.proxmox-iso.rocky9-kickstart' errored after 22 seconds 753 milliseconds: Error starting VM: start failed: QEMU exited with code 1
==> Wait completed after 22 seconds 754 milliseconds
2024/05/09 10:18:15 machine readable: error-count []string{"1"}
==> Some builds didn't complete successfully and had errors:
==> Wait completed after 22 seconds 754 milliseconds
2024/05/09 10:18:15 machine readable: proxmox-rl9-aarch64.proxmox-iso.rocky9-kickstart,error []string{"Error starting VM: start failed: QEMU exited with code 1"}
==> Some builds didn't complete successfully and had errors:
==> Builds finished but no artifacts were created.
--> proxmox-rl9-aarch64.proxmox-iso.rocky9-kickstart: Error starting VM: start failed: QEMU exited with code 1
==> Builds finished but no artifacts were created.
2024/05/09 10:18:15 [INFO] (telemetry) Finalizing.
2024/05/09 10:18:15 waiting for all plugin processes to complete...
2024/05/09 10:18:15 /usr/local/bin/packer: plugin process exited
The text was updated successfully, but these errors were encountered:
When filing a bug, please include the following headings if possible. Any
example text in this template can be deleted.
Overview of the Issue
When attempting to create a virtual machine using aarch64 as the architecture, the packer script fails:
The same build process works under x86_64. These builds are using the UEFI firmware, not BIOS. It appears for aarch64, there needs to be an option to set the bus for the that device in order to accommodate native, non-x86_64 architectures. This is not using aarch64 emulation under x86_64.
Reproduction Steps
Run packer script on an aarch64 machine (not emulated). The current build is meant to run packer to provision a template and use a kickstart script to install and configure a Rocky Linux 9.3 VM/template.
Plugin and Packer version
Simplified Packer Buildfile
To reproduced the error
In the shell console, this is the result:
In the proxmox console, the build fails, and shows that the CDROM is trying to be mounted on an ide bus:
Operating system and Environment details
CPU(s): Cortex-A72 (also tested under ARMv8 (M128-26))
System: SolidRun CEX7 Platform (Also tested on Ampere Altra)
Kernel Version: 6.8.9-1.el9.elrepo.aarch64 and Linux 6.1.0-20-arm64 (2024-04-11)
Proxmox version: pve-manager/8.1.7/ee1c3736ef6a6541
Log Fragments and crash.log files
Relevant log information:
The text was updated successfully, but these errors were encountered: