Pavel Boldyrev

Ah, that's migration of a `promox_virual_environment_file` resource, not a VM. You'd probably need to put your cloud_init file to a shared datastore (ceph, nfs, cifs, etc) to support this scenario....

> But this promox_virtual_environment_file is already set to be shared as a nfs (NAS2), Great, then it doesn't need to be moved from node to node, as the file should...

@mmaced Please feel free to reopen this issue if you need further assistance.

Indeed, this is the same common problem with clone. The VM's resources are copied and stored in the provider state, but are missing from the plan. So, on the next...

Thanks a lot!❤️

Hi @krnwrks! It won't be possible to reliably populate the VM IP addresses at the end of VM provisioning flow without using [qemu guest agent](https://registry.terraform.io/providers/bpg/proxmox/latest/docs/resources/virtual_environment_vm#qemu-guest-agent). > This provider requires `agent.enabled...

Hm... The provider actually does [wait for a non-localhost IP address](https://github.com/bpg/terraform-provider-proxmox/blob/fb1105d93bd2fec4d9fe0cfa9155539d17d8b418/proxmox/nodes/vms/vms.go#L529-L553) 🤔 @krnwrks Could you pls. provide [additional details about your environment](https://github.com/bpg/terraform-provider-proxmox/blob/main/.github/ISSUE_TEMPLATE/bug_report.md?plain=1#L39-L44), and perhaps output from your plan execution? A...

As a workaround you may try adding something like this to your VM config: ```hcl provisioner "local-exec" { when = create command = "sleep 5s" } ```

There is a good analysis on "wait for IP" behaviour in https://github.com/bpg/terraform-provider-proxmox/issues/668#issuecomment-1785831601

I'm going to close this issue as I haven't heard back from the author with additional details. @krnworks, please feel free to reopen it if you need more support on...