Ok.
That's a pity. Where can I send a feature request ?
FYi, I think the best would be to combine, both custom and generated one cloud-init file. Therefore, I could set some config in GUI and use custom part from a file.
Unfortunately, it won't work either.
I did sth like this in my hookscript
`sed -i '/cicustom:/c\\cicustom: user=local:snippets/cloudinit-$vmid' /etc/pve/qemu-server/$vmid.conf
It overwrites old cicustom file from a vm config (which is called cloudinit-empty). But it does it after VM is started...
Hmm, I tried this and it seems like it stills try to acquire lock:
system("qm set $vmid --skiplock --cicustom user=local:snippets/cloudinit-$vmid");
sleep 5;
and I still get
trying to acquire lock...
can't lock file '/var/lock/qemu-server/lock-101.conf' - got timeout
Yeah, that's what I wanted to avoid. Manual step. :) I was hoping to just clone a VM in GUI, start and it is all ready. Is there maybe a some way to attach some script to clone procedure ? and attach empty cloutinit-$vmid file to newly cloned vm
Hmm, thats one option, however it would not work properly with a template in some cases. If I attach hookscript and clcustom to a template and then clone it , all new VMs, based on it, would use the same cicustom file. So everytime I start a new VM, this shared file would be edited. Therefore...
Hi, I have a problem with this kind of approach, I cannot edit already started VM.
My code looks like this
if ($phase eq 'pre-start') {
# First phase 'pre-start' will be executed before the guest
# ist started. Exiting with a code != 0 will abort the start
print "$vmid is...
I am not sure what do you mean to load from a different URL. I set vm to use a cicustom from a snippet file.
Wow, great thing, I did not know about hookscripts. I will try to add cicustom file snippet generation in pre-start phase. Hmm, but I guess I will have to store a cicustom snippet file...
Hmm I know these commands, but it would only give me a console way to pass this data. Not via GUI, like with simple clone feature available in Proxmox :/ and the best way IMHO would be with a custom and an autogenerated config merge with cloud-init.
Hmm, but I want to provide these data to the VM. My template VM is cloud-init ready image provided by Ubuntu/CentOS and I want set both hostname and additional user-data like puppet/apt configuration. Hostname, in auto-generated user-data, is set based on VM Name, and I would like to combine it...
Hi,
Is it possible to somehow combine a custom cloud-init with an auto generated one ?
I thought that maybe if I do not set values that are autogenerated in my custom file, I will get them from ones I set in GUI. For example in my cicustom file for user-data I set some puppet and apt config...
Ok, it seems like this is a bug only in GUI. I was able to do this from console, but there is a small error.
It was unable to remove this cloudinit image from a source node. I found vm-191-cloudinit image and removed it manually.
Hi, I am trying to do an online/offline migration of the VM, and I get an error when I have a cloud-init device attached.
I read this thread https://forum.proxmox.com/threads/vm-live-migration-fails-when-cloud-init-image-is-attached.44485/ and I thought this issue was fixed. Is it suppose to...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.