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
qemu-system-aarch64 fails to launch iso on arm64 platform using the same packer .pkr.hcl configuration settings which do boot the iso on qemu-system-x86_64
#145
Open
HariSekhon opened this issue
Jun 12, 2023
· 3 comments
Packer fails to boot the Ubuntu iso on my M1 Mac running qemu-system-aarch64 which drops into qemu boot shell instead, despite a very similar configuration successfully booting the Ubuntu iso on my Intel Mac running qemu-system-x86_64.
I believe this is more likely to be a packer plugin issue rather than a qemu because if I use UTM which uses qemu under the hood then I can boot the same Ubuntu iso.
Reproduction Steps
git clone https://github.com/HariSekhon/Packer-templates pack
cd pack
packer build ubuntu-arm64.qemu.pkr.hcl
Connect VNC viewer to the random VNC port as output in the log since it doesn't open automatically, as per issue #144, to see it is dropped into a qemu shell and doesn't find / boot the iso.
but if you check the x86_64 version it does boot:
packer build ubuntu-x86_64.qemu.pkr.hcl
Connect VNC viewer to the random port from the output to see it booting.
Plugin and Packer version
Same version running on both my Intel Mac and my M1 Mac
They're close to identical configurations aside from some commented out bits if you diff the two.
Operating system and Environment details
Mac M1 ARM processor running macOS 1.34 Ventura is the one using qemu-system-aarch64 that doesn't boot the iso
$ qemu-system-aarch64 -version
QEMU emulator version 8.0.2
The Intel Mac using qemu-system-x86_64 does boot the iso.
$ qemu-system-x86_64 -version
QEMU emulator version 8.0.2
Log Fragments and crash.log files
Include appropriate log fragments. If the log is longer than a few dozen lines,
please include the URL to the gist of the log or
use the Github detailed format instead of posting it directly in the issue.
Overview of the Issue
Packer fails to boot the Ubuntu iso on my M1 Mac running
qemu-system-aarch64
which drops into qemu boot shell instead, despite a very similar configuration successfully booting the Ubuntu iso on my Intel Mac runningqemu-system-x86_64
.I believe this is more likely to be a packer plugin issue rather than a
qemu
because if I use UTM which uses qemu under the hood then I can boot the same Ubuntu iso.Reproduction Steps
git clone https://github.com/HariSekhon/Packer-templates pack cd pack packer build ubuntu-arm64.qemu.pkr.hcl
Connect VNC viewer to the random VNC port as output in the log since it doesn't open automatically, as per issue #144, to see it is dropped into a qemu shell and doesn't find / boot the iso.
but if you check the x86_64 version it does boot:
Connect VNC viewer to the random port from the output to see it booting.
Plugin and Packer version
Same version running on both my Intel Mac and my M1 Mac
Simplified Packer Buildfile
x86_64 boots iso:
https://github.com/HariSekhon/Packer-templates/blob/main/ubuntu-x86_64.qemu.pkr.hcl
but arm aarch64 doesn't boot iso:
https://github.com/HariSekhon/Packer-templates/blob/main/ubuntu-arm64.qemu.pkr.hcl
They're close to identical configurations aside from some commented out bits if you diff the two.
Operating system and Environment details
Mac M1 ARM processor running macOS 1.34 Ventura is the one using
qemu-system-aarch64
that doesn't boot the isoThe Intel Mac using
qemu-system-x86_64
does boot the iso.Log Fragments and crash.log files
Include appropriate log fragments. If the log is longer than a few dozen lines,
please include the URL to the gist of the log or
use the Github detailed format instead of posting it directly in the issue.
From
PACKER_LOG=1
log:The qemu command run by the failing M1 Mac:
Full Log: https://gist.github.com/HariSekhon/d48fd89d5d1ce1bc957415e174a392f5
The qemu command run by the succeeding Intel Mac:
Full Log: https://gist.github.com/HariSekhon/ffed6bcf30fb48eb63dbb07e96426101
The text was updated successfully, but these errors were encountered: