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

    Migrating RHEL from VMWare - disks not showing up

    Scheduled Pinned Locked Moved Solved Advanced features
    4 Posts 3 Posters 471 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.
    • R Offline
      rporter
      last edited by

      I'm testing XCP-ng/XOA as a possible replacement for vmware, and have run into an issue with the online migration.

      Because of a prior issue, I have created an NFS datastore and successfully migrated a few Windows machines. Any machine that I'm trying to migrate, I first vmotion to the NFS datastore. We're running VSphere 7.0u3, with hosts running ESXi 7.0u3 as well

      Now I'm testing with a few RHEL machines. They are on VM hardware version 11 and running RHEL 7 or 8.

      After migration, the VMs disks don't show up and it boots into emergency mode. There are no sda, sdb, etc items in the /dev directory

      The source was using a vmware Paravirtual driver, which I thought was the problem, but the issue continues even after switching it to an LSI Logic SAS controller

      The import task succeeds and the disks are there and connected to the VM, the OS just doesn't seem to be able to see it.

      Any suggestions, or am I stuck with exporting to OVF, converting the OVF to OVA, and importing on the Xen side?

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

        Hi,

        Have you read this part? https://docs.xcp-ng.org/installation/migrate-to-xcp-ng/#ova

        It's likely your RHEL doesn't have the Xen PV drivers in the kernel. Just follow the instructions there and it should work 🙂

        R 1 Reply Last reply Reply Quote 1
        • I Offline
          imaginapix @rporter
          last edited by

          @rporter

          Are there really no disks or just not under the expected name /dev/sd....

          You might check if there are /dev/xvd.... devices. This change can happen because XCP-NG and VMware handle the "hardware" differently. Had the same problem with some VMs and it also changed

          This effect also can change the network interface name, so you might check that too.

          1 Reply Last reply Reply Quote 0
          • R Offline
            rporter @olivierlambert
            last edited by

            @olivierlambert

            That did it

            Tested with both the LSI and Paravirtual - both succeeded

            Thanks

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