Categories

  • All news regarding Xen and XCP-ng ecosystem

    143 Topics
    4k Posts
    dthenotD
    @Andrew Hello, I'm also getting error on some VMs while trying to export a disk and also trying to even start some VMs from NFS (that were fine before). Is it still a problem? It might have multiple causes. If it's still an issue, could you share the logs: /var/log/{SMlog,xensource.log,daemon.log}. It contains information that could help us investigate. The VDI not detached cleanly means that the VDI still has a reference to the host it was running on before. It's might be caused by the xenopsd error earlier or maybe it's the cause. If you are sure no tapdisk are using the VDI, you can look at tap-ctl list output on each host. You can clean this reference with the script in /opt/xensource/sm/resetvdis.py single <VDI UUID>.

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    Y
    @yllar @mik @Pilow @marcvds Hello, we think we now understand better this issue. We think it's a Xen issue with regard to PCI devices on segment 0001 (which is your case) and not a dom0 driver issue. Could you give a try to this ISO installer please? Please note that this is a custom test ISO and it is therefore not officially supported, do not use it for production, it is just to confirm that it fixes your issue, we will release a supported ISO in the future (target date for now is June). unsupported test ISO for you to test: https://nextcloud.vates.tech/index.php/s/iHf8sqq39EqE683 Regards, Yann

  • All Xen Orchestra related questions/reports

    3k Topics
    28k Posts
    L
    @anthoineb in fix_records at line 105 you have is_a_snapshot for one case, and is-a-snapshot for an elif. Is the XML attribute formatted with dashes or underscores in the state.db? Or is it possible that records might exist with either format and this catches both potential cases? (I only have underscores in my /var/lib/xcp/state.db)

  • Our hyperconverged storage solution

    47 Topics
    745 Posts
    J
    @Mathieu-L linstor n l was included in my original post. All nodes were updated to May 2026 Security and Maintenance Updates for XCP-ng 8.3 LTS, all nodes were restarted. May 2026 Updates #2 for XCP-ng 8.3 LTS was released, and a couple days later I installed on all hosts. No host restarted. When xen04 was restarted, that is when this issue happened. I had used systemctl restart linstor-controller here (https://xcp-ng.org/forum/post/105309) to restart the controller.

  • Non-English speakers

    35 Topics
    113 Posts
    olivierlambertO
    Ah excellente nouvelle Je passe le sujet en résolu !