Categories

  • All news regarding Xen and XCP-ng ecosystem

    143 Topics
    4k Posts
    D
    Hello all, XenClean/XenBootFix 9.1.152 have been released. This release fixes VSA-2026-012 (DLL sideloading vulnerability in XenClean and XenBootFix). If your VM is running 9.1.146, you don't need to update. You just need to replace any XenClean and XenBootFix files you downloaded. The package\XenClean and package\XenBootFix directories contain fixed versions of the aforementioned tools. package\XenTools-x64.msi has not changed from version 9.1.146, and is only provided as a convenience. The installation MSI does not include the fixed XenBootFix. You must use the one from package\XenBootFix or download the tool directly from GitHub! The next release of the XCP-ng Windows Guest Tools will contain a fixed version of XenBootFix. Get it here: https://github.com/xcp-ng/win-pv-drivers/releases
  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    D
    @vlamincktr said: @acebmxer I may just need to re-evaluate our backup strategy and adjust it so there is more time for the backups, I could also just run the daily delta's, the main issue is the weekly fulls that I run as a precaution, I'm always paranoid about something happening with the daily delta chain and having an unusable backup so i also pull dedicated weekly full backups which take a lot of time to run. I've also considered running the full backups at different days to spread them out more, sounds like one of those is my best option rather than adding more cost/complexity. I would absolutely change this backup plan, to running monthly full backups (weekly full backups are overkill for most). The backup mechanism in XO has improved a ton (since launch). Without more detail, types of VMs, workloads etc it's really difficult for anyone to offer a perfect answer, but most people here would likely agree that weekly full's aren't a benefit here. Changing the window on your backups is also an option as you mentioned, but that is only shifting when the work is being performed, not the type of work performed. If you have a 1TB server and you're backing that up daily with delta's and weekly with full backups you're backing up something like 1300 GB every week (of course this depends on your delta data change).
  • 3k Topics
    28k Posts
    D
    @florent said: ping @julienxovates I think we can change thie behavior ( accepting a xo-server start even if a zombie process is still running) Hello, Today I tried to update again with the same steps and a reboot and it still shows out of date. [image: 1778007914995-887782ff-6408-4788-a761-4d13d6b0ee95-image-resized.jpeg]
  • Our hyperconverged storage solution

    45 Topics
    732 Posts
    DAYELAD
    Hello, I’m experiencing an issue on an XCP-ng cluster using XOSTOR. Environment: 3-node XCP-ng cluster XOSTOR distributed storage (2x2Tob nvme on each host) XOA for management Management network 1Gb/s Storage Network 10Gb/s MTU 1500 everywhere (no jumbo frames) So during VM migrations, creation, destroy XOA loses connection to my host pool, VMs keep running normally Hosts remain reachable (SSH / HTTPS / ping OK), Connection comes back after some time 30s to 1min. Observations: No significant CPU or RAM saturation No obvious disk latency issues (iostat looks normal) No errors reported on NICs xapi process remains active (no crash or freeze) The problem is intermittent and seems random. i've monitored nic with iftop and i see no bandwith bottleneck et and can see that XOSTOR is using 10gb network only. Has anyone experienced similar behavior with XOSTOR? And how to Fix it ? Thanks in advance for your help.
  • 34 Topics
    102 Posts
    B
    La remarque a été intégrée dans l'article: https://www.myprivatelab.tech/xcp_lab_v2_ha#perte-master Merci encore pour le retour.