What is the output of the following command:

cloud-init schema --system

I am using terraform to setup a VM but it's the same approach for cloud-init:
cloud_config

#cloud-config
preserve_hostname: false
hostname: ${hostname} 
create_hostname_file: true
users:
  - name: ansible
    groups:
      - sudo
    sudo:
      - ALL=(ALL) NOPASSWD:ALL
    shell: /bin/bash
    ssh_authorized_keys:
      - "ssh-ed25519 somekeyl"
      - "ssh-ed25519 otherkey"

network_config:

#cloud-config
network:
  version: 1
  config:
    - type: physical
      name: enX0
      subnets:
        - type: static
          address: ${ip_address}
          netmask: ${netmask}
          gateway: ${gateway}
          dns_nameservers:
%{ for dns_server in dns ~}
            - ${dns_server}
%{ endfor ~}

Maybe a silly question: Your template supports cloud-init ?

@amititre331
If you want to configure ip settings using cloud-init you have to use the option network_config instead of cloud_config.

Unbrand_CreateVmBody_{
memory	[...]
name_description	[...]
name_label*	[...]
clone	[...]
gpuGroup	[...]
vgpuType	[...]
autoPoweron	[...]
vifs	[...]
copyHostBiosStrings	[...]
template*	[...]
affinity	[...]
vdis	[...]
install	{...}
cloud_config	[...]
network_config	string
boot	[...]
destroy_cloud_config_vdi	[...]
}

By the way, do not share your tokens on the internet

This approach isn’t entirely foolproof since I can’t use a wildcard, and I don’t know how many disks will be attached to the VM. For now, it will never exceed two disks, so I can explicitly include both in the ignore_changes statement. That’s an acceptable solution for us. Thanks for your support.

Hi all,

I have a general question about the Terraform provider.

At the moment, all my VMs are managed by Terraform, so far, so good. However, there’s one feature I’m missing. Terraform doesn’t seem to support disk migration. When I change the sr_id in the xenorchestra_vm resource, I get the following error:

Error: disk update action 'disk migration Update (Sr ID update)' not handled

I’m aware that I can use "ignore_changes = [disk]", but in that case, I lose the ability to modify the disk size through Terraform.

I’m not really happy with the idea of managing my VMs partly in Terraform and partly in XO. Another possible workaround is to set "ignore_changes = all", using Terraform only to create or remove systems, and handling all other changes through XO or Ansible.

How are you handling this situation?

Here is a full logging (xensource.log) the moment terraform creates the vm (carlo111).
I really hope someone can give me some clues. Because this is a showstopper.
Debug-terraform2.txt

I am still troubleshooting this case.

I created 2 new templates:
Template1 based on a default debian13-netinstall iso image
Template2: based on a debian cloud-init raw file: https://cdimage.debian.org/images/cloud/trixie/latest/debian-13-generic-amd64.raw

Running terraform with template1 runs fine. A vm is created with a disk.
Running terraform with template2 --> vm is created without a disk.
Manually creating a vm using template2 runs also fine.

[21:33 dacshyp002 ~]# xe vbd-list vm-uuid=a6b4c48d-16c0-a333-fa90-c8b4b13d6c2a
uuid ( RO)             : 06552805-ddfa-7f80-a55e-9d878d626ad2
          vm-uuid ( RO): a6b4c48d-16c0-a333-fa90-c8b4b13d6c2a
    vm-name-label ( RO): debian13-generic-cloud-tmpl
         vdi-uuid ( RO): 5c793847-b331-4f65-be71-9463c68e09c8
            empty ( RO): false
           device ( RO): xvdb

I can't reproduce the problem at my homelab. There are some differences at home:

• running xoa in a container (commit 82891)
• all vdi's are stored on local storage (at work we are using iscsi luns)
• just one xcp-ng server

Looking at the debug logging I can see the VDI and VBD are created but also removed during the setup of the VM. At this point I am not using cloud-init.
Creation of VDI and VBD:

Oct 29 11:57:18 dacshyp002 xapi: [ info||67090 :::80|OpaqueRef:973e5688-b5a7-d197-cb55-95834b9abec6|mux] VDI.create dbg:OpaqueRef:973e5688-b5a7-d197-cb55-95834b9abec6 sr:589dad4d-2391-c2a9-589c-d34a9a7757ea vdi_info:{"sm_config":{},"sharable":false,"persistent":true,"physical_utilisation":0,"virtual_size":32212254720,"cbt_enabled":false,"read_only":false,"snapshot_of":"","snapshot_time":"19700101T00:00:00Z","is_a_snapshot":false,"metadata_of_pool":"","ty":"user","name_description":"","name_label":"debiancloud.vhd","content_id":"","vdi":""}

Oct 29 11:57:18 dacshyp002 xapi: [debug||67090 HTTPS 172.28.4.10->:::80|VBD.create R:9725689f8e64|vbdops] VBD.create (device = 0; uuid = 2f57bc16-c913-ecd5-dce4-9261a7a0e6ed; ref = OpaqueRef:9549bde7-4ff8-dda0-703b-6efbf7397155)

Some seconds later I see the following:

Oct 29 11:57:29 dacshyp002 xapi: [debug||68871 HTTPS 172.28.4.10->:::80|VBD.unplug R:b9f5584469dd|audit] VBD.unplug: VBD = '2f57bc16-c913-ecd5-dce4-9261a7a0e6ed' Oct 29 11:57:30 dacshyp002 xapi: [debug||67090 HTTPS 172.28.4.10->:::80|VBD.destroy R:cf37a355d7de|audit] VBD.destroy: VBD = '2f57bc16-c913-ecd5-dce4-9261a7a0e6ed' 
Oct 29 11:57:30 dacshyp002 xapi: [debug||67090 HTTPS 172.28.4.10->:::80|VBD.destroy R:cf37a355d7de|xapi_vbd_helpers] VBD.destroy (uuid = 2f57bc16-c913-ecd5-dce4-9261a7a0e6ed; ref = OpaqueRef:9549bde7-4ff8-dda0-703b-6efbf7397155)

During the proces I checked all VDI's on my storage :

while true; do echo '==================================='; xe vdi-list sr-uuid=589dad4d-2391-c2a9-589c-d34a9a7757ea | grep name-label; sleep 1; done

===================================
          name-label ( RW): debiancloud.vhd
          name-label ( RW): dacsvm002-osdisk
          name-label ( RW): dacsvm03-dhcp01-osdisk
          name-label ( RW): dacsvm01-osdisk
          name-label ( RW): debiancloud.vhd
          name-label ( RW): debiancloud.vhd
          name-label ( RW): Debian Bookworm 12_uruva
          name-label ( RW): sebas-vm-disk
          name-label ( RW): dacsvm01-osdisk
...
===================================
          name-label ( RW): debiancloud.vhd
          name-label ( RW): dacsvm002-osdisk
          name-label ( RW): dacsvm03-dhcp01-osdisk
          name-label ( RW): dacsvm01-osdisk
          name-label ( RW): debiancloud.vhd
          name-label ( RW): debiancloud.vhd
          name-label ( RW): debiancloud.vhd
          name-label ( RW): Debian Bookworm 12_uruva
          name-label ( RW): sebas-vm-disk
          name-label ( RW): dacsvm01-osdisk
...
===================================
          name-label ( RW): debiancloud.vhd
          name-label ( RW): dacsvm002-osdisk
          name-label ( RW): dacsvm03-dhcp01-osdisk
          name-label ( RW): dacsvm01-osdisk
          name-label ( RW): debiancloud.vhd
          name-label ( RW): debiancloud.vhd
          name-label ( RW): Debian Bookworm 12_uruva
          name-label ( RW): sebas-vm-disk
          name-label ( RW): dacsvm01-osdisk

Update:
I tried to create a vm using a basic terraform config and using another template. Still the same problem, vm created without a disk.

tofu apply  -var-file="carlo111.tfvars"

OpenTofu used the selected providers to generate the following execution plan. Resource actions are indicated with
the following symbols:
  + create

OpenTofu will perform the following actions:

  # module.vm.xenorchestra_vm.vm will be created
  + resource "xenorchestra_vm" "vm" {
      + auto_poweron                        = false
      + clone_type                          = "full"
      + core_os                             = false
      + cpu_cap                             = 0
      + cpu_weight                          = 0
      + cpus                                = 2
      + destroy_cloud_config_vdi_after_boot = false
      + exp_nested_hvm                      = false
      + hvm_boot_firmware                   = "uefi"
      + id                                  = (known after apply)
      + ipv4_addresses                      = (known after apply)
      + ipv6_addresses                      = (known after apply)
      + memory_max                          = 2126512128
      + memory_min                          = (known after apply)
      + name_label                          = "carlo111"
      + power_state                         = "Running"
      + start_delay                         = 0
      + template                            = "3dbf5448-0337-40e1-ebfc-f3f47e2cb0dd"
      + vga                                 = "std"
      + videoram                            = 8

      + disk {
          + name_label = "carlo111-osdisk"
          + position   = (known after apply)
          + size       = 32212254720
          + sr_id      = "589dad4d-2391-c2a9-589c-d34a9a7757ea"
          + vbd_id     = (known after apply)
          + vdi_id     = (known after apply)
        }

      + network {
          + device         = (known after apply)
          + ipv4_addresses = (known after apply)
          + ipv6_addresses = (known after apply)
          + mac_address    = (known after apply)
          + network_id     = "d4ddcfb0-6d3e-d267-b200-d7d1fec1edc8"
        }
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
  OpenTofu will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

module.vm.xenorchestra_vm.vm: Creating...
module.vm.xenorchestra_vm.vm: Still creating... [10s elapsed]
module.vm.xenorchestra_vm.vm: Creation complete after 14s [id=95b3b0c6-ac8e-fe4b-2f55-ba0d8ff04005]

[20:09 dacshyp002 ~]# xe vbd-list vm-uuid=95b3b0c6-ac8e-fe4b-2f55-ba0d8ff04005
[20:25 dacshyp002 ~]# 

main.tf

resource "xenorchestra_vm" "vm" {
  name_label = var.vm_name
  template   = var.template_uuid
  cpus       = var.cpus
  memory_max = var.memory * 1024 * 1024
  hvm_boot_firmware = "uefi"
  clone_type = "full"

  disk {
    sr_id      = var.sr_uuid
    name_label = "${var.vm_name}-osdisk"
    size       = var.disk_size * 1024 * 1024 * 1024
  }

  network {
    network_id = var.network_id
  }
}

I don't know if it is related, I see the following errors during the creation of the vm:

Oct 28 20:44:07 dacshyp002 xapi: [error||458 |xapi events D:20adbb444ff6|xenops] events_from_xapi: missing from the cache: [ 532cad38-f1ae-433b-b7ac-e0399613fe24 ]
Oct 28 20:44:07 dacshyp002 xapi: [error||458 |xapi events D:20adbb444ff6|xenops] events_from_xapi: extra items in the cache: [ 95b3b0c6-ac8e-fe4b-2f55-ba0d8ff04005 ]

[20:44 dacshyp002 log]# xe vm-list uuid=532cad38-f1ae-433b-b7ac-e0399613fe24
uuid ( RO)           : 532cad38-f1ae-433b-b7ac-e0399613fe24
     name-label ( RW): Control domain on host: dacshyp002
    power-state ( RO): running


[20:45 dacshyp002 log]# xe vm-list uuid=1c210250-1f89-b0e3-c1e6-f7bee976e94c
uuid ( RO)           : 95b3b0c6-ac8e-fe4b-2f55-ba0d8ff04005
     name-label ( RW): carlo111
    power-state ( RO): running

Manually creating the vm using the same template is not a problem.

Hi all,

I was able to create VMs using my Terraform code until I set the parameter destroy_cloud_config_vdi_after_boot to true.

Initially, it created a virtual machine and, after booting, removed the Cloud-Init disk as expected. However, from that point on, the VM started being created without a disk, even though tofu apply shows the following:

      + disk {
          + name_label = "carlo123-osdisk"
          + position   = (known after apply)
          + size       = 32212254720
          + sr_id      = "589dad4d-2391-c2a9-589c-d34a9a7757ea"
          + vbd_id     = (known after apply)
          + vdi_id     = (known after apply)
        }

tofu apply failes with:

│ Error: jsonrpc2: code -32000 message: Can't create cloud init config drive for VM without disks: {"message":"Can't create cloud init config drive for VM without disks","name":"Error","stack":"Error: Can't create cloud init config drive for VM without disks\n    at Xapi.createCloudInitConfig (file:///opt/xo/xo-builds/xen-orchestra-202510281611/@xen-orchestra/xapi/vm.mjs:418:13)\n    at Xo.<anonymous> (file:///opt/xo/xo-builds/xen-orchestra-202510281611/packages/xo-server/src/api/vm.mjs:191:26)\n    at Task.runInside (/opt/xo/xo-builds/xen-orchestra-202510281611/@vates/task/index.js:175:22)\n    at Task.run (/opt/xo/xo-builds/xen-orchestra-202510281611/@vates/task/index.js:159:20)\n    at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202510281611/packages/xo-server/src/xo-mixins/api.mjs:469:18)"}
│ 
│   with module.vm.xenorchestra_vm.vm,
│   on ../modules/vm/main.tf line 20, in resource "xenorchestra_vm" "vm":
│   20: resource "xenorchestra_vm" "vm" {```

This my main.tf

data "template_file" "cloud_config" {
  template = file("${path.module}/cloud-init.yaml.tftpl")

  vars = {
    hostname   = var.vm_name
  }
}

data "template_file" "cloud_network_config" {
  template = file("${path.module}/network-config.yaml.tftpl")

  vars = {
    ip_address = var.ip_address
    netmask    = var.netmask 
    gateway    = var.gateway
    dns        = join(", ", var.dns)
  }
}

resource "xenorchestra_vm" "vm" {
  name_label = var.vm_name
  name_description = var.description
  template   = var.template_uuid
  cpus       = var.cpus
  memory_max = var.memory * 1024 * 1024
  hvm_boot_firmware = "uefi"
  auto_poweron = false
  destroy_cloud_config_vdi_after_boot = true
  power_state = "Running"
  clone_type = "full"

  disk {
    sr_id      = var.sr_uuid
    name_label = "${var.vm_name}-osdisk"
    size       = var.disk_size * 1024 * 1024 * 1024
  }

  dynamic "disk" {
    for_each = var.data_disks
    content {
      sr_id      = var.sr_uuid
      name_label = "${var.vm_name}-${disk.value.name}"
      size       = disk.value.size * 1024 * 1024 * 1024
    }
  }

  network {
    network_id = var.network_id
  }

  cloud_config = var.ip_address != "" ? data.template_file.cloud_config.rendered : null
  cloud_network_config = var.ip_address != "" ? data.template_file.cloud_network_config.rendered : null

When I commented out the cloud_config line the vm is created without a disk.
Xensource.log also shows the following :

Oct 28 16:23:59 dacshyp001 xapi: [ info||11548 :::80|dispatch:VM.provision D:c4cf2cdf383f|taskhelper] task Async.VM.provision R:57a7bfeaacf3 forwarded (trackid=e7b951e8d29a4f9c673e51262f6144c9)
Oct 28 16:23:59 dacshyp001 xapi: [ info||11548 HTTPS 172.28.4.11->:::80|Async.VM.provision R:57a7bfeaacf3|xapi_vm_helpers] VM.set_is_a_template('false')
Oct 28 16:23:59 dacshyp001 xapi: [error||188 |xapi events D:596426783cc2|xenops] events_from_xapi: missing from the cache: [ ff4ff6a6-379a-4ec0-9dd2-ae28f8b6bc2c ]
Oct 28 16:23:59 dacshyp001 xapi: [error||188 |xapi events D:596426783cc2|xenops] events_from_xapi: missing from the cache: [ ff4ff6a6-379a-4ec0-9dd2-ae28f8b6bc2c ]

Running the following command:

[15:44 dacshyp002 ~]# xe vm-list uuid=ff4ff6a6-379a-4ec0-9dd2-ae28f8b6bc2c
uuid ( RO)           : ff4ff6a6-379a-4ec0-9dd2-ae28f8b6bc2c
     name-label ( RW): Control domain on host: dacshyp001
    power-state ( RO): running

XOA commit 45ef6

I’m not sure where to start troubleshooting this, any help would be appreciated.
Thanks in advance,
Carlo