[Users] How to import KVM machines into oVirt iSCSI
René Koch (ovido)
r.koch at ovido.at
Wed Jan 30 11:00:28 UTC 2013
Hi,
The following command migrates a KVM vm named "test-rhel6" to your
export domain "ovirt-engine:/data/nfs/export" with qcow2, thin
provisioned disk and ovirtmgmt-network from KVM host "kvm-host":
# virt-v2v -i libvirt -ic qemu+ssh://root@kvm-host/system -o rhev -os
ovirt-engine:/data/nfs/export -of qcow2 -oa sparse -n ovirtmgmt
test-rhel6
See "virt-v2v --help" for details...
You can also create a profile in /etc/virt-v2v.conf to avoid command
line arguments for virt-v2v...
For migration you need an export domain which must be NFS (not iSCSI).
So the migration steps are:
1. create export domain
2. activate export domain on datacenter
3. install virt-v2v on ovirt engine host
4. migrate host to export domain
5. import vm from export domain
--
Best Regards
René Koch
Senior Solution Architect
============================================
ovido gmbh - "Das Linux Systemhaus"
Brünner Straße 163, A-1210 Wien
Phone: +43 720 / 530 670
Mobile: +43 660 / 512 21 31
E-Mail: r.koch at ovido.at
============================================
On Wed, 2013-01-30 at 11:43 +0100, Nicolas Ecarnot wrote:
> Hi,
>
> Reading the docs all day long helped me to setup a nice Data center in
> iSCSI mode, connected to a big LUN in a san.
> Many many points are working, mostly thanks to you, people of this list.
>
> Apart from this oVirt setup (1 manager, 3 nodes, 1 san), I have a
> completely separated ubuntu hypervisor running a standalone local KVM
> with a local storage.
>
> I have not a clear view of how I will manage to import these VM into oVirt.
>
> Of course, I've read about ovirt-v2v (and its huge amount of
> dependencies...), but I'm not sure this is the way I have to follow?
> As far as I've understood, v2v seems to be dedicated to connection
> between oVirt datacenters, or vmware or Xen plateforms, but I see
> nothing about the connection to a distant standalone KVM hypervisor.
>
> One more thing that is unclear to me, and seems related, is the notion
> of export / import domain. I read that this principle could allow me to
> export (then to backup) my VMs. This could help me to import some VMs.
> But I read that this export domain has to be the same type of my
> datacenter (iscsi), so this is not helping me with my standalone kvm
> hypervisor.
>
> I'd be glad to get some light on these points.
>
More information about the Users
mailing list