Recent content by snknick

Cheers, appreciate it! Other thing I've noticed is Cloud-Init now offers to install as a service from the start. Is that preferred or does it break anything vs running the script you have to change it over? So far no luck in 7.2 following the instructions carefully. Everything looks like it...

Going through to see if I can get it running on 7.2. Documentation misses out the following lines from Qemu.pm my $conf = PVE::QemuConfig->load_config($vmid); my $ostype = $conf->{ostype};

I have checked my DNS and I don't see anything obviously wrong, but I strongly suspect something is amiss (it's always DNS...). I'll keep digging and update here in case I find something that might help someone else down the line.

Not working for any of the Debian 11 images I've tried, however D11 does not have any OpenStack specific images which is what I've been using for Debian 10. I've tried generic and genericcloud for Debian 11 but neither work... leaving them on static just has them pick a randomly and already in...

OK so.. I think I have it figured out. I have no idea why it works like this but I've tested it a dozen times now and I'm getting the same thing. Under the Cloud-init options for ProxMox there is an IP Config setting. Naturally, I've been setting this to DHCP for my templates. When I do so...

Well for the official images I don't boot them at all (other than when I modified it to add my workaround). Pretty much the setup is: wget https://cdimage.debian.org/cdimage/openstack/current-10/debian-10-openstack-amd64.qcow2 qm create 9000 --name debian10-cloud --memory 2048 --net0...

Interesting as I've been using the Debian 10 and 11 official cloud images, I would have thought that hostname before network would be standard to avoid this exact issue. Looks like I have a bit more learning to do as I'm not sure how exactly to change up the order of things, I've been using the...

As per title.. have set up cloud-init for rapid VM creation, however the hostname change is occurring after the machine registers with the DNS server, resulting in the IP/MAC being associated with the template name instead of the VMs new name. I realise this is the DNS being bad at updating...