@MathieuRA

Thank you for the PR merge.
I've tested this and both REST API and XO6 seem to work perfectly.
As this issue is resolved, do I need to close this topic or how does things work here?

Br,
Aki

@MathieuRA

Wow thank you for super fast response! I did check the XO6 also previously and noticed that it had the option to define VCPU count but it didn't work, this explains it completely
Waiting for merge. I will test and share results here once available.

Thanks again!

Dear Community and Vates staff,

I'm trying to automate VM creation using XO REST API, specifically using /rest/v0/pools/_/actions/create_vm endpoint.
Looks like this endpoint doesn't yet support defining CPU count for the VM. I have XO Community setup in the lab which is compiled from sources. Version is commit c70f9, while writing this it's 9 commits behind master.

After searching another topics, I found following, https://xcp-ng.org/forum/post/87887

8 Jan 2025, 18:14
We will try to add support for CPU settings soon.
Also, expect things to accelerate in 2025 regarding the REST API.

This sounds awesome, but as we are already over year 2025, would there be any information available when CPU settings are available in the REST API ?
Are there any alternative methods available for this need? Previously mentioned Topic mentions JSON RPC but is there any docs available for this interface.

Attaching also screenshot of create_vm endpoint schema from swagger:

Thank you in advance!

Br,
Aki

Dear Community,

Any hints what might trigger following issue when I try to create proxy inside XO (please check attached screenshot below).
XO is installed by following https://xen-orchestra.com/docs/installation.html#from-the-sources instructions.

Most likely I'm doing something wrong, since I couldn't find anything similar from the forum search.

Operating system information:

• OS = Debian 10 (Buster)
• Node version = v16.14.2

Thank you in advance!

Br,
Aki