I'm not sure if this is the same bug, but the same issue is happening on master commit 1640a.

@Forza thanks. But as @normanghenderson a live migrate from 8.2 -> 8.3 didn't work for me either. I tried that approach first, made the 8.3 to a new pool but it delivered some XCP API Errors ... which thinking of it now might have been a firewall issue but I manually checked access between the systems and everything seemed fine. I now have everything running on 8.2. Have some non important VM on the new server that is 8.2 and will upgrade that one to 8.3 then see if I can migrate other VM away from the 8.2 systems. If that works, I'm all good. If not ... I will have to start over from scratch. But thanks everyone for the quick replies.

on another simpler install (One host, one XOA, no proxy, SMB remote in same lan not an S3 remote), XOA 5.112.1 same problem ! I think something has been broken along the way @bastien-nollet @florent granular file restore is important for us, otherwise we have to get Veeam Agent backup instead of XO Backup

I'm seeing something similar, not sure if its the same issue, but mine stops at 95% and just hangs there: [12:18 sto-xcp1 ~]# xe task-list uuid ( RO) : c1056d36-b195-056a-4121-e82d7fc851fb name-label ( RO): [XO] Importing content into VDI [ESXI]DEBIAN 12 fiona.iextreme.org-flat.vmdk on SR Local storage name-description ( RO): status ( RO): pending progress ( RO): 0.950 The nbdkit debug-log can be found here: https://mirror2.iextreme.org/temp/stderr Edit: some additional info Xen Orchestra, commit 1640a Master, commit 1640a

Let me ping @mathieuRA

@ph7 Thank you!

After moving from Node 22 to Node 24 on my XO instance I started to see more "Error: ENOMEM: not enough memory, close" for my backup jobs even though my XO VM has 8GB of RAM... I will revert back to Node 22 for now.

No pun, just wait for everyone to get back from our yearly Vates internal event

@ideal perhaps you could use advantage of dynamic memory https://docs.xcp-ng.org/vms/#dynamic-memory to oversubscribe memory and have all 4 VMs up at once... or reduce the allocated memory of your VMs, you seem to have a pretty big VM in terms of memory in comparison to the 2 others on your screenshot

@isdpcman-0 said in Install mono on XCP-ng: Our RMM tools will run on CentOS but fail to install because they are looking for mono to be on the system. How can I install Mono on an XCP-ng host so we can install our monitoring/management tools? Reply I think it is advised to consider hosts as appliances and not install any external packages (repos are disabled for that purpose, that's probably your issue for installing anything) even in case of clusters of many hosts in a pool, you should deploy same packages on all hosts to expect compliancy between hosts... better use SNMP to monitor you hosts ? or standard installed packages ?

@Forza Thanks for the details, I managed to reproduce after a few trials. I'll try to fix it and keep you informed.

From another post I gathered that there is an auto-scan feature that run by default every 30 seconds which seems to cause a lot issue when the storage contains a lot of disks or you have a lot of storage. It is not completely clear if this auto-scan feature is actually necessary and to some customers Vates helpdesk has suggested to reduce the frequency of the scan from 30 seconds to 2 minutes and that seems to have improved the overall experience. The command would be this: xe host-param-set other-config:auto-scan-interval=120 uuid=<Host UUID> where UUID is the pool master UUID. Of course I won't run that in production without Vates support re-assurance that doing so it won't have a negative impact but I think is worth mentioning this. In my situation I can see how frequents scan would cause delay on the other tasks considering that effectively my system is always under scanning with probably the scan task itself being affected by it.

Ah nice!

We are in the process of commissioning a batch of R770 with this broadcom nic. @stormi , has a new installer been made available?

Hi Forza, Have you finished migrating the workloads? If you are still looking for an easy migration solution, you can try Vinchin Backup & Recovery. It will replace the driver during migration intelligently.

@Pilow Agreed however as our xcp-ng hosts are in the cloud with OVH Cloud we cannot use a physical appliance. We are currently setting up a dedicated OVH server for pfSense.

@MajorP93 throw in multiple garbage collections during snap/desnap of backups on a XOSTOR SR, and these SR scans really get in the way

Create an appliance with all those VMs and configure the order and delay inside it.

I hope someone will reply to my post here about how to check status on this but I believe I've resolved the main issue: I disabled and re-enabled the whole task itself yesterday and it ran this morning as scheduled.