Team - XO Backend group | XCP-ng and XO forum

Melissa FR

@jacob.becker Hi Jacob, I made a fix and it should be available on the next release

pierrebrunet

@Andrew This branch is now merged, thank you for your feedback!

pierrebrunet

@jr-m4 Hi,
We have found this issue in another thread, it is now merged

pierrebrunet

@manilx @andrew @abudef @robertblissitt
Here is the branch we are working on: https://github.com/vatesfr/xen-orchestra/tree/fix_alias_vhd

It should fix the issue, in case you have time to test it

pierrebrunet

@Andrew Hi,
I am on it, thank you for the report!

pierrebrunet

@abudef Hi,
Do you think this doc can help you?

Link to doc

I think it needs some improvements, feel free to enhance it if you feel it is necessary!

pierrebrunet

@JB @christopher-petzel Thanks for your patience! We are glad it works well!

florent

@jr-m4 you can export the heap memory of the nodeJS process by doing kill -SIGUSER2 <xoserverpid>

onte that this will increase a lot the memory consumed by the xo process even when its done exporting the memory . This will help us know what xo is doing at the moment

florent

@acebmxer we are far more explicit on the real usage of NBD, paing the way to mark a failed NBD connexion as an error in a few month

also working on a diagnostic tool to be more efficient on the checks

thank you all for your time

florent

@probain the first checkc to do are network one :

is there a default backup network on he pool ? if yes the xo will only look at this network

check if :

the xo can access network(s) with nbd enabled
the host have an ip on those networks
are you on ipv4 or v6 ?
xo can access the ip of the host on the nbd newtork

Team - XO Backend

Posts

Member List