yahoo-eng-team team mailing list archive

["Pedro A. Aranda" <2018178@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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

** Affects: cloud-init
     Importance: Undecided
         Status: New

** Attachment added: "This is the minimal cloud-init ISO I used to test the process"
   https://bugs.launchpad.net/bugs/2018178/+attachment/5669755/+files/uc3m-seed.iso

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/2018178

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

Status in cloud-init:
  New

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/2018178/+subscriptions