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

    New guest tools ISO for Linux and FreeBSD. Can you help with the tests?

    Development
    13
    61
    9994
    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
      thomas0046 @stormi last edited by

      @stormi Hi Stormi, firstly, thx for all good work U guys are doing ! And I have problem, that Im not able to get IP address info from my Rocky Linux 8.4(I have only one NIC conencted eth0).
      When Im using newest guest tools from EPEL repo (xe-guest-utilities-latest version 7.21.0.1.el8), those tools cant be started at all.
      When Im using newest guest tools from xcp-ng-testing repo(ISO:guest-tools-8.2.0-9.xcpng8.2, tools version 7.20.0-9) as you suggested in some previous post, those tools works, I can even get correct information about OS release, and virtualization state is reporting as "Optimized(version 7.20 installed)", but in network tab, no guest IP address is reported (unknown).

      What is strange is that I had RC version of Rocky Linux 8.3 laying around from testing in the past, so I tried to install guest tools from my platform (Citrix 7.0), it is able to report IP address correctly.

      That leads to me to think, that somehow Rocky Linux 8.4 isnt fully supported yet ?
      If you need more info(logs/screens), please let my know, thx

      stormi 1 Reply Last reply Reply Quote 0
      • stormi
        stormi Vates 🪐 XCP-ng Team 🚀 @thomas0046 last edited by

        @thomas0046 @Darkbeldin tried to reproduce, but the IP address is correctly reported in Xen Orchestra with Rocky 8.4 and the guest tools from XCP-ng (btw you don't need to pull the guest tools from the testing repo now, as they have been pushed as a regular update).

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

          I realize I haven't announced it on this thread (I thought I had) : the guest tools ISO that was tested in this thread have been released as an update to XCP-ng.

          See https://xcp-ng.org/blog/2021/06/28/summer-security-and-bugfix-updates/

          You can still provide feedback, of course, but you don't need to try to pull packages from the testing repository for now.

          1 Reply Last reply Reply Quote 0
          • P
            Pierre Briec last edited by

            Hi @stormi ,

            I have an Ipfire fresh VM which is not detected by the installer. How can I add support for this distro which seems to be LFS (linux from scratch) based.
            I would like to have the guest-tools installed on it.
            Can you help me please or tell me how can i add it manually?
            I can provide all information you want.

            thanks in advance
            Pierre

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

              Hi @Pierre-Briec,

              If Ipfire is based on LFS, I suppose there's no RPM nor DEB package management. In this case you can use the .tgz tarball and install it manually, and make sure to install enable the xe-linux-distribution service (using the provided initscript or the systemd unit). But maybe there's a way to install a RPM or a DEB package through some compatibility tool, in which case you may try them.

              You may also have to tweak the xe-linux-distribution file to make it recognize your distro. If it has a /etc/os-release file, then future versions of xe-linux-distribution, not released yet, will recognize it automatically.

              Ideally, it would be nice to work towards pushing the tools directly in the distro, so that you could install them from their repositories when needed. We can provide some help if a packager gets it touch with us or if you want to try to contribute them yourself.

              P 1 Reply Last reply Reply Quote 0
              • P
                Pierre Briec @stormi last edited by

                Hi @stormi
                Thanks for your answer

                Hi @Pierre-Briec,

                If Ipfire is based on LFS, I suppose there's no RPM nor DEB package management. In this case you can use the .tgz tarball and install it manually, and make sure to install enable the xe-linux-distribution service (using the provided initscript or the systemd unit). But maybe there's a way to install a RPM or a DEB package through some compatibility tool, in which case you may try them.

                That's true. There is only a package management pakfire for the addons. I will look at the tgz if i can install it.
                Ipfire is using SysVinit script. I'm not very familiar with that and if someone can help me with that.

                You may also have to tweak the xe-linux-distribution file to make it recognize your distro. If it has a /etc/os-release file, then future versions of xe-linux-distribution, not released yet, will recognize it automatically.

                I can provide this file /etc/os-release

                NAME="IPFire"
VERSION="2.27"
ID=ipfire
VERSION_ID=2
PRETTY_NAME="IPFire 2.27 (x86_64) - core160"
ANSI_COLOR="0:31"

                hope it helps

                Ideally, it would be nice to work towards pushing the tools directly in the distro, so that you could install them from their repositories when needed. We can provide some help if a packager gets it touch with us or if you want to try to contribute them yourself.

                The IPFire is a german project so it's not easy for me to communicate with the team. I can make tests and even provide a remote access to a VM test through XO if need.

                thanks
                Pierre

                1 Reply Last reply Reply Quote 0
                • P
                  Pierre Briec last edited by

                  Hi @stormi

                  I've tried to modify the xe-linux-distribution file but i definitly don't have the skills to modify it. I don't understand the sed commands to identify
                  Can someone help me with that?

                  thanks in advance
                  Pierre

                  stormi 1 Reply Last reply Reply Quote 0
                  • stormi
                    stormi Vates 🪐 XCP-ng Team 🚀 @Pierre Briec last edited by

                    @pierre-briec You may try this version of the script: https://raw.githubusercontent.com/xenserver/xe-guest-utilities/master/mk/xe-linux-distribution

                    P 1 Reply Last reply Reply Quote 0
                    • P
                      Pierre Briec @stormi last edited by Pierre Briec

                      @stormi
                      Thanks
                      Now, the OS seems to be detected
                      Here is the content of /var/cache/xe-linux-distribution

                      [root@ipfire-test ~]# cat /var/cache/xe-linux-distribution
os_distro="ipfire"
os_majorver="2"
os_minorver="unknown"
os_uname="5.10.55-ipfire"
os_name="IPFire 2.27 (x86_64) - core160"
[root@ipfire-test ~]#

                      I still don't know why xcp-center doesn't detect the agent management and if it would work as expected

                      alt text
                      alt text

                      I also change the xe-linux-distribution in /etc/init.d because the function action is not available in ipfire. I don't know what is the best way.
                      Is there anything to change?

                      thanks
                      Pierre

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

                        I think XCP-ng Center doesn't consider that the agent is working correctly if it doesn't report the IP address to the host.

                        P 1 Reply Last reply Reply Quote 0
                        • P
                          Pierre Briec @stormi last edited by

                          @stormi

                          So i've made a mistake? the VM has an IPv4 address in local network but no gateway yet

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

                            I can't say whether there's an issue with the way you run the agent (xe-daemon) or in the agent itself. Maybe the way it collects the IP addresses is not compatible with how ipfire handles networking.

                            P 1 Reply Last reply Reply Quote 0
                            • P
                              Pierre Briec @stormi last edited by

                              @stormi

                              yes, they are renaming the network interfaces (like red0, green0, blue0) and perhaps it's the problem.
                              So the agent should work as expected in PVHVM ? My previous VM it was only in PV.
                              thanks for your answer

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

                                Yes, the agent runs well in HVM VMs. Actually there are almost no reasons why you should use a PV VM nowadays.

                                P 1 Reply Last reply Reply Quote 0
                                • P
                                  Pierre Briec @stormi last edited by

                                  @stormi
                                  As Xcp-center reports that agent is not installed, i was afraid that it wouldn't work as expected.
                                  I don't want to have low performances on that VM which will be the internet gateway.

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

                                    Actually, on any recent enough Linux system (ie not many years old) , the PV drivers are directly included in the kernel. Unless, maybe, a very specific distro decides that they don't want Xen support in their kernel.

                                    So the tools you install on the VMs are merely an agent to make the VM more cooperative with the hypervisor, but they don't affect performance.

                                    The situation is different on Windows systems where you need to install PV drivers to achieve better performance.

                                    1 Reply Last reply Reply Quote 1
                                    • Forked by  stormi stormi 
                                    • First post
                                      Last post