Categories

  • All news regarding Xen and XCP-ng ecosystem

    143 Topics
    4k Posts
    stormiS
    Indeed, no reboot required if those are the only patches that you are applying, as indicated in the blog post.

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    poddingueP
    The "PIF is not attached" usually means the network interface selected as the migration network isn't currently active on the target host. It can happen after upgrades if the host hasn't been fully rebooted. Worth checking whether a reboot of both hosts changes anything, and running xe pif-list to see whether that specific PIF shows currently-attached: true on the target. If the PIF looks attached in xe but migration still fails, might be worth a ping to Team-XAPI-Network.

  • All Xen Orchestra related questions/reports

    3k Topics
    28k Posts
    P
    @poddingue there is a notion of appliance too (group of VMs) https://docs.xcp-ng.org/appendix/cli_reference/#appliance-commands where you can start/stop a group of VMs, never tried it, doesn't seem to have a boot order in the vAPP neither

  • 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/

  • Non-English speakers

    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.