Categories

  • All news regarding Xen and XCP-ng ecosystem

    145 Topics
    5k Posts
    Y
    @dinhngtu Yes, I've submitted a false positive report here: https://www.bitdefender.com/en-us/business/submit

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    dthenotD
    @samuelolavo Hello, Could the fact that this is a local LVM SR on a non-master host be relevant to how make_chain_rw is being handled? Yes, it's indeed what's happening. The check for the SRMaster (for a shared SR it's the master but for a local it's supposed to be done on the host directly) is failing and always saying False. I'll fix this. Thank you for the help

  • All Xen Orchestra related questions/reports

    3k Topics
    29k Posts
    E
    @olivierlambert (first post, def won't be last though, break through being shy) Apologies in advance if wrong location. ;( Heads up: What I observed, PIF status may show "Disconnected" on healthy OVS LACP bonds Wanted to flag something in case it saves someone a debugging detour — after upgrading from an older XOA build (472 commits behind) (yes I know) to current master, the network view showed our eth2+eth3 bond's PIFs as "Disconnected" pool-wide, including individual PIFs on 2 of 3 hosts in the per-network detail panel. Gave me a tense scare (client-facing subnet/vlan), so we went to CLI to get ground truth before assuming an outage (though obvious services working fine in that network). * ovs-appctl bond/show on all three hosts: lacp_status: negotiated, both members enabled/may_enable: true, active traffic balanced across both interfaces (balance-tcp). * ethtool confirms link detected, 10Gb/s full duplex, both physical NICs. * XAPI's own PIF object reports currently-attached: true for the bond master. So the bond itself is fully healthy — this looks like it's specific to how the PIF status is being surfaced in XO 6, not an actual connectivity problem or a stale XAPI record. Sharing in case it's useful data toward the read-only-mode maturity you mentioned in the announcement. XO commit: 5.208.3 (rebuilt from source today) All nodes(3) within the last week: XCP-ng version: 8.3.0 (xapi 26.1.16, network_backend: openvswitch)

  • Our hyperconverged storage solution

    53 Topics
    814 Posts
    J
    Hello! Got this error when upgrade piraeus operator from 2.11.0 to 2.12.0 Curious to know when a new version of linstor will be supported? time="2026-09-23T17:46:01Z" level=fatal msg="LINSTOR 1.33.1 (REST API 1.27.0) is not supported: the driver requires REST API 1.29 or newer in the 1.x series, shipped with LINSTOR 1.35" [image: image.jpeg] jonathon@jonathon-framework:~$ linstor --controllers=10.2.0.10,10.2.0.11,10.2.0.12,10.2.0.13,10.2.0.14 controller v linstor controller 1.33.1; GIT-hash: 95da7940d6efb6a39ea303c5f37b03478a6fab0b [image: image.jpeg] [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