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

@dkidd255 @jamesg I didn't forgot about it, but I still don't have access to relevant hardware (for reasons outside of my control). In the meantime, if that happens to be related, can you try the patch that allows disabling hvm-pirq (this is going to be globally available soon) ?

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

I am in the same situation as @vhaelan. same as in same iGPU (alderlake) passed-through, same output for those latest commands, same OS (Fedora CoreOS on latest Xcp-Ng stable). Tried current avenues suggested in this thread with no progress. It seems vhaelan has settled with CoreOS under Proxmox (which works!). He also mentioned it works in Debian under XCP-ng, though I haven't tested that myself. I would appreciate additional suggestions for troubleshooting to take this further, in case anyone has any other ideas.

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

@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: 1713513115366-bab449b6-55cb-4e9f-b0af-ce8e9bb19d22-%D0%B8%D0%B7%D0%BE%D0%B1%D1%80%D0%B0%D0%B6%D0%B5%D0%BD%D0%B8%D0%B5.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