XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Install XO from sources.

    Scheduled Pinned Locked Moved Xen Orchestra
    24 Posts 8 Posters 2.8k Views 7 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • G Offline
      Greg_E @AlexanderK
      last edited by

      @AlexanderK

      The ronivay script requires you to select an option (#2 to update).

      I look at things this way, it's good to have more people working on scripts like this.

      1 Reply Last reply Reply Quote 0
      • F Offline
        fatek
        last edited by

        Very nice job @acebmxer
        Well done

        1 Reply Last reply Reply Quote 1
        • VertuxV Offline
          Vertux @AlexanderK
          last edited by

          @AlexanderK said:

          which is the difference with this?
          https://github.com/ronivay/XenOrchestraInstallerUpdater

          Using the above around 5-6 years with no issues at all

          e.g. XenOrchestraInstallerUpdater does not support Debian 13 yet.

          1 Reply Last reply Reply Quote 0
          • acebmxerA Offline
            acebmxer
            last edited by acebmxer

            Made some updates to this project. Any existing users please see note. I have also updated the initial post.

            ⚠️ Upgrading from an earlier version of this script? Read this first.
            This version bumps the config schema to v2 (adds PUBLIC_URL and ENCRYPT_REDIS_CREDENTIALS) and corrects two config.toml generation bugs. Your xo-config.cfg is migrated automatically and non-destructively, but the corrected /etc/xo-server/config.toml is only written by --reconfigure.

            Run --reconfigure once before resuming normal updates:

            ./install-xen-orchestra.sh --reconfigure
            This regenerates config.toml with the fixes (your old file is backed up first; data in /var/lib/xo-server is untouched). It is strongly recommended if you set both REDIRECT_TO_HTTPS=true and REVERSE_PROXY_TRUST — that combination previously produced a duplicate [http] section and silently dropped one of the settings.

            Afterwards, run --update as normal for routine XO updates — --update does not need to be preceded by --reconfigure again.

            Also added option to adjust Xen Orchestras memory allocation. Useful if you are getting out of memory errors or added more memory to XO.

            ==============================================
              Xen Orchestra Memory Allocation
            ==============================================
            
              Setting                       Value
              ----------------------------- -----------------------------------
              Total system RAM              5399 MB
              Current xo-server heap limit  4887 MB
              Recommended heap limit        4887 MB
            
            1 Reply Last reply Reply Quote 0

            Hello! It looks like you're interested in this conversation, but you don't have an account yet.

            Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

            With your input, this post could be even better 💗

            Register Login
            • First post
              Last post