XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    VM won't start with internal error

    Scheduled Pinned Locked Moved Xen Orchestra
    7 Posts 3 Posters 1.1k Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S Offline
      slevan
      last edited by olivierlambert

      VM after provisioning won't start with the following error:

      vm.start
      {
        "id": "efc26b66-a6be-2edf-d467-8b7a3f34877c",
        "bypassMacAddressesCheck": false,
        "force": false
      }
      {
        "code": "INTERNAL_ERROR",
        "params": [
          "xenopsd internal error: (Failure
        \"Error from xenguesthelper: xenguest: xc_dom_parse_image: [2] panic: xc_dom_boot.c:89: xc_dom_compat_check: guest typ\")"
        ],
        "call": {
          "method": "VM.start",
          "params": [
            "OpaqueRef:f2b1621a-ffdb-4c42-b4b6-d671a7050205",
            false,
            false
          ]
        },
        "message": "INTERNAL_ERROR(xenopsd internal error: (Failure
        \"Error from xenguesthelper: xenguest: xc_dom_parse_image: [2] panic: xc_dom_boot.c:89: xc_dom_compat_check: guest typ\"))",
        "name": "XapiError",
        "stack": "XapiError: INTERNAL_ERROR(xenopsd internal error: (Failure
        \"Error from xenguesthelper: xenguest: xc_dom_parse_image: [2] panic: xc_dom_boot.c:89: xc_dom_compat_check: guest typ\"))
          at Function.wrap (/usr/local/lib/node_modules/xo-server/node_modules/xen-api/src/_XapiError.js:16:12)
          at /usr/local/lib/node_modules/xo-server/node_modules/xen-api/src/transports/json-rpc.js:37:27
          at AsyncResource.runInAsyncScope (node:async_hooks:203:9)
          at cb (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/util.js:355:42)
          at tryCatcher (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/util.js:16:23)
          at Promise._settlePromiseFromHandler (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/promise.js:547:31)
          at Promise._settlePromise (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/promise.js:604:18)
          at Promise._settlePromise0 (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/promise.js:649:10)
          at Promise._settlePromises (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/promise.js:729:18)
          at _drainQueueStep (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/async.js:93:12)
          at _drainQueue (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/async.js:86:9)
          at Async._drainQueues (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/async.js:102:5)
          at Immediate.Async.drainQueues [as _onImmediate] (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/async.js:15:14)
          at processImmediate (node:internal/timers:471:21)
          at process.callbackTrampoline (node:internal/async_hooks:130:17)"
      }
      
      1 Reply Last reply Reply Quote 0
      • olivierlambertO Offline
        olivierlambert Vates 🪐 Co-Founder CEO
        last edited by

        Hi,

        We need more context if you need assistance.

        S 1 Reply Last reply Reply Quote 0
        • S Offline
          slevan @olivierlambert
          last edited by

          @olivierlambert

          A new VM was provisioned on the host and when I go to start it this is the error I get. it is a linux VM with Ubuntu 20.04. It is like it can't see the boot sector to boot the VM, but this is the only eror I get so I have no idea how to troubleshoot this.

          1 Reply Last reply Reply Quote 0
          • olivierlambertO Offline
            olivierlambert Vates 🪐 Co-Founder CEO
            last edited by

            It's better if you give a more explicit context. XCP-ng version for example, if patched and so on.

            S 1 Reply Last reply Reply Quote 0
            • S Offline
              slevan @olivierlambert
              last edited by

              @olivierlambert

              Latest version fully patched 8.2.

              1 Reply Last reply Reply Quote 0
              • olivierlambertO Offline
                olivierlambert Vates 🪐 Co-Founder CEO
                last edited by

                Can you try to boot it with xe vm-start uuid=<VM UUID> and report the error message?

                1 Reply Last reply Reply Quote 0
                • DanpD Online
                  Danp Pro Support Team
                  last edited by

                  What is your process for provisioning a VM? What template are you using?

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post