Categories

  • All news regarding Xen and XCP-ng ecosystem

    145 Topics
    5k Posts
    semarieS
    @andersonalipio I would be interested to get some elements from your installation. your /var/log/sdn-controller-plugin.log file (on the host) in order to check the parameter passed by XO. output of xe network-param-list uuid=$UUID (for the network concerned) or xe network-list params=all (if uuid is unknown) output of xe pool-list params=other-config (for xo:sdn-controller:* elements) output of xe vif-list params=uuid,network-uuid,other-config (for xo:sdn-controller:* elements) Feel free to share it privately via PM if you prefer, possibly using https://paste.vates.tech/ . Cc @Team-XO-Backend too (as it could be from XO side)

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    M
    @Danp Thanks for that command, I had a similar command I found but it didn't display the timestamp fully so I couldn't pinpoint the time of the message, but I had a feeling this was there the issue was. [Fri Aug 7 16:26:44 2026] CIFS VFS: Server 192.168.x.x has not responded in 120 seconds. Reconnecting... Lots of these types of messages since yesterday. And df -h does hang as that's something I was testing yesterday when debugging to see if some disk had got full that I hadn't spotted. There has definitely been a few network disconnects over the past 24 hours as I was testing various things which requires a bit of fiddling with the cables and jumping between networks, and it's quite possible that this happened during the backup window but I can't recall for sure. The Storage Repositories are all reporting as working correctly in XO, XOA, XCP-ng Centre. What's the next steps to fix this? I assume there is a way without deleting the Storage Repository in either XO/XOA/XCP-ng Centre and re-attaching it?

  • All Xen Orchestra related questions/reports

    3k Topics
    29k Posts
    olivierlambertO
    I have a theory that I'd like you to test on a specific branch. It might be an Undici bug, but I'm far from being sure. You need Node >=22.19 to make it work. Switch to the branch named fix_undici_paused_parser_crash, build it and try again.

  • Our hyperconverged storage solution

    50 Topics
    796 Posts
    olivierlambertO
    Great, thanks for the feedback!

  • Non-English speakers

    37 Topics
    131 Posts
    AtaxyaNetworkA
    @jeremie1977 Ah, oui effectivement je n'ai pas testé avec plusieurs disques ! Et j'ai du typo dans la doc, je vais faire une PR pour modifier Je pense que c'est du a la façon d'insérer les disques et les DVD coté XCP-ng. Je vais investiguer !