Search results

  1. C

    Cloud-init image only applies configuration on second boot

    Thanks so much @Kurosawa! That change worked for me as well. I changed qm set ${vmid} --ide2 local-lvm:cloudinit to qm set ${vmid} --scsi1 local-lvm:cloudinit and now cloud-init runs on first boot! It's strange that @mira wasn't able to reproduce the problem. It would be good to resolve...
  2. C

    Cloud-init image only applies configuration on second boot

    Here are mine: PVE version: proxmox-ve: 6.3-1 (running kernel: 5.4.106-1-pve) pve-manager: 6.4-4 (running version: 6.4-4/337d6701) pve-kernel-5.4: 6.4-1 pve-kernel-helper: 6.4-1 pve-kernel-5.4.106-1-pve: 5.4.106-1 ceph-fuse: 12.2.11+dfsg1-2.1+b1 corosync: 3.1.2-pve1 criu: 3.11-3...
  3. C

    Cloud-init image only applies configuration on second boot

    I am having a similar problem, but for me, it only happens if I try to use the UEFI "ovmf" --bios flag. On first boot, the ata2 disk, corresponding to the cloud-init disk, is not reported by the linux kernel, even though it is present in the PVE config. If I remove qm set ${vmid} --efidisk0...
  4. C

    Rerunning cloud-init

    Hi mira, Thanks - that is useful information to know. It's possible that I booted it once with this config, but with some other problem which caused it to fail to boot, but the config was still registered by cloud-init but not stored in netplan, and so never "took". Is there a way to force it...
  5. C

    Rerunning cloud-init

    Hi, I have a VM set up with cloud-init according to the instructions at https://pve.proxmox.com/wiki/Cloud-Init_Support using the Ubuntu Focal cloud image. This all worked flawlessly the first time I did it (thanks!). However, later I wanted to change the network configuration without...