Offline
@coolsport00 Hello, I don't know the VMware feature you're talking about.
I would use Packer https://github.com/vatesfr/packer-plugin-xenserver and Cloud Base init https://cloudbase-init.readthedocs.io/en/latest/intro.html to build a Windows VM template. The sysprep would be run at the end of the packer for example using the provisioner powershell or in the shutdown_command
NB: do not forget to deploy guest tools inside the template.
@dinhngtu might have also suggestions
Hello @tmnguyen
About the XOSTOR limit, I read the devs saying it is like this as of now.
About using Linstor created by and for XOSTOR with another apps, in your case a Talos Kubernetes cluster, I think it should work, but all the volumes not created by XOSTOR would be unmanaged neither by XOSTOR nor by XO. So imagine, one admin would check in XO that a XOSTOR SR is not used anymore in the XO web ui, and would remove it. But would not think that it was also used for PV/PVC Kubernetes. There is this kind of risk. And as of now we do not support this.
By the way, we are going to start this month to write a CSI driver for Kubernetes for Xen Orchestra. This means from within a Kubernetes cluster you will create PVs/PVCs that would be backed by VM disks, aka VDIs
Subscribe to this topic if you want to be notified for the updates on this https://xcp-ng.org/forum/topic/10301/devops-megathread-what-you-need-and-how-we-can-help
Hello, I suggest you look also for Packer to build ready to use VM templates, with cloud-init, guest tools, and the softwares you'd need. There's a blog post for this https://xcp-ng.org/blog/2024/02/22/using-packer-with-xcp-ng/.
@Tristis-Oris
Hello, thanks for the report. I will try to fix and improve things, but before I have a few questions.
For your information, the defaults cloud-init configs snippets come from here: https://github.com/vatesfr/xen-orchestra/blob/master/packages/xo-web/src/common/cloud-config.js#L78-L88
For growpart it depends of the template used. Last time I tested it was working with a Debian 12 template from the XOA Hub.
@markxc said in create a new vm using a iso setting cpu ram network via api:
Out of curiosity: how do you handle the Xen Orchestra appliance installation?
We use Packer, a Debian iso and an Ansible playbook in the ansible provisioner. See https://developer.hashicorp.com/packer/integrations/hashicorp/ansible/latest/components/provisioner/ansible
With this setup, we achieve these tasks:
We also have a CI/CD pipeline doing this automatically.
@irtaza9 I am glad to read you find a solution that works for you. And thanks for sharing!
Hello there, we released a new Pulumi Xen Orchestra provider last month ! It's worth noting that the work on this was started by some contributors from DESY, and that now we (Vates) commit to support and maintain it. This demonstrate the strength of joined work from both community and Vates on free and open source softwares 
So what is offered is to declare your infrastructure as code, in Javascript or Typescript, Go, or Python (pick the one you prefer 
) and to deploy, maintain, and update it.
@irtaza9 Hey, I tried quickly on my local laptop but was not able to handle to auth. So I asked internally who already knows how this works. (Unfortunately I cannot spend multiple hours on this)
Hello, the Hub is offered as is. We'll update the available templates soon. In the meantime you can convert any VM to be a template.
More here :
Hello @nick.lloyd, the logic of expected_ip_cidr = "10.0.0.0/16" is available in Terraform, not in XO. But as you're building a Python script you could implements there the same logic: define a variable for your expected cidr, and poll the IP of the VM until it matches.
Else, as you're using Python, you might be interested by the Pulumi Python SDK we will release this month. It allows you to easily define your infrastructure as code like with Terraform, but using Python 
There you will also have the expected_ip_cidr param, in Python..
https://pypi.org/project/pulumi-xenorchestra/
https://github.com/vatesfr/pulumi-xenorchestra/
https://www.pulumi.com/product/infrastructure-as-code/
@dsmteam Yes I totally agree, a user who logs out from XO, might also have the choice to logout from all SSO'ed applications. That would be for the feature request list
Hello, thanks for the report. Actually XO does not implement Single Log Out. So it is expected that only the session related to XO is invalidated when the user click on the logout button.
Maybe something to add in XO6 ping @pdonias ?
@bufanda I think we'll be able to add backup support to Terraform when 1. the provider will use the new Rest API, and 2. when this API will offer endpoints for backups management. I took note. (This won't be done in minutes )
About Ansible, it'll depends also if/when we start work on it.
@kiu Thanks, it's in our backlog. We'll update you when it would move to planned tasks.
@kagbasi-ngc it looks like the same issue you had in https://xcp-ng.org/forum/topic/10140/bsod-with-inaccessible-boot-device-after-uninstalling-the-xcp-ng-guest-tools/ is the solution suggested by @dinhngtu works here?
@kagbasi-ngc I am not sure, but I would force shutdown it from XO, then boot it again. If it does not work I'd try some fail safe mode, but I did not used Windows VMs that much this last years. Maybe someone else would be more helpful...
Hello, are the guest tools and drivers installed on this Windows VM https://docs.xcp-ng.org/vms/#windows ?
@wezke Hello, can you switch to this latest version of the provider, ensure that your configuration is still valid or fix what would be needed, and report how it behaves?
https://registry.terraform.io/providers/vatesfr/xenorchestra/latest
