That's was nice! Thanks Dietmar Meanwhile, I get some errors here... Certain because I am doing something pretty ugly.
So, this is my steps: 1 - I alreay have a KVM VM with Alpine Linux in it. The VMID is 101. 2 - I add a cloud disk to VM 101. I add it to ZFS local storage... I local storage I get this error [1] 3 - I went to Cloud-init, fill all information, such user and password bla bla bla... Click Regenerate Image 4 - I created a new VM, attached the cloud-init and try to boot over it - I use qm set VMID -ide2 local-zfs:vm-101-cloudinit and try it also with -scsi1 5 - I get a not bootable disk [1] - qm set 102 -ide2 local:101/vm-101-cloudinit.qcow2 update VM 102: -ide2 local:101/vm-101-cloudinit.qcow2 pve01:~# qm start 102 kvm: -drive file=/var/lib/vz/images/101/vm-101-cloudinit.qcow2,if=none,id=drive-ide2,format=qcow2,cache=none,aio=native,detect-zeroes=on: file system may not support O_DIRECT kvm: -drive file=/var/lib/vz/images/101/vm-101-cloudinit.qcow2,if=none,id=drive-ide2,format=qcow2,cache=none,aio=native,detect-zeroes=on: Could not open '/var/lib/vz/images/101/vm-101-cloudinit.qcow2': Invalid argument start failed: command '/usr/bin/kvm -id 102 -name teste-cloud-init -chardev 'socket,id=qmp,path=/var/run/qemu-server/102.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/102.pid -daemonize -smbios 'type=1,uuid=e9cf7789-c0c2-4c80-9896-a89666fa9d3f' -smp '1,sockets=1,cores=1,maxcpus=1' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vga std -vnc unix:/var/run/qemu-server/102.vnc,x509,password -cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce -m 512 -k pt-br -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:9677e1b7547a' -drive 'file=/var/lib/vz/images/101/vm-101-cloudinit.qcow2,if=none,id=drive-ide2,format=qcow2,cache=none,aio=native,detect-zeroes=on' -device 'ide-hd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=100' -device 'virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5' -drive 'file=/dev/zvol/rpool/data/vm-102-disk-1,if=none,id=drive-scsi0,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0' -netdev 'type=tap,id=net0,ifname=tap102i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=96:D9:5B:B1:1D:FA,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'' failed: exit code 1 Thank you --- Gilberto Nunes Ferreira (47) 3025-5907 (47) 99676-7530 - Whatsapp / Telegram Skype: gilberto.nunes36 2018-03-20 9:32 GMT-03:00 Dietmar Maurer <[email protected]>: > I already added some docs here: > > https://git.proxmox.com/?p=pve-docs.git;a=blob;f=qm-cloud-init.adoc;h= > cfac011c659440e4b4b91d985dea79f98e5f083c;hb=HEAD > > > > On March 20, 2018 at 1:16 PM Alexandre DERUMIER <[email protected]> > wrote: > > > > > > >>Sorry for newbie skills. > > no problem. > > > > cloudinit is managed on the vm, > > first you can add a "cloudinit" disk (add device, like for efi disk) > > > > then you have a new cloudinit section in the vm configuration. > > > > (maybe try to refresh your browser if you don't see them) > > _______________________________________________ > pve-devel mailing list > [email protected] > https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel > _______________________________________________ pve-devel mailing list [email protected] https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
