Orphan VDIs in XO show health problem

wilsonqanda

Version:
XO:
From:
Xen Orchestra, commit 0a28a
To:
Xen Orchestra, commit b89c2

XCP-ng:
From:
8.3 loaded from ISO: xcp-ng-8.3.0-rc1.iso
To:
8.3 loaded from ISO: xcp-ng-8.3.0-20250606.iso
and haven't update it since until there is a major version release.

Issue:
Orphan VDIs in XO show health problem for my "base copy" snapshots as it can't find the VDIs anymore for some reason?
Note: I have clone of before the XO update and have both XO commit 0a28a and commit b89c2 running that's why I was able to take snapshots below so not everything is all lost and done for...

From: (before update)

To: (after update)

Is it ok to delete it seem like I can't delete it... in fear of breaking all my VMs.

olivierlambert

Adding @team-storage in the loop

anthoineb

@wilsonqanda, can you share the /var/log/SMlog? Do you installed qcow2 release and use some qcow2 VDIs?

wilsonqanda

Really appreciate your help !

This is the SMlog on one of the machine. I cannot rule out qcow2 but I definitely upgrade it from back in the early release of 8.3a and 8.3b. If I did use qcow2 I probably install and forgot about it... but its definitely affecting every VMs on the XO (commit b89c2)

SMlog.txt
SMlog2.txt

I have also notice that all the VMs on the XO (commit b89c2) run on debian 12 all have missing disks.

FROM:
Xen Orchestra, commit 0a28a (Pre Update on XO disk available still as long as I use the old GUI)

TO:
Xen Orchestra, commit b89c2 (Post Update on XO missing Disks)
Surprisingly the VM still loads and run without the disks but extremely confusing...

Snapshots on it fail for both XO commit version with the following error might be a related issue too which I just notice now:

vm.revert
{
  "snapshot": "d0734350-87a4-97f8-97dc-9d9ac5c24b5d"
}
{
  "code": "INVALID_VALUE",
  "params": [
    "snapshot_metadata:HVM__boot_policy",
    "null"
  ],
  "task": {
    "uuid": "058f49ac-82cc-a49b-eaaf-d20e4a319432",
    "name_label": "Async.VM.revert",
    "name_description": "",
    "allowed_operations": [],
    "current_operations": {},
    "created": "20260106T02:19:26Z",
    "finished": "20260106T02:19:26Z",
    "status": "failure",
    "resident_on": "OpaqueRef:ea86afa1-6562-0eac-79fc-75be4ce1cb2a",
    "progress": 1,
    "type": "<none/>",
    "result": "",
    "error_info": [
      "INVALID_VALUE",
      "snapshot_metadata:HVM__boot_policy",
      "null"
    ],
    "other_config": {},
    "subtask_of": "OpaqueRef:NULL",
    "subtasks": [],
    "backtrace": "(((process xapi)(filename ocaml/xapi/xapi_vm_snapshot.ml)(line 432))((process xapi)(filename ocaml/xapi/xapi_vm_snapshot.ml)(line 428))((process xapi)(filename ocaml/xapi/xapi_vm_snapshot.ml)(line 471))((process xapi)(filename ocaml/xapi/message_forwarding.ml)(line 2334))((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 2292))((process xapi)(filename ocaml/xapi/rbac.ml)(line 188))((process xapi)(filename ocaml/xapi/rbac.ml)(line 197))((process xapi)(filename ocaml/xapi/server_helpers.ml)(line 77)))"
  },
  "message": "INVALID_VALUE(snapshot_metadata:HVM__boot_policy, null)",
  "name": "XapiError",
  "stack": "XapiError: INVALID_VALUE(snapshot_metadata:HVM__boot_policy, null)
    at Function.wrap (file:///opt/xo/xo-builds/xen-orchestra-202512260040/packages/xen-api/_XapiError.mjs:16:12)
    at default (file:///opt/xo/xo-builds/xen-orchestra-202512260040/packages/xen-api/_getTaskResult.mjs:13:29)
    at Xapi._addRecordToCache (file:///opt/xo/xo-builds/xen-orchestra-202512260040/packages/xen-api/index.mjs:1078:24)
    at file:///opt/xo/xo-builds/xen-orchestra-202512260040/packages/xen-api/index.mjs:1112:14
    at Array.forEach (<anonymous>)
    at Xapi._processEvents (file:///opt/xo/xo-builds/xen-orchestra-202512260040/packages/xen-api/index.mjs:1102:12)
    at Xapi._watchEvents (file:///opt/xo/xo-builds/xen-orchestra-202512260040/packages/xen-api/index.mjs:1275:14)"
}

wilsonqanda

@anthoineb Is there a cmd to check on the xcp-ng to see if "qcow2" was ever installed? Likely I either never did or installed and forgot about it but I did ready about it previously but don't remember if I acted on it or not.

anthoineb

@wilsonqanda qcow2 packages are in a separate repository. You should have setup the repo, a grep -r "qcow2" /etc/yum.repos.d/ should tell you if it was setup on your host.