[pve-devel] [PATCH qemu-server 1/6] cloudinit: add cloudinit section for current generated config.

aderumier at odiso.com aderumier at odiso.com
Thu Apr 1 12:22:01 CEST 2021

Le jeudi 01 avril 2021 à 10:54 +0200, Thomas Lamprecht a écrit :
> actually, why isn't the pending section enough for this?
> If stuff can be hot plugged then we can do so and if only that
> changed we
> can just remove it from pending, as normally?

Well, for example, if you change the vm name , how to you manage that ?
do you want to keep it as pending  until we regenerate cloudinit drive?

or more complex, if you change the mac address of the vm. (so
unplug/replug the nic)
for the nic, you don't want to keep it as pending, as technically, is
really plugged.

or if you change the storage of the cloudinit drive, currently they a
no way to known if we need to regenerate it.

The main problem is that pending section, is more for pending qemu
not pending cloudinit config drive regeneration.

For me, both are differents.

Currently,it's working well when vm is offline, because we don't have
any pending, and we regenerate the disk at vm startup.

(I'm really looking to use cloudinit for online config changes, like
for containers)

More information about the pve-devel mailing list