I noticed my backup report was missing from my inbox, when i look into XOA the plugin is disabled.

When i try to enable it (with the old settings):
Log: strict mode: unknown keyword: "enumNames"

I tried to delete configuration but end up with the same result after i re-entered all credentials.

I just rebuild from source, still the same.

@olivierlambert after fiddeling around with almost every advice including dpkg-reconfigure grub-pc and to re-enable OS Proper (which aparently was disabled between 20.04 and 22.04) the one thing that worked for me was to purge grub* and reinstall it.

So i still have no idear what was going on, but i have my VM booting now on 22.04
Thanks for all the idears.

As this is just a test restore of my live system i have a snapshot pre-release upgrade. Can i do something else besides using grub-install and update-grub ? I have found this while looking for the error: https://askubuntu.com/questions/1404066/executing-grub2-command-nativedisk-before-boot-for-huge-disks

But to me its unclear why its should be necessary to mess with the disk module all of a sudden.

I converted to PVHVM after using grub-install /dev/xvda successfully on Ubuntu 20.04 LTS and it boots just fine.

Now if i do-release-upgrade to 22.04 LTS the VM hangs on GRUB "grub_disk_native_sectors".
Am i missing something ?

I am not sure why exactly, probably because the inital Install is quite old, i think its coming from 14.04. or 16. I will try to install grub on xvda and convert it. I was not aware that PV would become "suddenly" an issue

@stormi Yes its a PV VM

Coming from 20.04 LTS i updated my VM to 22.04 LTS and now i cant start it anymore:

vm.start
{
  "id": "9a540088-556f-30ba-434f-317697ca6532",
  "bypassMacAddressesCheck": false,
  "force": false
}
{
  "code": "INTERNAL_ERROR",
  "params": [
    "xenopsd internal error: (Failure
  \"Error from xenguesthelper: xenguest: xc_dom_parse_image: [2] panic: xc_dom_core.c:693: xc_dom_find_loader: no loader found\")"
  ],
  "call": {
    "method": "VM.start",
    "params": [
      "OpaqueRef:c817057a-3994-4447-8ed1-8322610029c9",
      false,
      false
    ]
  },
  "message": "INTERNAL_ERROR(xenopsd internal error: (Failure
  \"Error from xenguesthelper: xenguest: xc_dom_parse_image: [2] panic: xc_dom_core.c:693: xc_dom_find_loader: no loader found\"))",
  "name": "XapiError",
  "stack": "XapiError: INTERNAL_ERROR(xenopsd internal error: (Failure
  \"Error from xenguesthelper: xenguest: xc_dom_parse_image: [2] panic: xc_dom_core.c:693: xc_dom_find_loader: no loader found\"))
    at Function.wrap (/opt/xen-orchestra/packages/xen-api/src/_XapiError.js:16:12)
    at /opt/xen-orchestra/packages/xen-api/src/transports/json-rpc.js:35:21
    at runNextTicks (node:internal/process/task_queues:60:5)
    at processImmediate (node:internal/timers:447:9)
    at process.callbackTrampoline (node:internal/async_hooks:130:17)"
}

Maybe because this VM was created as 18.04 some years ago? How can i fix that

@planedrop are you using LVM for that or how are u doing that? I never bothered with the problem because i dont have enough local space for 8TB disk snapshots anyways.

Thanks for the heads up. A [NOSNAP] Feature sounds like a good idea though

@olivierlambert maybe i missunderstood things, the RAW Disk from my XO VM is the 7TB data disk "[NOBAK] xoa_backup_hdd".
The system disk is "xoa_sda" is not RAW.

So i thought excluding the disk with "[NOBAK]" would make me able to snapshot the VM (system disk). So whenever you have attached a RAW device makes you unable to snapshot the VM.

Detaching it, taking a snapshot and reattaching it would work however?

@olivierlambert Okay but obviously i can create snapshots on the RAW SR (here OPensense in the screenshot above). So this is a should but bould sometiomes does work situation ?-)