@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

@McHenry hello, thanks for the report. Can you open a suggestion on Github so we can plan it or next roadmap? Have a good day.

Could you please provide the output of (for the master and the candidate host): xe host-list params=software-version It does seem odd....

Ping @dthenot

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.

@florent can you help him?

@plaidypus You can configure the disk within the guest OS to match whatever formatting you want. I would suspect the performance gains would be included as well, but you'd have to test and verify.

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

@sborrill And for completeness, try pvshim (a.k.a. pv-in-pvh) using xl: Download https://ftp.netbsd.org/pub/NetBSD/NetBSD-10.1/amd64/binary/kernel/netbsd-INSTALL_XEN3_DOMU.gz Create /root/nbpv containing: name = "nbpv" type="pvh" pvshim=1 pvshim_cmdline="pv-shim console=xen pv-linear-pt=true" kernel = "/root/netbsd-INSTALL_XEN3_DOMU.gz" memory = 1024 Boot VM successfully with xl create -c nbpv So pv-in-pvh does work (does require pv-linear-pt=true on shim command line though).

@RawbDeeni Thank you! I had the same problem using 8.2 lts. I ended up formatting and using 8.3, and I didn't have any issues after that. I'm glad I found a better alternative to use this hypervision from a vmware end user for over 10 years until Broadcom killed it.

I got this error on a backup, that the VM was created on 8.2 but at this point the hosts are both updated to 8.3. Is there something I am missing? I am new-ish to XCP/Xen, but really liking it. Not sure what other info to include here. I was trying to do DR. I am trying CR now, and assuming it will work based on your conversation. I don't think I really need CR in this case, I am probably only backing up this VM once a year. Zabbix (zabbix-host) Snapshot Start: 2025-04-23 11:34 End: 2025-04-23 11:34 VM (2.09 TiB free - thin) - xcp-dr-zabbix transfer Start: 2025-04-23 11:34 End: 2025-04-24 00:26 Duration: 13 hours Error: (intermediate value) is not iterable Start: 2025-04-23 11:34 End: 2025-04-24 00:26 Duration: 13 hours Error: (intermediate value) is not iterable Start: 2025-04-23 11:34 End: 2025-04-24 00:26 Duration: 13 hours Error: (intermediate value) is not iterable Type: full

Ping @lsouai-vates

@piotrlotr1 I think my original mini-lab did this, I had mistakenly joined these hosts to the big lab pool, found out is was wrong and detached them to make a mini-lab pool. There were some oddities when I did this, but I just worked past them and created their own pool and did my warm migrations. Wish I had taken better notes of this when I did it. I wiped and rebuilt my mini-lab now, so no going back.

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

so that is probably only a off by one error in the task code Thanks andrew

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

@McHenry xo-cli backupNg.getLogs --json limit='json:500' should work ( the command line parameter are considered as string )