@stormi That is quite possible. I'll open a ticket for further investigation.

Hello all, XenClean 9.1.148 Prerelease is now available with a fix for error 1605 during execution. This is a XenClean-only prerelease. https://github.com/xcp-ng/win-pv-drivers/releases/tag/v9.1.148

@benapetr said in New project - XenAdminQt - a cross-platform GNU/Linux, macOS, Windows native thick client: you can switch between them nope, that just 2 from multiple nics. Need press add ip address to add other NICs. Now i see how it works.

Adding: is there a possibility to see the vm-export progress in the XCP-ng Center in a next update? Actually we only can see the vm-import progress. Thanks!

Thank you every visitors and for those who did not had the chance to visit fosdem check this report: https://xcp-ng.org/blog/2026/02/19/fosdem-2026-follow-up/ [image: vates-xcp-ng-at-fosdem-2026-1.webp] One question, I promised to forward to the forum, how many VM are you running on XCP-ng ? Dozen, hundreds, thousands or more ?

If I remember some previous discussions, EVE-ng uses some features that doesn't work in nested mode with Xen.

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

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