Le 5/09/22 à 09:29, Mark Schouten via pve-devel a écrit : > _______________________________________________ > pve-devel mailing list > pve-devel@lists.proxmox.com >Hi,
>>Not trying to break this thread, feel free to poke me off-list if this >>message is not supposed to be sent in this thread. >> >>Concerning cloud-init. There is something with Proxmox cloud-init that if you >>keep the cloud-init drive, after every boot, the sshd host-keys change. Is >>that something fixable? Or am I doing it wrong? 😄 Hi, Mark. The main problem is the cloud-init has not been created to change ip configuration after the vm create. It's really created for vm first init, it's "by design" like this. (yes, that's sucks) The only way to change ip address, is to regenerated a new cdrom id, to get cloudinit launch is early service. But this also regenerated ssh host-keys. I have done tests last year, I never was able to skip this. I known that very last version of cloudinit have support for nic hotplug, to add ip on new hotplug iface, but I don't think it's working for already existing interface. Personally, I'm use opennebula guest tools instead cloudinit, they are simple bash script, easily extendable, udev hook for hotplug is working,... I have added support last year to generate config drive format, it's not available in the gui, but can be added in a template manually https://www.mail-archive.com/pve-devel@lists.proxmox.com/msg02621.html the guest daemon are available here: https://github.com/OpenNebula/addon-context-linux https://github.com/OpenNebula/addon-context-windows _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
