CBT Error when powering on VM

rustylh

Does this help?

rustylh

That last power on attempt log

{
  "id": "0mfciiw3i",
  "properties": {
    "method": "vm.start",
    "params": {
      "id": "14d739cc-ac03-591f-f9e2-0206000c4fc4",
      "bypassMacAddressesCheck": false,
      "force": false
    },
    "name": "API call: vm.start",
    "userId": "6b37221b-22b6-452b-ba2a-7bd46fc924a9",
    "type": "api.call"
  },
  "start": 1757420053758,
  "status": "failure",
  "updatedAt": 1757420054029,
  "end": 1757420054029,
  "result": {
    "code": "INTERNAL_ERROR",
    "params": [
      "Not_found"
    ],
    "call": {
      "duration": 267,
      "method": "VM.start",
      "params": [
        "* session id *",
        "OpaqueRef:570f1cc5-9197-4bd4-8fc3-f75f90e36e4b",
        false,
        false
      ]
    },
    "message": "INTERNAL_ERROR(Not_found)",
    "name": "XapiError",
    "stack": "XapiError: INTERNAL_ERROR(Not_found)\n    at Function.wrap (file:///usr/local/lib/node_modules/xo-server/node_modules/xen-api/_XapiError.mjs:16:12)\n    at file:///usr/local/lib/node_modules/xo-server/node_modules/xen-api/transports/json-rpc.mjs:38:21\n    at runNextTicks (node:internal/process/task_queues:60:5)\n    at processImmediate (node:internal/timers:454:9)\n    at process.callbackTrampoline (node:internal/async_hooks:130:17)"
  }

olivierlambert

@rustylh Can you try another kernel version or a safe mode if available in the Grub menu of your VM? It seems the OS cannot boot anymore, for whatever reason happened inside the VM.

rustylh

I tried the second Kernel. I can try safe from Grub. I am not familiar with that, but I will try.

rustylh

Same result

olivierlambert

To me, you have an issue inside your OS. You can try to mount the disk of this VM in another VM and try to check what's going on, maybe do a file system check or something.

rustylh

Ok, thank you for looking. Is there anything in my previous screen shots that sticks out? Something else I can try?

olivierlambert

I would check inside the OS that cannot boot anymore, running an fsck

That's what I would do

rustylh

Ok, this is weird. I just created a new VM with new name. It is booting and hung at the same message.
vdb vdb-5696: 19 xenbu_dev_prob on device/vdb/5696

Not sure what to think.

olivierlambert

That's an OS issue, as I said. You need to mount it in another VM as an extra drive, or use a LiveCD to explore the filesystem

rustylh

I understand. However, this is a bran new VM I just created with a new name.

AtaxyaNetwork

@rustylh How are you creating your VM ?

rustylh

Center. I'm trying to get away from that and go with XO

rustylh

Can I do everything in XOA Lite that I can in XCP-NG Center?

olivierlambert

It's hard to tell what's going on. So to avoid any environment issue, deploy quickly an XOA free, create a VM and see from there.

rustylh

Just passing this. I have created a new VM twice now. Once DNF updates are done and it reboots it boots to grub. I'm reinstalling now and will be updating grub before the reboot I guess.

olivierlambert

OK keep us posted. Which Alma version exactly? (so we can try to reproduce)

rustylh

I am still hoping for a miracle with the original VM. Why are there two disks shown if I select the VM in XOA and click attach disk. Image attached Disks Shown.png

rustylh

rustylh

AlmaLinux 8.10