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

    VM Creation Failure | "Expected int64, got 'N'\"

    Scheduled Pinned Locked Moved Unsolved Management
    17 Posts 2 Posters 290 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.
    • olivierlambertO Offline
      olivierlambert Vates 🪐 Co-Founder CEO @kagbasi-ngc
      last edited by

      kagbasi-ngc Yes, top is executed from your Dom0, which is... a VM 😉 When you run memtest, you run it on the entire host. And yes, ideally let it run entirely.

      K 1 Reply Last reply Reply Quote 0
      • K Offline
        kagbasi-ngc @olivierlambert
        last edited by

        olivierlambert Awesome, thanks for the explanation - I suspected that. Cool, I'm gonna let it run all 4 passes. Also, should I run the same on the other two hosts?

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

          If it's a lab and you can afford the time, at least we'll be on the safe side

          K 1 Reply Last reply Reply Quote 0
          • K Offline
            kagbasi-ngc @olivierlambert
            last edited by

            olivierlambert Cool, I'll run the other two when I get back. I'll kick them off simultaneously.

            K 1 Reply Last reply Reply Quote 1
            • K Offline
              kagbasi-ngc @kagbasi-ngc
              last edited by

              olivierlambert So, as luck would have it, the lab lost partial power around 10pm last night - right when the memtest had reached 98% complete on the 4th pass. Unfortunately, I'm gonna have to run the tests again and let it run over the weekend.

              It took about 10 hours to run, so that should be enough hours over the weekend for all three hosts to finish.

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

                Ouch 😄

                K 1 Reply Last reply Reply Quote 0
                • K Offline
                  kagbasi-ngc @olivierlambert
                  last edited by

                  olivierlambert yeah, I almost cried when it happened.

                  K 1 Reply Last reply Reply Quote 0
                  • K Offline
                    kagbasi-ngc @kagbasi-ngc
                    last edited by kagbasi-ngc

                    olivierlambert Memory tests on all three hosts completed successfully; results below.

                    VMH01 (Master)
                    VMH01_Image1.png

                    VMH01_Image2.png

                    VMH02
                    VMH02_Image1.png

                    VMH02_Image2.png

                    VMH03
                    VMH03_Image1.png

                    VMH03_Image2.png

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

                      Great, so at least we can rule out a memory or CPU issue with memory 🙂

                      K 1 Reply Last reply Reply Quote 0
                      • K Offline
                        kagbasi-ngc @olivierlambert
                        last edited by

                        olivierlambert Yes we can, however, it's unsettling not knowing the root cause. But seems that restarting the Xen Toolstack may have resolved this issue.

                        I haven't attempted creating a VM yet, so I'll do that when I get in tomorrow.

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