@olivierlambert Hi Olivier, See attached (never realised you could just download these! Would have been handy a few times in the past...) Apologises for the large size, the full error message was too large so snipped out a load of the UUID's. plugin.configure { "id": "perf-alert", "configuration": { "hostMonitors": [ { "smartMode": false, "uuids": [ ], "alarmTriggerLevel": 90, "excludeUuids": false } ], "vmMonitors": [ { "uuids": [ "5f7e0255-4946-9399-f3b4-124cf668138e", "6dcfd1b6-f380-a6b5-7307-40be4af070bb", ], "smartMode": true, "alarmTriggerLevel": 90, "alarmTriggerPeriod": 600, "excludeUuids": false }, { "smartMode": false, "variableName": "memoryUsage", "alarmTriggerLevel": 90, "uuids": [ "5f7e0255-4946-9399-f3b4-124cf668138e", "6dcfd1b6-f380-a6b5-7307-40be4af070bb", ], "excludeUuids": false, "alarmTriggerPeriod": 600 } ], "srMonitors": [ { "smartMode": false, "uuids": [ "af7de4c2-9afd-e25e-21c3-adec82597c88", "9fdaeedd-0ffa-221e-aba0-d66637f89492", ], "alarmTriggerLevel": 90, "excludeUuids": false } ], "toEmails": [ "blanked@blank" ], "baseUrl": "http://xoa.blank.com" } } { "code": 10, "data": { "errors": [ { "instancePath": "/vmMonitors/0/smartMode", "schemaPath": "#/properties/vmMonitors/items/oneOf/0/properties/smartMode/anyOf/0/not", "keyword": "not", "params": {}, "message": "must NOT be valid" }, { "instancePath": "/vmMonitors/0/smartMode", "schemaPath": "#/properties/vmMonitors/items/oneOf/0/properties/smartMode/anyOf/1/const", "keyword": "const", "params": { "allowedValue": false }, "message": "must be equal to constant" }, { "instancePath": "/vmMonitors/0/smartMode", "schemaPath": "#/properties/vmMonitors/items/oneOf/0/properties/smartMode/anyOf", "keyword": "anyOf", "params": {}, "message": "must match a schema in anyOf" }, { "instancePath": "/vmMonitors/0/uuids", "schemaPath": "#/properties/vmMonitors/items/oneOf/1/properties/uuids/not", "keyword": "not", "params": {}, "message": "must NOT be valid" }, { "instancePath": "/vmMonitors/0/excludeUuids", "schemaPath": "#/properties/vmMonitors/items/oneOf/2/properties/excludeUuids/const", "keyword": "const", "params": { "allowedValue": true }, "message": "must be equal to constant" }, { "instancePath": "/vmMonitors/0", "schemaPath": "#/properties/vmMonitors/items/oneOf", "keyword": "oneOf", "params": { "passingSchemas": null }, "message": "must match exactly one schema in oneOf" } ] }, "message": "invalid parameters", "name": "XoError", "stack": "XoError: invalid parameters at invalidParameters (/opt/xo/xo-builds/xen-orchestra-202505011024/packages/xo-common/api-errors.js:26:11) at default._configurePlugin (file:///opt/xo/xo-builds/xen-orchestra-202505011024/packages/xo-server/src/xo-mixins/plugins.mjs:175:13) at default.configurePlugin (file:///opt/xo/xo-builds/xen-orchestra-202505011024/packages/xo-server/src/xo-mixins/plugins.mjs:199:16) at Xo.configure (file:///opt/xo/xo-builds/xen-orchestra-202505011024/packages/xo-server/src/api/plugin.mjs:12:3) at Task.runInside (/opt/xo/xo-builds/xen-orchestra-202505011024/@vates/task/index.js:175:22) at Task.run (/opt/xo/xo-builds/xen-orchestra-202505011024/@vates/task/index.js:159:20) at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202505011024/packages/xo-server/src/xo-mixins/api.mjs:469:18)" }

@Danp said in XOA fails after update to 5.106.0: @ferrao Prior to the latest release, the trial worked without actually activating the license on the XOA > Licenses tab. Double check that the license is activated (should look like this) -- [image: 1746139916552-d905469d-2f34-485e-bb8e-61e388faa430-image.png] This is what it will look like if the license hasn't been activated -- [image: 1746140018468-b08a2fff-939f-40af-832e-f50d020e8817-image.png] Oh man... That's a new thing? You're totally right. It's now working correctly again.

@gduperrey Ok, thank you. Appreciate the explanation.

@blackliner Honestly I never had this use case, but I would imagine terraform has a feature for this. I'll look into it, it's got me curious

Hi, Thanks for your report. Ideally, move XOA VM on another SR than the one doing the maintenance mode. Alternatively, you can do it manually with the CLI or XO Lite. You raised a valid question: XOA should have detected it was itself on the target SR and prevent it. However, even if it sounds simple, it might not be trivial. Anyway, I'm adding @lsouai-vates in the loop so we can improve this in the future

That's a security problem, due to Spectre/Meltdown, it's very dangerous to run a VM that could have more vCPUs than pCPUs on a host.

@Byte0 The json: makes the rest of the value interpreted as JSON, otherwise it is interpreted as a plain string. It is therefore required for all non-string values. Some method params (like memory for vm.set) accept both integers and strings, that's why it was working.

I mean I agree with the idea that sounds good, I need to be reviewed again to see if we could do better than we did

Dual stack support for IPv4 + IPv6 on the management interface in XCP-ng 8.3: requires reinstalling to define both IPv4 and IPv6 for the management interface is still experimental, there are a few known issues CC @BenjiReis @gthvn1 @andriy.sultanov

Hi, Indeed, the pre requisite section is pretty clear about it: https://docs.xen-orchestra.com/installation#packages-and-pre-requisites And the error message was clear too: The engine "node" is incompatible with this module. Expected version ">=20.18". Got "18.19.1" However, if you think there's a way to improve this, let us know, we'll be happy to assist

@olivierlambert Just to be sure. Thanks.

Looks to be correct on the current release of XO from Source and reads as "Prevent Migration"

@olivierlambert Ok, will do. Thanks!

@ronan-a Any more information about RawISCSISR usage? I can't seem to find any good match on the web.

Merged. Works as intented, thank you.

@olympicgreg Hello! And thanks for your feedback on the ACL subject. I note this on our XO-6 next features, so we will discuss on it and see what we can improve. Indeed the ACL subject is quite not trivial and we keep on working on it. Have a good day and don't hesitate to give us feedbacks on XO features.

@NathanO Hello there! We have a feature on the isPubKeyTooShort spamming on the XO next sprint priority, so to me it should be available on May 2025 XO release. Check at the next blogspots to keep informed. Hope my comment responds to your questions, have a good day!

@Tomcatter yes it was already implemented in XO-Lite [image: 1744189947925-f1dc4d66-3ffc-43cc-baca-56f934901f99-image.png] You can find it from the pool view. (click on a pool on the treeview and then on the VM tab) It is also planned for XO-6, it is in our backlog for next features. Does it respond to your questions?

@lawrencesystems @olivierlambert Thought I'd provide an update here...only fair After getting everything running again, I was able to add 2 physical XCP Hosts to XO and get things going -> create a Pool; create some VMs; test Live Migration (not VDI-based yet); import from VMW (an issue there with Linux); but overall...able to dive into it a bit deeper and see how things in XCP/XO work vs VMW. So far, after getting through my initial issues...I think it's ok I think my Host2 network issue may have stemmed from attempting to add it back into XO when I was no longer seeing it in the Settings > Servers area after adding it to a Pool. I wasn't aware it would disappear from that area when adding it to a Pool. I don't think the documentation states this (unless I overlooked it? if not, would be helpful I think). Anyway...thanks to all for chiming in!

@FMOTrust I had this issue as well on a Slave host in my test environment. I was able to do Network Reset from xsconsole, but then after the Host rebooted to finish the reset, the Host reverted back to not having/seeing the Mgmt network, and...like you, I couldn't see any NICs either. Since this was for testing, and I had no VMs on it, I just reinstalled XCP. I think there's a way to reset XCP I saw in another Forums post by removing the Local SR? Olivier shared that in the post..but I don't remember what post it was. Not sure if this is a test or prod Host/environment for you...but if you can, unless someone from the Vates team comments, I think all that can be done is reinstall.