Categories

  • All news regarding Xen and XCP-ng ecosystem

    142 Topics
    4k Posts
    B
    I just released 0.0.4! Still an alpha, but it's becoming pretty usable - there was over 60 commits of code cleanup, polish and also limited testing of all visible features - pretty much everything that is now visible in the UI should be operational at this point, option pages, properties of hosts, pools, VDIs, configuration of NICs, even bonding and advanced stuff like pool password / secret rotation. All XAPI actions and commands were already ported over from C# variant, so my focus now is only on finishing it into a final usable product. We also have some features that original client doesn't have (such as XenCache explorer)! Next on my to-do is to add all features that are currently missing completely: HA, GPU, PCIe, VM import / export etc. Note: I will not be porting over any licensed or proprietary Citrix stuff. This tool may work with XenServer just fine, but I will not be porting over any of the proprietary features, because I will never use it and I have no way to test it either.

  • Everything related to the virtualization platform

    1k Topics
    14k Posts
    A
    Thank you all for information. I will try to virtualize GPU to Windows VMs.

  • All Xen Orchestra related questions/reports

    3k Topics
    27k Posts
    DustyArmstrongD
    @Pilow Thanks for your reply. I only have 1 XO currently, the other old one is offline - they're both on the same physical box, just a different Docker container. The old XO is currently downed and has been for a while, it never interacted with this new pool I made either. I downed it, restored my XO config to the new XO, which all worked fine. Steps were: Down old XO Up new XO and restore XO config (same IP), all good Install XCP on new hosts (hardware refresh) Create pool from new hosts on new XO Warm migrate VMs from old hosts to new hosts, all good My old XO server hasn't interacted with any of this, it can't, it would cause a clash by using the same ports. I haven't checked yet today, but I'm hoping it just kind of resolves itself now the audit logs are showing the correct VM info. I feel like it's just a sticky frontend cache of some sort.

  • Our hyperconverged storage solution

    40 Topics
    715 Posts
    I
    @ronan-a Thanks

  • Non-English speakers

    31 Topics
    90 Posts
    olivierlambertO
    Yes, account aren't related