Good news it worked !
Nothing better than to start by a good old cleaning and battery replacement !

Will continue to play and learn more about XCP-ng and XOA now!

Thank you guys, for the help!

With kind regards.

@Danp, @DustinB ,
I have taken the full machine apart, did a full clean up and cpu repaste.
I also changed the Bios battery. After that the VM is now starting correctly.

I will give another try with XOA Deploy and see how it goes. I would like to double check if I'm reproducing the original issue.

With kind regards.

Not sure If correct but the vhd-tool check seem quite basic.
Looks like it only do kind of a "wrapper" check and not a full integrity check

$ vhd-tool check 4156d2ea-d39d-436d-b89f-06ad64949c53.vhd 
0 START of section 'footer_at_top'
1ff END of section 'footer_at_top'
200 START of section 'header'
5ff END of section 'header'
600 START of section 'BAT'
195ff END of section 'BAT'
67a00 START of section 'locator block 0'
67bff END of section 'locator block 0'
67c00 START of section 'locator block 1'
67dff END of section 'locator block 1'
67e00 START of section 'locator block 2'
67fff END of section 'locator block 2'

Hi all,
Continuing the investigation,
Since the VM is booting, I'm imaging all disks with qemu-img.
What I'm doing is boot on SysrescueISO, then image to vhd each disks, will see if it works.
On thing which is interesting is that I have a consistent I/O error on one of the device.
I'm guessing that could be the cause of my issue, when I try to do a VMexport.
Also, wondering why no issue has been found on the vhd, will have to investigate that part as well.

Best.

Hi
I tried again and failed with the same error message..
xe vm-export vm=c57a4225-3adb-b422-34ec-d2a23c6223c9 filename=/run/sr-mount/a7f6df31-412f-d5e9-4163-8af75b1df8ad/dlt-sin-mducv8.xva
The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem.
message: Unix.Unix_error(Unix.EIO, "read", "")

Hum in this last reproduction, I the issue happened 3hours after I triggered the export...
I have a feeling this is an hardware issue here...
Anyone any other idea ? Advice where to look at?

[EDIT] I have manage to export another vm without issue.

Best.
Matth.

@Danp thank you for the help.

I have looked at all vhd in my disk and they are all good as per vhd-tool check.
Regarding the logs in xensource logs the first error is showing up few mins after I trigger the export.

#!/bin/bash

# Script to check all VHD files in the current directory using vhd-tool

set +e  # Don't exit on error

total=0
failed=0

echo "Checking VHD files..."
echo ""

# Loop through all .vhd files in current directory
for vhd_file in *.vhd; do
    # Skip if no .vhd files found
    [ -e "$vhd_file" ] || continue
    
    ((total++))
    
    # Run vhd-tool check
    if vhd-tool check "$vhd_file" > /dev/null 2>&1; then
        echo "PASS: $vhd_file"
    else
        echo "FAIL: $vhd_file"
        ((failed++))
    fi
done

# Report
echo ""
echo "===================="
echo "Total: $total"
echo "Failed: $failed"
echo "===================="

[ $failed -eq 0 ] && exit 0 || exit 1

/checkvhd.sh 
Checking VHD files...

PASS: 014e122e-7908-4566-be52-31fc40ea6042.vhd
PASS: 054f3177-e40b-4c87-86c6-88ac9db3edfe.vhd
PASS: 154c4dd3-651d-404b-8df0-e85a07aa5bf6.vhd
PASS: 16f68c2a-74d7-4698-8276-56bdc686e161.vhd
PASS: 18b4a57f-3c77-42da-973c-d136375878da.vhd
PASS: 1a129b44-a562-4555-8785-2bfaa1f98455.vhd
PASS: 1e62a336-bb27-40f0-8da5-1f53cbeeee83.vhd
PASS: 24b6ede5-b698-4a9d-acb1-a4898d78cf8c.vhd
PASS: 24b82a29-9fe2-47af-a68b-f36a73b34624.vhd
PASS: 2d8b1375-4fc8-46eb-b1f6-2d887e37602c.vhd
PASS: 2e3897fb-7d45-4098-9956-d985636d9a12.vhd
PASS: 3165bf7b-ca6f-4a30-b33d-bda31e2c67ab.vhd
PASS: 31832728-0001-407d-85f6-0de340e2dbda.vhd
PASS: 32f501b3-47df-4730-824b-f9e297e9d12c.vhd
PASS: 346c5bf0-6635-4f1b-af32-fc9f8fac5088.vhd
PASS: 3a7f68ce-b342-4d03-878f-956e74074b6a.vhd
PASS: 406f2750-fea7-4389-920f-0b080335284f.vhd
PASS: 4156d2ea-d39d-436d-b89f-06ad64949c53.vhd
PASS: 475b16f8-f1c0-40b6-b181-99f83f14dd73.vhd
PASS: 52656fa5-d418-45e0-9e65-07a450af2476.vhd
PASS: 69042c99-b0a3-47ab-8c2b-48303c4cc6bc.vhd
PASS: 6a79914e-67e0-4ac9-b93e-2e393aaa7b97.vhd
PASS: 6b0919bb-7d0a-4036-a833-0313476a11a3.vhd
PASS: 7e2fc00c-7208-4132-aa4a-7db818c7a94b.vhd
PASS: 824af8d0-112b-479b-b474-6e5a26e0d8b2.vhd
PASS: 8f6d6a7c-5390-43bd-b0b5-55f8e681453a.vhd
PASS: 94453b92-3a69-416b-9c08-9f0b91b2aee1.vhd
PASS: 947ad175-06a7-4881-8725-aba36d2cda66.vhd
PASS: 97e577dc-b0be-4990-8e06-c0c4333aef82.vhd
PASS: 9889a738-cfd4-447d-962a-8fd88222d8ab.vhd
PASS: 9c93fa78-4b17-41b1-b794-8bfa165ed4b4.vhd
PASS: a3408bda-9c26-4333-b535-3a008109b98c.vhd
PASS: a3c69ec6-f56e-4d25-ba71-023a38eef8e3.vhd
PASS: a8c45c4c-8925-41a3-a78d-c30d6e20c261.vhd
PASS: b119ad26-f0dc-4965-b726-9dc3fc815130.vhd
PASS: b12002da-56b6-451c-ad4d-a6c16a79fc12.vhd
PASS: b24f9236-6b68-4214-812d-9e98994467aa.vhd
PASS: b34f20b8-6681-42e9-b234-116989286699.vhd
PASS: b5ff8f04-0ace-4b23-9f0b-7a6c5328bef5.vhd
PASS: b932bc63-a47d-49cb-9d28-a57ad61e7ad9.vhd
PASS: be06df0b-cbb7-4dfe-8eaf-697de4d8850b.vhd
PASS: cb88a496-8c80-41e2-b3de-055916a3a32c.vhd
PASS: ce66b785-5b1b-43c8-9ece-dc456508014c.vhd
PASS: ddb84192-3e35-4541-86da-d4326a6bbea7.vhd
PASS: de27f27e-65b8-42d3-929f-f34f0544149a.vhd
PASS: e054e9da-08e7-40b1-8c55-0fd2ae97ee5f.vhd
PASS: e449742e-5007-4be6-89c0-2529d00dbf28.vhd
PASS: f0ee695e-dcb4-49e6-ac17-4a64f65998a6.vhd
PASS: f20e6bb0-4cba-4030-87fc-ddbaca262169.vhd
PASS: f28a0554-6530-4055-a67e-d970ab1c4cc1.vhd
PASS: f5dd3ee4-7006-43fc-8254-98eb45505639.vhd

====================
Total: 51
Failed: 0
====================

I'll give another export try to see if it works this time.

best.

Hello

Hope this help here is how I manage to configure GPU Passthrough.

In my case I have follow the documentation on XCP-ng website : https://docs.xcp-ng.org/compute/

To sum up with XOA 8.3 here is what I did:

ssh to XCP host, to identify the GPU PCI and run lspci to find my GPU.

[root@xen ~]# lspci
...
0f:00.0 VGA compatible controller: NVIDIA Corporation GA102 [GeForce RTX 3090] (rev a1)

Then disable the GPU for being used by XCP-ng itself( Dom0) using the XCP-ng uuid

[root@xen ~]# xe pci-list
uuid ( RO)           : 7970825f-dd1c-c270-93a3-6761f00e1362
    vendor-name ( RO): NVIDIA Corporation
    device-name ( RO): GA102 [GeForce RTX 3090]
         pci-id ( RO): 0000:0f:00.0

xe pci-disable-dom0-access uuid=<pci uuid>

3 reboot the XCP-ng host

4 Then from XOA attached the PCI related to my GPU to my guest VM.

5 install official Nvidia drivers ( closed source ) and have then the card available in the guest.

What I didn't do is adding a vGPU in the guest configuration:

I did it some times ago, also I don't recall having to do any specific configuration in the Bios to make this work.

PS: I have an issue, I don't have output to the Display port or HDMI of this video card, which is not a blocker for me as that's not my immediate needs.

Best.

Hello,

Version:
XCP-NG 8.3.0 on an HP DL380 G9

I'm exporting my vm using this command:

xe vm-export vm=2129ae0c-a46f-5a07-2d5f-3a9d7d1baf42 filename=/run/sr-mount/a7f6df31-412f-d5e9-4163-8af75b1df8ad/myVMtoExport.xva

But after few minutes I'm getting this error which is not clear to me
The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem.
message: Unix.Unix_error(Unix.EIO, "read", "")

I don't really understand where to look at, in the Xensource logs I have the same message but doesn't give me a clue what could be the issue.
My VM is working correctly I can start it up and use it normally. So I don't understand where could be the issue.
I have tested to run this export both with the machine runinng and the machine stopped in both case I have the same issue.
Xensource logs.

Feb  3 00:18:29 xenserver-singapore xapi: [debug||468 |xapi events D:a6cda345829c|dummytaskhelper] task timeboxed_rpc D:59c515615584 created by task D:a6cda345829c
Feb  3 00:18:29 xenserver-singapore xapi: [debug||103857 /var/lib/xcp/xapi|post_root|dummytaskhelper] task dispatch:event.from D:ecf675861053 created by task D:a6cda345829c
Feb  3 00:18:31 xenserver-singapore xapi: [ info||103858 /var/lib/xcp/xapi|post_cli|cli] xe vm-export vm=2129ae0c-a46f-5a07-2d5f-3a9d7d1baf42 filename=/run/sr-mount/a7f6df31-412f-d5e9-4163-8af75b1df8ad/myVMtoExport.xva username=root password=(omitted)
Feb  3 00:18:31 xenserver-singapore xapi: [ info||103858 /var/lib/xcp/xapi|session.login_with_password D:0931d04b6244|xapi_session] Session.create trackid=9fb57b0b73643570129b41898af5ace9 pool=false uname=root originator=cli is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49
Feb  3 00:18:31 xenserver-singapore xapi: [debug||103859 /var/lib/xcp/xapi|post_root|dummytaskhelper] task dispatch:pool.get_all D:0ab57cda82a5 created by task D:0931d04b6244

[…]

Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|VM.export D:a9ace20058a5|backtrace] Export of VM R:073ca66fb5e4 failed with exception Unix.Unix_error(Unix.EIO, "read", "")
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|VM.export D:a9ace20058a5|backtrace] Raised Unix.Unix_error(Unix.EIO, "read", "")
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|VM.export D:a9ace20058a5|backtrace] 1/18 xapi Raised at file unix.ml, line 258
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|VM.export D:a9ace20058a5|backtrace] 2/18 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-unix/unixext.ml, line 476
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|VM.export D:a9ace20058a5|backtrace] 3/18 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-unix/unixext.ml, line 490
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|VM.export D:a9ace20058a5|backtrace] 4/18 xapi Called from file ocaml/xapi/stream_vdi.ml, line 296
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|VM.export D:a9ace20058a5|backtrace] 5/18 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 24
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|VM.export D:a9ace20058a5|backtrace] 6/18 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 39
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|VM.export D:a9ace20058a5|backtrace] 7/18 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 24
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|VM.export D:a9ace20058a5|backtrace] 8/18 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 39
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|VM.export D:a9ace20058a5|backtrace] 9/18 xapi Called from file ocaml/xapi/stream_vdi.ml, line 263
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|VM.export D:a9ace20058a5|backtrace] 10/18 xapi Called from file list.ml, line 110
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|VM.export D:a9ace20058a5|backtrace] 11/18 xapi Called from file ocaml/xapi/export.ml, line 707
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|VM.export D:a9ace20058a5|backtrace] 12/18 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 24
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|VM.export D:a9ace20058a5|backtrace] 13/18 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 39
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|VM.export D:a9ace20058a5|backtrace] 14/18 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 24
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|VM.export D:a9ace20058a5|backtrace] 15/18 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 39
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|VM.export D:a9ace20058a5|backtrace] 16/18 xapi Called from file ocaml/xapi/server_helpers.ml, line 75
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|VM.export D:a9ace20058a5|backtrace] 17/18 xapi Called from file ocaml/xapi/server_helpers.ml, line 97
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|VM.export D:a9ace20058a5|backtrace] 18/18 xapi Called from file ocaml/libs/log/debug.ml, line 250
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|VM.export D:a9ace20058a5|backtrace]
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|handler:http/get_export D:cfa528131e78|backtrace] VM.export D:a9ace20058a5 failed with exception Unix.Unix_error(Unix.EIO, "read", "")
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|handler:http/get_export D:cfa528131e78|backtrace] Raised Unix.Unix_error(Unix.EIO, "read", "")
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|handler:http/get_export D:cfa528131e78|backtrace] 1/9 xapi Raised at file ocaml/libs/log/debug.ml, line 271
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|handler:http/get_export D:cfa528131e78|backtrace] 2/9 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 24
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|handler:http/get_export D:cfa528131e78|backtrace] 3/9 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 39
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|handler:http/get_export D:cfa528131e78|backtrace] 4/9 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 24
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|handler:http/get_export D:cfa528131e78|backtrace] 5/9 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 39
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|handler:http/get_export D:cfa528131e78|backtrace] 6/9 xapi Called from file ocaml/xapi/xapi_http.ml, line 257
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|handler:http/get_export D:cfa528131e78|backtrace] 7/9 xapi Called from file ocaml/xapi/server_helpers.ml, line 75
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|handler:http/get_export D:cfa528131e78|backtrace] 8/9 xapi Called from file ocaml/xapi/server_helpers.ml, line 97
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|handler:http/get_export D:cfa528131e78|backtrace] 9/9 xapi Called from file ocaml/libs/log/debug.ml, line 250
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|handler:http/get_export D:cfa528131e78|backtrace]
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|xapi_http_session_check D:dc664bf0073e|backtrace] handler:http/get_export D:cfa528131e78 failed with exception Unix.Unix_error(Unix.EIO, "read", "")
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|xapi_http_session_check D:dc664bf0073e|backtrace] Raised Unix.Unix_error(Unix.EIO, "read", "")
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|xapi_http_session_check D:dc664bf0073e|backtrace] 1/10 xapi Raised at file ocaml/libs/log/debug.ml, line 271
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|xapi_http_session_check D:dc664bf0073e|backtrace] 2/10 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 24
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|xapi_http_session_check D:dc664bf0073e|backtrace] 3/10 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 39
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|xapi_http_session_check D:dc664bf0073e|backtrace] 4/10 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 24
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|xapi_http_session_check D:dc664bf0073e|backtrace] 5/10 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 39
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|xapi_http_session_check D:dc664bf0073e|backtrace] 6/10 xapi Called from file ocaml/xapi/rbac.ml, line 229
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|xapi_http_session_check D:dc664bf0073e|backtrace] 7/10 xapi Called from file ocaml/xapi/rbac.ml, line 239
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|xapi_http_session_check D:dc664bf0073e|backtrace] 8/10 xapi Called from file ocaml/xapi/server_helpers.ml, line 75
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|xapi_http_session_check D:dc664bf0073e|backtrace] 9/10 xapi Called from file ocaml/xapi/server_helpers.ml, line 97
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|xapi_http_session_check D:dc664bf0073e|backtrace] 10/10 xapi Called from file ocaml/libs/log/debug.ml, line 250
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80|xapi_http_session_check D:dc664bf0073e|backtrace]
Feb  3 00:22:24 xenserver-singapore xapi: [ info||103860 :::80|xapi_http_session_check D:dc664bf0073e|taskhelper] task Export of VM R:073ca66fb5e4 forwarded
Feb  3 00:22:24 xenserver-singapore xapi: [debug||103860 :::80|xapi_http_session_check D:dc664bf0073e|taskhelper] the status of R:073ca66fb5e4 is failure; cannot set it to `failure
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 HTTP 127.0.0.1->:::80|get_export|backtrace] xapi_http_session_check D:dc664bf0073e failed with exception Unix.Unix_error(Unix.EIO, "read", "")
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 HTTP 127.0.0.1->:::80|get_export|backtrace] Raised Unix.Unix_error(Unix.EIO, "read", "")
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 HTTP 127.0.0.1->:::80|get_export|backtrace] 1/8 xapi Raised at file ocaml/libs/log/debug.ml, line 271
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 HTTP 127.0.0.1->:::80|get_export|backtrace] 2/8 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 24
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 HTTP 127.0.0.1->:::80|get_export|backtrace] 3/8 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 39
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 HTTP 127.0.0.1->:::80|get_export|backtrace] 4/8 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 24
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 HTTP 127.0.0.1->:::80|get_export|backtrace] 5/8 xapi Called from file ocaml/xapi/xapi_http.ml, line 114
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 HTTP 127.0.0.1->:::80|get_export|backtrace] 6/8 xapi Called from file ocaml/xapi/server_helpers.ml, line 75
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 HTTP 127.0.0.1->:::80|get_export|backtrace] 7/8 xapi Called from file ocaml/xapi/server_helpers.ml, line 97
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 HTTP 127.0.0.1->:::80|get_export|backtrace] 8/8 xapi Called from file ocaml/libs/log/debug.ml, line 250
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 HTTP 127.0.0.1->:::80|get_export|backtrace]
Feb  3 00:22:24 xenserver-singapore xapi: [debug||103860 HTTP 127.0.0.1->:::80|get_export|xapi_http] Leaving RBAC-handler in xapi_http after: INTERNAL_ERROR: [ Unix.Unix_error(Unix.EIO, "read", "") ]
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80||backtrace] get_export failed with exception Unix.Unix_error(Unix.EIO, "read", "")
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80||backtrace] Raised Unix.Unix_error(Unix.EIO, "read", "")
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80||backtrace] 1/8 xapi Raised at file ocaml/libs/log/debug.ml, line 271
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80||backtrace] 2/8 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 24
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80||backtrace] 3/8 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 39
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80||backtrace] 4/8 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 24
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80||backtrace] 5/8 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 39
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80||backtrace] 6/8 xapi Called from file ocaml/xapi/xapi_http.ml, line 364
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80||backtrace] 7/8 xapi Called from file ocaml/xapi/xapi_http.ml, line 370
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80||backtrace] 8/8 xapi Called from file ocaml/libs/log/debug.ml, line 250
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80||backtrace]
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80||http_internal_errors] Responding with 500 Internal Error due to Unix.Unix_error(Unix.EIO, "read", "")
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80||backtrace] Raised Unix.Unix_error(Unix.EIO, "read", "")
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80||backtrace] 1/1 xapi Raised at file (Thread 103860 has no backtrace table. Was with_backtraces called?, line 0
Feb  3 00:22:24 xenserver-singapore xapi: [error||103860 :::80||backtrace]
Feb  3 00:22:24 xenserver-singapore xapi: [ info||103858 /var/lib/xcp/xapi|session.logout D:639c98ef4e1a|xapi_session] Session.destroy trackid=9fb57b0b73643570129b41898af5ace9
Feb  3 00:22:24 xenserver-singapore xapi: [error||103858 /var/lib/xcp/xapi|post_cli|cli] Converting exception INTERNAL_ERROR: [ Unix.Unix_error(Unix.EIO, "read", "") ] into a CLI response
Feb  3 00:22:24 xenserver-singapore xapi: [error||103858 /var/lib/xcp/xapi|post_cli|backtrace] Raised Server_error(INTERNAL_ERROR, [ Unix.Unix_error(Unix.EIO, "read", "") ])
Feb  3 00:22:24 xenserver-singapore xapi: [error||103858 /var/lib/xcp/xapi|post_cli|backtrace] 1/12 xapi Raised at file ocaml/xapi-cli-server/cli_operations.ml, line 5569
Feb  3 00:22:24 xenserver-singapore xapi: [error||103858 /var/lib/xcp/xapi|post_cli|backtrace] 2/12 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 24
Feb  3 00:22:24 xenserver-singapore xapi: [error||103858 /var/lib/xcp/xapi|post_cli|backtrace] 3/12 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 39
Feb  3 00:22:24 xenserver-singapore xapi: [error||103858 /var/lib/xcp/xapi|post_cli|backtrace] 4/12 xapi Called from file ocaml/xapi-cli-server/cli_operations.ml, line 3264
Feb  3 00:22:24 xenserver-singapore xapi: [error||103858 /var/lib/xcp/xapi|post_cli|backtrace] 5/12 xapi Called from file ocaml/xapi-cli-server/cli_operations.ml, line 3318
Feb  3 00:22:24 xenserver-singapore xapi: [error||103858 /var/lib/xcp/xapi|post_cli|backtrace] 6/12 xapi Called from file ocaml/xapi-cli-server/cli_operations.ml, line 3328
Feb  3 00:22:24 xenserver-singapore xapi: [error||103858 /var/lib/xcp/xapi|post_cli|backtrace] 7/12 xapi Called from file ocaml/xapi-cli-server/cli_operations.ml, line 5979
Feb  3 00:22:24 xenserver-singapore xapi: [error||103858 /var/lib/xcp/xapi|post_cli|backtrace] 8/12 xapi Called from file ocaml/xapi-cli-server/xapi_cli.ml, line 203
Feb  3 00:22:24 xenserver-singapore xapi: [error||103858 /var/lib/xcp/xapi|post_cli|backtrace] 9/12 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 24
Feb  3 00:22:24 xenserver-singapore xapi: [error||103858 /var/lib/xcp/xapi|post_cli|backtrace] 10/12 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 39
Feb  3 00:22:24 xenserver-singapore xapi: [error||103858 /var/lib/xcp/xapi|post_cli|backtrace] 11/12 xapi Called from file ocaml/xapi-cli-server/xapi_cli.ml, line 173
Feb  3 00:22:24 xenserver-singapore xapi: [error||103858 /var/lib/xcp/xapi|post_cli|backtrace] 12/12 xapi Called from file lib/backtrace.ml, line 177
Feb  3 00:22:24 xenserver-singapore xapi: [error||103858 /var/lib/xcp/xapi|post_cli|backtrace]
Feb  3 00:22:52 xenserver-singapore xapi: [debug||103999 /var/lib/xcp/xapi|post_root|dummytaskhelper] task dispatch:session.logout D:fbe10c055f6a created by task D:04f66e8e9f3b
Feb  3 00:22:52 xenserver-singapore xapi: [ info||103999 /var/lib/xcp/xapi|session.logout D:38b18bd3e736|xapi_session] Session.destroy trackid=252eff3f40d674d751f860653cd0403a
Feb  3 00:22:52 xenserver-singapore xapi: [debug||104000 /var/lib/xcp/xapi|post_root|dummytaskhelper] task dispatch:session.slave_login D:394e12272834 created by task D:04f66e8e9f3b
Feb  3 00:22:52 xenserver-singapore xapi: [ info||104000 /var/lib/xcp/xapi|session.slave_login D:552a39cb718b|xapi_session] Session.create trackid=c945eaa1e1349d16aa7e3bb33fd90bbb pool=true uname= originator=xapi is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49

Any idea that could point in the correct direction or a workaround to backup this VM would be greatly appreciated.

With kind regards.

Maybe that's my issue ?
Investing this part

# journalctl -k | grep -i nvidia

Hello
I'm having issues with GPU Pass-through and monitor output.

Machine :

=== System Information ===
Linux xcp 4.19.0+1 #1 SMP Fri Sep 19 15:09:21 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux

=== CPU Information ===
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                16
On-line CPU(s) list:   0-15
Thread(s) per core:    1
Core(s) per socket:    16
Socket(s):             1
Vendor ID:             AuthenticAMD
CPU family:            25
Model:                 33
Model name:            AMD Ryzen 9 5950X 16-Core Processor
Stepping:              0
CPU MHz:               3400.159
BogoMIPS:              6799.86
Hypervisor vendor:     Xen
Virtualization type:   none
L1d cache:             32K
L1i cache:             32K
L2 cache:              512K
L3 cache:              65536K
Flags:                 fpu de tsc msr pae mce cx8 apic mca cmov pat clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm cmp_legacy abm sse4a misalignsse 3dnowprefetch bpext ibpb vmmcall fsgsbase bmi1 avx2 bmi2 erms rdseed adx clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 clzero xsaveerptr arat vaes vpclmulqdq rdpid

=== Memory Information ===
              total        used        free      shared  buff/cache   available
Mem:           3.9G        328M        3.1G         11M        584M        3.4G
Swap:          1.0G          0B        1.0G

=== Disk Information ===
NAME                                                                                                      MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
nvme0n1                                                                                                   259:0    0  1.8T  0 disk 
├─nvme0n1p5                                                                                               259:5    0    4G  0 part /var/log
├─nvme0n1p3                                                                                               259:3    0  1.8T  0 part 
│ ├─VG_XenStorage--bdb1579e--9234--e722--123e--c66741306b23-VHD--a5b16c73--daf5--4ac7--858a--8a1a1e4c8518 253:1    0   20G  0 lvm  
│ ├─VG_XenStorage--bdb1579e--9234--e722--123e--c66741306b23-VHD--daec9532--032f--4e02--8594--39db5ddeb780 253:2    0 25.1G  0 lvm  
│ └─VG_XenStorage--bdb1579e--9234--e722--123e--c66741306b23-MGT                                           253:0    0    4M  0 lvm  
├─nvme0n1p1                                                                                               259:1    0   18G  0 part /
├─nvme0n1p6                                                                                               259:6    0    1G  0 part [SWAP]
├─nvme0n1p4                                                                                               259:4    0  512M  0 part /boot/efi
└─nvme0n1p2                                                                                               259:2    0   18G  0 part 
tdc                                                                                                       254:2    0 19.2M  1 disk 
tda                                                                                                       254:0    0   20G  0 disk 
tdb                                                                                                       254:1    0   25G  0 disk 

=== PCI Devices ===
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 7
01:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream
02:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
02:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
02:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
02:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
03:00.0 PCI bridge: ASMedia Technology Inc. ASM1184e 4-Port PCIe x1 Gen2 Packet Switch
04:01.0 PCI bridge: ASMedia Technology Inc. ASM1184e 4-Port PCIe x1 Gen2 Packet Switch
04:03.0 PCI bridge: ASMedia Technology Inc. ASM1184e 4-Port PCIe x1 Gen2 Packet Switch
04:05.0 PCI bridge: ASMedia Technology Inc. ASM1184e 4-Port PCIe x1 Gen2 Packet Switch
04:07.0 PCI bridge: ASMedia Technology Inc. ASM1184e 4-Port PCIe x1 Gen2 Packet Switch
05:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
07:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
09:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP
09:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
09:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
0a:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
0b:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
0c:00.0 Non-Volatile memory controller: Phison Electronics Corporation E18 PCIe4 NVMe Controller (rev 01)
0d:00.0 VGA compatible controller: NVIDIA Corporation GA102 [GeForce RTX 3090] (rev a1)
0d:00.1 Audio device: NVIDIA Corporation GA102 High Definition Audio Controller (rev a1)
0e:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function
0f:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP
0f:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP
0f:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
0f:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller

=== USB Devices ===
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 003 Device 002: ID 8087:0029 Intel Corp. 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 05e3:0625 Genesys Logic, Inc. 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 09eb:0131 IM Networks, Inc. 
Bus 001 Device 005: ID 056a:0084 Wacom Co., Ltd Wireless adapter for Bamboo tablets
Bus 001 Device 004: ID 09ea:0130  
Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

=== Network Interfaces ===
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether a8:a1:59:8c:14:a6 brd ff:ff:ff:ff:ff:ff
3: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 56:a2:fe:c9:6b:e2 brd ff:ff:ff:ff:ff:ff
4: xenbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether a8:a1:59:8c:14:a6 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.2/24 brd 192.168.0.255 scope global xenbr0
       valid_lft forever preferred_lft forever
5: vif1.0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
31: vif14.0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff

I have my gpu passthrough to my VM

0d:00.1 Audio device: NVIDIA Corporation GA102 High Definition Audio Controller (rev a1)
	Subsystem: NVIDIA Corporation Device 1454
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin B routed to IRQ 55
	Region 0: Memory at fc080000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: [60] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Capabilities: [78] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 <64us
			ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 75.000W
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 256 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 16GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <512ns, L1 <4us
			ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
			ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Range AB, TimeoutDis+, LTR-, OBFF Via message
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
		LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1-
			 EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
	Capabilities: [100 v2] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
		AERCap:	First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
	Capabilities: [160 v1] #25
	Kernel driver in use: pciback

and it is correctly detected on my guest vm, nvtop output below.

I have tested pop-os and linux mint and both have the issue, I can't get the output to a monitor, either Display Port or HDMI.
Pop-os did work but after a xcp-ng reboot didn't work anymore.

In xensource.log I can see the PCI attached to the VM:

Nov 15 23:43:35 xcp xenopsd-xc: [debug||2557 |VM.start R:a916cad08a80|xenops_utils] TypedTable: Writing VM/ce27cd37-8e30-c687-7169-941d89590099/vif.0
Nov 15 23:43:35 xcp xenopsd-xc: [debug||2557 |VM.start R:a916cad08a80|xenops_server] PCI.add ce27cd37-8e30-c687-7169-941d89590099.0000:0d:00.1 {"address":{"fn":1,"dev":0,"bus":13,"domain":0},"position":0,"id":["ce27cd37-8e30-c687-7169-941d89590099","0000:0d:00.1"]}
Nov 15 23:43:35 xcp xenopsd-xc: [debug||2557 |VM.start R:a916cad08a80|xenops_utils] TypedTable: Writing PCI/ce27cd37-8e30-c687-7169-941d89590099/pci.0000:0d:00.1
Nov 15 23:43:35 xcp xenopsd-xc: [debug||2557 |VM.start R:a916cad08a80|xenops_server] PCI.add ce27cd37-8e30-c687-7169-941d89590099.0000:0d:00.0 {"address":{"fn":0,"dev":0,"bus":13,"domain":0},"position":1,"id":["ce27cd37-8e30-c687-7169-941d89590099","0000:0d:00.0"]}
Nov 15 23:43:35 xcp xenopsd-xc: [debug||2557 |VM.start R:a916cad08a80|xenops_utils] TypedTable: Writing PCI/ce27cd37-8e30-c687-7169-941d89590099/pci.0000:0d:00.0

In the Guest VM, on a Virtual-1 display is deteced by xrandr, couldn't manage to get a monitor detected.

Nov 15 23:43:35 xcp xenopsd-xc: [debug||2557 |VM.start R:a916cad08a80|xenops_utils] TypedTable: Writing VM/ce27cd37-8e30-c687-7169-941d89590099/vif.0
Nov 15 23:43:35 xcp xenopsd-xc: [debug||2557 |VM.start R:a916cad08a80|xenops_server] PCI.add ce27cd37-8e30-c687-7169-941d89590099.0000:0d:00.1 {"address":{"fn":1,"dev":0,"bus":13,"domain":0},"position":0,"id":["ce27cd37-8e30-c687-7169-941d89590099","0000:0d:00.1"]}
Nov 15 23:43:35 xcp xenopsd-xc: [debug||2557 |VM.start R:a916cad08a80|xenops_utils] TypedTable: Writing PCI/ce27cd37-8e30-c687-7169-941d89590099/pci.0000:0d:00.1
Nov 15 23:43:35 xcp xenopsd-xc: [debug||2557 |VM.start R:a916cad08a80|xenops_server] PCI.add ce27cd37-8e30-c687-7169-941d89590099.0000:0d:00.0 {"address":{"fn":0,"dev":0,"bus":13,"domain":0},"position":1,"id":["ce27cd37-8e30-c687-7169-941d89590099","0000:0d:00.0"]}
Nov 15 23:43:35 xcp xenopsd-xc: [debug||2557 |VM.start R:a916cad08a80|xenops_utils] TypedTable: Writing PCI/ce27cd37-8e30-c687-7169-941d89590099/pci.0000:0d:00.0

I'm starting to get out of idea what could be the issue here..
Any advice to progress the troubleshooting are welcome.

With kind regards.

Good news it worked !
Nothing better than to start by a good old cleaning and battery replacement !

Will continue to play and learn more about XCP-ng and XOA now!

Thank you guys, for the help!

With kind regards.

@Danp, @DustinB ,
I have taken the full machine apart, did a full clean up and cpu repaste.
I also changed the Bios battery. After that the VM is now starting correctly.

I will give another try with XOA Deploy and see how it goes. I would like to double check if I'm reproducing the original issue.

With kind regards.