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

    New Rust Xen guest tools

    Scheduled Pinned Locked Moved Development
    146 Posts 37 Posters 54.7k Views 33 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.
    • Tristis OrisT Offline
      Tristis Oris Top contributor
      last edited by

      I installed tools on next distro:
      just installed and check if OS is recognized, metrics available. Have no idea what else can go wrong if install succeed.

      Alma linux 8.9, Alma linux 9.3, Fedora server 39, OpenSuse Leap 15.5, Oracle 8.9, Oracle 9.3.

      1 Reply Last reply Reply Quote 0
      • Tristis OrisT Offline
        Tristis Oris Top contributor
        last edited by

        weird, but now i got error on fresh Oracle 8.9.
        not sure if anyone use servers with enabled selinux.

        dnf localinstall xen-guest-agent-0.4.0-0.fc37.x86_64.rpm
        
        Oracle Linux 8 BaseOS Latest (x86_64)                                                                                                        40 MB/s |  68 MB     00:01
        Oracle Linux 8 Application Stream (x86_64)                                                                                                   39 MB/s |  54 MB     00:01
        Latest Unbreakable Enterprise Kernel Release 7 for Oracle Linux 8 (x86_64)                                                                   38 MB/s |  27 MB     00:00
        Last metadata expiration check: 0:00:05 ago on Fri 02 Feb 2024 07:59:24 AM EST.
        Dependencies resolved.
        ============================================================================================================================================================================
         Package                                      Architecture                        Version                                   Repository                                 Size
        ============================================================================================================================================================================
        Installing:
         xen-guest-agent                              x86_64                              0.4.0-0.fc37                              @commandline                              1.2 M
        
        Transaction Summary
        ============================================================================================================================================================================
        Install  1 Package
        
        Total size: 1.2 M
        Installed size: 3.7 M
        Is this ok [y/N]: y
        Downloading Packages:
        Running transaction check
        Transaction check succeeded.
        Running transaction test
        Transaction test succeeded.
        Running transaction
          Preparing        :                                                                                                                                                    1/1
          Installing       : xen-guest-agent-0.4.0-0.fc37.x86_64                                                                                                                1/1
        error: lsetfilecon: (-1 ad2886979f8f9a9f9b404a9e9b3f2018781ceb;65bce739, system_u:object_r:lib_t:s0) No such file or directory
        error: Plugin selinux: hook fsm_file_prepare failed
        
        Error unpacking rpm package xen-guest-agent-0.4.0-0.fc37.x86_64
          Verifying        : xen-guest-agent-0.4.0-0.fc37.x86_64                                                                                                                1/1
        
        Failed:
          xen-guest-agent-0.4.0-0.fc37.x86_64
        
        Error: Transaction failed
        
        rpm -i xen-guest-agent*
        error: lsetfilecon: (-1 ad2886979f8f9a9f9b404a9e9b3f2018781ceb;65bcebdc, system_u:object_r:lib_t:s0) No such file or directory
        error: Plugin selinux: hook fsm_file_prepare failed
        error: unpacking of archive failed on file /usr/lib/.build-id/ce/ad2886979f8f9a9f9b404a9e9b3f2018781ceb;65bcebdc: cpio: (error 0x2)
        error: xen-guest-agent-0.4.0-0.fc37.x86_64: install failed
        
        yannY T 2 Replies Last reply Reply Quote 0
        • yannY Offline
          yann Vates 🪐 XCP-ng Team @Tristis Oris
          last edited by

          @Tristis-Oris I must say the error message is rather obscure. Can you please open a ticket for this one too?

          1 Reply Last reply Reply Quote 0
          • D Offline
            Davidj 0
            last edited by

            On Fedora 39, you must enable the daemon manually after you install the package. This is probably true on all RPM-based systems.

            $ sudo systemctl enable --now xen-guest-agent.service
            

            I'd be happy to submit a pull request to add that to the RPM package if you will point me at the right repo.

            yannY 2 Replies Last reply Reply Quote 0
            • yannY Offline
              yann Vates 🪐 XCP-ng Team @Davidj 0
              last edited by

              @Davidj-0 unfortunately not enabling daemons at first install is the standard behavior in RPM world. I already had a look at changing this for one package, and it turns out to be messy with unforeseen impact, so I gave up with the excuse that admins of RPM-based distros already have to live with this idiosyncrasy anyway.
              I added this in install instructions in the Gitlab release notes already.

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

                IIRC you can just enable and start the service in a %post scriptlet. It's does not conform to Fedora's and RedHat policy for packages included in their repositories, but here the repository is external and we know for sure that the vast majority of users just wants it to be enabled.

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

                  @stormi that would need to be done only if not upgrading then, or it would interfere with local admin's choice.

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

                    @yann This is a common condition in scriptlets, yes.

                    1 Reply Last reply Reply Quote 0
                    • yannY Offline
                      yann Vates 🪐 XCP-ng Team @Davidj 0
                      last edited by

                      @Davidj-0 @Tristis-Oris I started a pull request for this. Seems to work for simple cases, but if you want to shake it in real life that can help!
                      [shortcut to test RPM]

                      Tristis OrisT 1 Reply Last reply Reply Quote 0
                      • Tristis OrisT Offline
                        Tristis Oris Top contributor @yann
                        last edited by

                        @yann

                        • install over old version. Nothing changed at XO ( waited for about 1-2 min), but after vm reboot it show new tools version.
                        • install over old version, restart tools service systemctl restart xen-guest-agent.service - got new version at XO.
                        • removed old tools first dnf remove xen-guest-agent, reboot host, then install new one.
                        rpm -i xen-guest-agent*
                        Removed "/etc/systemd/system/multi-user.target.wants/xen-guest-agent.service".
                        Created symlink /etc/systemd/system/multi-user.target.wants/xen-guest-agent.service → /usr/lib/systemd/system/xen-guest-agent.service.
                        

                        So it works good. Maybe also add service reload in case of update?

                        1 Reply Last reply Reply Quote 0
                        • T Offline
                          Theo @Tristis Oris
                          last edited by

                          Hi @Tristis-Oris,
                          I have the same installation problem as you.
                          When I try to install, it gives me the same error message.
                          How did you solve this?

                          error: lsetfilecon: (-1 ad2886979f8f9a9f9b404a9e9b3f2018781ceb;65bcebdc, system_u:object_r:lib_t:s0) No such file or directory
                          error: Plugin selinux: hook fsm_file_prepare failed
                          Error: Transaction failed
                          
                          Tristis OrisT 1 Reply Last reply Reply Quote 0
                          • Tristis OrisT Offline
                            Tristis Oris Top contributor @Theo
                            last edited by

                            @Theo main point to avoid such issues without tuning the OS.
                            easy way - disable selinux.

                            yannY 1 Reply Last reply Reply Quote 0
                            • yannY Offline
                              yann Vates 🪐 XCP-ng Team @Tristis Oris
                              last edited by

                              @Tristis-Oris said in New Rust Xen guest tools:

                              @Theo main point to avoid such issues without tuning the OS.
                              easy way - disable selinux.

                              I'd like to point out, while this is useful to test the tools, it is not recommended to do that on a production VM - sorry if that sound obvious, but better safe than sorry 🙂

                              T 1 Reply Last reply Reply Quote 1
                              • C Offline
                                CJ @yann
                                last edited by

                                @yann I can't recall, but does it kick out a notice about that like BSD does? If not, is that a possible addition?

                                yannY 1 Reply Last reply Reply Quote 0
                                • T Offline
                                  Theo @yann
                                  last edited by

                                  @yann said in New Rust Xen guest tools:

                                  @Theo main point to avoid such issues without tuning the OS.
                                  easy way - disable selinux.
                                  

                                  I'd like to point out, while this is useful to test the tools, it is not recommended to do that on a production VM - sorry if that sound obvious, but better safe than sorry 🙂

                                  Yes, I agree, disabling SELinux should not be the preferred solution.
                                  It looks more like a bug in the RPM package.

                                  1 Reply Last reply Reply Quote 0
                                  • Tristis OrisT Offline
                                    Tristis Oris Top contributor
                                    last edited by

                                    But weird that i succesfully install tools on same distro before.

                                    T 1 Reply Last reply Reply Quote 0
                                    • T Offline
                                      Theo @Tristis Oris
                                      last edited by

                                      @Tristis-Oris said in New Rust Xen guest tools:

                                      But weird that i succesfully install tools on same distro before.

                                      What version of the RPM package do you have installed?
                                      Is it only xen-guest-agent package that cannot be installed?

                                      Tristis OrisT 1 Reply Last reply Reply Quote 0
                                      • Tristis OrisT Offline
                                        Tristis Oris Top contributor @Theo
                                        last edited by

                                        @Theo @yann

                                        Same with old one aaaand with dnf update. Looks i found the cause.

                                        https://support.oracle.com/knowledge/Oracle Linux and Virtualization/3002168_1.html

                                        my first tests was at Feb 2-4, and next day it was broken))))

                                        T 1 Reply Last reply Reply Quote 0
                                        • T Offline
                                          Theo @Tristis Oris
                                          last edited by Theo

                                          @Tristis-Oris said in New Rust Xen guest tools:

                                          @Theo @yann

                                          Same with old one aaaand with dnf update. Looks i found the cause.

                                          https://support.oracle.com/knowledge/Oracle Linux and Virtualization/3002168_1.html

                                          my first tests was at Feb 2-4, and next day it was broken))))

                                          Yes, that's probably it.
                                          Some more discussion on the topic:

                                          https://community.oracle.com/mosc/discussion/4558317/oel-8-8-8-9-dnf-upgrade-error-plugin-selinux-hook-fsm-file-prepare-failed-since-this-mornig
                                          https://unix.stackexchange.com/questions/767829/cant-run-rpm-due-to-calling-hook-fsm-file-prepare-in-selinux-plugin-on-oracle-l

                                          1 Reply Last reply Reply Quote 0
                                          • yannY Offline
                                            yann Vates 🪐 XCP-ng Team @CJ
                                            last edited by

                                            @CJ it looks like people really want to get it auto-enabled (which makes sense) so if we don't discover major problems we'll just let it auto-enable on first install. But yes, if it turns out it is better to leave it disabled but default a notice makes sense.

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