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

    win 2019 vm-checkpoint failed on xcp-ng 7.6

    Scheduled Pinned Locked Moved Solved Compute
    4 Posts 2 Posters 585 Views 1 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.
    • C Offline
      cheese
      last edited by

      I met a strange issue when doing vm-checkpoint for a win 2019 VM:

      # xe vm-checkpoint uuid=9e379243-2eba-b273-037c-60f5d53b4422 new-name-label=lirb-checkpoint
      The server failed to handle your request, due to an internal error.  The given message may give details useful for debugging the problem.
      message: xenopsd internal error: (Failure "Error from emu-manager: xenguest Invalid argument")
      

      The xenguest error log in daemon.log:

      May 19 10:54:39 xxxx-sanhoobt xenguest-39-emp[13598]: xc: detail: Failed allocation for dom 39: 1024 extents of order 0
      May 19 10:54:39 xxxx-sanhoobt xenguest-39-emp[13598]: xc: error: Failed to populate physmap (16 = Device or resource busy): Int
      ernal error
      May 19 10:54:39 xxxx-sanhoobt xenguest-39-emp[13598]: xc: error: Failed to populate pfns for batch of 1024 pages: Internal erro
      r
      May 19 10:54:39 xxxx-sanhoobt xenguest-39-emp[13598]: xc: error: Restore failed (16 = Device or resource busy): Internal error
      May 19 10:54:39 xxxx-sanhoobt xenguest-39-emp[13598]: xenguest: xc_domain_restore: [1] Restore failed (16 = Device or resource 
      busy)
      May 19 10:54:39 xxxx-sanhoobt emu-manager-39[13596]: poll failed because revents=0x11 for `xenguest`.
      May 19 10:54:39 xxxx-sanhoobt emu-manager-39[13596]: Error for emu `xenguest`: wait_for_event => Invalid argument
      May 19 10:54:39 xxxx-sanhoobt emu-manager-39[13596]: Error waiting for events: `Invalid argument`.
      May 19 10:54:39 xxxx-sanhoobt emu-manager-39[13596]: Error sending message to emu client: `Broken pipe`.
      May 19 10:54:39 xxxx-sanhoobt emu-manager-39[13596]: Emu `xenguest` exited with an error: 1.
      May 19 10:54:39 xxxx-sanhoobt emu-manager-39[13596]: Reporting: `error:xenguest Invalid argument#012`...
      

      The final error comes from xenguest. Any idea about this?

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

        Hmm weird. Sounds like emu manager related.

        1 Reply Last reply Reply Quote 0
        • C Offline
          cheese
          last edited by

          I figured out that it is an old issue. It is fatal when memory-dynamic-max is less than memory-static-max.

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

            Wow, didn't know it was possible to violate those rules!

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