Search results

btw: same issue with Ubuntu 17.10 and netplan version 2. Seems like it is currently impossible to configure Proxmox KVM Ubuntu servers network with cloud-init.

the key will be the comparison between a working and non working VM. Maybe you install a fresh new 18.10 VM https://www.ubuntu.com/download/server to confirm, that network config will NOT work as in my case. Then you compare packages, configs and logs between your working 18.10 VM and this...

mhm I am facing the exact same issue on 18.10 as well. There is the exact same version installed as you mentioned (18.10: 18.5-45-g3554ffe8-0ubuntu1~18.10.1) Is your test VM a new VM installed with a ISO or is it older? If new, what exact ISO did you use? Could you send me the cloud-init.log...

thanks so far @mira did you compare cloud-init version of you 18.04 and 18.10 machine? Any difference here?

Logs attached. Just to make sure again: 134.255.231.41/24 is not the IP set in Proxmox Cloud-Init GUI. This is the IP set during installation of the VM with the ubuntu ISO. IP set in Proxmox Cloud-Init GUI is 185.223.28.197/24 (see QM config) Maybe the datasource (mounted ISO inside the VM) is...

Thanks for your answer, I hope you can help me out here. Debian 8/9 with Cloud-Init works fine btw, even the network config. I still assume that this has something to do with netplan network config v2 and cloud-init is not able to read your format, but I am not sure. Here you have everything...

Hi, I am playing arround with Cloud-Init to setup Ubuntu 18.04 VMs: - Hostname - User password change - disk resize works fine so far, but I do not get a static IP configured. I figured out, Ubuntu is using Netplan v2 and Proxmox does not Support netplan v2, right? Any ideas on how to achieve...

Hi, we tried to migrate a SolusVM KVM VPS (Win2016) in raw format to Proxmox qcow2. We used following command to convert the image: When I try to start a KVM VPS in proxmox with this converted qcow2 file, I get "inaccessable boot device" (Windows Bluescreen) after a while trying to load...

yes indeed, figured out with and killed it with kill -9 afterwards. Anyway, the scope message persists. Facing this issue on several nodes, different VPS and on different windows OS. Some nodes do have this kernel: Some this:

Hi, we are facing issues for some time now, where KVM servers suddenly freeze. We need to stop them trough proxmox and then try to start them again, but it immediately says: any ideas?

mb, https://pve.proxmox.com/wiki/Dynamic_Memory_Management can confirm it "started" at > 80% mem usage.

Hi, i configured ballooning for our Windows KVM machines and it seems to work: http://prntscr.com/n03mej When I sum all KVM machines "Memory usage" I will get something like 40 gb memory usage (18 KVM machines). Furthermore there are 15 LXC container on that node (memory usage something like 6...

Hi, I am not able to enable the Discard Feature on my KVM VPS stored on qcow2 images (stored in an ext4 directory): http://prntscr.com/mwsbuy Virtio SCSI is enabled. Any ideas? UPDATE: My storage was VIRTIO Block instead of SCSI, works now.

Hi, anyone else facing the issue when booting a Windows VPS (KVM) the first time after installation (clone) it takes a long time to after it finishes this step: http://prntscr.com/mwdz4q Next reboot goes very fast. Any ideas what this may cause?

will check that very soon. It is not very professional if a customers sees the mounted cdrom with plain text administrator password indeed.

ahh, wrong file mate. It is /usr/share/perl5/PVE/API2/Qemu.pm Works fine! Password will be put in plain text into the META_DATA.json from proxmox.

I have upgraded to 5.3 - then executed your patch from hrere https://forum.proxmox.com/threads/finally-cloudbase-init-windows-servers.48823/#post-235155 worked fine, thanks mate!! Adjusted [DEFAULT] username=Admin to Administrator in the cloudinit config, Administrator password changing works...

thanks, worked!

when I try to execute your patch I get: Could you upload your complete Cloudinit.pm @Craig St George?

thanks @chengkinhung and @Craig St George for your hints! I managed to setup networking including nameservers with your suggestions. Did not manage to modify the Administrator password yet. When I have a look into the USER_DATA file it looks good: #cloud-config hostname: windows2016-de-image...