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

    spec of xen-hypervisor

    Scheduled Pinned Locked Moved Development
    8 Posts 3 Posters 2.8k Views 1 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.
    • T Offline
      tzirechnoy
      last edited by

      Good day.

      I'm trying to apply that patch https://lists.gt.net/xen/devel/432779 to xen-hypervisor, and at first looking for it's spec to rebuild.

      Could you please point me out where is the current one lying? I've found one at github.com/xcp-ng/xcp/ , but it is 4.7.4-4.1 , and updates from https://updates.xcp-ng.org/7.4/ got me xen-hypervisor-4.7.5-4.4.x86_64 and also suggests xen-hypervisor-4.7.5-5.2.x86_64 .

      1 Reply Last reply Reply Quote 0
      • stormiS Offline
        stormi Vates 🪐 XCP-ng Team
        last edited by stormi

        Hi.

        Most parts of the process of building updates are still manual at the moment and we still don't store and publish the source RPMs that match the published RPMs (well, the need you just expressed should raise the priority for that!).

        I don't know what this package was built from and there's no changelog but I'll try to find the relevant information. There is a chance that the answer would have to wait for wednesday though.

        1 Reply Last reply Reply Quote 0
        • T Offline
          tzirechnoy
          last edited by

          Oh, Wednesday would be nice (it is not urgent in any way).

          However, I should note, that it is possibly not only for that my need: it could be a GPL violation to publish rpms from a modified .spec without publishing .spec.

          1 Reply Last reply Reply Quote 0
          • stormiS Offline
            stormi Vates 🪐 XCP-ng Team
            last edited by

            Yeah, work on XCP-ng has been made up to now with very limited resources so we can easily find things that are not ok in this regard. Not very good from a community open-source fork, is it? But we'll fix that rather quickly now that they hired someone (me) full time 🙂

            1 Reply Last reply Reply Quote 0
            • R Offline
              r1 XCP-ng Team
              last edited by r1

              tzirechnoy You should be able to apply the patch and rebuild hypervisor yourself from DDK.

              A DDK is special VM offered by Citrix (for now...) in which all the current XCP-ng source packages can be patched and rebuilt.

              T 1 Reply Last reply Reply Quote 0
              • T Offline
                tzirechnoy @r1
                last edited by

                I suspect, that a default build in DDK would lead to more or less xenserver binaries, not xcp-ng, isn't it?

                R 1 Reply Last reply Reply Quote 0
                • stormiS Offline
                  stormi Vates 🪐 XCP-ng Team
                  last edited by

                  To my knowledge (final confirmation on wednesday 🙂 ), xcp-ng's xen packages come from the same source packages as XenServer's, with only a change to remove trademarked material (they put a trademarked Citrix logo in the RPM).

                  1 Reply Last reply Reply Quote 0
                  • R Offline
                    r1 XCP-ng Team @tzirechnoy
                    last edited by

                    tzirechnoy Thats ok as it would work for you. And as stormi mentioned, there is no difference in binaries except the ones he mentioned. So you would not see any execution differences.

                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post