Categories

  • All news regarding Xen and XCP-ng ecosystem

    145 Topics
    5k Posts
    Y
    @dinhngtu Received the following feedback from Bitdefender Enterprise Support Team (as expected): We can confirm that the file is clean and is currently not detected by our engines.

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    J
    @poddingue Our HA-pool is a 3 host system, yes. I'll add a note about our plans to go paid in that feedback-item. Thanks for the tip. In the meantime, I'm testing and reporting as much as I can. In order to hopefully help the product be better for all. Cheers!

  • All Xen Orchestra related questions/reports

    3k Topics
    29k Posts
    J
    @carloum70 said: Some update: After removing the ip-address from eth4 the following messages disappeared [warn] SC: (script_service_do_query_liveset) reporting "heartbeat approaching timeout". host[1].time_since_last_hb=30408. [info] SC: (script_service_do_query_liveset) "Heartbeat approaching timeout" turned FALSE By the way I forgot to mention that each time I enable HA the following warning appears in xha.log Sep 29 13:31:56 CEST 2026 [warn] BM: cannot open bonding status file (/proc/net/bonding/bond0). (2) Sep 29 13:31:56 CEST 2026 [info] BM: this is not bonded. Terminating bonding thread. bond0 (eth2 + eth3) is the management interface and also used for the HA. Watch out if backup network isn’t configured, all of your host’s backups will be sent through the management network! The same also for migrations of VMs. Like you said a dedicated bond for HA will help, as it will keep the heavy backups, VM migrations and general storage away from this traffic.

  • 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