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

    Import from VMware

    Scheduled Pinned Locked Moved Xen Orchestra
    18 Posts 4 Posters 723 Views 3 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.
    • O Offline
      Olest
      last edited by

      I'm using NodeJS v18.19.1

      How do you shutdown VM remote from XO if I should dig into if ESXI free is the problem?

      Have updated XO and deleted failed VM import.

      Trying import with cold migration.

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

        Let's see first if it works in cold migration 🙂

        1 Reply Last reply Reply Quote 0
        • O Offline
          Olest
          last edited by

          Cold migration worked without errors 🙂

          But it cannot boot - any idea?

          Udklip.PNG

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

            Yes: /dev/sda2 doesn't exist anymore, it's likely /dev/xvda2 instead, since it's using Xen (assuming you have PV drivers in such old CentOS version)

            1 Reply Last reply Reply Quote 0
            • O Offline
              Olest
              last edited by

              Hard to restore the VM at VMware as the migration in XO broke the VM.
              Updated to Centos 5.11 and halted it manually before migration and this time it can boot fine.

              BUT cold migration still broke the VM on VMware.

              Udklip.PNG

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

                It's like because of a lock file not released 🤔

                1 Reply Last reply Reply Quote 0
                • O Offline
                  Olest
                  last edited by

                  No lock files to find but left for 30 min and when I came back the error was gone...

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

                    Probably a timer on the lock on VMware side. Since the transfer finished, the lock was released in the end after some time.

                    1 Reply Last reply Reply Quote 0
                    • O Offline
                      Olest
                      last edited by

                      Looks like PowerOffVM_Task is not supported on ESXI Free.
                      Maybe you could read the ESXI license information and disable warm migration for ESXI Free.
                      Or ask user to shutdown VM when ready. Right now it just hang waiting for VM to shutdown.

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

                        That's interesting 🤔 @florent ?

                        1 Reply Last reply Reply Quote 0
                        • florentF Offline
                          florent Vates 🪐 XO Team @Olest
                          last edited by

                          @Olest
                          that's a nice catch, every day I discover new limits of the vmware licensing . At least we could catch the error and show something useful to the user

                          D 1 Reply Last reply Reply Quote 1
                          • D Offline
                            DustinB @florent
                            last edited by

                            @florent said in Import from VMware:

                            @Olest
                            that's a nice catch, every day I discover new limits of the vmware licensing . At least we could catch the error and show something useful to the user

                            Just wait, everything free from VMWare is going away, so it'll just be the assumption that if you should be able to do it, you won't be able to.

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