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

    Error when cloning or copying VDIs of Windows VMs in 8.2

    Scheduled Pinned Locked Moved Solved Compute
    7 Posts 5 Posters 1.5k 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
      castrillo
      last edited by

      Hi

      Last week I upgraded one of my pools from 8.1 to 8.2 with the recommended method.

      Now I've found that I cannot create new VMs from any of my custom Windows templates or snapshots. Whenever I copy/clone one snapshots, VM or template I get the following error:

      The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem.
      message: Subprocess exited with unexpected code 127; stdout = [ ]; stderr = [ ]

      I've also tried to create a new template from a fresh Windows 2019 server with the same result: I've created a new VM from the base Windows 2019 template, installed the OS and XCP-ng tools, updates and then converted it to a template. Using this new template as a source for a new VM.

      If I take a custom CentOS 7 template all the operations described above work flawlessly.

      If you need more data please let me know.

      Thanks a lot

      1 Reply Last reply Reply Quote 0
      • DanpD Offline
        Danp Pro Support Team
        last edited by

        Is your host fully patched? You will likely need to check the logs for further details.

        C 1 Reply Last reply Reply Quote 0
        • C Offline
          castrillo @Danp
          last edited by

          @danp Thanks for your reply.
          I reviewed the logs but found nothing I could use to explain why the clone/copy operation is failing. I´ll do some tests and post the content of the logs files here.

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

            I feel really stupid, there were some new updates to be applied, and one of those solved the problem.
            Thanks @danp for pointing me in the right direction.

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

              Don't feel stupid. I'm not sure about your problem origin and how updates fixed it, but keep us posted if it happens again 🙂

              1 Reply Last reply Reply Quote 0
              • radioactivR Offline
                radioactiv
                last edited by

                I ran into the same problem after upgrading from 8.1 to 8.2. My VMs were Windows 10, and the clones were being initiated by UDS Enterprise.

                yum update -y fixed it, without a reboot or toolstack restart.

                jamesbeldockJ 1 Reply Last reply Reply Quote 1
                • jamesbeldockJ Offline
                  jamesbeldock @radioactiv
                  last edited by

                  Confirming that @radioactiv's fix is all I needed too:

                  yum update -y
                  

                  on my XCP-NG CLI did it.

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