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

    New Rust Xen guest tools

    Scheduled Pinned Locked Moved Development
    162 Posts 39 Posters 125.0k Views 36 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.
    • olivierlambertO Offline
      olivierlambert Vates 🪐 Co-Founder CEO
      last edited by

      @yann can you update the README accordingly?

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

        @olivierlambert updating the README will be quick enough... but if the sig is indeed mandatory we need to setup something for this first... and autosigning from a CI rather requires doing that on a trusted runner rather than on gitlab-provided ones, so that requires some provisioning and IT work first.

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

          @flakpyro the old format is still supported, and actually the [trusted=yes] in the old-style configuration shown in the release notes does work in my quick test with our own Debian 13 hub template.

          D 1 Reply Last reply Reply Quote 1
          • D Offline
            David_5.1 @yann
            last edited by

            One-line format should work fine with Trixie, but as the “new” deb822 format has been supported since Debian Jessie, it should be usable on most installs.

            Jessie manpage for reference : https://manpages.debian.org/jessie/apt/sources.list.5.en.html#:~:text=rfc822

            1 Reply Last reply Reply Quote 0
            • J Offline
              john.c
              last edited by john.c

              @yann Though the deb822 format allows for that file in sources format, to have the signing key tied to that file’s specified repositories. Very important as it ensures that the key is only used by that repository, unless otherwise specified. The old format typically tends to apply that key to all repositories. So even repositories which shouldn’t use it could, worse the key was trusted for all repositories by the client.

              In the new format the repositories can have the specific key tied to them, on the client side as well as the server side.

              yannY 1 Reply Last reply Reply Quote 1
              • yannY Offline
                yann Vates 🪐 XCP-ng Team @john.c
                last edited by

                @john.c OK, that will be useful when the repo is signed, but for now I don't see what adverse effect it can have. Do I miss something?

                Also we try to avoid breaking support for older OS versions, so we'll likely continue to advertise the old format for older versions of Debian.

                J 1 Reply Last reply Reply Quote 0
                • J Offline
                  john.c @yann
                  last edited by john.c

                  @yann said in New Rust Xen guest tools:

                  @john.c OK, that will be useful when the repo is signed, but for now I don't see what adverse effect it can have. Do I miss something?

                  Also we try to avoid breaking support for older OS versions, so we'll likely continue to advertise the old format for older versions of Debian.

                  @yann From Debian 13.0.0 (code name Trixie) having repository signing is mandatory. Without it apt will straight refuse to install, update or upgrade its packages.

                  Also doing with deb822 format will help to protect the GPG Key, used by Vates from abuse by another repository. Especially if that repository is hosting malware laden deb packages. As only the Vates repository can then use that signing key, as defined in the sources file.

                  Refusing to install, update or upgrade is an adverse effect wouldn’t you say?

                  1 Reply Last reply Reply Quote 0
                  • DustyArmstrongD Offline
                    DustyArmstrong @dClauzel
                    last edited by

                    Testing the agent out on Arch Linux (mainly due to the spotty 'support' in the AUR/generally) and it is working fine - better than what I had before (which did not report VM info properly). I've set it up as a systemd service to replace the previous one I had, also working as expected.

                    This would be fun to contribute towards.

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

                      Not sure is it an issue. Agent itself is working.

                      Welcome to Ubuntu 24.04.3 LTS (GNU/Linux 6.14.0-37-generic x86_64)

                      systemctl status xen-guest-agent
● xen-guest-agent.service - Xen guest agent
     Loaded: loaded (/usr/lib/systemd/system/xen-guest-agent.service; enabled; preset: enabled)
     Active: active (running) since Mon 2026-02-09 14:28:41 MSK; 36min ago
   Main PID: 959 (xen-guest-agent)
      Tasks: 17 (limit: 19041)
     Memory: 4.8M (peak: 6.7M)
        CPU: 76ms
     CGroup: /system.slice/xen-guest-agent.service
             └─959 /usr/sbin/xen-guest-agent

Feb 09 14:28:41 oris systemd[1]: Started xen-guest-agent.service - Xen guest agent.
Feb 09 14:28:41 oris xen-guest-agent[959]: cannot parse yet os version Custom("24.04")

                      Welcome to Ubuntu 24.04.3 LTS (GNU/Linux 6.17.0-14-generic x86_64)

                      systemctl status xen-guest-agent
● xen-guest-agent.service - Xen guest agent
     Loaded: loaded (/usr/lib/systemd/system/xen-guest-agent.service; enabled; preset: enabled)
     Active: active (running) since Mon 2026-02-09 15:04:31 MSK; 1s ago
   Main PID: 9058 (xen-guest-agent)
      Tasks: 17 (limit: 76999)
     Memory: 2.5M (peak: 4.7M)
        CPU: 32ms
     CGroup: /system.slice/xen-guest-agent.service
             └─9058 /usr/sbin/xen-guest-agent

Feb 09 15:04:31 k3s xen-guest-agent[9058]: Specified IFLA_INET6_CONF NLA attribute holds more(most likely new kernel) data which is unknown to netlink-packet-route crate, expecting 236, got 240
Feb 09 15:04:31 k3s xen-guest-agent[9058]: Specified IFLA_INET6_CONF NLA attribute holds more(most likely new kernel) data which is unknown to netlink-packet-route crate, expecting 236, got 240
Feb 09 15:04:31 k3s xen-guest-agent[9058]: Specified IFLA_INET6_CONF NLA attribute holds more(most likely new kernel) data which is unknown to netlink-packet-route crate, expecting 236, got 240
Feb 09 15:04:31 k3s xen-guest-agent[9058]: Specified IFLA_INET6_CONF NLA attribute holds more(most likely new kernel) data which is unknown to netlink-packet-route crate, expecting 236, got 240
Feb 09 15:04:31 k3s xen-guest-agent[9058]: Specified IFLA_INET6_CONF NLA attribute holds more(most likely new kernel) data which is unknown to netlink-packet-route crate, expecting 236, got 240
Feb 09 15:04:31 k3s xen-guest-agent[9058]: Specified IFLA_INET6_CONF NLA attribute holds more(most likely new kernel) data which is unknown to netlink-packet-route crate, expecting 236, got 240
Feb 09 15:04:31 k3s xen-guest-agent[9058]: Specified IFLA_INET6_CONF NLA attribute holds more(most likely new kernel) data which is unknown to netlink-packet-route crate, expecting 236, got 240
Feb 09 15:04:31 k3s xen-guest-agent[9058]: Specified IFLA_INET6_CONF NLA attribute holds more(most likely new kernel) data which is unknown to netlink-packet-route crate, expecting 236, got 240
Feb 09 15:04:31 k3s xen-guest-agent[9058]: Specified IFLA_INET6_CONF NLA attribute holds more(most likely new kernel) data which is unknown to netlink-packet-route crate, expecting 236, got 240
Feb 09 15:04:31 k3s xen-guest-agent[9058]: Specified IFLA_INET6_CONF NLA attribute holds more(most likely new kernel) data which is unknown to netlink-packet-route crate, expecting 236, got 240
                      J 1 Reply Last reply Reply Quote 0
                      • olivierlambertO Offline
                        olivierlambert Vates 🪐 Co-Founder CEO
                        last edited by

                        Question for @yann or @teddyastie I assume

                        1 Reply Last reply Reply Quote 0
                        • J Offline
                          john.c @Tristis Oris
                          last edited by

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

                          Not sure is it an issue. Agent itself is working.

                          Welcome to Ubuntu 24.04.3 LTS (GNU/Linux 6.14.0-37-generic x86_64)

                          systemctl status xen-guest-agent
● xen-guest-agent.service - Xen guest agent
     Loaded: loaded (/usr/lib/systemd/system/xen-guest-agent.service; enabled; preset: enabled)
     Active: active (running) since Mon 2026-02-09 14:28:41 MSK; 36min ago
   Main PID: 959 (xen-guest-agent)
      Tasks: 17 (limit: 19041)
     Memory: 4.8M (peak: 6.7M)
        CPU: 76ms
     CGroup: /system.slice/xen-guest-agent.service
             └─959 /usr/sbin/xen-guest-agent

Feb 09 14:28:41 oris systemd[1]: Started xen-guest-agent.service - Xen guest agent.
Feb 09 14:28:41 oris xen-guest-agent[959]: cannot parse yet os version Custom("24.04")

                          Welcome to Ubuntu 24.04.3 LTS (GNU/Linux 6.17.0-14-generic x86_64)

                          systemctl status xen-guest-agent
● xen-guest-agent.service - Xen guest agent
     Loaded: loaded (/usr/lib/systemd/system/xen-guest-agent.service; enabled; preset: enabled)
     Active: active (running) since Mon 2026-02-09 15:04:31 MSK; 1s ago
   Main PID: 9058 (xen-guest-agent)
      Tasks: 17 (limit: 76999)
     Memory: 2.5M (peak: 4.7M)
        CPU: 32ms
     CGroup: /system.slice/xen-guest-agent.service
             └─9058 /usr/sbin/xen-guest-agent

Feb 09 15:04:31 k3s xen-guest-agent[9058]: Specified IFLA_INET6_CONF NLA attribute holds more(most likely new kernel) data which is unknown to netlink-packet-route crate, expecting 236, got 240
Feb 09 15:04:31 k3s xen-guest-agent[9058]: Specified IFLA_INET6_CONF NLA attribute holds more(most likely new kernel) data which is unknown to netlink-packet-route crate, expecting 236, got 240
Feb 09 15:04:31 k3s xen-guest-agent[9058]: Specified IFLA_INET6_CONF NLA attribute holds more(most likely new kernel) data which is unknown to netlink-packet-route crate, expecting 236, got 240
Feb 09 15:04:31 k3s xen-guest-agent[9058]: Specified IFLA_INET6_CONF NLA attribute holds more(most likely new kernel) data which is unknown to netlink-packet-route crate, expecting 236, got 240
Feb 09 15:04:31 k3s xen-guest-agent[9058]: Specified IFLA_INET6_CONF NLA attribute holds more(most likely new kernel) data which is unknown to netlink-packet-route crate, expecting 236, got 240
Feb 09 15:04:31 k3s xen-guest-agent[9058]: Specified IFLA_INET6_CONF NLA attribute holds more(most likely new kernel) data which is unknown to netlink-packet-route crate, expecting 236, got 240
Feb 09 15:04:31 k3s xen-guest-agent[9058]: Specified IFLA_INET6_CONF NLA attribute holds more(most likely new kernel) data which is unknown to netlink-packet-route crate, expecting 236, got 240
Feb 09 15:04:31 k3s xen-guest-agent[9058]: Specified IFLA_INET6_CONF NLA attribute holds more(most likely new kernel) data which is unknown to netlink-packet-route crate, expecting 236, got 240
Feb 09 15:04:31 k3s xen-guest-agent[9058]: Specified IFLA_INET6_CONF NLA attribute holds more(most likely new kernel) data which is unknown to netlink-packet-route crate, expecting 236, got 240
Feb 09 15:04:31 k3s xen-guest-agent[9058]: Specified IFLA_INET6_CONF NLA attribute holds more(most likely new kernel) data which is unknown to netlink-packet-route crate, expecting 236, got 240

                          Is this a graphical (desktop) based VM running the agent?

                          @olivierlambert If his VM is a desktop graphical Ubuntu then, it’s Kernel will be regularly updated with each new standard lifecycle point be an upgraded HWE kernel. So will be frequently getting this message, new info in the kernel. HWE kernels are default in modern Ubuntu desktop environments!

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

                            @john.c server, no UI.

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