@andSmv thanks for coming back on this. Actually you are right it is a limit on Windows OS as per documentation here https://learn.microsoft.com/en-us/windows-server/get-started/editions-comparison-windows-server-2019?tabs=full-comparison. Should have checked this before I asked the question

@ruskofd is right. You should be able to use the cloud_network_config attribute to achieve this. The following code is untested but should launch a vm with a static IP. Please see the xenorchestra_vm resource docs and the cloud-init networking v1 docs for more details. resource "xenorchestra_vm" "static_ip_vm" { .... cloud_network_config = <<EOF network: version: 1 config: - type: physical name: eth0 subnets: - type: static address: STATIC_IP/24 gateway: GATEWAY_IP dns_nameservers: - 8.8.8.8 EOF } Let me know if you have any questions or issues using cloud_network_config, As for the blog post, the VM would have been assigned an ip address via dhcp (assuming the guest OS had cloud-init installed which was true for the VM template in the blog post).

@axel I just ran the installation script on a Debian 10 VM and it worked as expected. Even when using the "official" way, sometimes the installation can fail due to things like -- issues with recent commit to github repo issues with upstream dependency etc This is why the pre-built XOA appliance exists. Feel free to open an issue over on the script's Github repo if you continue to encounter issues.

Yes, for now and until the proxies are available, everything is going through the XOA. In your example, it goes from Site 2 (VM1) to Site 1 (XOA) and then to site 3 (VM1 replicated) If you are interested into proxies, feel free to subscribe on the form at the end of the article, we are planning to have an alpha version as soon as possible