

Here is a small usability suggestion. In the Resources dashboard, in Pool view and Host view, positions of CPU and RAM are swapped. I occasionally get a brain freeze when switching between Host and Pool dashboard.


Here is a small usability suggestion. In the Resources dashboard, in Pool view and Host view, positions of CPU and RAM are swapped. I occasionally get a brain freeze when switching between Host and Pool dashboard.
Snapshots.
There is no information about them in any dashboard.
There is no way to manage them.
@olivierlambert
Tested on one of the previous exports and import with " xe vm-import" was successful. VM Windows OS starts normally.
@olivierlambert
I have tested several scenarios on 1TB test VM.
Mounted share from same storage where backups from XO are stored.

We are facing up with Xen Orchestra backup issue: Full VM backups failing with "Body Timeout Error".
IT happens on specific conditions. After some experimentation we can reproduce this consistently on several hosts.
Findings bellow.
![]()
Here are log entries from:
Xen Orchestra (/var/log/syslog):

XCP-NG host (/var/log/xensource.log):

(notice that Xen Orchestra registers the error and sends reports much sooner (almost at the beginning of VM backup task) and XCP-NG host at the real end of VM backup task (was monitoring tasks in Xen Orchestra))
This happens when (must meet both conditions below):
Additional things we noticed:
Windows VMs with large virtual disks as of 1TB are failing all the time (tested about several dozen times). Virtual disks with about 150GB of free space fail only sometimes (failing usually when backing up in parallel with other VMs). Does not matter what particular OS version or type (We have tested with Windows server 2022, Windows Server 2012 R2 and Windows 11), partition table (MRB or GPT) and what filesystem (NTFS, ReFS, exFAT) is used.
Backing up Linux VMs with large free spaces usually does NOT fail (roughly about 99% of backups are successful) but sometimes backing up in parallel with other VMs fails. We have tested on Debian 12.9 and virtual disk with about 1TB of free space.
Behavior does not change when changing XCP-NG host or storage provisioning type (fat or thin). XCP-NG hosts (using LTS 8.2.1) and Xen Orchestra are up to date.