Categories

  • All news regarding Xen and XCP-ng ecosystem

    143 Topics
    4k Posts
    A
    abudef said: I was thinking more of updating the entire set of the agent and drivers, similar to how XenServer VM Tools for Windows have it implemented. Using a scheduled job, they regularly check whether an update is available, and if so, they carry out the update of both the agent and the drivers themselves. Hi, how’s it looking regarding a possible automatic update?
  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    maximsachsM
    Unfortunately, we will have a bit of delay from our side. We are only able to get sufficient downtime for testing with the servers in the first half of August. So I will have to wait until then to try out the fixes.
  • 3k Topics
    28k Posts
    P
    @jvanabra Hi, From the first log file you uploaded, I see there is a timeout issue during the transfer. It is this part which triggers a bug (thank you for highlighting that!) where an alias is missing because the directory itself is not present. There may be two causes to this: either your SR is under a lot of pressure and makes some timeouts, or there is a firewall or network config making timeouts after 72s
  • 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 !