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
    J
    @TeddyAstie I think there's alot of interest in the Intel platform because of the lack of ridiculous licensing for virtualization features. The problem is that you need a pretty current 6.x kernel to use them and XCP-ng/XenServer is just stuck on a really aging kernel right now. As exposed in this thread, the PCIe pass-through isn't really working properly under XCP-ng. Even if pass-through worked, that's kinda lame because the real purpose would be to chop up the GPU into SR-IOV instances so multiple workloads could have a GPU. The Proxmox community is already rockin' and rollin' with this. I watched a video a couple of days ago where a B70 was chopped up into Qty.4, 8GB GPU's via SR-IOV and passed to clients. No ridiculous mega-$$$$ licensing. It just worked.

  • All Xen Orchestra related questions/reports

    3k Topics
    29k Posts
    christopher-petzelC
    @olivierlambert I feel like the cause of the timeout is what I posted here: https://xcp-ng.org/forum/post/107454 The incidents of the errors in syslog correspond by matching pool, date and time to the incidents of errors in XO backup. I've traced through several of these incidents in the syslog and matched them to the errors in the XO metadata backup and matched these to missing metadata backup files in the directory on the storage server (ex. 20260807T041000Z) which is created even if the backup fails. I would look in older logs to see if maybe this has been happening for a long time, possibly before an XO update now shows the error, but my syslog data only goes back 30 days. The XO metadata backup errors started over 30 days.

  • 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 !