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

    Xen Orchestra and guest utilities on Fedora 36, XCP-ng 8.2

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

      Hello, I have some issues with the xen orchestra reporting no data on networking despite the fact I installed the guest utilities them. Indeed the same issue is on xcp-ng center. Do you have any idea what could be wrong? I checked the github of the upstream repository and it wasn't updated in years.

      P.S. I submitted a bug report to fedora bugzilla, will keep posted if they can solve it. As this isn't just for one VM. I have 2 servers, and both the same issue

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

        @adriangabura you did a good sum-up.

        That's why we started to rewrite it from scratch (in fact, we started... this week!)

        See https://gitlab.com/xen-project/xen-guest-agent

        The goal is to provide a full upstream repo, not just owned by Citrix but by the whole Xen project, and being active/fast to modify it.

        Without talking about the current code base which is... not great 😄

        1 Reply Last reply Reply Quote 0
        • A Offline
          adriangabura
          last edited by

          Hi! I wished to update that the Fedora 36 guest utilities provide now the networking data, they fixed the issue.

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

            I think it's "because" we fixed it upstream and then Fedora packaged the fix in their latest update 🙂

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