@CptHyper Yes, Only that card is working. I am using 6 of them in a pool and works great for about a year now. You will also need the driver for your Guest VM as well. Overall pretty easy to set this up once you find the driver!

@thenorthernlight I did not try that as yet, but i was able to do a host reboot and now the host doesn't recognize one of the cards. I have hunch the GPU or its riser card perhaps was not properly seated after the service. I will update again after reseating the risers and GPUS to see if that works. If not then I will try putting the old ones back in.

I also just checked the console for xoa and seems to have some memory issues. I am running this xoa with 6 vcpu and 8gb memory.

@Danp

Some more details about my setup/environment
Version i am running is xoa 7.77.2 and I am on the stable channel

xo-server 5.107.3

• node: 18.12.1
• npm: 8.19.2
• xen-orchestra-upload-ova: 0.1.4
• xo-server: 5.107.3
• xo-server-auth-github-enterprise: 0.2.2
• xo-server-auth-google-enterprise: 0.2.2
• xo-server-auth-ldap-enterprise: 0.10.6
• xo-server-auth-saml-enterprise: 0.10.1
• xo-server-backup-reports-enterprise: 0.17.2
• xo-server-netbox-enterprise: 0.3.5
• xo-server-telemetry: 0.5.0
• xo-server-transport-email-enterprise: 0.6.0
• xo-server-transport-icinga2-enterprise: 0.1.1
• xo-server-transport-nagios-enterprise: 1.0.0
• xo-server-transport-slack-enterprise: 0.0.0
• xo-server-transport-xmpp-enterprise: 0.1.1
• xo-server-usage-report-enterprise: 0.10.2
• xo-server-xoa: 0.17.1
• xo-web-enterprise: 5.108.0
• xoa-cli: 0.33.0
• xoa-updater: 0.45.1

Details of the Problematic Backup Job

• Backing up 13 VMS running in in the same server pool as xoa
• Daily Backup job set for 11:15 PM
• Retention = 30
• backup to an NFS Remote

I have other delta backup jobs for other vms in this environment which seem to not fail. I do not think the time has much to do with this issue because it seems to fail if i disable all other backup jobs and keep only this one enabled. I started to get these errors but I don't really know what the error means in this context.

Thanks

I am getting some strange errors with a backup job which i had running for few months with little issue..

Any ideas what can be the issue.

Unable to get the true granularity: 60

{
  "id": "e03a39e3-9546-957d-6e01-4ab40a9cca72"
}
{
  "message": "Unable to get the true granularity: 60",
  "name": "FaultyGranularity",
  "stack": "FaultyGranularity: Unable to get the true granularity: 60
    at XapiStats._getAndUpdateStats (file:///usr/local/lib/node_modules/xo-server/src/xapi-stats.mjs:353:13)"
}

worker exited with code null

backupNg.runJob
{
  "id": "f375c1ca-e526-4b0d-b6dd-61eeb6a7498b",
  "schedule": "edc353a4-8237-4a16-aea4-d3906fb07051",
  "vms": [
    "8a698e9e-abe8-168d-eefc-12cfbf62ff1b",
    "c0959e5a-3e1f-b159-297d-b1e9e3389abe",
    "a43e7f1c-a96e-b08e-8695-c0f18b4dba2d",
    "1fa82ed0-1e50-eb6b-97d3-e71725312c54"
  ]
}
{
  "message": "worker exited with code null",
  "name": "Error",
  "stack": "Error: worker exited with code null
    at ChildProcess.<anonymous> (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/backups/runBackupWorker.js:15:38)
    at ChildProcess.emit (node:events:513:28)
    at ChildProcess.patchedEmit [as emit] (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/configure.js:135:17)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
    at Process.callbackTrampoline (node:internal/async_hooks:130:17)"
}

Where does the VM creation date that XOA shows come from? This particular machine is an old 2012 windows server which was made many years ago. Definitely was not created in July this year.

@CptHyper Yes, Only that card is working. I am using 6 of them in a pool and works great for about a year now. You will also need the driver for your Guest VM as well. Overall pretty easy to set this up once you find the driver!

@julien-f It is likely a broken xva. I did interrupt those as they were exporting, however I was a bit confused as to why it was checked by a different backup task. In other words this screen clip is from a delta backup, not a xva export.

I was more expecting it to show up on the XVA export backup task.

What exactly does this mean? (XVA MIGHT BE BROKEN) This is showing up in a Delta Backup Job results. I also have a seperate backup job for an XVA but im not sure what this mean for it to show up in the delta backup result.

I have a windows server 2012 guest which I have been dragging along. For some reason it does not seem to boot correctly. It starts up into recovery mode and is able to run its disk repair, but when it tries to get to windows, the vm keeps powering off.

I decided to try an boot an ubuntu iso to see if i can mount the disk and run a file system check that way. The boot hangs at the screen below for a few minutes

Once I am in however the vm's disk does not appear. I have done this before to repair other linux vms successfully, but for some reason I cannot get this vm to boot correctly.

@thenorthernlight So I was able to open up the host and remove all PCIE cards and riser cards. At a glace everything appears to have made proper contact, however after reseating the cards and booting again and sure enough it appears to work again. I did not have to run any testing in the bios although the server does do a pre boot inventory check each time for changes. Host is HPE Proliant DL380 G9.

@thenorthernlight I did not try that as yet, but i was able to do a host reboot and now the host doesn't recognize one of the cards. I have hunch the GPU or its riser card perhaps was not properly seated after the service. I will update again after reseating the risers and GPUS to see if that works. If not then I will try putting the old ones back in.