It's great, thank you so far! I've noticed, that the reported OS in XenOrchestra (and XCP-ng Center) is reported differently compared to Citrix Tools. Is this intentional? For example, this is a Windows Server 2025 and not a Windows 11 24h2. [image: 1760339734958-37736f8f-199d-48a9-a6da-18ae49cb667c-grafik.png]

@psafont Sounds good on point #1. On point #2 I agree LLA shouldn't be the primary management IPv6 address on the interface, but you could run into trouble by not having a LLA address assigned at all. All of the IPv6 standards assume a LLA is assigned to an interface running IPv6 for things like NDP or RA to work ergo mysterious things could break as a result of an LLA address not being assigned. Just spitballing here, but if you're concerned that only an LLA would be assigned to an interface then perhaps there could be logic to disable IPv6 for said management interface if no non-LLA address is assigned, or IPv4 could be preferred if only LLA addresses as assigned?

XCP-ng 8.2 has just reached its end of life, but the adventure continues with XCP-ng 8.3 (and other versions to come). You can read the communication on this point on our blog: https://xcp-ng.org/blog/2025/09/16/xcp-ng-8-2-lts-reached-its-end-of-life/ To continue benefiting from updates and developments, we invite you, if you haven't already done so, to upgrade your systems to XCP-ng 8.3. A relevant thread has been around for quite some time if you want to participate in early testing of the updates: https://xcp-ng.org/forum/topic/9964/xcp-ng-8-3-updates-announcements-and-testing/

Yes, the old method should work

@TrapoSAMA All of mine are 2022, but saw this in previous driver versions with 2025. Low priority on this so I haven't fixed it yet.

@uberiain said in XCP-ng Center 25.04 Released: Hi, with this modification on MainWindow.cs in private List<TabPage> GetNewTabPages() adding this at the end: This will add the tab back in XCP-ng Center but I don't think it works in XCP-ng 8.3. I just upgraded from 8.2.1 to 8.3 when I logged into XCP-ng Center I saw the error message Active Directory authorization is not available","Server 'xcp-ng-TEST' has failed to connect to the Active Directory server. INTERNAL_ERROR: [ Xapi_systemctl.Systemctl_fail(""INTERNAL_ERROR: [ Subprocess exited with unexpected code 1; stdout = [ ]; stderr = [ Job for winbind.service failed because the control process exited with error code. See \""systemctl status winbind.service\"" and \""journalctl -xe\"" for details.\n ] ]"") ]","xcp-ng-TEST","Jul 11, 2025 3:58 PM"," # systemctl status winbind.service winbind.service - Samba Winbind Daemon Loaded: loaded (/usr/lib/systemd/system/winbind.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2025-07-11 16:01:28 AEST; 3min 15s ago Docs: man:winbindd(8) man:samba(7) man:smb.conf(5) Main PID: 9593 (code=exited, status=1/FAILURE) Status: "Starting process..." I haven't figured out what to do yet. None of the users can log into XCP-ng Center using their Active Directory credentials and only root can log in. EDIT: Actually winbind wasn't even used in XCP-ng 8.2.1, I'm not sure why this service started up in 8.3. XCP-ng 8.2.1# systemctl status winbind.service ● winbind.service - Samba Winbind Daemon Loaded: loaded (/usr/lib/systemd/system/winbind.service; disabled; vendor preset: disabled) Active: inactive (dead) Docs: man:winbindd(8) man:samba(7) man:smb.conf(5) But I can see that windbind is used for XenServer 8.4 https://docs.xenserver.com/en-us/xenserver/8/users Anyone got suggestions on how to get AD authentication working with XCP-ng Center again? Or add users manaully? SOLUTION: What I found after following the steps in the in the XenServer page above is that if I disable AD Authentication then re-enable it then it will work. To Disable AD Authentication: xe pool-disable-external-auth Enable AD Authentication: xe pool-enable-external-auth auth-type=AD service-name=full-qualified-domain config:user=username config:pass=password Without the Users tab in XCP-ng Center, CLI command is needed to add or remove users. Refer to the XenServer page above. xe subject-add subject-name=entity_name

@dinhngtu Thanks and good point. After my previous post I did stumble across some info (can't find the links) that suggested something similar. If I'm remembering correctly, the basic idea was the flash/NVRAM memory on the motherboard, which stores boot entries, is limited. If it's full, it's possible / may be necessary to do some cleanup using the bios itself or utilities available for Linux (efibootmgr) and Windows (bcdedit). I've not tried this myself as our install is working properly, but perhaps that can help someone else in the event they stumble across this particular issue.

@Danp Oh thanks, that makes sense, though I am not sure how I got it to work in the POC... Cold migration will be fine for the time being anyway

@yllar Maybe it was because of the loopdevice not being completely created indeed. No error for this GC run. Everything should be ok then

@MW6 You've lost two disks in a single array, you're data is lost. Time to restore from backup.

@olivierlambert The only place running XCP-ng on things like an RK3588 make sense is for home lab stuff, I probably wouldn't even build work lab stuff on these. Never enough ram (so far) and limited cores, plus almost everything will need to be running in virtual processor architecture. All that said, it might be neat to simulate these ARM processors in x86 so that we could create a VM of the Pi, etc.

On the VMware side, it's possible VMware doesn't set the right mode, so try to boot in BIOS or UEFI to see if it boots.

@igor You are welcome !

@john-c As I mentioned in the release notes, @dinhngtu told me (and tested) that if Secure Boot is enforced, then Bitlocker doesn't fail on unexpected firmware changes. Maybe worth giving it a try?