Posts made by cunrun

@jorge-gbs Hello, I have done a fair amount of testing on this but haven't come up with much. Since the GFX card is from 2016 odd I did find that installing Windows 2016 natively onto the server hardware worked. But as soon as you update the driver you get a blue screen of death. I think this is going to be a firmware issue on the GFX card itself but I don't know how to update that and if it's going to be a pain at this stage, then it sounds like it will not be as reliable as one would hope.

I haven't tried creating a 2016 VM and passing it through. That might work, until it updates at least. You may have more luck than I did, but I still have the card in a server in case one of us figures it out.

Just to recap the things I've tried:

XCP-NG 8.1, 8.2 and 8.3 Beta - All have the same issue as you describe.
Passing through to - 2015 Windows 10 VM up to 2017 Windows 10. Windows 2019. Ubuntu. Nothing worked.
Dell R730xd server and a Dell R740. Same issue.

On a side note, I tried the GIU USB pass through feature in 8.3 beta and I had the same results so there's a possibility it's something I haven't done with the Dom0 stuff.

I will ask, to any admins that are reading, that it might be a time to take down the S7150x2 from the documentation as it might be too old to work, now.

@john-c Yeah, tried all of that. I get the same issue with older GPU's when vGPU'ing them. So I'm wondering if it's a setting on the Dell Server BIOS.

Just providing feedback:

Love the XO interface at the start, very helpful. Also, I do like the colour scheme. It turned a few heads in the datacentre the other day.

Using a Dell R740xd with 2 GPU's to pass through - Works fine and given the GPU's to a VM each (for 3D mapping).

After watching Lawrence Systems device passthrough vid, I managed to view a PUSB in the XOA via the host. I managed to pass it through to a Windows 10 VM but cannot see if in the device manager. Assuming that this still in beta stages so will try a different set of USB devices for testing but so far the Seagate RSS LLC_00000000NAB7AQ06 doesn't show in Windows.

Happy to test further

Some further updates on this particular issue. I managed to see the graphics card on a Windows 2016 standard (older ISO) install. I installed it natively onto the Dell server. It worked for about 20 minutes before it crashed the server and then kept crashing each time Windows loaded. So it would seem that this may be possible if using Windows 2016 Server standard, and possibly if I can work out how to update the firmware of the graphics unit.

I do know that a Radeon FirePro W2100 and a Radeon PRO WX 3200 work for passthrough. I have both running on one server feeding a 3D globe VM and a 3d processing VM. It's a shame I cannot get the AMD Radeon S7150x2 working.

Deal all,

So, non of the above seemed to work. I'd imagine there's some sort of firmware update I need on the graphics card to get this to function properly.

All,

Very good suggestions. I will try them later today!

@splastunov I've done that but it prompts that it can't see the graphics card. It works fine on normal pass through.

I think we are going to use pass though to just run a giant VM and chuck graphics related things at it. It was a bargain purchase at £150 for the graphics card so I'm going to keep it. I installed Windows Server 2019 DC and it was a similar result so it's a possibility that the firmware is out of date on the GFX card? Clutching at straws really.

@planedrop So what I have tried so far:

Hardware
CPU model Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
GPUs G200eR2, Tonga XT GL [FirePro S7150], Oland GL [FirePro W2100], Tonga XT GL [FirePro S7150]
Core (socket) 32 (2)
Hyper-threading (SMT) Enabled
Manufacturer info Dell Inc. (PowerEdge R730xd)
BIOS info Dell Inc. (2.12.1)

Software
Version 8.2 XCP-NG
Windows 10, versions 1709 to 22H2
Ubuntu 18.04

What's interesting is that in device manager there is a PCI card showing up but you cannot install the graphics card drivers to it. In Ubuntu I get an issue where I get logged out in 1 minute. Taking the graphics card out of the equation it runs fine. If I have the graphics card set to be passthrough only, it can be seen but then I have an over kill graphics card on one VM.

I think I'm going to abandon the idea as it's take too long to sort. It seems to me like a bug/setting/issue with the BIOS, hardware and software. But it's too broad to troubleshoot too much more.

Cheers

@planedrop Yes, that's right. It can't detect a gpu.

Hello,

I'm having issues seeing a graphics card in the Windows OS on a fresh install with vGPU.

I enabled SR-IOV on the BIOS
Installed 8.2
Copied and installed the mxgpu-2.0.0.amd.iso

In Xen Orchestra I can see and divide the GPU's from the card on the VM. This shows up in Xen Orchestra fine. What I can't do is install the drivers for this card in the OS on the VM I'm giving it to.

What troubleshooting steps do I need to take to get this to be seen? It seems odd that all else can see the graphics card except the VM I've associated it to.

Running on Dell R730xd Server with AMD Radeon S7150x2 graphics card. Fresh build of everything this morning. I have another R730xd and it does the same on that.

@olivierlambert

Up to date.

{
  "data": {
    "mode": "full",
    "reportWhen": "always"
  },
  "id": "1694769218021",
  "jobId": "feeeefb8-0463-483a-a385-adc3a81be5e7",
  "jobName": "PS-XCP-01 - Full VM Backup",
  "message": "backup",
  "scheduleId": "032cb383-47dd-4dc4-b0b0-3f091f662656",
  "start": 1694769218021,
  "status": "failure",
  "infos": [
    {
      "data": {
        "vms": [
          "89aee0c4-f8f1-6961-1e85-aa76f7644220"
        ]
      },
      "message": "vms"
    }
  ],
  "tasks": [
    {
      "data": {
        "type": "VM",
        "id": "89aee0c4-f8f1-6961-1e85-aa76f7644220",
        "name_label": "HBW16EXC10"
      },
      "id": "1694769219646",
      "message": "backup VM",
      "start": 1694769219646,
      "status": "failure",
      "tasks": [
        {
          "id": "1694769220046",
          "message": "snapshot",
          "start": 1694769220046,
          "status": "failure",
          "end": 1694769220397,
          "result": {
            "code": "NO_HOSTS_AVAILABLE",
            "params": [],
            "task": {
              "uuid": "15664390-4605-717d-d394-4f4ca8c0005b",
              "name_label": "Async.VM.snapshot",
              "name_description": "",
              "allowed_operations": [],
              "current_operations": {},
              "created": "20230915T09:13:40Z",
              "finished": "20230915T09:13:40Z",
              "status": "failure",
              "resident_on": "OpaqueRef:b71238e8-bce1-4a59-b9be-870e2de57558",
              "progress": 1,
              "type": "<none/>",
              "result": "",
              "error_info": [
                "NO_HOSTS_AVAILABLE"
              ],
              "other_config": {},
              "subtask_of": "OpaqueRef:NULL",
              "subtasks": [],
              "backtrace": "(((process xapi)(filename ocaml/xapi/xapi_vm_helpers.ml)(line 788))((process xapi)(filename ocaml/xapi/message_forwarding.ml)(line 1240))((process xapi)(filename lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xapi)(filename ocaml/xapi/rbac.ml)(line 231))((process xapi)(filename ocaml/xapi/server_helpers.ml)(line 103)))"
            },
            "message": "NO_HOSTS_AVAILABLE()",
            "name": "XapiError",
            "stack": "XapiError: NO_HOSTS_AVAILABLE()\n    at XapiError.wrap (/usr/local/lib/node_modules/xo-server/node_modules/xen-api/dist/_XapiError.js:21:12)\n    at _default (/usr/local/lib/node_modules/xo-server/node_modules/xen-api/dist/_getTaskResult.js:18:38)\n    at Xapi._addRecordToCache (/usr/local/lib/node_modules/xo-server/node_modules/xen-api/dist/index.js:752:51)\n    at /usr/local/lib/node_modules/xo-server/node_modules/xen-api/dist/index.js:785:14\n    at Array.forEach (<anonymous>)\n    at Xapi._processEvents (/usr/local/lib/node_modules/xo-server/node_modules/xen-api/dist/index.js:773:12)\n    at Xapi._watchEvents (/usr/local/lib/node_modules/xo-server/node_modules/xen-api/dist/index.js:908:14)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)"
          }
        },
        {
          "id": "1694769220412",
          "message": "clean-vm",
          "start": 1694769220412,
          "status": "success",
          "end": 1694769220417,
          "result": {
            "merge": false
          }
        }
      ],
      "end": 1694769220422,
      "result": {
        "code": "NO_HOSTS_AVAILABLE",
        "params": [],
        "task": {
          "uuid": "15664390-4605-717d-d394-4f4ca8c0005b",
          "name_label": "Async.VM.snapshot",
          "name_description": "",
          "allowed_operations": [],
          "current_operations": {},
          "created": "20230915T09:13:40Z",
          "finished": "20230915T09:13:40Z",
          "status": "failure",
          "resident_on": "OpaqueRef:b71238e8-bce1-4a59-b9be-870e2de57558",
          "progress": 1,
          "type": "<none/>",
          "result": "",
          "error_info": [
            "NO_HOSTS_AVAILABLE"
          ],
          "other_config": {},
          "subtask_of": "OpaqueRef:NULL",
          "subtasks": [],
          "backtrace": "(((process xapi)(filename ocaml/xapi/xapi_vm_helpers.ml)(line 788))((process xapi)(filename ocaml/xapi/message_forwarding.ml)(line 1240))((process xapi)(filename lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xapi)(filename ocaml/xapi/rbac.ml)(line 231))((process xapi)(filename ocaml/xapi/server_helpers.ml)(line 103)))"
        },
        "message": "NO_HOSTS_AVAILABLE()",
        "name": "XapiError",
        "stack": "XapiError: NO_HOSTS_AVAILABLE()\n    at XapiError.wrap (/usr/local/lib/node_modules/xo-server/node_modules/xen-api/dist/_XapiError.js:21:12)\n    at _default (/usr/local/lib/node_modules/xo-server/node_modules/xen-api/dist/_getTaskResult.js:18:38)\n    at Xapi._addRecordToCache (/usr/local/lib/node_modules/xo-server/node_modules/xen-api/dist/index.js:752:51)\n    at /usr/local/lib/node_modules/xo-server/node_modules/xen-api/dist/index.js:785:14\n    at Array.forEach (<anonymous>)\n    at Xapi._processEvents (/usr/local/lib/node_modules/xo-server/node_modules/xen-api/dist/index.js:773:12)\n    at Xapi._watchEvents (/usr/local/lib/node_modules/xo-server/node_modules/xen-api/dist/index.js:908:14)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)"
      }
    }
  ],
  "end": 1694769220423
}

It seems that some of the VM's have now finished backing up, after forcing them. One of them keeps failing, hence the above error message.

Hello All,

Backups have been running quite happily for months, and now they are failing with NO_HOSTS_AVAILABLE. I'm not sure how to diagnose this.

Can someone point me in the direction of the logs, troubleshooting, what this actually means (as it seems to be a generic message) . Please bear in mind that I am a newb at Opensource Linux flavour OS' so be gentle with your assumptions

For info, I'm running a Dell R740XD with a TrueNAS Scale Z2 configuration. I have XCP-NG setup on a another Dell server R7515 and a standard licence (so no deltas backups). The backups are sent to the TrueNAS box at about 1TB 3 times a week. There is a snapshot once a week on the TrueNAS that has a retention of 2 weeks. I have auto delete turned on in the backup settings in XO.

Assuming I've done everything correctly, which I should be the case as it has been running fine for months, I can't see what the issue is.

I'm one version behind on the XO and up to date on the TrusNAS.

Regards

Ryan