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

@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

@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