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

    Import VM From VMware - A Few Issues (Lnx Boot Issue, No IP in Lnx, CD ROM Eject Error)

    Scheduled Pinned Locked Moved Solved Management
    8 Posts 2 Posters 121 Views
    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
      coolsport00
      last edited by coolsport00

      I used the XO "Import From VMware" tool. I performed this on 3 VMs with no issues encountered during import. But, post-import, there are some as noted in the following:

      1. On 2 Ubuntu VMs, v22.04 and v24.04, I am unable to boot the VM after import because XO assigns the VMs the "secure boot" option. The VMs are not configured for Secure Boot in VMware. I disable this option in VM > Adv tab, reboot and it then boots ok, but this is an issue which should be addressed. Maybe it's only for UEFI-based VMs?
      2. When attempting to install Guest Tools via ISO. I can attach the ISO to the VM, but when I run the "sudo mount /dev/cdrom" cmd, it states "special device /dev/cdrom does not exist".
      3. I then try to eject the ISO and receive an error like "<some character string>/vbd.xvdd does not exist in xenopsd."
      4. The NIC of these imported Linux VMs is down after import...not sure why. I place it "up", but even so...they do not receive an IP address. I imported a Windows 2022 server and it did get an IP address, but it also has the eject ISO error as well.

      Any thoughts on how to resolve these issues. If I choose to migrate from VMware,, this would be a huge deterrent to doing so.
      Thanks!

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

        @olivierlambert -
        I have resolved the CD device eject error/issue...by guessing 😉 To resolve the above error, for any VMware VM that is either migrated (V2V) into XO or imported (via .ova file), do the following:

        1. After migration or import, power the VM on if not already.
        2. Resolve the NIC issue (for Linux; see the Netplan discussion above) and verify the VM (Windows and Linux) attain an IP
        3. Install the XO Guest Tools for Windows downloaded from the Citrix site and via install cmd for Linux (Ubnt = sudo apt install xe-guest-utilities -y) and reboot the VM(s)
        4. Once the VM is up and you confirm Tools is installed, simply power down the VM, then power it back on. For Windows VMs, if an ISO was connected when shutting down, it will be disconnected upon startup. You can test connect and disconnect an ISO and it should eject fine; for Linux, if an ISO was connected when shutting down, it will still be connected, but you should now be able to eject the ISO.
        5. Also note, I had the mount error in Linux VMs with the /dev/cdrom as well, but that error also gets resolved after performing the VM shutdown

        Thanks!

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

          I did some researching on possible resolutions -> running the xe vm-cd-eject cmd on the XCP Host doesn't work..I get the same error as in XO. I also verified the VMs I migrated from VMW did NOT have an ISO attached to them prior to migration. I should also say I got this same behavior even if I exported the VMW VMs to .ova then import them to XO.

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

            I was able to find a post which discussed the known NIC issue in Linux imported VMs (by Brandon Lee):
            https://www.virtualizationhowto.com/2024/02/migrate-from-vmware-to-xcp-ng-a-vsphere-admins-perspective/

            It kinda makes sense I guess why this happens -> the NIC is given a static name in Netplan initially when the VM is created. When the VM is migrated/imported into XO, this Netplan NIC name is NOT changed in the Netplan .yml file during migration, thus the OS can't get an IP. To rectify this, change the name XO gives the NIC in the Linux OS (eth0 for Ubnt2204 or enX0 for Ubnt2404) in the .yml file, reboot the VM, then you'll be able to get an IP if you use DHCP. You can then also install Guest Tools by using a pkg mgr (apt for Ubnt).

            The only remaining problem I'm having now is the CD eject issue. And again..this is on both imported Linux and Windows VMs.

            1 Reply Last reply Reply Quote 0
            • C coolsport00 marked this topic as a question
            • C Offline
              coolsport00
              last edited by

              @olivierlambert -
              I have resolved the CD device eject error/issue...by guessing 😉 To resolve the above error, for any VMware VM that is either migrated (V2V) into XO or imported (via .ova file), do the following:

              1. After migration or import, power the VM on if not already.
              2. Resolve the NIC issue (for Linux; see the Netplan discussion above) and verify the VM (Windows and Linux) attain an IP
              3. Install the XO Guest Tools for Windows downloaded from the Citrix site and via install cmd for Linux (Ubnt = sudo apt install xe-guest-utilities -y) and reboot the VM(s)
              4. Once the VM is up and you confirm Tools is installed, simply power down the VM, then power it back on. For Windows VMs, if an ISO was connected when shutting down, it will be disconnected upon startup. You can test connect and disconnect an ISO and it should eject fine; for Linux, if an ISO was connected when shutting down, it will still be connected, but you should now be able to eject the ISO.
              5. Also note, I had the mount error in Linux VMs with the /dev/cdrom as well, but that error also gets resolved after performing the VM shutdown

              Thanks!

              1 Reply Last reply Reply Quote 0
              • C coolsport00 has marked this topic as solved
              • olivierlambertO Offline
                olivierlambert Vates 🪐 Co-Founder CEO
                last edited by

                Thanks for your feedback. Adding @thomas-dkmt in the loop in case we want to document that somewhere 🙂

                C 1 Reply Last reply Reply Quote 1
                • C Offline
                  coolsport00 @olivierlambert
                  last edited by coolsport00

                  @olivierlambert No problem at all. I'm documenting as I go. I have some feature requests I think should be added to XO to make it more intuitive. How do I go about doing that? Create a post here or submit somewhere else?
                  Thanks.

                  UPDATE: I see in the XO docs on how to:
                  https://beta.xen-orchestra.com/docs/community.html#feature-requests
                  Seems it's best to do so here with relevant info. I'll do it in batches so as not to overload on volume of posts 😄

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

                    If you take time to explain functionally your issue, go to https://github.com/vatesfr/xen-orchestra/issues (search first if it exists already, otherwise create a new issue).

                    Thanks!

                    C 1 Reply Last reply Reply Quote 0
                    • C Offline
                      coolsport00 @olivierlambert
                      last edited by

                      @olivierlambert Ok, will do. Thanks!

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