@samuelolavo Yes, I do use NUT, but I don’t want to install any additional packet on XCP-ng. The way I found leverage the SSH authorized keys restrictions, and so you only need to change one file. Thanks for the link anyway

@samuelolavo Thanks for your answer It's very weird because by seeing the command outputs that you pasted, it looks like everything is behaving as it should be. Even the PCI ID (segment:bus:device:function) seems to stay correct (0000:03:00.0) I'll ask others internally.

@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.

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