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

    Windows VM - No ram reported?

    Scheduled Pinned Locked Moved Solved Xen Orchestra
    3 Posts 2 Posters 252 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.
    • N Offline
      nerdyviking88
      last edited by

      Fresh install of XO, spun up a testing Windows VM, used the Windows Update tools/drivers. Sees the drivers, agent is installed, reports an IP, all works well. Except XO can't see the ram usage. It just reports as 0.

      I've tried this with two different installs now, same thing. Tried with Win 2016 and 2019, no difference.

      This is the from source build of XO, running in docker from the image ronivay/xen-orchestra due to how quickly I could add it ot my existing pool.

      1 Reply Last reply Reply Quote 0
      • N Offline
        nerdyviking88 @olivierlambert
        last edited by

        @olivierlambert

        I blew away the docker container and did a fresh build of XO from source on a *buntu box. Issue resolved itself with that. Must be a bad build in the docker.

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

          Hi,

          If it's reported at 0, it could mean:

          1. The agent doesn't report anything
          2. XO can't access the stats of the host

          In the mean time, double check https://xen-orchestra.com/docs/community.html#report-a-bug to

          N 1 Reply Last reply Reply Quote 0
          • N Offline
            nerdyviking88 @olivierlambert
            last edited by

            @olivierlambert

            I blew away the docker container and did a fresh build of XO from source on a *buntu box. Issue resolved itself with that. Must be a bad build in the docker.

            1 Reply Last reply Reply Quote 0
            • olivierlambertO olivierlambert marked this topic as a question on
            • olivierlambertO olivierlambert has marked this topic as solved on
            • First post
              Last post