@stormi Installed on our 2 production pools, DR and remote sites, 46 hosts total ranging from Dell, Lenovo, HP, and Supermicro servers, no issues to report!
-
RE: XCP-ng 8.3 updates announcements and testing
-
RE: XCP-ng 8.3 updates announcements and testing
Installed on my usual test systems without issue. (AMD and Intel)
Ran a backup on a pool not using CBT, no issue.
Ran a backup on a pool that uses CBT, no issues.
SSH public key auth continues to work as before. -
RE: XCP-ng 8.3 updates announcements and testing
Installed on my usual selection of hosts. (A mixture of AMD and Intel hosts, SuperMicro, Asus, and Minisforum). No issues after a reboot, PCI Passthru, backups, etc continue to work smoothly. Also installed on a HP GL325 Gen 10 with no issues after reboot.
-
RE: XCP-ng 8.3 updates announcements and testing
@gduperrey Updated my usual test hosts, (Minisforum and Supermicro X11) as well as an two sets of 2 host AMD pools (one pool of HP DL320 Gen10s and another of Asus Epyc servers of some sort, and lastly a Dell R360 without issue.
-
RE: XCP-ng 8.3 updates announcements and testing
@gduperrey Installed on my usual round test hosts. No issues to report so far! With such a small change i wasn't expecting anything to go wrong!
-
RE: XCP-ng 8.3 updates announcements and testing
Installed on my usual selection of hosts. (A mixture of AMD and Intel hosts, SuperMicro, Asus, and Minisforum). No issues after a reboot, PCI Passthru, backups, etc continue to work smoothly
-
RE: log_fs_usage / /var/log directory on pool master filling up constantly
One of our pools. (5 hosts, 6 NFS SRs) had this issue when we first deployed it. I engaged with support from Vates and they changed a setting that reduced the frequency of the SR.scan job from 30 seconds to every 2 mins instead. This totally fixed the issue for us going on a year and a half later.
I dug back in our documentation and found the command they gave us
xe host-param-set other-config:auto-scan-interval=120 uuid=<Host UUID>Where hosts UUID is your pool master.
-
RE: XCP-ng 8.3 updates announcements and testing
@stormi Installed on my usual test hosts (Intel Minisforum MS-01, and Supermicro running a Xeon E-2336 CPU). Also installed onto a 2 host AMD epyc pool. Updates went smooth, backups continue to function as before.
3 windows 11 VMs had secure boot enabled. In XOA i clicked "Copy pool's default UEFI certificates to the VM" after the update was complete. The VMs continued to boot without issue after.
-
RE: XCP-ng 8.3 updates announcements and testing
installed on 2 test machines
Machine 1:
Intel Xeon E-2336
SuperMicro board.Machine 2:
Minisforum MS-01
i9-13900H
32 GB Ram
Using Intel X710 onboard NICBoth machines installed fine and all VMs came up without issue after. My one test backup job also seemed to run without any issues.
-
RE: XCP-ng 8.3 updates announcements and testing
@gduperrey installed on 2 test machines
Machine 1:
Intel Xeon E-2336
SuperMicro board.Machine 2:
Minisforum MS-01
i9-13900H
32 GB Ram
Using Intel X710 onboard NICBoth machines installed fine and all VMs came up without issue after.
I ran a backup job after to test snapshot coalesce, no issues there.
-
RE: Backups in OX v6
@jr-m4 I feel the same way about XO6 myself and I've only been a XCP-NG user since 2024. XO5 is fast and easy to navigate, i find myself struggling much more with XO6 and find myself back using 5 more often than not.
-
RE: XCP-ng 8.3 updates announcements and testing
Installed on my usual test systems without issue. (AMD and Intel)
Ran a backup on a pool not using CBT, no issue.
Ran a backup on a pool that uses CBT, no issues.
SSH public key auth continues to work as before. -
RE: Backups in OX v6
If i can also add some feedback to how backups look in XO6. In its current from is very hard to see what VM is currently being backed up in a job. In XO5 clicking on tasks showed you a quick at a glance view of what VMs were being backedup and their current progress.
In XO6, unless im missing something this is missing:

I think it would be useful to be able to monitor backup progress as we currently can in XO5.
-
RE: New Tools 9.2.445 update failure
@dinhngtu I will mention that the package was deployed via windows SCCM deployment tools so that may have also played a part in leaving the old product code behind. After running the above script we were able to deploy 9.2.445 via SCCM without issue and no old product codes were left behind.
-
RE: New Tools 9.2.445 update failure
Looks like we ended up with a corrupt duplicate install in the MSI installer database.
After some googling and learning how the installer determines the currently installed version from the tools github page i was able to come up with a command to check what version windows thought was installed, i noticed on working installs no error was output however on broken servers the command would end with an error.
PS C:\xcpng-winpv-9.2.445.0-Release-x64\xcpng-winpv-9.2.445.0-Release-x64\package> $Installer.ProductsEx("", "", 7) | ForEach-Object { [PSCustomObject]@{ ProductName = $_.InstallProperty("ProductName") ProductVersion = $_.InstallProperty("VersionString") ProductCode = $_.ProductCode() } } | Where-Object { $_.ProductName -like "*XCP-ng*" } ProductName ProductVersion ProductCode ----------- -------------- ----------- XCP-ng Windows Guest Tools 9.2.385.0 {A9CDEFA1-AB19-426F-8065-64331E634A62} InstallProperty At line:2 char:5 + [PSCustomObject]@{ + ~~~~~~~~~~~~~~~~~~ + CategoryInfo : OperationStopped: (:) [], COMException + FullyQualifiedErrorId : System.Runtime.InteropServices.COMExceptionI fed this output to Calude for a bit help and to shed some light on the issue and its solution, it first had me check for duplicate install entries:

After confirming the presence of a unreadable entry it was able to create a powershell script to remove the bad entry.
From the LLMs output:
This script computes the packed GUID itself (no hand-conversion errors), exports a backup of each key, and does a dry run by default so you can see what it would delete. Run it from an elevated, 64-bit PowerShell. How to use it: Run it as is. It prints the packed GUID (confirm it matches 970CA0A0E00DBC0488B2F1DE377268AA) and lists which keys exist. If the list looks right, set $DryRun = $false and run again. It tries msiexec /x first and only falls back to registry deletion if that fails. Note that on the real run it attempts the msiexec step before any registry work, and the registry section runs even if msiexec fails. Re-run your listing script. Only the 9.2.385.0 row should remain. Caveats: This leaves a few residual references behind, such as entries in ...\Installer\UserData\S-1-5-18\Components and ...\Installer\UpgradeCodes. Windows Installer ignores these once the product keys are gone, so they’re harmless for your purposes. If the bad entry turns out to be a per-user install rather than machine-wide, the keys will live under a user SID instead of S-1-5-18. The “Not present” lines would tell you that. In that case, tell me and I’ll adjust the paths. The backup .reg files let you restore anything with a double-click if something goes wrong.I am by no means anywhere near an expert in powershell as i spend most of my time on Linux, this all AI generated but it was able to remove the entry and get the installer moving along on VMs where it would no proceed prior.
-
RE: XCP-ng Windows PV tools announcements
Running into an installation issue with this new version. I created a separate thread here about the issue:
https://xcp-ng.org/forum/topic/12580/new-tools-9.2.445-update-failure -
New Tools 9.2.445 update failure
Noticed a new version of the tools had been released however while trying to upgrade we are met with the following error:

As you can see we are already running a more recent version than we are being prompted to upgrade to before proceeding.
Install log attached:
install.txt -
RE: XCP-ng 8.3 updates announcements and testing
Installed on my test hosts, no issues.
-
RE: XCP-ng 8.3 updates announcements and testing
Installed on my usual test hosts once again. This time i made sure to test backup job behaviour multiple times across the same two pools that gave me trouble last time. All backup job runs (4 runs on one pool, 2 on another) have been successful.
-
RE: XCP-ng 8.3 updates announcements and testing
@jr-m4 I had this issue on one of the pools i tested on as well and was able to fix the issue by following the fix here:
https://xcp-ng.org/forum/topic/10603/sr_backend_failure_46-the-vdi-is-not-available-not-detached-cleanly/3