@gleh After the update and a manual primary host reboot I was able to start new VMs and migrate VMs, but still could not run rolling pool update. I tried restarting tool stack, but it did not help.

pool.rollingReboot
{
  "pool": "40a08640-88dc-7ff9-9190-e13b89025b4d",
  "bypassBackupCheck": false,
  "shutdownPinnedVms": false
}
{
  "code": "CANNOT_EVACUATE_HOST",
  "params": [
    "NO_HOSTS_AVAILABLE,OpaqueRef:26968b78-860d-1842-a001-c93c8f07c895|NO_HOSTS_AVAILABLE,OpaqueRef:535b4eba-bc66-85a2-db6a-a857495bfafc|NO_HOSTS_AVAILABLE,OpaqueRef:49b9453d-5725-26ad-c1db-be85f5bf0cc4|NO_HOSTS_AVAILABLE,OpaqueRef:9c17b691-1b3d-3aee-138b-8e3a7ea7e58a|NO_HOSTS_AVAILABLE,OpaqueRef:c29f5630-a246-8413-8477-73f75cfb4c61|NO_HOSTS_AVAILABLE,OpaqueRef:5440c209-4e36-97e8-6d8c-74f20f82d710|NO_HOSTS_AVAILABLE,OpaqueRef:00581b21-7700-0803-9708-d0ffac2bf2f8"
  ],
  "call": {
    "duration": 4,
    "method": "host.assert_can_evacuate",
    "params": [
      "* session id *",
      "OpaqueRef:a8fb168d-bd82-5c1a-60fe-e965eefc43ef"
    ]
  },
  "message": "CANNOT_EVACUATE_HOST(NO_HOSTS_AVAILABLE,OpaqueRef:26968b78-860d-1842-a001-c93c8f07c895|NO_HOSTS_AVAILABLE,OpaqueRef:535b4eba-bc66-85a2-db6a-a857495bfafc|NO_HOSTS_AVAILABLE,OpaqueRef:49b9453d-5725-26ad-c1db-be85f5bf0cc4|NO_HOSTS_AVAILABLE,OpaqueRef:9c17b691-1b3d-3aee-138b-8e3a7ea7e58a|NO_HOSTS_AVAILABLE,OpaqueRef:c29f5630-a246-8413-8477-73f75cfb4c61|NO_HOSTS_AVAILABLE,OpaqueRef:5440c209-4e36-97e8-6d8c-74f20f82d710|NO_HOSTS_AVAILABLE,OpaqueRef:00581b21-7700-0803-9708-d0ffac2bf2f8)",
  "name": "XapiError",
  "stack": "XapiError: CANNOT_EVACUATE_HOST(NO_HOSTS_AVAILABLE,OpaqueRef:26968b78-860d-1842-a001-c93c8f07c895|NO_HOSTS_AVAILABLE,OpaqueRef:535b4eba-bc66-85a2-db6a-a857495bfafc|NO_HOSTS_AVAILABLE,OpaqueRef:49b9453d-5725-26ad-c1db-be85f5bf0cc4|NO_HOSTS_AVAILABLE,OpaqueRef:9c17b691-1b3d-3aee-138b-8e3a7ea7e58a|NO_HOSTS_AVAILABLE,OpaqueRef:c29f5630-a246-8413-8477-73f75cfb4c61|NO_HOSTS_AVAILABLE,OpaqueRef:5440c209-4e36-97e8-6d8c-74f20f82d710|NO_HOSTS_AVAILABLE,OpaqueRef:00581b21-7700-0803-9708-d0ffac2bf2f8)
    at XapiError.wrap (file:///opt/xo/xo-builds/xen-orchestra-202608130941/packages/xen-api/_XapiError.mjs:16:12)
    at file:///opt/xo/xo-builds/xen-orchestra-202608130941/packages/xen-api/transports/json-rpc.mjs:38:21
    at runNextTicks (node:internal/process/task_queues:65:5)
    at processImmediate (node:internal/timers:502:9)"
}

@gleh @flakpyro I have the same problem after this update. Can't migrate a VM. Can't run rolling pool reboot. Did a tool stack restart, did not help. Big issue as the pool master will have to be rebooted with live VMs running. I was able to suspend/unsuspend a VM. I could stop but not start a VM on the pool.

vm.migrate
{
  "targetHost": "388f9aad-2e39-41fa-acac-18a498eeac34",
  "vm": "450015b0-e878-5067-e8b6-8d0513a750f6"
}
{
  "code": "INTERNAL_ERROR",
  "params": [
    "xenopsd internal error: Hotplug.Hotplug_error(\"Failed to read /xapi/450015b0-e878-5067-e8b6-000000000001/private/vif/1/trunks\")"
  ],
  "task": {
    "uuid": "8e1d9888-9f9f-ebab-8a9f-87d2cd651113",
    "name_label": "Async.VM.pool_migrate",
    "name_description": "",
    "allowed_operations": [],
    "current_operations": {},
    "created": "20260815T18:38:30Z",
    "finished": "20260815T18:38:32Z",
    "status": "failure",
    "resident_on": "OpaqueRef:a8fb168d-bd82-5c1a-60fe-e965eefc43ef",
    "progress": 1,
    "type": "<none/>",
    "result": "",
    "error_info": [
      "INTERNAL_ERROR",
      "xenopsd internal error: Hotplug.Hotplug_error(\"Failed to read /xapi/450015b0-e878-5067-e8b6-000000000001/private/vif/1/trunks\")"
    ],
    "other_config": {},
    "subtask_of": "OpaqueRef:NULL",
    "subtasks": [],
    "backtrace": "(((process xenopsd-xc)(filename ocaml/xenopsd/lib/xenops_server.ml)(line 2917))((process xenopsd-xc)(filename ocaml/xenopsd/lib/xenops_server.ml)(line 2966))((process xenopsd-xc)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xenopsd-xc)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 39))((process xenopsd-xc)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xenopsd-xc)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 39))((process xenopsd-xc)(filename ocaml/libs/stunnel/stunnel.ml)(line 414))((process xenopsd-xc)(filename ocaml/xenopsd/lib/xenops_server.ml)(line 2865))((process xenopsd-xc)(filename ocaml/xenopsd/lib/xenops_task.ml)(line 103))((process xenopsd-xc)(filename ocaml/xenopsd/lib/xenops_task.ml)(line 111))((process xenopsd-xc)(filename ocaml/xenopsd/lib/xenops_server.ml)(line 3412))((process xenopsd-xc)(filename ocaml/xenopsd/lib/xenops_server.ml)(line 3422))((process xenopsd-xc)(filename ocaml/xenopsd/lib/xenops_server.ml)(line 3443))((process xenopsd-xc)(filename ocaml/xapi-idl/lib/task_server.ml)(line 192))((process xapi)(filename ocaml/xapi/xapi_xenops.ml)(line 3481))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 39))((process xapi)(filename ocaml/xapi/xapi_xenops.ml)(line 3652))((process xapi)(filename ocaml/xapi/xapi_vm_migrate.ml)(line 262))((process xapi)(filename ocaml/xapi/xapi_vm_migrate.ml)(line 268))((process xapi)(filename ocaml/xapi/xapi_vm_migrate.ml)(line 293))((process xapi)(filename ocaml/xapi/xapi_vm_migrate.ml)(line 434))((process xapi)(filename ocaml/xapi/xapi_xenops.ml)(line 3490))((process xapi)(filename ocaml/xapi/xapi_vm_migrate.ml)(line 458))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 39))((process xapi)(filename ocaml/xapi/message_forwarding.ml)(line 141))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 39))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 39))((process xapi)(filename ocaml/xapi/message_forwarding.ml)(line 2519))((process xapi)(filename ocaml/xapi/rbac.ml)(line 228))((process xapi)(filename ocaml/xapi/rbac.ml)(line 238))((process xapi)(filename ocaml/xapi/server_helpers.ml)(line 78)))"
  },
  "message": "INTERNAL_ERROR(xenopsd internal error: Hotplug.Hotplug_error(\"Failed to read /xapi/450015b0-e878-5067-e8b6-000000000001/private/vif/1/trunks\"))",
  "name": "XapiError",
  "stack": "XapiError: INTERNAL_ERROR(xenopsd internal error: Hotplug.Hotplug_error(\"Failed to read /xapi/450015b0-e878-5067-e8b6-000000000001/private/vif/1/trunks\"))
    at XapiError.wrap (file:///opt/xo/xo-builds/xen-orchestra-202608130941/packages/xen-api/_XapiError.mjs:16:12)
    at default (file:///opt/xo/xo-builds/xen-orchestra-202608130941/packages/xen-api/_getTaskResult.mjs:13:29)
    at Xapi._addRecordToCache (file:///opt/xo/xo-builds/xen-orchestra-202608130941/packages/xen-api/index.mjs:1329:24)
    at file:///opt/xo/xo-builds/xen-orchestra-202608130941/packages/xen-api/index.mjs:1363:14
    at Array.forEach (<anonymous>)
    at Xapi._processEvents (file:///opt/xo/xo-builds/xen-orchestra-202608130941/packages/xen-api/index.mjs:1353:12)
    at Xapi._watchEvents (file:///opt/xo/xo-builds/xen-orchestra-202608130941/packages/xen-api/index.mjs:1560:14)"
}

@florent

Running delta backup with CBT to S3.
NBD connections=1
Yes, NBD. No VHD only.
Yes, NBD is enabled and working on all pool hosts.
Yes, XO can access the network used for NBD.
No, a default backup network as not been assigned.
No more logs from journalctl.

My normal large nightly delta backup to S3 ran and did not produce any new errors. So far, just the one error once.

@florent @olivierlambert I also have the same issue. I see there have been a lot of XO updates to the backups. Maybe this is fixing a hidden problem?

CR works, but normal delta backups to S3 have the issue on some of the VMs (on a test run). All the VMs on this backup are Linux.

A second run of the same delta backups all worked. I'll have to see what happens for the normal nightly backup with a lot more VMs...

(edit fix logs):

 2026-07-28T23:17:34.544Z xo:xapi:vdi WARN invalid HTTP header in response body {
   body: 'HTTP/1.1 500 Internal Error\r\n' +
     'content-length: 318\r\n' +
     'content-type: text/html\r\n' +
     'connection: close\r\n' +
     'cache-control: no-cache, no-store\r\n' +
     '\r\n' +
     '<html><body><h1>HTTP 500 internal server error</h1>An unexpected error occurred; please wait a while and try again. If the problem persists, please contact your support representative.<h1> Additional information </h1>VDI_INCOMPATIBLE_TYPE: [ OpaqueRef:4a172cde-c772-2b6c-100d-f63ea5e4d842; CBT metadata ]</body></html>'
 }
 2026-07-28T23:17:34.552Z xo:xapi:xapi-disks WARN can't compute delta OpaqueRef:6ec8ab35-d377-cd33-ce94-72a7a4e9e3b0 from OpaqueRef:4a172cde-c772-2b6c-100d-f63ea5e4d842, fall back to a full {
   error: Error: invalid HTTP header in response body
       at checkVdiExport (file:///opt/xo/xo-builds/xen-orchestra-202607281243/@xen-orchestra/xapi/vdi.mjs:39:19)
       at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
       at async Xapi.exportContent (file:///opt/xo/xo-builds/xen-orchestra-202607281243/@xen-orchestra/xapi/vdi.mjs:263:5)
       at async #getExportStream (file:///opt/xo/xo-builds/xen-orchestra-202607281243/@xen-orchestra/xapi/disks/XapiVhdStreamSource.mjs:123:20)
       at async XapiVhdStreamSource.init (file:///opt/xo/xo-builds/xen-orchestra-202607281243/@xen-orchestra/xapi/disks/XapiVhdStreamSource.mjs:135:23)
       at async #openExportStream (file:///opt/xo/xo-builds/xen-orchestra-202607281243/@xen-orchestra/xapi/disks/Xapi.mjs:186:7)
       at async #openNbdStream (file:///opt/xo/xo-builds/xen-orchestra-202607281243/@xen-orchestra/xapi/disks/Xapi.mjs:97:22)
       at async XapiDiskSource.openSource (file:///opt/xo/xo-builds/xen-orchestra-202607281243/@xen-orchestra/xapi/disks/Xapi.mjs:268:18)
       at async XapiDiskSource.init (file:///opt/xo/xo-builds/xen-orchestra-202607281243/@xen-orchestra/disk-transform/dist/DiskPassthrough.mjs:28:41)
       at async file:///opt/xo/xo-builds/xen-orchestra-202607281243/@xen-orchestra/backups/_incrementalVm.mjs:104:5
 }
 2026-07-28T23:17:34.553Z xo:xapi:xapi-disks INFO export through vhd

@olivierlambert Working again. Thanks!

@olivierlambert I have a full Realtek 8125/8126/8127 update to replace the existing r8125 driver, as required to support newer chips.

The new 8125 driver drops the 8126 support but you just install the 8126 if needed (requires newer 8125 driver to avoid module conflicts).

@andriy.sultanov No error... returns nothing.

@rzr Updates installed and running. I also run the snapshot-fixer.py and xapi_leaked_vbds.py scripts... The fixer found/fixed lots on many pools...

@andriy.sultanov I have the same error... On one pool, I ran snapshot-fixer.py and it fixed about 50 of them, but xapi_leaked_vbds.py still returns an error (before and after fix):

Traceback (most recent call last):
  File "./xapi_leaked_vbds.py", line 23, in <module>
    snap = xapi.VM.get_parent(snap)
  File "/usr/lib/python3.6/site-packages/XenAPI.py", line 317, in __call__
    return self.__send(self.__name, args)
  File "/usr/lib/python3.6/site-packages/XenAPI.py", line 198, in xenapi_request
    result = _parse_result(getattr(self, methodname)(*full_params))
  File "/usr/lib/python3.6/site-packages/XenAPI.py", line 292, in _parse_result
    raise Failure(result['ErrorDescription'])
XenAPI.Failure: ['HANDLE_INVALID', 'VM', 'Ref:119']

@acebmxer This has been reported before. XO needs to report an actual error for this problem.

@rzr Again, installed on several active pools. Running correctly for my use.

@rzr Up and running on several pools. Rolling pool reboot worked (after fixing a few non-upgrade issues). Running normal operations, replication, backup, migration, NFS, ISO, etc.

xenpm get-core-temp is mostly working. Not working on AMD Ryzen 5 5600U as expected. HP DL G8 Intel E5-2673 v2 shows 64 CPUs. The actual CPUs show correctly, the higher ones (that don't exist) show [CPUxx] Unable to fetch temperature (19 - No such device). HP DL G10 Intel Xeon(R) Gold 62xx and Desktop Core i7 11th and 7th are good.

@rzr Updates installed everywhere (on top of the previous updates). Rolling pool reboot worked this time (with correct prep).

@poddingue Since setting NBD=1, I have not seen the problem.

SR is NFS on dual 40G ethernet with a TrueNAS scale 25.10 server using all NVMe SSD, so storage performance is as good as I can make it.

I'll have to enable NBD=2 again to see if it still happens and if I can find the relevant part of the logs. As this is a random problem I can't recreate it on a normal test environment.

@All-Ki Thanks for your work!

ProLiant DL360p Gen8

UID Light        | 0x01              | ok
Sys. Health LED  | no reading        | ns
01-Inlet Ambient | 33 degrees C      | ok
02-CPU 1         | 55 degrees C      | ok
03-CPU 2         | 50 degrees C      | ok
04-P1 DIMM 1-6   | 45 degrees C      | ok
05-P1 DIMM 7-12  | 44 degrees C      | ok
06-P2 DIMM 1-6   | 38 degrees C      | ok
07-P2 DIMM 7-12  | 43 degrees C      | ok
08-P1 Mem Zone   | 42 degrees C      | ok
09-P1 Mem Zone   | 45 degrees C      | ok
10-P2 Mem Zone   | 39 degrees C      | ok
11-P2 Mem Zone   | 40 degrees C      | ok
12-HD Max        | 35 degrees C      | ok
13-Chipset 1     | 52 degrees C      | ok
14-Chipset1 Zone | 45 degrees C      | ok
15-P/S 1 Inlet   | 34 degrees C      | ok
16-P/S 1 Zone    | 40 degrees C      | ok
17-P/S 2 Inlet   | 42 degrees C      | ok
18-P/S 2 Zone    | 43 degrees C      | ok
19-PCI #1        | disabled          | ns
20-PCI #2        | disabled          | ns
21-VR P1         | 60 degrees C      | ok
22-VR P2         | 56 degrees C      | ok
23-VR P1 Mem     | 39 degrees C      | ok
24-VR P1 Mem     | 36 degrees C      | ok
25-VR P2 Mem     | 32 degrees C      | ok
26-VR P2 Mem     | 36 degrees C      | ok
27-VR P1Mem Zone | 38 degrees C      | ok
28-VR P1Mem Zone | 36 degrees C      | ok
29-VR P2Mem Zone | 31 degrees C      | ok
30-VR P2Mem Zone | 33 degrees C      | ok
31-HD Controller | 71 degrees C      | ok
32-HD Cntlr Zone | 52 degrees C      | ok
33-PCI 1 Zone    | 43 degrees C      | ok
34-PCI 1 Zone    | 46 degrees C      | ok
35-LOM Card      | 70 degrees C      | ok
36-PCI 2 Zone    | 50 degrees C      | ok
37-System Board  | 52 degrees C      | ok
38-System Board  | 45 degrees C      | ok
39-Sys Exhaust   | 43 degrees C      | ok
40-Sys Exhaust   | 46 degrees C      | ok
41-Sys Exhaust   | 46 degrees C      | ok
42-SuperCAP Max  | 33 degrees C      | ok
Fan Block 1      | 94.86 percent     | ok
Fan Block 2      | 94.86 percent     | ok
Fan Block 3      | 94.86 percent     | ok
Fan Block 4      | 94.86 percent     | ok
Fan Block 5      | 94.86 percent     | ok
Fan Block 6      | 94.86 percent     | ok
Fan Block 7      | 94.86 percent     | ok
Fan Block 8      | 94.86 percent     | ok
Power Supply 1   | 205 Watts         | ok
Power Supply 2   | 210 Watts         | ok
Power Meter      | 430 Watts         | ok
Power Supplies   | 0x01              | ok
Fans             | 0x02              | ok
Memory           | 0x40              | ok
C1 P1I Bay 1     | 0x01              | ok
C1 P1I Bay 2     | 0x01              | ok
C1 P1I Bay 3     | 0x01              | ok
C1 P1I Bay 4     | 0x01              | ok
C1 P2I Bay 5     | 0x01              | ok
C1 P2I Bay 6     | 0x01              | ok
C1 P2I Bay 7     | 0x01              | ok
C1 P2I Bay 8     | 0x01              | ok

ProLiant DL360 Gen10

UID              | 0x01              | ok
SysHealth_Stat   | 0x01              | ok
01-Inlet Ambient | 19 degrees C      | ok
02-CPU 1         | 52 degrees C      | ok
03-CPU 2         | 63 degrees C      | ok
04-P1 DIMM 1-6   | disabled          | ns
05-PMM 1-6       | disabled          | ns
06-P1 DIMM 7-12  | 44 degrees C      | ok
07-PMM 7-12      | disabled          | ns
08-P2 DIMM 1-6   | disabled          | ns
09-PMM 1-6       | disabled          | ns
10-P2 DIMM 7-12  | 48 degrees C      | ok
11-PMM 7-12      | disabled          | ns
12-HD Max        | 35 degrees C      | ok
13-Exp Bay Drive | disabled          | ns
14-Stor Batt 1   | 18 degrees C      | ok
15-Front Ambient | 24 degrees C      | ok
16-VR P1         | 48 degrees C      | ok
17-VR P2         | 54 degrees C      | ok
18-VR P1 Mem 1   | 31 degrees C      | ok
19-VR P1 Mem 2   | 29 degrees C      | ok
20-VR P2 Mem 1   | 35 degrees C      | ok
21-VR P2 Mem 2   | 36 degrees C      | ok
22-Chipset       | 42 degrees C      | ok
23-BMC           | 79 degrees C      | ok
24-BMC Zone      | 49 degrees C      | ok
26-HD Cntlr Zone | 40 degrees C      | ok
29-I/O Zone      | 37 degrees C      | ok
30-PCI 1         | disabled          | ns
31-PCI 1 Zone    | 45 degrees C      | ok
32-PCI 2         | disabled          | ns
33-PCI 2 Zone    | 44 degrees C      | ok
34-PCI 3         | disabled          | ns
35-PCI 3 Zone    | disabled          | ns
37-Rear HD Max   | disabled          | ns
38-Battery Zone  | 43 degrees C      | ok
39-P/S 1 Inlet   | 42 degrees C      | ok
40-P/S 2 Inlet   | 48 degrees C      | ok
41-P/S 1         | 46 degrees C      | ok
42-P/S 2         | 55 degrees C      | ok
43-E-Fuse        | 45 degrees C      | ok
44-P/S 2 Zone    | 53 degrees C      | ok
49-CPU 1 PkgTmp  | 84 degrees C      | ok
50-CPU 2 PkgTmp  | 94 degrees C      | ok
61-AHCI HD Max   | disabled          | ns
69-PCI 1 M2      | disabled          | ns
70-PCI 1 M2 Zn   | disabled          | ns
71-PCI 2 M2      | disabled          | ns
72-PCI 2 M2 Zn   | disabled          | ns
73-PCI 3 M2      | disabled          | ns
74-PCI 3 M2 Zn   | disabled          | ns
Fan 1            | 0x01              | ok
Fan 1 DutyCycle  | 26.26 percent     | ok
Fan 1 Presence   | 0x02              | ok
Fan 2            | 0x01              | ok
Fan 2 DutyCycle  | 23.52 percent     | ok
Fan 2 Presence   | 0x02              | ok
Fan 3            | 0x01              | ok
Fan 3 DutyCycle  | 23.52 percent     | ok
Fan 3 Presence   | 0x02              | ok
Fan 4            | 0x01              | ok
Fan 4 DutyCycle  | 23.52 percent     | ok
Fan 4 Presence   | 0x02              | ok
Fan 5            | 0x01              | ok
Fan 5 DutyCycle  | 23.52 percent     | ok
Fan 5 Presence   | 0x02              | ok
Fan 6            | 0x01              | ok
Fan 6 DutyCycle  | 24.30 percent     | ok
Fan 6 Presence   | 0x02              | ok
Fan 7            | 0x01              | ok
Fan 7 DutyCycle  | 24.30 percent     | ok
Fan 7 Presence   | 0x02              | ok
Power Supply 1   | 0x01              | ok
PS 1 Input       | 200 Watts         | ok
Power Supply 2   | 0x01              | ok
PS 2 Input       | 190 Watts         | ok
Power Meter      | 400 Watts         | ok
Fans             | 0x01              | ok
Power Supplies   | 0x01              | ok
Memory Status    | 0x40              | ok
Megacell Status  | 0x04              | ok
Intrusion        | Not Readable      | ns
CPU Utilization  | 252 unspecified   | ok
PS 1 Output      | 190 Watts         | ok
PS_Volt_Out_01   | 12 Volts          | ok
PS_Volt_In_01    | 205 Volts         | ok
PS_Curr_Out_01   | 15.80 Amps        | ok
PS_Curr_In_01    | 1 Amps            | ok
PS 2 Output      | 180 Watts         | ok
PS_Volt_Out_02   | 12 Volts          | ok
PS_Volt_In_02    | 204 Volts         | ok
PS_Curr_Out_02   | 15.10 Amps        | ok
PS_Curr_In_02    | 0.90 Amps         | ok
27.1-LOM-Communi | 68 degrees C      | ok
28.1-LOM Card-I/ | 84 degrees C      | ok
25.1-HD Controll | 39 degrees C      | ok
25.2-HD Controll | 45 degrees C      | ok
25.3-HD Controll | 41 degrees C      | ok
LOM_Link_P1      | 0x02              | ok
LOM_Link_P2      | Not Readable      | ns
LOM_Link_P3      | Not Readable      | ns
LOM_Link_P4      | Not Readable      | ns
ALOM_Link_P1     | 0x02              | ok
ALOM_Link_P2     | 0x02              | ok
Dr_Stat_1I1_B001 | 0x01              | ok
Dr_Stat_2I1_B005 | 0x01              | ok
CPU_Stat_C1      | 0x80              | ok
CPU_Stat_C2      | 0x80              | ok

I found the first step. It's looking for the vendor as the whole name proliant dl360p gen8

Then I have a few working, and several that don't.

Works: Total Power, CPUs Temp, Fans Speed.

@olivierlambert With the new IPMI plugin for XO I was hoping to see support for HP servers. But at least it seems I can add it to my installation and then post my results.

I added "hp" as a vendor and all of the plugin settings (if you leave it blank there is an error when saving).

But I still see no sensor data for the hosts in XO.

Any thoughts on what I should add? check? do? to make it work?

@florent As a note, I'm using Debian as the base OS for XO. Other OS, like Ubuntu may have other name conflicts...

As for links, the dropdown box should show the link and it's destination). As a link, I don't think you need to "follow" it when selected (like a directory would), it's just a file. I did not check other non-standard files (like devices).

If I select a directory to restore then it would be good if the links are included. Both tar and zip do support links, so they should be restorable.

@florent Ubuntu LVM file restore is working! (commit 38931)

Now for another important issue I noticed with file restore (not directly LVM).

Symbolic links don't show up. They should be restorable alone, but more importantly you need to be able to see and follow them for directories.

For example. In Ubuntu, /bin is a link to /usr/bin. It is important to be able to click on /bin as a link to /usr/bin so files can be found in the backup. Another example is /vmlinuz that is a link to boot/vmlinuz-5.10.0-44-amd64. At worst the file restore should show a link (and it's destination), even if I can't restore the link. This is not just a LVM issue.

@florent LVM restore still failed for me (fix_flr commit b7230). Trying file restore from Ubuntu 22 VM (on S3 delta backup). Single VDI, 3 partitions (bios, uefi boot, LVM root). Accessing the LVM root.

Jun  5 15:26:28 xo2 kernel: [16230.122916] loop5: detected capacity change from 0 to 21474836480
Jun  5 15:26:35 xo2 xo-server[4046]: 2026-06-05T19:26:35.793Z xo:api WARN admin | backupNg.listFiles(...) [146ms] =!> Error: Command failed: mount --options=loop,ro,sizelimit=20397948928,offset=1075838976 --source=/tmp/ouit10u6k3f/vhd0 --target=/tmp/d4l0v4n01h
Jun  5 15:26:35 xo2 xo-server[4046]: mount: /tmp/d4l0v4n01h: unknown filesystem type 'LVM2_member'.

@rzr Installed and running. Not expecting any issues because I'm not using SMB/CIFS, ice card, or CPU with affected microcode.

Rolling pool reboot failed me again... This time it got stuck evacuating a host with no VMs.