Yeah, it's not a MAAS deploy issue, but a subiquity PXE install issue (MAAS deploys this system fine).
@Tai this bit looks weird to me:
[ 0.000000] Kernel command line: BOOT_IMAGE=/casper/vmlinuz debug root=/dev/ram0 ramdisk_size=1500000 ip=dhcp url=http://10.229.56.0/jammy-live-server-arm64.iso autoinstall ds=nocloud-net;s=http://10.229.56.0/ --- [ 0.000000] Unknown kernel command line parameters "autoinstall --- BOOT_IMAGE=/casper/vmlinuz ramdisk_size=1500000 ip=dhcp url=http://10.229.56.0/jammy-live-server-arm64.iso ds=nocloud-net;s=http://10.229.56.0/", will be passed to user space.
Like that there maybe two "---" delimiters. Can you provide the grub.cfg used?
Yeah, it's not a MAAS deploy issue, but a subiquity PXE install issue (MAAS deploys this system fine).
@Tai this bit looks weird to me:
[ 0.000000] Kernel command line: BOOT_IMAGE= /casper/ vmlinuz debug root=/dev/ram0 ramdisk_ size=1500000 ip=dhcp url=http:// 10.229. 56.0/jammy- live-server- arm64.iso autoinstall ds=nocloud-net;s=http:// 10.229. 56.0/ --- /casper/ vmlinuz ramdisk_ size=1500000 ip=dhcp url=http:// 10.229. 56.0/jammy- live-server- arm64.iso ds=nocloud-net;s=http:// 10.229. 56.0/", will be passed to user space.
[ 0.000000] Unknown kernel command line parameters "autoinstall --- BOOT_IMAGE=
Like that there maybe two "---" delimiters. Can you provide the grub.cfg used?