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

    Management agent not detected after VM migrated - Windows XCP-ng PV drivers 9.0.9137

    Scheduled Pinned Locked Moved XCP-ng
    2 Posts 2 Posters 14 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.
    • T Offline
      tmk
      last edited by

      I've been testing out the new XCP-ng Windows PV drivers (version 9.0.9137) and I've run across what appears to be a bug.

      The tools status shows normally in Xen Orchestra for a VM with the tools installed but if I migrate a VM to a different host Xen Orchestra seems to lose that connection. After migration it shows a status of "Management agent not detected". The only thing that can bring it back to recognizing that the tools are installed is a reboot of the guest. I've tried restarting all 4 of the xcp-ng/xen related Windows services and that doesn't help either, only a reboot.

      I've tested this on a Windows Server 2022 VM that had the XenServer VM Tools removed with XenClean and then the new tools installed. I have also tested it with a fresh install of Windows Server 2019 and only the new tools installed. Finally, I have confirmed the same behavior with a Windows 11 VM that had the XenServer VM Tools removed with XenClean and then the new tools installed.

      We are running XCP-ng with all of the latest updates installed and Xen Orchestra version 5.112.1

      One of the side effects of the tools not being detected after a migration is that it no longer shows memory usage on the Stats tab (until a reboot of the VM). Here are some before/after migration screenshots of one of the servers with some of the changes highlighted.

      General tab before migration:

      firefox_l2plQ2mAct.png

      General tab after migration:

      firefox_0YUJEKIuMl.png

      Advanced tab before migration:

      firefox_xCT4oEZWTS.png

      Advanced tab after migration:

      firefox_zElGLugSky.png

      Stats tab before migration:

      firefox_DP1BUXx6Nr.png

      Stats tab after migration:

      firefox_tJdXbvLUgQ.png

      Has anyone else seen this behavior?

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

        Hi,

        IIRC, it's a known (cosmetic) problem (just the report, but the tools are still working). Also IIRC, @dinhngtu has or works on a patch.

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