Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue when migrating VM #3506

Closed
julien-f opened this issue Oct 9, 2018 · 9 comments
Closed

Issue when migrating VM #3506

julien-f opened this issue Oct 9, 2018 · 9 comments

Comments

@julien-f
Copy link
Member

julien-f commented Oct 9, 2018

Potential issue with vm.migrate:

vm.migrate
{
  "vm": "7f5adcd1-c474-0a57-cb97-08dd6bb1ba96",
  "mapVifsNetworks": {
    "e7f25a81-abea-2685-454b-36aeec5674b5": "b060aa40-0751-ea66-64b1-f971a7cc68c5"
  },
  "migrationNetwork": "db925e86-9c72-c4a4-e224-e769bb3dc726",
  "sr": "6612320a-f7fb-7d14-c8cb-ce65941bc53d",
  "targetHost": "d5be4114-d578-47c2-818a-d93a6d1b008d",
  "id": "7f5adcd1-c474-0a57-cb97-08dd6bb1ba96"
}
{
  "message": "HANDLE_INVALID(host, OpaqueRef:NULL)",
  "stack": "XapiError: HANDLE_INVALID(host, OpaqueRef:NULL)
    at wrapError (/usr/local/lib/node_modules/xo-server/node_modules/xen-api/src/index.js:112:9)
    at _call.catch.error (/usr/local/lib/node_modules/xo-server/node_modules/xen-api/src/index.js:1038:18)
    at run (/usr/local/lib/node_modules/xo-server-xoa/node_modules/core-js/modules/es6.promise.js:66:22)
    at /usr/local/lib/node_modules/xo-server-xoa/node_modules/core-js/modules/es6.promise.js:79:30
    at flush (/usr/local/lib/node_modules/xo-server-xoa/node_modules/core-js/modules/_microtask.js:18:9)
    at _combinedTickCallback (internal/process/next_tick.js:73:7)
    at process._tickCallback (internal/process/next_tick.js:104:9)",
  "code": "HANDLE_INVALID",
  "params": [
    "host",
    "OpaqueRef:NULL"
  ],
  "method": "VM.migrate_send"
}

Don't know how to reproduce, currently waiting for more info.

@etlweather
Copy link
Contributor

I'm getting this error at the moment. I'm attempting to migrate a VM that is running on XenServer 6.5 to XCP-ng 7.6. The VM is shutdown.

@julien-f
Copy link
Member Author

Is it this exact error, with OpaqueRef:NULL?

@PipeTenMatt
Copy link

PipeTenMatt commented May 8, 2019

I'm seeing this error too.

Xen 6.5 host to XCP-ng 7.6 host, the VM is shut down.

vm.migrate

{
  "vm": "0194b45d-d8c2-7916-dc52-804645f307fe",
  "mapVifsNetworks": {
    "6af79efc-68ac-6700-d11e-a4e1bdd9f6ad": "d4b39ff4-7749-e08f-4d91-e93e1cb00400"
  },
  "migrationNetwork": "32a4aaf8-9f25-e61b-d4b1-f0b9bad292eb",
  "sr": "44df89fe-2cd4-6fe2-d28a-30b077686883",
  "targetHost": "f12c980a-146d-499e-90db-03d2cf41163f"
}
{
  "code": "HANDLE_INVALID",
  "params": [
    "host",
    "OpaqueRef:NULL"
  ],
  "call": {
    "method": "VM.migrate_send",
    "params": [
      "OpaqueRef:ccdbd6ff-163e-4a30-5519-a82af7d506dc",
      {
        "SM": "http://10.0.103.31/services/SM?session_id=OpaqueRef:945c848b-66b0-4899-94b3-e92bb6519d06",
        "host": "OpaqueRef:04a8449f-b842-47e8-8843-863a22213f4a",
        "xenops": "http://10.0.103.31/services/xenops?session_id=OpaqueRef:945c848b-66b0-4899-94b3-e92bb6519d06",
        "session_id": "OpaqueRef:945c848b-66b0-4899-94b3-e92bb6519d06",
        "master": "http://10.0.103.31/"
      },
      true,
      {
        "OpaqueRef:2b431dd2-c2ac-9ddd-f3b3-ddab95eb54db": "OpaqueRef:5dbe98be-8490-4eac-94ae-42737c9f9a82"
      },
      {
        "OpaqueRef:559d0a2f-982a-dfbb-fc1e-b610173afd49": "OpaqueRef:385b2097-d6ed-4efa-b250-eab78f71fba5"
      },
      {
        "force": "true"
      }
    ]
  },
  "message": "HANDLE_INVALID(host, OpaqueRef:NULL)",
  "name": "XapiError",
  "stack": "XapiError: HANDLE_INVALID(host, OpaqueRef:NULL)
    at Function.wrap (/opt/xen-orchestra/packages/xen-api/src/_XapiError.js:16:11)
    at /opt/xen-orchestra/packages/xen-api/src/index.js:635:55
    at Generator.throw (<anonymous>)
    at asyncGeneratorStep (/opt/xen-orchestra/packages/xen-api/dist/index.js:58:103)
    at _throw (/opt/xen-orchestra/packages/xen-api/dist/index.js:60:291)
    at tryCatcher (/opt/xen-orchestra/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:512:31)
    at Promise._settlePromise (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:569:18)
    at Promise._settlePromise0 (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:614:10)
    at Promise._settlePromises (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:690:18)
    at _drainQueueStep (/opt/xen-orchestra/node_modules/bluebird/js/release/async.js:138:12)
    at _drainQueue (/opt/xen-orchestra/node_modules/bluebird/js/release/async.js:131:9)
    at Async._drainQueues (/opt/xen-orchestra/node_modules/bluebird/js/release/async.js:147:5)
    at Immediate.Async.drainQueues (/opt/xen-orchestra/node_modules/bluebird/js/release/async.js:17:14)
    at runCallback (timers.js:810:20)
    at tryOnImmediate (timers.js:768:5)
    at processImmediate [as _immediateCallback] (timers.js:745:5)"
}
```

@vmpr
Copy link

vmpr commented Jun 6, 2019

same problem in my case, migrate a shutdown vm from xenserver 6.5 to xcp-ng 7.6 - any ideas how to fix it?

@PipeTenMatt
Copy link

In the end I just used the Continuous Replication option within XO.

@Jarli01
Copy link
Contributor

Jarli01 commented Jun 6, 2019

In the end I just used the Continuous Replication option within XO.

That's not a migration though, at least not how migration is meant to work.

@PipeTenMatt
Copy link

Well no, but if a VM is offline, it doesn't matter how it's migrated over to another box right? :)

@Jarli01
Copy link
Contributor

Jarli01 commented Jun 6, 2019

Well no, but if a VM is offline, it doesn't matter how it's migrated over to another box right? :)

I suppose, but you're essentially restoring from backup at that point. Whereas a migration takes the working VM and moves it to another host.

@olivierlambert
Copy link
Member

Didn't see that in a while. Closing but if someone still have the issue, go ahead :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants