Thanks for the detailed bug report. I used your reproducer steps, but I got a slightly different result. I'm still not getting the NoCloud identification, but in my case, I can't force ds-identify to identify it. In order for ds-identify to identify NoCloud, it needs to see a "cidata" filesystem label somewhere (or see the relevant kernel args), but "cidata" is not showing up on the sr0 device:
root@ubuntu:/run/cloud-init# lsblk -o name,mountpoint,label NAME MOUNTPOINT LABEL loop0 /snap/core20/1328 loop1 /snap/snapd/14549 loop2 /snap/lxd/22340 sr0 vda ├─vda1 / cloudimg-rootfs ├─vda14 └─vda15 /boot/efi UEFI Have you seen this as well, or have I missed a step in trying to reproduce this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961832 Title: jammy-server-cloudimg-amd64-disk-kvm.img NoCloud data source not detected with qemu SATA cdrom To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1961832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
