Categories

  • All news regarding Xen and XCP-ng ecosystem

    145 Topics
    5k Posts
    J
    Installed on 3xDell PowerEdge R350 in HA. And so far, I haven't noticed anything out of the ordinary.

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    Z
    Had what looks like a similar issue on a local EXT (file-based) SR, XCP-ng 8.3, sm-3.2.12-23.5. Sequence: snapshot of a running Windows VM → disk resized (60 → 75 GB) → snapshot deleted while running. The VM froze. SMlog showed the live leaf-coalesce failing on the parent resize, then reporting success anyway: Expanding COW image virt size for VDI <parent>: 60.000G -> 75.000G qemu-img resize <parent>.qcow2 80530636800 _doCoalesceLeaf: EXCEPTION util.CommandException, Operation not permitted *** finished leaf-coalesce successfully Leaf-coalesce failed on <leaf>, skipping Afterward the VM wouldn't start (SR_BACKEND_FAILURE_46, stale tapdisk), the GC kept failing with HANDLE_INVALID for the parent VDI, and qemu-img info on the parent showed corrupt: true. Windows wouldn't boot after cleanup, so I restored from a veeam backup and moved on. Hopefully the sm-3.2.12-25.1 fix covers this issue too.

  • All Xen Orchestra related questions/reports

    3k Topics
    29k Posts
    Z
    @poddingue said: Thanks for posting the fix. The same thing came up in an older thread, https://xcp-ng.org/forum/topic/9957, where disabling IPv6 also made xoa check go green. @HamiltonWDS explained a likely reason in https://xcp-ng.org/forum/post/87831: Node tries the addresses with a short timeout and can end up on the IPv6 one. Your curl -6 test helps a lot here, because it shows IPv6 doesn't connect at all on that network, so it's more than a slow path. Turning it off in XOA seems reasonable if you don't use IPv6 there; if you do, I'd guess the router side is where it really needs fixing, though I could be wrong (still haven't migrated to IPv6 myself ). Curious whether it sorts out the Cloud Backup too. XOA is using our management network where ipv6 is not needed and not enabled. Looks like our cloud backup finally ran for the first time in while too.[image: cloudbackup.jpg]

  • Our hyperconverged storage solution

    54 Topics
    824 Posts
    J
    @poddingue Turns out it is all secondary-to-secondary out of sync. So that makes it less intense, though if primary dies I wonder how it will resolve this, or if it will become split brained. Still unsure of how it happened, but the ones I manually cleaned up have not come back. Going to continue to manually clear them up. If it happens again I will have an alert setup to notify me, and I have all the xcp-ng logs and everything to be able to see what happened. If that happens I will post here with details and logs for the resource so we can see how it occurs. [image: image.jpeg]

  • Non-English speakers

    37 Topics
    136 Posts
    J
    @AtaxyaNetwork Merci pour tes recherches ! Oui "cd_label" serait cool comme ajout au plugin ce qui permet sur les distro type Fedora/Redhat de ne pas avoir de boot_command à gérer