Offline
@florent The following error occurred:
Mar 16 18:38:10 XOA xo-server[4001]: 2026-03-16T17:38:10. 246Z xo:rest-api:error-handler INFO [GET] /vms/0691be81-7ce9-7dba-9387-5620f8e0c52f/vdis (404)
XO version: Master, commit 15917
xcp-ng version: 8.3 with the latest updates.
What’s interesting is that there are two xcp-ng servers, and the problem only occurs on one of them.
@FritzGerald workaround
yum update --exclude=net-snmp*
@kagbasi-ngc
RHEL 10.x only supports CPUs from amd64_v3 onwards, while yours is amd64_v2. Rocky / Almalinux builds for even older CPUs.
https://xcp-ng.org/forum/topic/11447/almalinux-10-dvd-won-t-boot-in-uefi-mode/2
Which ISO are you booting?
The default Alamlinux 10 only supports CPUs from amd64 v3 upwards. You need to download the amd64 v2 installer separately.
@hoh
How can I boot it, because so far I have not been able to. I tried PV-bootloader=pygrub but it fails.
xl dmesg output
(XEN) [939408.303345] d47v0 Triple fault - invoking HVM shutdown action 3
(XEN) [939408.303347] *** Dumping Dom47 vcpu#0 state: ***
(XEN) [939408.303350] ----[ Xen-4.17.5-13 x86_64 debug=n Not tainted ]----
(XEN) [939408.303351] CPU: 0
(XEN) [939408.303352] RIP: 0008:[<000000000367a562>]
(XEN) [939408.303354] RFLAGS: 0000000000010046 CONTEXT: hvm guest (d47v0)
(XEN) [939408.303356] rax: 0000000000000000 rbx: 00000000566e6558 rcx: 0000000000000000
(XEN) [939408.303357] rdx: 00000000000000e9 rsi: ffffffff849600a6 rdi: 0000000000000004
(XEN) [939408.303359] rbp: 0000000040000000 rsp: 000000000373cf70 r8: 65584d4d566e6558
(XEN) [939408.303360] r9: 0000000000000026 r10: 6920485650206e65 r11: 7a696c616974696e
(XEN) [939408.303361] r12: 0000000000000005 r13: 0000000000000000 r14: 0000000000000000
(XEN) [939408.303362] r15: 0000000000000000 cr0: 0000000080000011 cr4: 0000000000000020
(XEN) [939408.303363] cr3: 0000000002c10000 cr2: 0000000000000000
(XEN) [939408.303364] fsb: 0000000000000000 gsb: 0000000003738f80 gss: 0000000000000000
(XEN) [939408.303366] ds: 0010 es: 0010 fs: 0000 gs: 0000 ss: 0010 cs: 0008
Since the xcp-ng 8.3 update, there is again no console for PVH VMs, neither XO nor XO Lite.
@florent said in XO VM Backup Started and never completed:
this look like the most recent backup job did not use CBT , but the previous was using it
is it intendend ?Válasz
This backup has been running like this for a long time, until yesterday's XO update. It has not been configured since then.
Same issue, here is xo-server logs:
Jul 01 04:00:07 xoa xo-server[15851]: }
Jul 01 04:00:07 xoa xo-server[15851]: }
Jul 01 04:00:07 xoa xo-server[15851]: code: 'UND_ERR_ABORTED'
Jul 01 04:00:07 xoa xo-server[15851]: at async Promise.all (index 1) {
Jul 01 04:00:07 xoa xo-server[15851]: at async file:///opt/xo/xo-builds/xen-orchestra-202506301858/@xen-orchestra/backups/_incrementalVm.mjs:67:5
Jul 01 04:00:07 xoa xo-server[15851]: at async XapiDiskSource.init (file:///opt/xo/xo-builds/xen-orchestra-202506301858/@xen-orchestra/disk-transform/dist/DiskPassthrough.mjs:28:41)
Jul 01 04:00:07 xoa xo-server[15851]: at async XapiDiskSource.openSource (file:///opt/xo/xo-builds/xen-orchestra-202506301858/@xen-orchestra/xapi/disks/Xapi.mjs:194:18)
Jul 01 04:00:07 xoa xo-server[15851]: at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
Jul 01 04:00:07 xoa xo-server[15851]: at #openNbdStream (file:///opt/xo/xo-builds/xen-orchestra-202506301858/@xen-orchestra/xapi/disks/Xapi.mjs:92:21)
Jul 01 04:00:07 xoa xo-server[15851]: at XapiStreamNbdSource.close (file:///opt/xo/xo-builds/xen-orchestra-202506301858/@xen-orchestra/xapi/disks/XapiStreamNbd.mjs:81:19)
Jul 01 04:00:07 xoa xo-server[15851]: at XapiStreamNbdSource.close (file:///opt/xo/xo-builds/xen-orchestra-202506301858/@xen-orchestra/disk-transform/dist/DiskPassthrough.mjs:34:29)
Jul 01 04:00:07 xoa xo-server[15851]: at XapiVhdStreamSource.close (file:///opt/xo/xo-builds/xen-orchestra-202506301858/@xen-orchestra/xapi/disks/XapiVhdStreamSource.mjs:160:22)
Jul 01 04:00:07 xoa xo-server[15851]: at BodyReadable.destroy (/opt/xo/xo-builds/xen-orchestra-202506301858/node_modules/undici/lib/api/readable.js:51:13)
Jul 01 04:00:07 xoa xo-server[15851]: error: RequestAbortedError [AbortError]: Request aborted
Jul 01 04:00:07 xoa xo-server[15851]: 2025-07-01T02:00:07.508Z xo:backups:worker WARN possibly unhandled rejection {
Jul 01 04:00:07 xoa xo-server[15851]: 2025-07-01T02:00:07.484Z @xen-orchestra/xapi/disks/Xapi WARN can't connect through NBD, fallback to stream export
Jul 01 04:00:06 xoa xo-server[15851]: }
Jul 01 04:00:06 xoa xo-server[15851]: }
Jul 01 04:00:06 xoa xo-server[15851]: backtrace: '(((process xapi)(filename lib/backtrace.ml)(line 210))((process xapi)(filename ocaml/xapi/storage_utils.ml)(line 141))((process xapi)(f>
Jul 01 04:00:06 xoa xo-server[15851]: subtasks: [],
Jul 01 04:00:06 xoa xo-server[15851]: subtask_of: 'OpaqueRef:NULL',
Jul 01 04:00:06 xoa xo-server[15851]: other_config: {},
Jul 01 04:00:06 xoa xo-server[15851]: ],
Jul 01 04:00:06 xoa xo-server[15851]: ''
Jul 01 04:00:06 xoa xo-server[15851]: 'Failed to calculate changed blocks for given VDIs. [opterr=Source and target VDI are unrelated]',
Jul 01 04:00:06 xoa xo-server[15851]: '',
Jul 01 04:00:06 xoa xo-server[15851]: 'SR_BACKEND_FAILURE_460',
Jul 01 04:00:06 xoa xo-server[15851]: error_info: [
Jul 01 04:00:06 xoa xo-server[15851]: result: '',
Jul 01 04:00:06 xoa xo-server[15851]: type: '<none/>',
Jul 01 04:00:06 xoa xo-server[15851]: progress: 1,
Jul 01 04:00:06 xoa xo-server[15851]: resident_on: 'OpaqueRef:a08170fe-0f8d-4a9d-b890-b65bfa0f5aeb',
Jul 01 04:00:06 xoa xo-server[15851]: status: 'failure',
Jul 01 04:00:06 xoa xo-server[15851]: finished: '20250701T02:00:06Z',
Jul 01 04:00:06 xoa xo-server[15851]: created: '20250701T02:00:05Z',
Jul 01 04:00:06 xoa xo-server[15851]: current_operations: {},
Jul 01 04:00:06 xoa xo-server[15851]: allowed_operations: [],
Jul 01 04:00:06 xoa xo-server[15851]: name_description: '',
Jul 01 04:00:06 xoa xo-server[15851]: name_label: 'Async.VDI.list_changed_blocks',
Jul 01 04:00:06 xoa xo-server[15851]: uuid: 'f6981d73-138e-3fac-c944-1218e9f54934',
Jul 01 04:00:06 xoa xo-server[15851]: task: task {
Jul 01 04:00:06 xoa xo-server[15851]: url: undefined,
Jul 01 04:00:06 xoa xo-server[15851]: call: undefined,
Jul 01 04:00:06 xoa xo-server[15851]: ],
Jul 01 04:00:06 xoa xo-server[15851]: ''
Jul 01 04:00:06 xoa xo-server[15851]: 'Failed to calculate changed blocks for given VDIs. [opterr=Source and target VDI are unrelated]',
Jul 01 04:00:06 xoa xo-server[15851]: '',
Jul 01 04:00:06 xoa xo-server[15851]: params: [
Jul 01 04:00:06 xoa xo-server[15851]: code: 'SR_BACKEND_FAILURE_460',
Jul 01 04:00:06 xoa xo-server[15851]: at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
Jul 01 04:00:06 xoa xo-server[15851]: at Xapi._watchEvents (file:///opt/xo/xo-builds/xen-orchestra-202506301858/packages/xen-api/index.mjs:1270:14)
Jul 01 04:00:06 xoa xo-server[15851]: at Xapi._processEvents (file:///opt/xo/xo-builds/xen-orchestra-202506301858/packages/xen-api/index.mjs:1097:12)
Jul 01 04:00:06 xoa xo-server[15851]: at Array.forEach (<anonymous>)
Jul 01 04:00:06 xoa xo-server[15851]: at file:///opt/xo/xo-builds/xen-orchestra-202506301858/packages/xen-api/index.mjs:1107:14
Jul 01 04:00:06 xoa xo-server[15851]: at Xapi._addRecordToCache (file:///opt/xo/xo-builds/xen-orchestra-202506301858/packages/xen-api/index.mjs:1073:24)
Jul 01 04:00:06 xoa xo-server[15851]: at default (file:///opt/xo/xo-builds/xen-orchestra-202506301858/packages/xen-api/_getTaskResult.mjs:13:29)
Jul 01 04:00:06 xoa xo-server[15851]: at XapiError.wrap (file:///opt/xo/xo-builds/xen-orchestra-202506301858/packages/xen-api/_XapiError.mjs:16:12)
Jul 01 04:00:06 xoa xo-server[15851]: 2025-07-01T02:00:06.151Z @xen-orchestra/xapi/disks/Xapi INFO openNbdCBT XapiError: SR_BACKEND_FAILURE_460(, Failed to calculate changed blocks for give>
@olivierlambert I updated the XO from source, it looks good for now.
downgraded to version 20.19.2 . Unfortunately no change.
root@xoa:~# node -v
v22.16.0
@olivierlambert
I will check with XOA. For now, it seems to me to be a local problem, because I use quite a few XOs and I haven't had this problem yet. If I find something I will report it.
None. The XCP-ng host also runs XO. Same VLAN, same IP range (XCP-ng 172.31.30.3, XO: 172.31.30.4). So the packet doesn't even need to go out to a switch.
The XO has an old Xenserver 7.0 (I'm migrating from it), it runs stable, its IP is 172.31.30.5.
Hello !
When using a freshly installed xcp-ng 8.3 and source compiled XO, the connection between XO and XCP-ng is always broken.
I have attached the log:
un 03 12:45:24 xoa xo-server[572]: 2025-06-03T10:45:24.140Z xo:main INFO + Console proxy (bogi.kornel - ::ffff:172.31.60.45)
Jun 03 12:46:00 xoa xo-server[572]: _watchEvents SocketError: other side closed
Jun 03 12:46:00 xoa xo-server[572]: at TLSSocket.<anonymous> (/opt/xo5/xo-builds/xen-orchestra-202506021322/node_modules/undici/lib/dispatcher/client-h1.js:701:24)
Jun 03 12:46:00 xoa xo-server[572]: at TLSSocket.emit (node:events:530:35)
Jun 03 12:46:00 xoa xo-server[572]: at TLSSocket.patchedEmit [as emit] (/opt/xo5/xo-builds/xen-orchestra-202506021322/@xen-orchestra/log/configure.js:52:17)
Jun 03 12:46:00 xoa xo-server[572]: at endReadableNT (node:internal/streams/readable:1698:12)
Jun 03 12:46:00 xoa xo-server[572]: at processTicksAndRejections (node:internal/process/task_queues:90:21) {
Jun 03 12:46:00 xoa xo-server[572]: code: 'UND_ERR_SOCKET',
Jun 03 12:46:00 xoa xo-server[572]: socket: {
Jun 03 12:46:00 xoa xo-server[572]: localAddress: '172.31.30.4',
Jun 03 12:46:00 xoa xo-server[572]: localPort: 58826,
Jun 03 12:46:00 xoa xo-server[572]: remoteAddress: '172.31.30.3',
Jun 03 12:46:00 xoa xo-server[572]: remotePort: 443,
Jun 03 12:46:00 xoa xo-server[572]: remoteFamily: 'IPv4',
Jun 03 12:46:00 xoa xo-server[572]: timeout: undefined,
Jun 03 12:46:00 xoa xo-server[572]: bytesWritten: 49957,
Jun 03 12:46:00 xoa xo-server[572]: bytesRead: 1673042
Jun 03 12:46:00 xoa xo-server[572]: },
Jun 03 12:46:00 xoa xo-server[572]: call: {
Jun 03 12:46:00 xoa xo-server[572]: duration: 13,
Jun 03 12:46:00 xoa xo-server[572]: method: 'event.from',
Jun 03 12:46:00 xoa xo-server[572]: params: [
Jun 03 12:46:00 xoa xo-server[572]: '* session id *',
Jun 03 12:46:00 xoa xo-server[572]: [Array],
Jun 03 12:46:00 xoa xo-server[572]: '00000000000001936776,00000000000001936233',
Jun 03 12:46:00 xoa xo-server[572]: 60.1
Jun 03 12:46:00 xoa xo-server[572]: ]
Jun 03 12:46:00 xoa xo-server[572]: }
Jun 03 12:46:00 xoa xo-server[572]: }
Jun 03 12:46:00 xoa xo-server[572]: 2025-06-03T10:46:00.438Z xo:main INFO - Console proxy (bogi.kornel - ::ffff:172.31.60.45)
Helo!
in bios mode, how can I boot a PVH VM ?
@irtaza9 I have the main characteristics of such a temple:
Minimal install is the basis
root fs: ext4 and minimum 10G disk
IP: DHCP
ssh login: cloud-user
login, ssh public key only.
If you are interested I can make it available for download.
@dthenot After the upgrade, it is not possible to create a new machine from a template if the VPS disk is not on the SR where the template disk is.
P.S.: Unfortunately, moving the disk from one SR to another does not work. After moving the disk it becomes corrupt, and after reset it will not boot.
Hello !
Not enough CPU and not enough RAM, because the RAM is 32G (dynamic max) and the CPU is 16 (8 socket 2 core). The host has max 8 CPU and 27G ram.