Top contributor

Private

Posts

  • RE: Error: Can't init vhd directory without using alias

    @poddingue @Team-XO-Backend @pierrebrunet @florent I have the same issue in XO (delta backup to S3)... Caused by master commit adecd7306e2fa262ef77d71f83555d160f03aa03

    {
      "data": {
        "mode": "delta",
        "reportWhen": "never"
      },
      "id": "1789353842351",
      "jobId": "d6c0a656-62c5-4c39-a57a-f246b39f1cef",
      "jobName": "minio-test",
      "message": "backup",
      "scheduleId": "bd4ef436-fd85-4f16-bf9e-71d1d0c8586f",
      "start": 1789353842351,
      "status": "failure",
      "tasks": [
        {
          "id": "0mu0n2une-6717eycsj3k",
          "start": 1789353844394,
          "status": "failure",
          "tasks": [
            {
              "id": "0mu0n2unj-32t56n3u8vn",
              "start": 1789353844399,
              "status": "success",
              "end": 1789353844854,
              "result": {
                "removedFiles": [],
                "changedFiles": [],
                "merge": false,
                "size": 0
              },
              "message": "clean-vm"
            },
            {
              "id": "0mu0n2vw5-jwlf68g7htp",
              "start": 1789353846005,
              "status": "success",
              "end": 1789353847486,
              "result": "6d4454f8-5735-0581-1eba-a66021f22a50",
              "message": "snapshot"
            },
            {
              "id": "0mu0n2x1b-qze2zs5ytaq",
              "start": 1789353847487,
              "status": "failure",
              "tasks": [
                {
                  "id": "0mu0n2ylj-b5qu3cxprie",
                  "start": 1789353849511,
                  "status": "failure",
                  "end": 1789353849570,
                  "result": {
                    "code": "NOT_SUPPORTED",
                    "message": "Can't init vhd directory without using alias",
                    "name": "Error",
                    "stack": "Error: Can't init vhd directory without using alias\n    at RemoteVhdDisk.init (file:///opt/xo/xo-builds/xen-orchestra-202609132201/@xen-orchestra/backup-archive/dist/disks/RemoteVhdDisk.mjs:74:41)\n    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)\n    at async openDisposableDisk (file:///opt/xo/xo-builds/xen-orchestra-202609132201/@xen-orchestra/backup-archive/dist/disks/index.mjs:32:9)\n    at async Promise.all (index 0)\n    at async checkDisk (file:///opt/xo/xo-builds/xen-orchestra-202609132201/@xen-orchestra/backups/_runners/_writers/_checkDisk.mjs:5:3)\n    at async DiskConsumerVhdDirectory.write (file:///opt/xo/xo-builds/xen-orchestra-202609132201/packages/vhd-lib/disk-consumer/DiskConsumerVhdDirectory.mjs:98:7)\n    at async writeToVhdDirectory (file:///opt/xo/xo-builds/xen-orchestra-202609132201/packages/vhd-lib/disk-consumer/index.mjs:43:10)\n    at async RemoteAdapter.writeVhd (file:///opt/xo/xo-builds/xen-orchestra-202609132201/@xen-orchestra/backups/RemoteAdapter.mjs:487:14)\n    at async asyncEach.concurrency (file:///opt/xo/xo-builds/xen-orchestra-202609132201/@xen-orchestra/backups/_runners/_writers/IncrementalRemoteWriter.mjs:276:31)"
                  },
                  "message": "transfer"
                }
              ],
              "end": 1789353849570,
              "result": {
                "code": "NOT_SUPPORTED",
                "message": "Can't init vhd directory without using alias",
                "name": "Error",
                "stack": "Error: Can't init vhd directory without using alias\n    at RemoteVhdDisk.init (file:///opt/xo/xo-builds/xen-orchestra-202609132201/@xen-orchestra/backup-archive/dist/disks/RemoteVhdDisk.mjs:74:41)\n    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)\n    at async openDisposableDisk (file:///opt/xo/xo-builds/xen-orchestra-202609132201/@xen-orchestra/backup-archive/dist/disks/index.mjs:32:9)\n    at async Promise.all (index 0)\n    at async checkDisk (file:///opt/xo/xo-builds/xen-orchestra-202609132201/@xen-orchestra/backups/_runners/_writers/_checkDisk.mjs:5:3)\n    at async DiskConsumerVhdDirectory.write (file:///opt/xo/xo-builds/xen-orchestra-202609132201/packages/vhd-lib/disk-consumer/DiskConsumerVhdDirectory.mjs:98:7)\n    at async writeToVhdDirectory (file:///opt/xo/xo-builds/xen-orchestra-202609132201/packages/vhd-lib/disk-consumer/index.mjs:43:10)\n    at async RemoteAdapter.writeVhd (file:///opt/xo/xo-builds/xen-orchestra-202609132201/@xen-orchestra/backups/RemoteAdapter.mjs:487:14)\n    at async asyncEach.concurrency (file:///opt/xo/xo-builds/xen-orchestra-202609132201/@xen-orchestra/backups/_runners/_writers/IncrementalRemoteWriter.mjs:276:31)"
              },
              "message": "export",
              "data": {
                "id": "9890e0c4-ba3a-4810-8245-a49fdf16b16e",
                "isFull": false,
                "type": "remote"
              }
            }
          ],
          "infos": [
            {
              "message": "Transfer data using NBD"
            },
            {
              "message": "will delete snapshot data"
            },
            {
              "data": {
                "vdiRef": "OpaqueRef:59ead5f8-710e-0e75-969e-bc59be6fab7f"
              },
              "message": "Snapshot data has been deleted"
            }
          ],
          "end": 1789353852197,
          "result": {
            "code": "NOT_SUPPORTED",
            "message": "Can't init vhd directory without using alias",
            "name": "Error",
            "stack": "Error: Can't init vhd directory without using alias\n    at RemoteVhdDisk.init (file:///opt/xo/xo-builds/xen-orchestra-202609132201/@xen-orchestra/backup-archive/dist/disks/RemoteVhdDisk.mjs:74:41)\n    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)\n    at async openDisposableDisk (file:///opt/xo/xo-builds/xen-orchestra-202609132201/@xen-orchestra/backup-archive/dist/disks/index.mjs:32:9)\n    at async Promise.all (index 0)\n    at async checkDisk (file:///opt/xo/xo-builds/xen-orchestra-202609132201/@xen-orchestra/backups/_runners/_writers/_checkDisk.mjs:5:3)\n    at async DiskConsumerVhdDirectory.write (file:///opt/xo/xo-builds/xen-orchestra-202609132201/packages/vhd-lib/disk-consumer/DiskConsumerVhdDirectory.mjs:98:7)\n    at async writeToVhdDirectory (file:///opt/xo/xo-builds/xen-orchestra-202609132201/packages/vhd-lib/disk-consumer/index.mjs:43:10)\n    at async RemoteAdapter.writeVhd (file:///opt/xo/xo-builds/xen-orchestra-202609132201/@xen-orchestra/backups/RemoteAdapter.mjs:487:14)\n    at async asyncEach.concurrency (file:///opt/xo/xo-builds/xen-orchestra-202609132201/@xen-orchestra/backups/_runners/_writers/IncrementalRemoteWriter.mjs:276:31)"
          },
          "message": "backup VM",
          "data": {
            "id": "a081f208-4e40-2ca5-c68e-86106af5a8ef",
            "type": "VM",
            "name_label": "Utest",
            "progress": 0
          }
        }
      ],
      "end": 1789353852211,
      "infos": [
        {
          "data": {
            "vms": [
              "a081f208-4e40-2ca5-c68e-86106af5a8ef"
            ]
          },
          "message": "vms"
        }
      ]
    }```
  • RE: VDI export to VMDK results in a corrupted disk

    It's possible that the issue lies within VMware Workstation. 🤷

  • RE: VDI export to VMDK results in a corrupted disk

    Have you attempted to analyze the exported file using qemu-img?
    For example:

    qemu-img info file.vmdk
    qemu-img check file.vmdk
    
  • RE: VDI export to VMDK results in a corrupted disk

    Ah... ok. I think I originally checked the VM export.

    This could be a bug. Does it occur with all VDIs? What happens if you try to import the file back into XO?

  • RE: VDI export to VMDK results in a corrupted disk

    @abudef What steps are you performing to export the VDI as a VMDK?

  • RE: GPU Passthrough

    @coolsport00 Yes, I am using the GPUs with llama-swap to serve qwen3.8-27b and qwen3.6-35b for local inference with Bifrost as an AI gateway for local and cloud AI provider. Never tried vGPU myself.

  • RE: Not sure if its XOStor but ... VDIs disappearing

    @jcdick1 Ideally you should open a ticket via the Support Portal and provide the tunnel ID there along with a link to this discussion.

  • RE: Not sure if its XOStor but ... VDIs disappearing

    @jcdick1 We can take a look using the support tunnel of your XOA instance.

  • RE: Not sure if its XOStor but ... VDIs disappearing

    Have you check the status of the nodes and for faulty resources?

    linstor n l
    linstor r l --faulty
    

Member List

borzelB borzel Group Owner
1,523 Posts 376 Reputation
Tristis OrisT Tristis Oris Group Owner
654 Posts 66 Reputation
nikadeN nikade Group Owner
767 Posts 146 Reputation
planedropP planedrop Group Owner
714 Posts 107 Reputation
T tuxen Group Owner
271 Posts 64 Reputation
J JeffBerntsen Group Owner
365 Posts 183 Reputation
K KPS Group Owner
369 Posts 55 Reputation
ronivayR ronivay Group Owner
80 Posts 36 Reputation
A abufrejoval Group Owner
123 Posts 22 Reputation
A Andrew Group Owner
1,485 Posts 631 Reputation
gskgerG gskger Group Owner
520 Posts 288 Reputation
DanpD Danp Group Owner
2,955 Posts 447 Reputation