Categories

  • All news regarding Xen and XCP-ng ecosystem

    143 Topics
    4k Posts
    P
    @dthenot said: @probain Hello, It's likely linked to the List index out of range bug. That bug was linked to the SR scan failing to introduce CBT_metatadata VDI in the XAPI database, could you try to launch a xe sr-scan uuid=<SR UUID> and try again to disable CBT? If it does not work, could you share the /var/log/SMlog of around the time you are trying to disable CBT? I've sent you a DM for sharing the logs.. Unfortunately I "solved" the issue by deleting all snapshots related to each VM. Including CBT ones. That did make it so I could toggle CBT on the VDIs again. But I've collected the logs for you. This also seems like a good time to raise my suggestion to have somewhere at vates where we could upload details in a similar way to how TrueNAS does it. Suggested here: https://feedback.vates.tech/posts/69/suggesting-to-add-a-debug-file-option
  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    TeddyAstieT
    i2c error seems related to (I guess) a RGB controller that is presumably controlled by something else (or maybe not usable/non plugged). But it's harmless unless you are looking to configure RGB (but I don't think you want to do that anyway). EFI_MEMMAP warning is probably because Dom0 doesn't see UEFI mappings, as it relies on a different method to do UEFI calls. This is expected and this warning doesn't indicate a problem. The latest error is likely related to the first one. what I will miss /won't be able to do vs a user that has not these messages? (otherwise, why they would be raised) Nothing meaningful. if these messages /failures have an impact on the time during which the machine is booting? (it seems the load process is hanging for about a minute) No. if these messages /failures are officially documented somewhere? For the EFI_MEMMAP, XenServer has a article on it stating the same as me : https://support.citrix.com/external/article/CTX331542/citrix-hypervisor-82-efi-efimemmap-is-n.html how can I resolve these failures, because failures are failures... even if "one should not worry about them"? You may be able to hide it, like by blacklisting i2c and such, but TBF it's not worth the time.
  • 3k Topics
    28k Posts
    acebmxerA
    @florent said: @acebmxer back to work thank you for yor patience and help on this. I feel that it's not the same issue , with abrupt increase W will try our best to also fix this one Yes i replied to ticket also.... Yes you can do what is needed to XOA. Just looked at memory and it dropped.... [image: 1779875710969-screenshot_20260527_055458.png]
  • 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.
  • 35 Topics
    113 Posts
    olivierlambertO
    Ah excellente nouvelle Je passe le sujet en résolu !