Posts made by jedimarcus

Upgrade to latest solved the issue. But funnily enough, after the downgrade it's showing correctly on 5.75.0 too.

#weird #close

I know of Warhammer 40k, but I don't know who did the snapshot in 55k:

In XCP-ng Center, they look ok.

XOA is 5.75.0 #stable

Known issue?

@reinvtv It's a little bit of wasted resourced, but just have a few Xen Orchestra's running... just for this task.

IT is the job where you have to find a workaround for problems you can't fix yourself.

@wade_solarch Short answer: try to avoid that.

Back in the old XenServer days, you had to manually change the cpu feature flags so it would work at all.

https://xcp-ng.org/docs/requirements.html#pool-requirements
This confirms that you can't mix Intel & AMD in a pool

https://xcp-ng.org/docs/requirements.html#pool-requirements
This explains Heterogeneous pools a little

I updated XOA to 5.66 2 days ago and it messed up with my delta backups.

Instead of 2 hours it took 20 hours yesterday and same thing again today.

I don't see any notes in the changelogs that would explain this.

Anyone else?

@pdonias I did an update to Netbox 2.11.12 and it works now, so I don't need to tamper with my XOA.

@pdonias 2.9.9
Might that be too old?

...

    "body": {
      "name": "[TMP] Xen Orchestra Netbox plugin test - klcecdwwuqj",
      "slug": "xo-test-klcecdwwuqj",
      "description": "This type has been created by Xen Orchestra's Netbox plugin test. If it hasn't been properly deleted, you may delete it manually."
    },
    "error": {
      "name": [
        "Ensure this field has no more than 50 characters."
      ]
    }

Whenever I "Test Plugin" my Netbox config I get the following error, even after setting up valid SSL Cert (#letsencrypt)

For some odd reason, the sync did go through though... once at least... I see my VMs in Netbox (no IP adresses though).

Any easy way to debug this on XOA end? I don't see logs on Netbox (at all) to debug there either, that's why I'm asking here.

PS: Netbox sounds like a great tool but it's overwhelming... I hope that filling it up with lots of data from XOA will help as a big first step instead of starting from scratch. Netbox Plugin +1

\o/

You don't happen to have an example handy? Even if it's not PHP.

Either the libraries I'm trying are or my brain is too much used to REST to get the JSON RPC working.

Before wasting too much time trying to get this working, can someone just confirm that it should work? Can I connect to xo-server with JsonRPC using PHP? Or are there some websocket reasons why this can't work?

On the cli of your XCP-ng host, what does the following command output:

showmount -e 192.168.1.1

I can confirm.

• Template from Hub
• New SSH key selection in User/Profile screen of XOA
• Create new VM with SSH key selected
• Login over ssh with

ssh debian@<ip>

• Success

@cg You are aware that XOA is just a VM that you can reboot.

As a matter of fact, I did it this morning (even halted it for maintenance).

Of course it's weird since you are "killing" the interface you are currently using.

@nodesocket What tool did you use to export? cli? XOA? XCP-ng Center?
And what tool do you want to use to import?

TGIF...

you need to register to XOA, not to XCP-ng

Error message could be more helpful though.

@bahman have a look here.
https://github.com/vatesfr/xen-orchestra/tree/master/packages/xo-cli

If you want to automate absolutely everything, you need to get a cloud-init ubuntu template up and running and pass cloud-init parameters to it.

Try reinstalling and installing xo-cli again.

Got version v0.11.1

Trying to register I get the following error:

[16:12 02] xoa:jedi$ xo-cli --register http://192.168.0.13 root
Password: ***********
(node:44320) UnhandledPromiseRejectionWarning: TypeError: Converting circular structure to JSON
    --> starting at object with constructor 'ClientRequest'
    |     property 'socket' -> object with constructor 'Socket'
    --- property '_httpMessage' closes the circle
    at JSON.stringify (<anonymous>)
    at prettyFormat (/usr/local/lib/node_modules/xo-cli/node_modules/exec-promise/index.js:32:15)
    at onError (/usr/local/lib/node_modules/xo-cli/node_modules/exec-promise/index.js:48:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:44320) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:44320) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[16:12 02] xoa:jedi$

I'm trying to do this on my XOA appliance.
npm 6.14.11
node 14.16.0

Any help is appreciated.

@ivan there isn't a licence restriction on the XOA end, can you specify exactly what runs on your hosts?

XenServer 7.2 might have licence restrictions.
Destination host you didn't specify if XCP-ng or Citrix Hypervisor?