Categories

  • All news regarding Xen and XCP-ng ecosystem

    143 Topics
    4k Posts
    bogikornelB
    @pkgw I tested it with a cluster size of 2 megabytes. I got similar results to those with the default size.
  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    poddingueP
    From what I understand, when XCP-ng reverts to a snapshot it restores the full VM state from that point (metadata included, not just the disk contents) so the creation date field would get rolled back along with everything else; that might be why it now matches the snapshot timestamp rather than the original. I might be wrong about the internals though. It's a bit confusing if you were relying on that field to track VM history, and I don't think https://docs.xen-orchestra.com/xo5/manage_infrastructure#snapshot-management covers this explicitly. Might be worth a mention to @Team-Documentation-Knowledge-Management; it's the kind of thing that catches people off guard because nothing warns you upfront that metadata rolls back too. My $0.02.
  • 3k Topics
    28k Posts
    A
    @Pilow @acebmxer Thanx for your replies. And sorry, i havent seen your first reply between my last posts with the link to your existing Thread. So, i think this is some kind of a bigger thing. Will handle with care, but i have to leave for today. Maybe i have time to test the snapshot and revert workarounds on the weekend. But these are all production VMs. Have to coordinate. I have 2 NFS-SRs in the Pool. Will try to migrate VMs from one to the other and see if this helps. Kind Regards and thx again Alex
  • Our hyperconverged storage solution

    46 Topics
    739 Posts
    dthenotD
    Hello again, The updates have been made available and RPU with xostor should be safe to run https://xcp-ng.org/blog/2026/05/07/may-2026-updates-2-for-xcp-ng-8-3-lts/
  • 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.