Categories

  • All news regarding Xen and XCP-ng ecosystem

    142 Topics
    4k Posts
    B
    @bvitnik good catch, that form had multiple issues, I just fixed all of them - https://github.com/benapetr/XenAdminQt/commit/4847e85f2403f3c6fd328f17754c91df21c36502 this was one of them 0 benapetr committed to benapetr/XenAdminQt refactor of new SR wizard fixed missing NFS version selector made Test Connection button appear only when we create new SR, not ISO, because xapi doesn't support probe on ISO objects implemented drop-in descriptions when nothing is provided cleaned up some qvariant scraping and invalid creation of XenLib objects (like Host) instead we retrieve them from the cache now

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    A
    That is a frustrating loop to be in, especially with TrueNAS. Usually, when the VM fails to start after a change, it’s because XCP-ng is trying to pass through a PCI device (like an HBA) that isn't being released properly by the host. Have you checked if the "hide" parameters in your grub config are still correct? Sometimes an update can reset those, and the host grabs the controller before the VM can. Another thing to try is toggling the BIOS/UEFI mode in the VM settings - TrueNAS can be picky about that depending on which version you’re running.

  • All Xen Orchestra related questions/reports

    3k Topics
    28k Posts
    P
    Re: FILE RESTORE / overlapping loop device exists we still had this annoying probleme where we couldn't FLR our backup, source VM could be Windows or linux, with or without LVM... (see error logs in previous thread, overlapping loop...) latest XOA is installed. on a secondaray XO CE, I mounted the same remote, and NO PROBLEMS AT ALL... soooo I thought my main XOA is probably beaten up somewhere... but that was not it. all remotes on main XOA are attached to a XO PROXY (official, not CE) ! on the XO CE that is in another datacenter, I mounted the S3 remotes directly WITHOUT the proxy use, and it worked. On main XOA, we offload all backup tasks to proxies, so all remotes are attached to a proxy... I duplicated a remote, same conf, but without proxy, so that XOA would do the restore job, not the proxy, and voila, all is working as intended, FLR is okay on main datacenter. TLDR : FLR is not working with proxy attached remotes, if you duplicate the remote without the XO PROXY, all good @florent @bastien-nollet I think there is something to look into. probably a race condition, the XOA and the XO PROXY both try to mount the loop device ?

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

  • Non-English speakers

    34 Topics
    101 Posts
    B
    @AtaxyaNetwork Merci becuoup pour ce retour. Je vais compléter l'article dans ce sens.