@marcoi said:
Applied the latest pushed updated to production, no major issues.
Thank you for testing
The only thing to note is my backup XCP config failed Sunday, (...) This morning the backup ran without issues.
Glad it has finally to work, if problem occurs again feel free to ask about this feature in this subforum:
https://xcp-ng.org/forum/category/21/backup
Hello @mgr42
I can confirm that indeed today AMD iGPU passthrough is not working on XCP-ng.
I am currently (slowly) working on it.
There are other references about this topic in the Forum and on GitHub FYI:
https://xcp-ng.org/forum/topic/11918/amd-barcelo-passthrough-issues-any-success-stories
https://xcp-ng.org/forum/topic/8909/issue-to-load-gpu-passthrough-invalid-pci-rom-header-signature-expecting-0xaa55-got-0x4556
https://github.com/xcp-ng/xcp/issues/806
https://github.com/xapi-project/xen-api/commit/930ffb34e42d674b8234c3d8399fdba97efa6b38
On the setup I am working on, the Expansion ROM is provided indeed by firmware via the VFCT ACPI table.
I dumped it to a file and provided it to qemu-dm xen-pci-passthrough device via the romfile= argument (via a modified XAPI build).
I can now indeed see a ROM bar in the guest but unfortunately its content is not the content of the file therefore nothing works (amdgpu driver is unable to get its ROM and fails).
So now I'm debugging qemu to try to understand the issue with the emulated/passed-through ROM BAR.
Regards,
Yann
Kernel & Hypervisor team
timemaster5 created this issue in xcp-ng/xcp
open
Unable to set romfile for xen-pci-passthrough devices
#806
0
freddy77 committed to xapi-project/xen-api
CA-418993: Enable PCI ROM BAR before attempting to give permissions to the VM
Currently the VM is not able to access the ROM as the host
ROM BAR is disabled and not set.
Signed-off-by: Frediano Ziglio <frediano.ziglio@citrix.com>
@pedro_udifar object lock works quite well with xo
it is automatically detected if the s3 user has enough privilege to see if object lock is enabled
the main point is that it won't create "cache.json.gz" files since theses files must be updated, so the backup listing is a little slower
note that XO retention should be at least 1 more than object lock . At worst you will have error , saying that XO coudn't delete an old backup
The fix is on a separated branch : fix_s3_nonencrypted_to_encrypted_xva ( PR : https://github.com/vatesfr/xen-orchestra/pull/10061 )
fbeauchamp opened this pull request in vatesfr/xen-orchestra
open
fix(fs): compute the output stream precisely when encrypted
#10061
I've installed the latest updates to all hosts, and restarted everything. I also have all xcp-ng logs going into loki now, so next time something happens I will see everything lol.
[image: 1782860175138-156f9ac1-f1bb-47f3-a789-8551c8614805-image-resized.jpeg]
