How to move a virtual machine or image from one RHEV environment to another?

Latest response

I want to copy an image from one RHEV environment (running RHEV 3.5) to another environment (running RHEV 4.0).

What is the proper way to accomplish this?

Thanks,

Paul

Responses

I'd suggest export/import using an NFS based Export Storage Domain

That would the logical way to do it but neither domain has an Export Domain available to it.

The 'proper' way would be to use an export domain, as stated previously. However, if you don't have access to an export domain, you could try using Rear (relax-and-recover) to perform a v2v migration using a simple ISO domain, as demonstrated here:

http://blog.mit.bme.hu/meszaros/en/unix/ovirt-p2v-using-rear

Actually, I was able to create a temporary export domain in both environments, so that should simplify things more and it can be done the "proper" way. I put the export domain of the domain I want to move into maintenance mode, then detached it. I went to the "Storage" tab in the other RHEVM, the one I want to export to, and clicked on "Import Domain", enter the appropriate information for the NFS export share on the other server. But I keep getting a "Failed to retrieve existing storage domain information" error. The RHEVM I'm exporting from is RHEV 3.5, and the one I'm trying to import into is RHEV 4.0. Could this error possible be related to the version mismatch?

I'd double check the permissions on your NFS export and the underlying file system to ensure proper ownership and mode. If the path and permissions are correct, there may well be a compatibility issue between the versions

These are the contents of the folder - they were set by the RHEVM automatically so I assume they're correct:

[root@hostname temp-exports]# ll -lZ . drwxr-xr-x. vdsm kvm system_u:object_r:nfs_t:s0 3a055cae-a91b-4834-8a21-c57f2aa36353 -rwxr-xr-x. vdsm kvm system_u:object_r:nfs_t:s0 DIRECT_IO_TEST drwx------. root root system_u:object_r:file_t:s0 lost+found

These are the permissions on the folder itself: I just created the folder and then did "chown 36:36 temp-exports" on it. [root@hostname temp-exports]# ll -ldZ . drwxr-xr-x. vdsm kvm system_u:object_r:nfs_t:s0

This is the way its set in /etc/exports:

/temp-exports 0.0.0.0/0.0.0.0(rw)

Sorry, that formatting came through looking horrible - let's try again:

These are the contents of the folder - they were set by the RHEVM automatically so I assume they're correct:

[root@hostname temp-exports]# ll -lZ .

drwxr-xr-x. vdsm kvm system_u:object_r:nfs_t:s0 3a055cae-a91b-4834-8a21-c57f2aa36353

-rwxr-xr-x. vdsm kvm system_u:object_r:nfs_t:s0 DIRECT_IO_TEST

drwx------. root root system_u:object_r:file_t:s0 lost+found

These are the permissions on the folder itself: I just created the folder and then did "chown 36:36 temp-exports" on it.

[root@hostname temp-exports]# ll -ldZ .

drwxr-xr-x. vdsm kvm system_u:object_r:nfs_t:s0

This is the way its set in /etc/exports:

/temp-exports 0.0.0.0/0.0.0.0(rw)

Also, as a test, if I try to mount the remote NFS share from a command line, it does seem to mount without a problem

If anyone has been following this thread and facing a similar situation, I had opened a support ticket with Redhat and the issue was indeed a compatibility problem. The source environment turned out to actually be RHEV version 3.3 and images created in that environment can't be exported to a RHEV version 4.0 environment. It was possible to jump through a bunch of hoops to upgrade the version levels, but since it was only a single image that needed to be moved over, I just built a new one from scratch instead.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.