Pinging @julien-f maybe

Ping @lsouai-vates

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

Hehe congrats @Greg_E for finding the Easter egg then

Nice catch! I have the same issue here

We did that last year, but it triggered more problems than solving. Maybe we'll try to get back on it, but it's a decision on XO team (@lsouai-vates )

Please refresh, or disconnect/reconnect, it should be sync between the 2.

If you connect to any slave, XO will be redirected to the new master.

Indeed, because if XO is compromised, then it could disable immutability.

Indeed, @bufanda is right and pointing to the right direction. Thanks!

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

My previous ping didn't work so I will try my luck with @lsouai-vates

No, for XO there's no API nor UI to modify XOA network settings. Something we could change in the future (adding @lsouai-vates so we add it in the backlog, likely for XO 6).

For XCP-ng, I'm not sure, let me ping @stormi

Hi,

Thanks for asking. @julien-f are we managing IPv6 already via our helper script? Otherwise you need to indeed change it manually, like you would for a regular Debian VM. It's not exposed in XO UI because nobody asked before, but it doesn't mean it's a bad idea

For XCP-ng, yes you can change a network address in the Host/network tab.

Adding XO PO in the loop @lsouai-vates

@McHenry That's a very interesting result (adding @florent to see it and @thomas-dkmt to maybe document this).

Regarding health feature, how we could guess down which memory we could go to test if the test recovery VM boots?

Ping @julien-f

This is a dual bug:

1. In the Linux PV driver upstream
2. How it was backported by RedHat

Both upstream and RH are aware, avoid doing the update for now until we have the confirmation it's fixed.

@stormi we need someone assigned to this to monitor and report any news and progress.

Ping @lsouai-vates

Hi,

Indeed, XO anti affinity exists since 4 years in Xen Orchestra, see https://xen-orchestra.com/blog/xen-orchestra-5-57/

This is something else cooked by Citrix, so irrelevant while using XO anyway.