@Pix FYI, I was just doing some testing on this exact function and I was able to add a network to the pool when using the UUID for the host's matching PIF. The UUID you were using is from the pool's network, which won't work here. For example -- Networks [17:29 xenserver-slnqfzrh ~]# xe network-list uuid ( RO) : a379a6e7-f099-f838-6514-486de4d56e80 name-label ( RW): Pool-wide network associated with eth0 name-description ( RW): bridge ( RO): xenbr0 uuid ( RO) : b14a0bdd-2f77-25f7-3a76-b830ff971624 name-label ( RW): Pool-wide network associated with eth2 name-description ( RW): bridge ( RO): xenbr2 uuid ( RO) : 00b6604f-9098-023b-5880-0ef9f8e1b437 name-label ( RW): Pool-wide network associated with eth1 name-description ( RW): bridge ( RO): xenbr1 uuid ( RO) : e3be0e1a-9872-4b90-c851-35eb30a86920 name-label ( RW): Pool-wide network associated with eth3 name-description ( RW): bridge ( RO): xenbr3 uuid ( RO) : c54ecffe-9467-5d5f-cb73-ec10dedef2b9 name-label ( RW): Host internal management network name-description ( RW): Network on which guests will be assigned a private link-local IP address which can be used to talk XenAPI bridge ( RO): xenapi PIFs [17:49 xenserver-slnqfzrh ~]# xe pif-list network-uuid=00b6604f-9098-023b-5880-0ef9f8e1b437 uuid ( RO) : ea3edc31-9b23-402c-a65e-2316c88febb5 device ( RO): eth1 currently-attached ( RO): true VLAN ( RO): -1 network-uuid ( RO): 00b6604f-9098-023b-5880-0ef9f8e1b437 uuid ( RO) : 3a1ef416-787f-45b4-ace9-0147c2f3ca07 device ( RO): eth1 currently-attached ( RO): true VLAN ( RO): -1 network-uuid ( RO): 00b6604f-9098-023b-5880-0ef9f8e1b437 Adding a VLAN [18:27 21] xoa:xoa$ xo-cli network.create pool=63b7154a-1a6c-8642-525e-c6abb0acc941 name="VLAN20 - On Eth1" pif=ea3edc31-9b23-402c-a65e-2316c88febb5 vlan=json:20 52d18dc6-8078-a7ce-4bc5-d4337d2fb970 HTH, Dan

Hi, Can you describe the target/objective you want to achieve/expect?

@pxn said in Java SDK, XmlRpcClientException: Failed to parse server's response: Duplicate name: restrict_vtpm: If you still encounter this issue - I found the way to bypass it. You can create your own mapper by extending on RecursiveTypeParserImpl and just copy-paste logic from MapParser (package org.apache.xmlrpc.parser;), except that logic of checking duplication, then you can inject custom parser to your custom factory (Extend TypeFactoryImpl and override getParser method). And inject this Factory to your client new XmlRpcClient().setTypeFactory(new CustomFactory(client)); This works fine for me, I hope this could help you. Alex

Yes, you can have a list of all available calls by doing xo-cli list-commands

Yes, you can use JSON-RPC et REST APIs together for now We will try to add support for CPU settings soon. Also, expect things to accelerate in 2025 regarding the REST API.

@CodeMercenary Can't help you there. The only thing I use(d) is the cli on the xcp hosts themselves. reboot or shutdown

@samuelolavo Shell only handles string values, to pass other types to xo-cli you need to encode them in JSON and use the json: prefix: xo-cli resourceSet.create name=test-resource subjects=json:'["d301d9ea-9e22-4480-bf40-111111111111"]' objects=json:'["8fb06362-d8fe-598b-f819-11111111111111"]' shareByDefault=json:true

@samuelolavo No, users management and self service are not in the REST API yet.

@julien-f thanks! I have tested it and its working now! cheers Ringo

Yes, you can use Terraform directly

Hi @olivierlambert , Okay, I made some progress today and have worked out the steps to remove, delete or add drives to a VM. Removed drive from the server attached to and also deleted the disk itself xo-cli vdi.delete id=<the id of the VDI> Removed drive from the server attached to, but didn't delete the disk! xo-cli vdb.delete id=<the id of the VBD> Added a drive to the server xo-cli vm.attachDisk vdi=<the id of the VDI> vm=<the id of VM> If was the last one that I was missing. I'm still not sure of the difference between the 'uuid' and 'id' fields, but will use the 'id' as this seems to be what the commands are wanting. Thanks Kent.

Perfect, excellent news Enjoy XCP-ng!

@Morpheus0x Your feature request has been noted and will be put in the backlog. It appears to be trivial so it should we'll try to do it soon but I cannot tell you when.

I think it might be easier to do so with the new REST API, what do you think @julien-f ?

@splastunov said in Disable TX checksumming with API: XAPI Thank you, I found https://xapi-project.github.io/xen-api/networking.html

@cmuller Thank you! It's great to see code-sharing in the forum!

First of all, take a look at the general XO REST API documentation. Then, take a look at xo-cli --help which explain how to use it to interact with the REST API. You can list all VDIs at /rest/v0/vdis, snapshots are available at /rest/v0/vdi-snapshots. You also have the ability to list the VDIs attached to a specific VM at /rest/v0/vms/:id/vdis.

@samuelolavo Not exposed in the REST API yet. You can use the legacy API for this: xo-cli acl.get xo-cli resourceSet.getAll

@julien-f maybe there can we some recoverypoint endpoint? or remotes?