Deploying RHEV pt6 (Importing vSphere VMs)

Yep, you read that correctly folks. I’m going to show you how to import VMs from vSphere into RHEV, right from RHEV-M. Why would you want to do that?? For starters, maybe you simply want to move virtualization platforms. You have some virtual machines that you happen to like, you just don’t feel like rebuilding them from scratch. That doesn’t make you lazy at all. It means you’re planning. Or maybe a little lazy, but mostly that you don’t want to do your work over if there wasn’t anything wrong with it in the first place.

Work smarter, not harder.

In previous versions of RHEV, the “virt-v2v” tool was there, it just happened to be a command line tool that also required an intermediary host. The tool worked, but it wasn’t exactly convenient as it meant you had to step out of the RHEV-M management tool. Now you can import VMs en masse right from the “Virtual Machines” tab in RHEV-M. BOOM!

And yes, that would include both RHEL and Windows VMs.

The process is straightforward: click the “Import” button, provide the credentials for the vCenter environment and RHEV does a scan of the data store. Once complete, it provides a list of VMs that are shutdown and therefore available to be copied and converted. RHEL includes the necessary “virtio” drivers by default, and the Windows “virtio” driver can be added in just prior to the final import “OK”.

In the demo below, I highlight one each RHEL and Windows VM, but you can certainly import many VMs at once. The time that it takes is completely dependent on network bandwidth, VM size, thin provisioning vs pre-allocation, as well as read/write speeds (respectively) on both ends of the storage.

Let’s check out the video (best viewed in full screen):

That’s it. Really. It doesn’t get much simpler than that. I will say that you might want to coordinate a large import batch with your lunch schedule, but hopefully you can see the benefit of this tool.

As always, feel free to comment or ask questions.

Hope this helps,

Captain KVM

(And a big thanks to my colleagues Meital and Nisim for loaning me their lab for this demo!)

6 thoughts on “Deploying RHEV pt6 (Importing vSphere VMs)”

    1. Hi there,

      Thanks for stopping by. For the import tool in RHEV-M, it goes through vSphere, so you’ll likely not be able to use it if you’re only using the ESXi hypervisor without vCenter. HOWEVER, there is a command line version of the tool (virt-v2v) available that will work just fine with ESXi.

      Captain KVM

  1. I tried following your video to add our vSphere (5.5) as an external provider but the test fails and the logs show a 5050 error (which seems to be generic) are there any prerequisites on the VMware side which are needed to allow ovirt to connect?

  2. Hi, I am trying this but I can’t add vCenter as external provider because of missing certification. The docs say RHVM should ask to import certificate but it doesn’t. Do you know how can I import manually the vCenter certificate?

    1. Hi Nillo,

      Did you try with a different browser? I’ve seen some oddities with different browsers, honestly. Or check your popup blocker. If after all of that (should take 5 minutes total to check both), if it still doesn’t ask for the cert, open a support ticket.

      Captain KVM

Agree? Disagree? Something to add to the conversation?