@florent said: @acebmxer do you have something in the xo logs ( journalct probably ) ? from host sudo journalctl -u xo-server -n 50 -- No entries -- From XO - Currently on fbba0 commit (4 behind) Apr 20 15:21:51 xo-ce xo-server[849]: } Apr 20 15:21:51 xo-ce xo-server[849]: } Apr 20 15:22:35 xo-ce xo-server[849]: 2026-04-20T19:22:35.554Z xo:main INFO + Console proxy ( - 127.0.0.1) Apr 20 15:22:41 xo-ce xo-server[849]: 2026-04-20T19:22:41.365Z xo:main INFO - Console proxy ( - 127.0.0.1) Apr 20 15:22:55 xo-ce xo-server[849]: 2026-04-20T19:22:55.223Z xo:main INFO + Console proxy ( - 127.0.0.1) Apr 20 15:23:04 xo-ce xo-server[849]: 2026-04-20T19:23:04.562Z xo:main INFO - Console proxy ( - 127.0.0.1) Apr 20 16:11:49 xo-ce xo-server[849]: (node:849) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 update list> Apr 20 16:11:49 xo-ce xo-server[849]: 2026-04-20T20:11:49.190Z xo:xo-server WARN Node warning { Apr 20 16:11:49 xo-ce xo-server[849]: error: MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 update listen> Apr 20 16:11:49 xo-ce xo-server[849]: at genericNodeError (node:internal/errors:985:15) Apr 20 16:11:49 xo-ce xo-server[849]: at wrappedFn (node:internal/errors:539:14) Apr 20 16:11:49 xo-ce xo-server[849]: at _addListener (node:events:590:17) Apr 20 16:11:49 xo-ce xo-server[849]: at Tasks.addListener (node:events:608:10) Apr 20 16:11:49 xo-ce xo-server[849]: at TaskController.getTasks (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/tasks/tas> Apr 20 16:11:49 xo-ce xo-server[849]: at ExpressTemplateService.buildPromise (/opt/xen-orchestra/node_modules/@tsoa/runtime/src/ro> Apr 20 16:11:49 xo-ce xo-server[849]: at ExpressTemplateService.apiHandler (/opt/xen-orchestra/node_modules/@tsoa/runtime/src/rout> Apr 20 16:11:49 xo-ce xo-server[849]: at TaskController_getTasks (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/open-api/> Apr 20 16:11:49 xo-ce xo-server[849]: emitter: Tasks { Apr 20 16:11:49 xo-ce xo-server[849]: _events: [Object: null prototype], Apr 20 16:11:49 xo-ce xo-server[849]: _eventsCount: 2, Apr 20 16:11:49 xo-ce xo-server[849]: _maxListeners: undefined, Apr 20 16:11:49 xo-ce xo-server[849]: Symbol(shapeMode): false, Apr 20 16:11:49 xo-ce xo-server[849]: Symbol(kCapture): false Apr 20 16:11:49 xo-ce xo-server[849]: }, Apr 20 16:11:49 xo-ce xo-server[849]: type: 'update', Apr 20 16:11:49 xo-ce xo-server[849]: count: 11 Apr 20 16:11:49 xo-ce xo-server[849]: } Apr 20 16:11:49 xo-ce xo-server[849]: } Apr 20 16:11:49 xo-ce xo-server[849]: (node:849) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 remove list> Apr 20 16:11:49 xo-ce xo-server[849]: 2026-04-20T20:11:49.190Z xo:xo-server WARN Node warning { Apr 20 16:11:49 xo-ce xo-server[849]: error: MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 remove listen> Apr 20 16:11:49 xo-ce xo-server[849]: at genericNodeError (node:internal/errors:985:15) Apr 20 16:11:49 xo-ce xo-server[849]: at wrappedFn (node:internal/errors:539:14) Apr 20 16:11:49 xo-ce xo-server[849]: at _addListener (node:events:590:17) Apr 20 16:11:49 xo-ce xo-server[849]: at Tasks.addListener (node:events:608:10) Apr 20 16:11:49 xo-ce xo-server[849]: at TaskController.getTasks (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/tasks/tas> Apr 20 16:11:49 xo-ce xo-server[849]: at ExpressTemplateService.buildPromise (/opt/xen-orchestra/node_modules/@tsoa/runtime/src/ro> Apr 20 16:11:49 xo-ce xo-server[849]: at ExpressTemplateService.apiHandler (/opt/xen-orchestra/node_modules/@tsoa/runtime/src/rout> Apr 20 16:11:49 xo-ce xo-server[849]: at TaskController_getTasks (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/open-api/> Apr 20 16:11:49 xo-ce xo-server[849]: emitter: Tasks { Apr 20 16:11:49 xo-ce xo-server[849]: _events: [Object: null prototype], Apr 20 16:11:49 xo-ce xo-server[849]: _eventsCount: 2, Apr 20 16:11:49 xo-ce xo-server[849]: _maxListeners: undefined, Apr 20 16:11:49 xo-ce xo-server[849]: Symbol(shapeMode): false, Apr 20 16:11:49 xo-ce xo-server[849]: Symbol(kCapture): false Apr 20 16:11:49 xo-ce xo-server[849]: }, Apr 20 16:11:49 xo-ce xo-server[849]: type: 'remove', Apr 20 16:11:49 xo-ce xo-server[849]: count: 11 Apr 20 16:11:49 xo-ce xo-server[849]: } Apr 20 16:11:49 xo-ce xo-server[849]: }

@MajorP93 said: @florent Thanks! I did not have time (yet) to look into the heap export due to weekend being in between. I will update to current master and provide you with the heap export in the following days. Best regards no problem , the sooner we'll have these exports, the sooner we will be able to indentify what is leaking in your usage, since we already plugged the leaks we reproduced in our labs

@yannsionneau said: Can you retry with an up-to-date xcp-ng 8.3 please? FYI on recent XCP-ng 8.3 versions the pci-passthrough will enable the ROM expansion bar. The guest VM will have access to it, so no need to pass it via qemu anymore. See my comment on GitHub: https://github.com/xcp-ng/xcp/issues/786#issuecomment-4281846490 Regards, Yann I tried, yes. I confirmed as well on github that the patch does what it suppose to do - it exposes ROM BAR, but that alone is not sufficient to get our cards working. More in my other topic.. I believe it will still fix a lot of issues, and it could potentially fix amd gpu passthrough for some card, but not Phoenix, Raphael and this generation of Ryzen iGPUs (not sure specifically about Barcelo).. But it is a good progress anyway as I wouldn't be able to fix this ever on my own, so I am really glad it is done. Now I will probably get back to the topic and try to patch whatever else is needit and give it to people in a form of rpm package for the time being.. we will see, it is all about time

@gleveque Hello Can you retry with an up-to-date XCP-ng 8.3 host? PCI expansion ROM are now enabled when doing pass-through. The guest VM can now access the ROM bar. Regards, Yann