@danp Thank you. I will try this commit mentioned.

Hello,

yesterday evening I upgraded our Xen-Orchestra system. I upgraded Debian Buster (10) to Bullseye (11). After this I removed xen-orchestra completly and installed new from github master branch. I have this Version shown in "About": Xen-Orchestra, commit c2ba3

After this I could not start a windows VM because of a invalid paramter:

---Zitat---
vm.start
{
"id": "6e7c5e68-b034-6ec1-9656-73acbc44fe20",
"bypassMacAddressesCheck": false,
"force": false,
"host": "5c9587ea-ec8a-45b1-8b2b-5cb5c8efc4a0"
}
{
"code": 10,
"data": {
"errors": [
{
"code": null,
"reason": "strict",
"message": "should not contains property ["bypassMacAddressesCheck"]",
"property": "@"
}
]
},
"message": "invalid parameters",
"name": "XoError",
"stack": "XoError: invalid parameters
at Object.invalidParameters (/opt/xen-orchestra/packages/xo-common/src/api-errors.js:21:32)
at Object.call (/opt/xen-orchestra/packages/xo-server/src/xo-mixins/api.js:73:18)
at Api.callApiMethod (/opt/xen-orchestra/packages/xo-server/src/xo-mixins/api.js:300:19)"
}
---Zitat Ende---

Jobs for restarting VM's have a similar problem:

---Zitat---
vm.restart
{
"id": [
"32782bec-e5b5-c2ed-b46b-6831b7f80167",
"074a222c-54a7-4a09-8bfd-609ff95b94fb",
"62d0039c-d6de-3847-a4e1-a3573392e0d8",
"5a43b9e2-e44d-0814-0d08-c7c69ec6a823"
]
}
{
"code": 10,
"data": {
"errors": [
{
"code": null,
"reason": "type",
"message": "must be string, but is array",
"property": "@.id"
}
]
},
"message": "invalid parameters",
"name": "XoError",
"stack": "XoError: invalid parameters
at Object.invalidParameters (/opt/xen-orchestra/packages/xo-common/src/api-errors.js:21:32)
at Object.call (/opt/xen-orchestra/packages/xo-server/src/xo-mixins/api.js:73:18)
at Api.callApiMethod (/opt/xen-orchestra/packages/xo-server/src/xo-mixins/api.js:300:19)"
}
---Zitat Ende---

I thought this was caused by the upgrade to bullseye and tested jobs on a new Debian Buster and new master branch. Now on Version: Xen Orchestra, commit 8d692

But the same error for the job appears and job is not running.

Is this a bug, or is something wrong in my setup?

Best Regards, Torsten

Hi,
thank you for your support. I was out of Office for two weeks and will test this soon. I will give you feedback.

Regards, Torsten

@olivierlambert
Hi,
I want to restart two vm server in a fixed order.

• shutdown vm 1
• reboot vm 2
• start vm1

vm 1 should start after boot up of vm 2 is finished.

Hello,

how can I use the function "job.run.Sequence" for running jobs in a fixed order? I could not find a documentation for this.
I tried using this but I think I have not configured correct.

Best Regards, Torsten