[SOLVED] PVE 9.1.4 Debian 13 Cloud Init not working

tim.baumgartl

New Member
Jan 31, 2026
2
0
1
Germany
Hello,

it is my first post here. We currently test PVE for our own infrastructure and run in some trouble with cloud init on debian.
I tried every little step from this video and tried some fixes from this post.

The Problem:
After the first boot, the vm just show the console with "Debian GNU/Linux 13 localhost tty1 localhost login:" and not the VM name from pve. I also cannot login with my credentials.

My Settings:
  • BIOS SeaBIOS (also tested with UEFI)
  • Display Default (also tested with serial 0)
  • Machine Default i440fx
  • SCSI Controller VirtiIO SCSI single
  • Hard Disk sata0 (also tested with ide and scsi)
  • CloudInit Drive sata1 (also tested with ide and scsi)
  • Cloud-Init set User, Password, IP Config
  • Imported Disk: debian-13-nocloud-amd65.raw (also tested debian-13-nocloud-amd65.qcow2)
  • Button "Regenerate Image" pressed after every little change
I only use the gui for the config. Have anybody the same issues with that or any ideas how to fix it? My last 4 hours don`t have any success.

Edit:
Here the config file entry cat /etc/pve/qemu-server/108.conf
Code:
agent: 1
boot: order=sata0;ide2;net0
cipassword: alotofcharacters
ciuser: coolusername
cores: 2
cpu: host
ide2: none,media=cdrom
ipconfig0: ip=dhcp
memory: 4096
meta: creation-qemu=10.1.2,ctime=1769878285
name: test
net0: virtio=BC:24:11:96:80:F0,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
sata0: disk1:vm-108-disk-0,size=3G
sata1: disk1:vm-108-cloudinit,media=cdrom
scsihw: virtio-scsi-single
smbios1: uuid=dfbe7823-a8bf-477f-9cf4-6c4624c91fbc
sockets: 1
vmgenid: 60dbfaac-44bb-4324-b905-f2d3c5148946
 
Last edited:
Hi @tim.baumgartl , welcome to the forum.

Give "generic" image a try.

From Debian website: https://cdimage.debian.org/cdimage/cloud/
  • nocloud: Does not run cloud-init and boots directly to a root prompt. Useful for local VM instantiation with tools like QEMU.


As opposed to:
  • generic: Should run in any environment using cloud-init, for e.g. OpenStack, DigitalOcean and also on bare metal.
  • genericcloud: Identical to generic but with a reduced set of hardware drivers in the kernel. If it does not work for your use case, you should use the generic images.
Cheers


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
  • Like
Reactions: tim.baumgartl
Hi @tim.baumgartl , welcome to the forum.

Give "generic" image a try.

From Debian website: https://cdimage.debian.org/cdimage/cloud/
  • nocloud: Does not run cloud-init and boots directly to a root prompt. Useful for local VM instantiation with tools like QEMU.


As opposed to:
  • generic: Should run in any environment using cloud-init, for e.g. OpenStack, DigitalOcean and also on bare metal.
  • genericcloud: Identical to generic but with a reduced set of hardware drivers in the kernel. If it does not work for your use case, you should use the generic images.
Cheers


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Thank you very much... Exactly that was my problem... Sometimes reading ist very usefull...
Have a nice weekend!

PS: Used https://cdimage.debian.org/cdimage/cloud/trixie/latest/debian-13-generic-amd64.qcow2