@fohdeesha Thanks for the thorough explanation. Took me a while to get the network configuration working, but I think I've got it all working nicely now from a stock Ubuntu cloud image.

For those interested:

My cloud init:

#cloud-config
hostname: {name}
users:
  - default
ssh_import_id:
  - gh:<username>
package_update: true
package_upgrade: true
packages:
  - xe-guest-utilities
byobu_by_default: system
runcmd:
 - systemctl disable cloud-init
power_state:
  delay: "+1"
  mode: reboot
  message: Rebooting system
  timeout: 5
  condition: True

My network config:

version: 2
ethernets:
  eth0:
    addresses: []
    dhcp-identifier: mac
    dhcp4: true
    nameservers:
      search:
        - my.nameserver.local

@fohdeesha Thanks for the thorough explanation. Took me a while to get the network configuration working, but I think I've got it all working nicely now from a stock Ubuntu cloud image.

For those interested:

My cloud init:

#cloud-config
hostname: {name}
users:
  - default
ssh_import_id:
  - gh:<username>
package_update: true
package_upgrade: true
packages:
  - xe-guest-utilities
byobu_by_default: system
runcmd:
 - systemctl disable cloud-init
power_state:
  delay: "+1"
  mode: reboot
  message: Rebooting system
  timeout: 5
  condition: True

My network config:

version: 2
ethernets:
  eth0:
    addresses: []
    dhcp-identifier: mac
    dhcp4: true
    nameservers:
      search:
        - my.nameserver.local

@olivierlambert Thanks!

Maybe it's a non-issue, but I was wondering what is the right way for dealing with the XO CloudConfigDrive after a VM has been provisioned? Do I just leave it there, or should it be removed from the VM?

The other question I have relates to the cloud-init service. Should that be disabled after booting up?

So for example, should something like the following config be used with a stock ubuntu cloud image from https://cloud-images.ubuntu.com ?:

#cloud-config
hostname: {name}%
users:
  - default
ssh_authorized_keys:
  - ssh-rsa ...
package_update: true
package_upgrade: true
packages:
  - xe-guest-utilities
byobu_by_default: system
runcmd:
 - systemctl disable cloud-init
power_state:
  delay: "+30"
  mode: poweroff
  message: Bye Bye
  timeout: 30
  condition: True

And then remove the cloud config drive and then start the VM again, or can the disk be safely removed while the machine is running?