Cloud-init Sanity Check

virtualbitz

Active Member
Nov 6, 2020
42
5
28
34
I'm trying to activate a virtual VeloCloud Edge appliance on Proxmox VE. VeloCloud recently switched to a model where there is no longer a default password that you can use to log into the VM, instead you have to use cloud-init to set the password for you. I've been having trouble getting cloud-init to set the root password so that I can log into the console.

I'm not using the proxmox integrated cloud-init drive, and am instead creating my own iso and mounting a virtual SATA drive with a meta-data and user-data file.

meta-data contents

Code:
instance-id: some-hostname

local-hostname: some-hostname

user-data contents


Code:
#cloud-config
password: some-password
chpasswd: { expire: False }
ssh_pwauth: True
velocloud:
      vce:
            vco: some-vco-address
            activation_code: some-activation-code

It's definitely reading the meta-data file contents, because I can see from the console that it's initializing and finalizing cloud-init, and it does set the hostname correctly, however it never activates and I can't log in, which leads me to believe that it's not processing the user-data file at all. Do you guys see any syntax errors or anything obvious that would cause cloud-init to fail?
 
Last edited:
Disregard, I had the default CPU type set of kvm64, which was unsupported by the appliance. Switching to Host solved the problem.