Hi @eeldivad

You can use the json flag. xo-cli rest --json get vdis

Hi @irtaza9
You have a typo in your vm-templates URL.
fields instead of field

Hi @irtaza9.
The REST API is only available for admin users.
It is planned to handle other types of users in a few months

@irtaza9 you need to use the user-id, not the username

Hi @irtaza9
FYI, for about 2 years, VMs expose a creation field:

"creation": {
    "date": string,
    "template": string,
    "user": string
  },

With this you can filter VMs by creation.user to list only VMs created by a user.
/rest/v0/vms?filter=creation:user:<user-id>

I will create a card for this feature request to discuss with the whole XO team. I will keep you updated here

Hi @rtjdamen
This should be doable using xo-cli.
xo-cli backupNg.runJob id=<your-job-id> schedule=<your-schedule-id> vm=<your-vm-id>

@RS if you are using XO from source, you need to change your branch and rebuild XO

Hi @RS
Just to let you know, there is a branch available to test RPU/install patches with XenServer 8. (xs-8-install-updates)
Feel free to test and give feedback. Thanks

FYI, we have added this feature to our backlog

Hi
I created a card on our side to discuss this feature request.
I will keep you updated.

Hi @flakpyro
You can do xe help vm-migrate to see all available parameters and a small description.

BTW, in XO, if a network is specified for the migration, we call vm.migrate_send otherwise vm.pool_migrate.
vm.migrate_send also migrates VM's VIFs and VDIs.

Questions for the XCP team:

• What happens if you do a vm.migrate_send but the destination SR for the VDIs is the same?
• Is there a way to call vm.pool_migrate using a specific network?

Hi @Sugarat. thanks for the report.
Can you try this branch: fix-handle-inavlid-vm-creation?
This should fix the issue

@rs Yes, this is normal. I am still working on making the installation possible via XO.

Hi @RS.
I just wanted to know if you can test this branch: fix-xs-8-patches.
It should fix the list of missing patches (not the RPU or other update function from XO)

Well, the problem is here then.
The XAPI reports NULL (NULL) so XO can't compare your bios version and display if it is up to date or not.

@olivierlambert Do you know why there is no value here?

Good catch for the extra underscore, it will be fixed, BTW xo-cli should not return true. In your host's Advanced tab, what is shown in Manufacturer Information and BIOS Information?

Hi.
The IPMI plugin is only used to display hardware information if you are using mona_1.44gg.

To display if a BIOS update is available, we mainly fetch this endpoint: https://pictures.2cr.si/Images_site_web_Odoo/Pages_produit/VATES-BIOS_BMC_last-version.json

Does your host have access to this endpoint?
What is the ouput of xo-cli host.getBiosInfo id=<host-id>

Hi
Indeed. We will see how we can fix this bug.
Thanks

@JamfoFL As the bug appears to be non-trivial, I’ll create the issue on our end, and then we’ll see with the team to schedule this task. We’ll keep you updated here.