@florent said: @acebmxer back to work thank you for yor patience and help on this. I feel that it's not the same issue , with abrupt increase W will try our best to also fix this one Yes i replied to ticket also.... Yes you can do what is needed to XOA. Just looked at memory and it dropped.... [image: Screenshot_20260527_055458.png]

@redakula said in Coral TPU PCI Passthrough: Frigate.nvr which is one of the popular uses for the Coral do not recommend it for new installs either. Frigate updated their recommendations because of the Google decision to sunset the device and because there are alternative options available to frigate for image inferencing. The coral is still supported though, and frigate is not the only use case or platform that can benefit from an accelerator. At the end of the day if you've already got the hardware, and it's efficient enough to run, then not using it is a waste or resources that could be allocated to other VMs.

@darkbeldin For the record, both vm's were running on the same esxi host when exported. This may or may not be a factor (I suspect it is).

It's also explained very clearly here: https://xen-orchestra.com/docs/community.html (in the first point) Always update to latest code available before reporting a problem

We don't have any other report of this issue elsewhere. Double check you are on the completely latest XO version, and alternatively, try with XOA on latest channel.

Thanks for your input! I think it might be the one then Also, if there is a big problem with it, we can always update the package!

@the_spice @bullerwins @xerxist @hawkpro @vhaelan @ovicz Hi I published a post this morning with packages to test iGPU passthrough, if you have a non production host on which you can test it would be awesome: https://xcp-ng.org/forum/topic/12523/igpu-pci-passthrough-new-experimental-packages-need-testers Thanks! Regards, Yann

@m4rCsi Very nice, thanks for sharing the repo. We will defintely look carefully as we are also working on writing a XO CSI Driver. Ping @Cyrille

@olivierlambert we are thinking about implementing a relationnal DB in the future. Maybe it could offer to stock snapshots as "archived"... I don't know for now. I understand that it could be risky to delete old snapshots, and maybe the responsability of setting the snaspshots retention can be an ACL subject... There are plenty of avenues of work on this topic, and more generally on the retention of information about objects, tasks, and other actions. It's a real in-depth topic.

@fohdeesha lol :-). ok.... good to now :). Next optimization by decoupling harddisks and fans.... and always be quite on the datacenter :).

Update - changes are live in the dev branch now. So figured out the update / switching branches for the proxy by connecting the proxy to my xoa free account. That triggered the available update to next version. From there I found the command that needs to be ran on the proxy to switch back and forth... [image: Screenshot_20261009_143546.png] Latest branch [image: Screenshot_20261009_144414.png] stable branch [image: Screenshot_20261008_202716.png] Backup job ran sucessful. 2026-10-09T17_48_25.447Z - backup NG.txt After the proxy has been deployed... The proxy has been registered with your Xen Orchestra instance. You can manage it from the Xen Orchestra web interface. Next: register the proxy's updater and move it to the 'latest' channel. On the pool master (IP), set a password for the proxy's 'xoa' user (choose your own) and reboot the proxy VM: xe vm-param-set uuid=UUID xenstore-data:vm-data/system-account-xoa-password='<your password>' xe vm-reboot uuid=UUID SSH to the proxy as 'xoa' (IP) and run: sudo xoa-updater register - This registers it with your vates account. sudo xoa-updater configure-channel xo-proxy-appliance-latest - set to latest or stable sudo xoa-updater upgrade - This can be ran via the UI or this command. Both need to be done twice to do the upgrade and/or downgrade. register needs a free xen-orchestra.com account; see the README. And host connected via proxy. [image: Screenshot_20261009_150011.png]

@Pilow alright, cool! that sounds pretty much like a standard solution, too much options or details usually just confuses the end users

Perfect! Enjoy

that log appear again, without any actions from my side. [image: bab449b6-55cb-4e9f-b0af-ce8e9bb19d22-изображение.png]

@Raymondello you right, the issue is from the storage and I am looking into that. Thank you for sharing the UAT Testing, I didn't know about it

@dave.opc that's it keep us updated on this

its still there ie the host is still atached to that vdi im thinking this is the issue why my backups wont run anymore if not i will do it on the xen server cli, but it would be nice to know why this isnt working