Categories

  • All news regarding Xen and XCP-ng ecosystem

    143 Topics
    4k Posts
    A
    @dthenot Great! I'm happy I was able to help test it. I look forward to the update release. Interesting note, CR is faster when the snapshots are not deleted.... or CR is faster because of the update, I'll test again after the fix.
  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    P
    Yeah, as far as I understand, this looks like something RPU wasn't really designed to handle, and I'm not deep enough in the internals to say for sure how tricky it would be to add. My instinct is this sits more in feature request territory than a bug, so I'd suggest filing it on https://feedback.vates.tech with something like "RPU: graceful shutdown/restart for PCI-pinned VMs" and your actual topology in the description. The product team will understand the constraint much better with a concrete Ceph setup to look at. Someone here probably knows if there's a cleaner workaround than manually draining and shutting down the pinned VMs before each host update, but that's what I'd fall back on in the meantime.
  • 3k Topics
    28k Posts
    florentF
    @acebmxer said: connectNbdClientIfPossible yes connectNbdClientIfPossible is the nearest error message from the real cause Now, why does it fails ? nbd should be enabled on the network used for backups , do you have a default backup network defined ? xo must have at least one VIF on this network
  • Our hyperconverged storage solution

    44 Topics
    731 Posts
    olivierlambertO
    Different use cases: Ceph is better with more hosts (at least 6 or 7 minimum) while XOSTOR is better between 3 to 7/8. We might have better Ceph support in the future for large clusters.
  • 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.