Categories

  • All news regarding Xen and XCP-ng ecosystem

    139 Topics
    4k Posts
    D
    @acebmxer All looks good from the output. There might be some VMs that need fixes for Windows dbx updates to work properly, I'll try to add that in the official version.

  • Everything related to the virtualization platform

    1k Topics
    14k Posts
    psafontP
    @jmannik ah, indeed. Do you know which server / interface holds the IP 192.168.30.13? I suspect is still VMHost13, but a different interface. Until the members have configured their master as 192.168.30.13, you'll have this error. This can be done by a call, but since it's a delicate operation, it's better if there are no operations running on the pool. SSH into the VMHost13, and run xe host-list name-label=VMHost13 --minimal | xargs -I _ xe pool-designate-new-master host-uuid=_ This should write the new IP to the files of all the pool members and stop blocking this issue from enabling HA

  • All Xen Orchestra related questions/reports

    3k Topics
    26k Posts
    A
    @olivierlambert I updated and reran the backup. It was successful this time. Going to run it a couple more times to make sure, but it seems like it might be resolved.

  • Our hyperconverged storage solution

    36 Topics
    684 Posts
    olivierlambertO
    You can manually install XOSTOR yes.

  • Non-English speakers

    30 Topics
    85 Posts
    GlitchG
    @Davidj-0 Merci pour le retour, j'utilisais aussi une Debian pour mon test ^^