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

    Alpine 3.14 not detected correctly

    Scheduled Pinned Locked Moved Xen Orchestra
    4 Posts 3 Posters 657 Views 2 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.
    • ForzaF Offline
      Forza
      last edited by

      I upgraded an Alpine install today and see that XOA doesn't fully detect it. Not a big issue, just for info.

      Alpine 3.14
      54038c59-a0dc-4865-a0ce-f602d5747c6c-image.png
      d1b8c5dc-bc8f-4726-8d00-4aac85bcbd66-image.png

      Alpine 3.13
      81eaffa4-cd90-4fc0-bec9-2b31becdeeeb-image.png

      ps. Did you update the template? 🙂🐶
      ps2. I'd love templates using btrfs filesystem as rootfs.

      1 Reply Last reply Reply Quote 0
      • olivierlambertO Offline
        olivierlambert Vates 🪐 Co-Founder CEO
        last edited by

        The problem isn't coming from XO, it's the agent inside the VM that should return the right number. XO is just displaying that info.

        Check the guest itself to see how the number is parsed and why it's not up to date 🙂

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

          IIRC those strings are compiled in, so there would be an issue with the build process for alpine's xe-guest-utilities apk.

          ForzaF 1 Reply Last reply Reply Quote 1
          • ForzaF Offline
            Forza @stormi
            last edited by

            I created an issue on https://gitlab.alpinelinux.org/alpine/aports/-/issues/13506 to track this.

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