Categories

  • All news regarding Xen and XCP-ng ecosystem

    140 Topics
    4k Posts
    G
    @olivierlambert I did post an alternative script here: https://xcp-ng.org/forum/topic/8620/usb-passthrough-override-script-to-ensure-usb-policy-conf-consistency But it was later removed due to request by @stormi . I'm currently using my script which basically backs up your settings and overrides the default one (after backing it up on first install) on every boot. I know its a crude way to handle but it was only meant to be temporary till you guys find a solution. I have reposted it.

  • Everything related to the virtualization platform

    1k Topics
    14k Posts
    C
    As I can't find it anywhere: What exactly is happening on join/leave? Is the masking changing at runtime and affecting every new started VM, does the pool need to be rebooted after an older server has been removed, to "unlock" all features? I have a pool with HPE DL380 Gen 9 and 10 where Gen 9 will replaced with Gen 12. So I assume it makes sense to remove 9 first, then add 12. But how exactly is the masking process working? Should I reboot Gen 10 first (shutting down all VMs) or add 12, move VMs over... or just shutdown and start all currently running VMs? In the early days (~XenServer 6) it had to be done manually by getting CPU features, calculating the commons and give it as parameter to join command. What I did not see though, is: How exactly is it working on removal and what's best practice. (also: should be added to documentations)

  • All Xen Orchestra related questions/reports

    3k Topics
    26k Posts
    P
    @Mathieu said in ️ XO 6: dedicated thread for all your feedback!: Has anyone tried to access XO 6 via a reverse proxy? I'm using nginx proxy manager in a docker container to access my XO instance. Everything is working fine with XO5 (both XOCE and XOA). But when trying to access XO6 through the reverse proxy, it shows only a few info, with a circle loading on the top and nothing on the left bar: [image: 1766747700954-7c0cc74d-19cc-4a9e-858a-f53913c654c6-image-resized.png] If I access XOCE and XOA v6 by their IP address, it's working as expected. Websocket support and cache is activated on the reverse proxy, nothing else fancy on that side. Thanks. I haven't tried ngnix. But I access my though haproxy:443 - > xo:8443. And that works just fine. But there need to be a couple of fixes upstream in master to iron out the quirks with non-443 ports and such.

  • Our hyperconverged storage solution

    39 Topics
    702 Posts
    S
    That worked; thank you!!!

  • Non-English speakers

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