Trying to enable v2v and difficulty adding nbdinfo on xo 6

[edsilber]

Hoping that other people are having the same issue
Updated one of my test environments to XO6. I wet to test the V2v process and am stuck at the first step on adding nbdinfo.

I don't remember my exact sequence in Events. But in troubleshooting I worked manually installing libnbd.
That at least gave me results when I used the web interface that my version of nddingo was 1.6.1 when It expected 1.23.4
Web searches recommended adding a backport repo. But I thought that generally speaking XOA environment is supposed to be mostly an appliance and we shouldn't be messing with the underlying operating system.

Is anyone else seeing something similar?
I'm on Current version: 6.2.2 - XOA build: 20240311

[acebmxer]

@edsilber

This is from a fresh install of XO from sources...

this should have walked you through the process to import from vmware.

[edsilber]

@acebmxer Sadly the appliance install attempt fails.

Looking at logs there's a broken dependency somewhere.
I just wanted to know if other people are seeing the same thing in the appliance or if it's something in my environment that needs to be repaired.

{
"id": "0mmwhu52h",
"properties": {
"method": "esxi.installNbdInfoFromSource",
"params": {},
"name": "API call: esxi.installNbdInfoFromSource",
"userId": "e36282a5-4332-4681-8709-93e423768f93",
"type": "api.call"
},
"start": 1773865698857,
"status": "failure",
"updatedAt": 1773865699165,
"tasks": [
{
"id": "bot33xexbad",
"properties": {
"name": "Compile and installl nbdinfo"
},
"start": 1773865698857,
"status": "failure",
"tasks": [
{
"id": "lvl19oyl51n",
"properties": {
"name": "create directory"
},
"start": 1773865698857,
"status": "success",
"end": 1773865698858,
"result": "/tmp/xo-server6dcLvS"
},
{
"id": "exgxd1t73fr",
"properties": {
"name": "check if nbdinfo is already connected"
},
"start": 1773865698858,
"status": "success",
"end": 1773865698870
},
{
"id": "4drglc7aky5",
"properties": {
"name": "check if user is root"
},
"start": 1773865698870,
"status": "success",
"end": 1773865698880
},
{
"id": "qzlskxwzsm",
"properties": {
"name": "check if os is debian based"
},
"start": 1773865698880,
"status": "success",
"end": 1773865698891
},
{
"id": "rgjstdhd95",
"properties": {
"name": "installing dependencies"
},
"start": 1773865698891,
"status": "failure",
"end": 1773865699165,
"result": {
"code": 100,
"killed": false,
"signal": null,
"cmd": "apt-get install -y git dh-autoreconf pkg-config make libxml2-dev ocaml libc-bin",
"message": "Command failed: apt-get install -y git dh-autoreconf pkg-config make libxml2-dev ocaml libc-bin\nE: Unable to correct problems, you have held broken packages.\n",
"name": "Error",
"stack": "Error: Command failed: apt-get install -y git dh-autoreconf pkg-config make libxml2-dev ocaml libc-bin\nE: Unable to correct problems, you have held broken packages.\n\n at genericNodeError (node:internal/errors:984:15)\n at wrappedFn (node:internal/errors:538:14)\n at ChildProcess.exithandler (node:child_process:422:12)\n at ChildProcess.emit (node:events:518:28)\n at ChildProcess.patchedEmit [as emit] (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/configure.js:52:17)\n at maybeClose (node:internal/child_process:1104:16)\n at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)\n at Process.callbackTrampoline (node:internal/async_hooks:130:17)"
}
}
],
"infos": [
{
"message": "temp directory is /tmp/xo-server6dcLvS"
}
],
"end": 1773865699165,
"result": {
"code": 100,
"killed": false,
"signal": null,
"cmd": "apt-get install -y git dh-autoreconf pkg-config make libxml2-dev ocaml libc-bin",
"message": "Command failed: apt-get install -y git dh-autoreconf pkg-config make libxml2-dev ocaml libc-bin\nE: Unable to correct problems, you have held broken packages.\n",
"name": "Error",
"stack": "Error: Command failed: apt-get install -y git dh-autoreconf pkg-config make libxml2-dev ocaml libc-bin\nE: Unable to correct problems, you have held broken packages.\n\n at genericNodeError (node:internal/errors:984:15)\n at wrappedFn (node:internal/errors:538:14)\n at ChildProcess.exithandler (node:child_process:422:12)\n at ChildProcess.emit (node:events:518:28)\n at ChildProcess.patchedEmit [as emit] (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/configure.js:52:17)\n at maybeClose (node:internal/child_process:1104:16)\n at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)\n at Process.callbackTrampoline (node:internal/async_hooks:130:17)"
}
}
],
"end": 1773865699165,
"result": {
"code": 100,
"killed": false,
"signal": null,
"cmd": "apt-get install -y git dh-autoreconf pkg-config make libxml2-dev ocaml libc-bin",
"message": "Command failed: apt-get install -y git dh-autoreconf pkg-config make libxml2-dev ocaml libc-bin\nE: Unable to correct problems, you have held broken packages.\n",
"name": "Error",
"stack": "Error: Command failed: apt-get install -y git dh-autoreconf pkg-config make libxml2-dev ocaml libc-bin\nE: Unable to correct problems, you have held broken packages.\n\n at genericNodeError (node:internal/errors:984:15)\n at wrappedFn (node:internal/errors:538:14)\n at ChildProcess.exithandler (node:child_process:422:12)\n at ChildProcess.emit (node:events:518:28)\n at ChildProcess.patchedEmit [as emit] (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/configure.js:52:17)\n at maybeClose (node:internal/child_process:1104:16)\n at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)\n at Process.callbackTrampoline (node:internal/async_hooks:130:17)"

[acebmxer]

@edsilber

Yeah I am not sure. I havent seen heard anyone else having similar issues. I heard of other issues in regards to the actual migration but not the setup.

Now that you have logs posted maybe someone form Vates will chime in.