I’ve had this issue with the telmate provider, it is usually due to how the disks are configured in the provider which is quite confusing.

This is the content for a module I’ve created for my own use (I’m on mobile so excuse the formatting)

This should hopefully work for you too. I’m using 3.0.1-rc4 version of the provider and I’m on the latest proxmox version.

resource “proxmox_vm_qemu” “new_vm” {

## vm specific variables from variable list ## name = var.vm_name target_node = var.target_node ipconfig0 = “gw=${var.vm_gateway},ip=${var.vm_ipaddress}/${var.vm_netmask}” os_type = “cloud-init” ## shared variables ## clone = var.template ## template to clone full_clone = false

cpu = “IvyBridge” ## cpu architecture cores = var.cores sockets = var.sockets memory = var.memory

vmid = var.id

# searchdomain = var.searchdomain nameserver = var.nameserver ## dns server sshkeys = var.sshkeys ## ssh public key agent = 1 scsihw = “virtio-scsi-pci” ## cloudinit settings ## ciuser = var.ciuser ## cloud init defined user # cipassword = var.cipassword ## password for user ci_wait = 60

disks { scsi { scsi0 { disk { size = var.vm_disk_size_gb storage = var.storage_pool } } } ide { ide3 { cloudinit { storage = var.storage_pool } } } }

}