server cloud image for ARM64 doesn't support nocloud target in cloud-init

This bug was originally filed in Launchpad as [LP: #2018178](https://bugs.launchpad.net/cloud-init/+bug/2018178)

Launchpad details

affected_projects = []

assignee = None

assignee_name = None

date_closed = None

date_created = 2023-04-30T06:59:02.424296+00:00

date_fix_committed = 2023-05-01T14:58:28.629181+00:00

date_fix_released = 2023-05-01T14:58:28.629181+00:00

id = 2018178

importance = undecided

is_complete = False

lp_url = https://bugs.launchpad.net/cloud-init/+bug/2018178

milestone = None

owner = paaguti-p

owner_name = Pedro A. Aranda

private = False

status = incomplete

submitter = paaguti-p

submitter_name = Pedro A. Aranda

tags = []

duplicates = []

_Launchpad user **Pedro A. Aranda(paaguti-p)** wrote on 2023-04-30T06:59:02.424296+00:00_

Use case:

To provide students with a reliable way of creating a VM for the laboratory activities regardless of the platform they have, I use cloud-init to automate the VM creation process. This works nicely on Intel-based devices, but the number of students with ARM-based Macs is growing.

HW:

Macbook Pro with the UTM virtualisation app version 4.2.5
Tested both on Intel and Apple M-1/M-2 HW

Prerequisite:

Simple cloud-init CDROM iso image that creates a user in the VM (in real life, it configures the VM installing packages, config files and scripts the students need for their activities.

Procedure:

1.- Download the ubuntu-jammy-server QEMU image
2.- Expand the image to a 20G drive
3.- On UTM create a new VM (emulating when CPU != target of the image else virtualising)
4.- Attach cloud-init to CDROM unit
5.- Subtitute default drive created by UTM with expanded server image
6.- Boot the VM

The different modes and experiment results:
(OK meaning user set; KO meaning user not defined)
Horizontal is same image different platform/mode

Intel ARM
Intel Virtualise/OK Emulate/OK
ARM Emulate/KO Virtualise/KO

When the process succeeds, the log shows that the cloud-init looked for a NoCloud source. When the process failed, the cloud-init process doesn't show any message realted to the NoCloud source