@MathieuRA That worked! Thank you. I thought json was the default format and it seems --json must be right after the rest word. I tried putting it at the end and it didn't work but not a big deal. Thank you. How do you mark this post as resolved?

When I run this xo-cli rest get vdis it shows me a list of VDIs but not all of them. At the end it will show ... 1447 more items. Here's an example output

'vdis/b1129b5c-517e-49e2-834c-d386d5faa795', 'vdis/df3b5d1b-c3ca-40d2-8a93-49195a2b564b', 'vdis/21ea982e-3fdb-4966-be37-483dd5360f64', 'vdis/bf6d04aa-bccd-47a3-abe5-ebadd5eb3925', 'vdis/c7100c77-cc86-4f2f-9d37-37241ebfe048', 'vdis/a0b7cb90-1a08-4ecf-8dde-4391cde3a051', 'vdis/728686f9-4957-421c-9732-4ea48964ebb9', ... 1447 more items ]

I tried to set the limit to a high number but it doesn't seem to work. Anyone have any ideas?
xo-cli rest get vdis limit=9999

@Gurve Oh wow that's neat! It works! very cool we can use the same query search from the GUI.
Thank you.

@Gurve Even though I figured out how to do it all in xo-cli now, I haven't figured out how to build the filter search in the querystring using the API method you mentioned above. Could you give me a couple examples for my curiosity as I may need it in the future.
&filter=[namelabelSearch]

@Gurve I was trying it your way and then I noticed something in the doc where we can use xo-cli to call any REST method. So from your example we can do the following in xo-cli

get all VMs
xo-cli rest get vms

get single vm with id. this includes the VDI disks IDs I needed
xo-cli rest get vms/d55b0683-2fb9-7b06-6fa5-be6f2065e4b5

get vdis for a vm by vm id
xo-cli rest get vms/d55b0683-2fb9-7b06-6fa5-be6f2065e4b5/vdis

get VDI details with vdi ID
xo-cli rest get vdis/50436f36-5d5b-4048-9834-2cad0b869f66

Thank you so much!! you solved my problem

I figured out how to expand a VDI disk if I can get the id of the disk. But how do I get a list of disks attached to a VM if I have the name label of a vm? This is what I would run to get object details of the vm but I was hoping it would show a list of VDI ids attached to this VM but it doesn't.

xo-cli list-objects name_label=vmtest1

I'm trying to expand a VM disk using xo-cli or some automated method with a script. Anyone done this before and have an example?

@eeldivad i turned on "override-certs" option and it seems to work now. I'm still curious why the other build fails. Does anyone know how i can generate those 3 pem files manually to test?

@Danp I created a new xoa vm using this official script
bash -c "$(wget --no-verbose -O- https://xoa.io/deploy)"

I logged in and the sdn controller wasn't available until I signed up for the trial. I updated xoa as well.
Looks like sdn controller is installed after I enabled the trial version.

Then I added a host and tried to create a private network and it failed with this error:
80AC6283327F0000:error:0A000418:SSL routines:ssl3_read_bytes:tlsv1 alert unknown ca:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1590:SSL alert number 48

2025-02-18T01:49:06.687Z xo:xo-server:sdn-controller:tls-connect ERROR TLS connection failed {
Feb 17 20:49:06 xoa xo-server[3661]: error: [Error: 80AC6283327F0000:error:0A000418:SSL routines:ssl3_read_bytes:tlsv1 alert unknown ca:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1590:SSL alert number 48
Feb 17 20:49:06 xoa xo-server[3661]: ] {
Feb 17 20:49:06 xoa xo-server[3661]: library: 'SSL routines',
Feb 17 20:49:06 xoa xo-server[3661]: reason: 'tlsv1 alert unknown ca',
Feb 17 20:49:06 xoa xo-server[3661]: code: 'ERR_SSL_TLSV1_ALERT_UNKNOWN_CA'
Feb 17 20:49:06 xoa xo-server[3661]: },
Feb 17 20:49:06 xoa xo-server[3661]: address: 'x.x.x.x',
Feb 17 20:49:06 xoa xo-server[3661]: port: 6640
Feb 17 20:49:06 xoa xo-server[3661]: }

Is anyone else having issues with SDN controller from a fresh xoa install? This is the 4 time I've reinstalled xoa with a fresh VM. I'm now using this version:

Current version: 5.102.1 - XOA build: 20241004

• node: 20.18.0
• npm: 10.8.3
• xen-orchestra-upload-ova: 0.1.6
• xen-orchestra-web: 0.6.0
• xo-cli-premium: 0.32.1
• xo-server: 5.168.1
• xo-server-audit-premium: 0.12.1
• xo-server-auth-github-premium: 0.3.1
• xo-server-auth-google-premium: 0.3.1
• xo-server-auth-ldap-premium: 0.10.10
• xo-server-auth-oidc-premium: 0.3.0
• xo-server-auth-saml-premium: 0.11.0
• xo-server-backup-reports-premium: 1.4.4
• xo-server-load-balancer-premium: 0.10.1
• xo-server-netbox-premium: 1.7.0
• xo-server-netdata-premium: 0.2.0
• xo-server-perf-alert-premium: 0.6.0
• xo-server-sdn-controller-premium: 1.0.11
• xo-server-telemetry: 0.7.0
• xo-server-transport-email-premium: 1.1.0
• xo-server-transport-icinga2-premium: 0.1.2
• xo-server-transport-nagios-premium: 1.0.2
• xo-server-transport-slack-premium: 0.0.1
• xo-server-transport-xmpp-premium: 0.1.3
• xo-server-usage-report-premium: 0.10.6
• xo-server-web-hooks-premium: 0.3.4
• xo-server-xoa: 0.29.3
• xo-web-premium: 5.167.0
• xoa-cli: 0.40.1
• xoa-updater: 0.50.7

@Danp it returns v20.18.3

@Danp I think this is the latest version. it's the latest when I run the install from
https://github.com/ronivay/XenOrchestraInstallerUpdater

cat /opt/xo/xo-server/package.json | grep version
"version": "5.170.0",

Here's the commit from about page.
https://github.com/vatesfr/xen-orchestra/commit/66e677d7cbf0089fd48db0c4de1293ffa44cb0d8

0 fbeauchamp committed to vatesfr/xen-orchestra

feat(V2V/powerOff): handle queued state when stopping the VM (#8328)

zammad#34451

I restarted the service and see this error during start up

Feb 16 20:14:25 systemd[1]: Started XO Server.
Feb 16 20:14:26 xo-server[40452]: 2025-02-16T20:14:26.851Z xo:main INFO Configuration loaded.
Feb 16 20:14:26 xo-server[40452]: 2025-02-16T20:14:26.871Z xo:main INFO Web server listening on https://[::]:80
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.276Z xo:main INFO Setting up /robots.txt → /opt/xo/xo-builds/xen-orchestra-202502160214/packages/xo-server/robots.txt
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.342Z xo:main INFO Setting up / → /opt/xo/xo-web/dist/
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.342Z xo:main INFO Setting up /v6 → /opt/xo/xo-builds/xen-orchestra-202502160214/@xen-orchestra/web/dist
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.418Z xo:plugin INFO register audit
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.419Z xo:plugin INFO register auth-github
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.419Z xo:plugin INFO register auth-google
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.420Z xo:plugin INFO register auth-ldap
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.420Z xo:plugin INFO register auth-oidc
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.420Z xo:plugin INFO register auth-saml
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.421Z xo:plugin INFO register backup-reports
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.421Z xo:plugin INFO register load-balancer
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.421Z xo:plugin INFO register netbox
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.421Z xo:plugin INFO register perf-alert
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.422Z xo:plugin INFO register sdn-controller
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.422Z xo:plugin INFO register transport-email
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.422Z xo:plugin INFO register transport-icinga2
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.423Z xo:plugin INFO register transport-nagios
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.423Z xo:plugin INFO register transport-slack
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.423Z xo:plugin INFO register transport-xmpp
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.424Z xo:plugin INFO register usage-report
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.424Z xo:plugin INFO register web-hooks
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.424Z xo:plugin INFO register test
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.425Z xo:plugin INFO register test-plugin
Feb 16 20:14:27 xo-server[40452]: foobar
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.783Z xo:plugin INFO failed register test
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.783Z xo:plugin INFO Cannot read properties of undefined (reading 'default') {
Feb 16 20:14:27 xo-server[40452]:   error: TypeError: Cannot read properties of undefined (reading 'default')
Feb 16 20:14:27 xo-server[40452]:       at Xo.registerPlugin (file:///opt/xo/xo-builds/xen-orchestra-202502160214/packages/xo-server/src/index.mjs:369:18)
Feb 16 20:14:27 xo-server[40452]:       at runNextTicks (node:internal/process/task_queues:60:5)
Feb 16 20:14:27 xo-server[40452]:       at processImmediate (node:internal/timers:454:9)
Feb 16 20:14:27 xo-server[40452]:       at process.callbackTrampoline (node:internal/async_hooks:130:17)
Feb 16 20:14:27 xo-server[40452]: }
Feb 16 20:14:27 xo-server[40452]: strict mode: required property "discoveryURL" is not defined at "#/anyOf/0" (strictRequired)
Feb 16 20:14:27 xo-server[40452]: strict mode: missing type "object" for keyword "required" at "#/anyOf/1/properties/advanced" (strictTypes)
Feb 16 20:14:27 xo-server[40452]: strict mode: required property "authorizationURL" is not defined at "#/anyOf/1/properties/advanced" (strictRequired)
Feb 16 20:14:27 xo-server[40452]: strict mode: required property "issuer" is not defined at "#/anyOf/1/properties/advanced" (strictRequired)
Feb 16 20:14:27 xo-server[40452]: strict mode: required property "userInfoURL" is not defined at "#/anyOf/1/properties/advanced" (strictRequired)
Feb 16 20:14:27 xo-server[40452]: strict mode: required property "tokenURL" is not defined at "#/anyOf/1/properties/advanced" (strictRequired)
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.883Z xo:plugin INFO successfully register auth-google
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.883Z xo:plugin INFO successfully register auth-ldap
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.883Z xo:plugin INFO successfully register auth-oidc
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.883Z xo:plugin INFO successfully register auth-saml
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.883Z xo:plugin INFO successfully register netbox
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.883Z xo:plugin INFO successfully register transport-email
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.883Z xo:plugin INFO successfully register transport-icinga2
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.883Z xo:plugin INFO successfully register transport-nagios
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.883Z xo:plugin INFO successfully register transport-slack
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.883Z xo:plugin INFO successfully register transport-xmpp
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.883Z xo:plugin INFO successfully register usage-report
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.883Z xo:plugin INFO successfully register web-hooks
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.883Z xo:plugin INFO successfully register test-plugin
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.883Z xo:plugin INFO successfully register backup-reports
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.883Z xo:plugin INFO successfully register load-balancer
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.895Z xo:plugin INFO successfully register auth-github
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.895Z xo:plugin INFO successfully register audit
Feb 16 20:14:27 xo-server[40452]: 2025-02-16T20:14:27.896Z xo:plugin INFO successfully register perf-alert
Feb 16 20:14:28 xo-server[40452]: 2025-02-16T20:14:28.133Z xo:plugin INFO successfully register sdn-controller

@Danp i removed those 2 files and tried again. Now it hangs when I clicked on "Save configuration"
I see this in the log when it's hanging. I waited at least 5 minutes during the hang. I also noticed those 2 files were recreated in the same folder /var/lib/xo-server/data/sdn-controller so my guess is it's hanging trying to create the 3rd file client-cert.pem

Feb 16 19:59:25 xo-server[12428]: 2025-02-16T19:59:25.434Z xo:xo-server ERROR uncaught exception {
Feb 16 19:59:25 xo-server[12428]: error: TypeError: Cannot read properties of undefined (reading 'toString')
Feb 16 19:59:25 xo-server[12428]: at ReadFileContext.callback (/opt/xo/xo-builds/xen-orchestra-202502160214/node_modules/node-openssl-cert/index.js:3032:35)
Feb 16 19:59:25 xo-server[12428]: at FSReqCallback.readFileAfterOpen [as oncomplete] (node:fs:300:13)
Feb 16 19:59:25 xo-server[12428]: at FSReqCallback.callbackTrampoline (node:internal/async_hooks:130:17)
Feb 16 19:59:25 xo-server[12428]: }

@Danp the folder exists. I see 2 pem files there but client-cert.pem is missing. So it looks like it tried to create the 3 pem files but failed to create the client-cert.pem. Any suggestion?

ls /var/lib/xo-server/data/sdn-controller
ca-cert.pem client-key.pem

@Danp I just checked the logs and it's the same I listed above. I installed this as non-root user with sudo rights and then i rebuilt the vm with root permissions. This is a fresh install on a fresh OS so must be a bug somewhere. The problem is it doesn't auto-generate the keys as it said it would if I don't specify a path. If I create those 3 key files in a folder and specify the path then it will save properly. But these are blank files I created as I'm not sure how to generate them myself with openssl. Does anyone happen to have the command to use? This is just a test lab so I don't want to deal with letsencrypt or external certificate authorities.
Error: ENOENT: no such file or directory, open '/var/lib/xo-server/data/sdn-controller/client-cert.pem'

@BenjiReis I'm having the same problem. When I leave cert-dir empty and turn on override-certs and click "Save Configuration" then it gives me this error. This is a fresh build from ronivay's github with nothing but the basics installed. See screenshots.

ENOENT: no such file or directory, open '/var/lib/xo-server/data/sdn-controller/client-cert.pem'

@iLix That worked! I guess i forgot to enable NFSv4 after rebuilding it.

We recently rebuilt truenas. The setup allowed me to import the old pool after it scanned the drive. I then tried to create a new SR to the NFS share but it shows 3 different GUIDs and unable to create the SR.

I see 3 different GUIDs and when I click on the icon next to them to "Reattach SR" it says "In use" and then doesn't connect. The error log is
SR_BACKEND_FAILURE_73(, NFS mount error [opterr=mount failed on server 10.10.1.2 with return code 32], )

When I click on "Create" button it also gives the same error. I think those 3 GUIDs corresponds to 3 different xen hosts that were attached to this NFS in the past before I rebuilt truenas. Any ideas what I should do? I don't want to rebuild the pool and lose the data in it.