[Users] How to import KVM machines into oVirt iSCSI
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. -- Nicolas Ecarnot
On 01/30/2013 11:43 AM, 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.
Hi Nicolas, you can attach NFS export domain to iSCSI data-center. There is no need to have same export domain type as your data-center has. I hope it will help you to solve your problem. Kuba
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@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.
Le 30/01/2013 12:00, René Koch (ovido) a écrit :
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
Thank you to Alex, Jakub (you were right, an NFS export domain is OK with an iSCSI data center), and René. - On a separate server, I created a NFS shared space. - On oVirt web gui, I created a new export domain, plugged on the NFS space. - I activated it, linked it to my iSCSI data center. - On the oVirt manager, I installed virt-v2v and its numerous dependencies. Seemless. - Converting a domain using René's advices went all right (thank you). - Importing into oVirt was also OK. All those actions were related to linux VMs. Now, the problem comes with migrating windows vmachines. I read here at 3.3.1.2 : https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Virtualiza... that I had to install three things, more or less optional : - virtio-win (this one seems mandatory, as I'm getting the error : virt-v2v: blah blah blah missing : /usr/share/virtio-win/drivers/i386/WinXP or whatever windows OS - I tried many) - libguestfs-winsupport (I don't know whether it is mandatory, as I'm hitting the bug above.It seems important as it seems related to the file system, so quite useful) - Guest Tools ISO (this one seems to be similar to VmWare tools, if I understood it well), so I don't know if it's an improvement only, neither where to find it for oVirt and Fedora. Regards, -- Nicolas Ecarnot
Le 04/02/2013 16:17, Nicolas Ecarnot a écrit :
Now, the problem comes with migrating windows vmachines. I read here at 3.3.1.2 : https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Virtualiza...
that I had to install three things, more or less optional : - virtio-win (this one seems mandatory, as I'm getting the error : virt-v2v: blah blah blah missing : /usr/share/virtio-win/drivers/i386/WinXP or whatever windows OS - I tried many) - libguestfs-winsupport (I don't know whether it is mandatory, as I'm hitting the bug above.It seems important as it seems related to the file system, so quite useful) - Guest Tools ISO (this one seems to be similar to VmWare tools, if I understood it well), so I don't know if it's an improvement only, neither where to find it for oVirt and Fedora.
Regards,
Hu ho, I think I hit this bug : http://thr3ads.net/libguestfs/2011/11/1623975-Virtio-win-RPM and http://thr3ads.net/libguestfs/2011/11/1624040-Windows-P2V-migration-temporar... I have a RHN account, so I was able to download the missing virtio-win rpm and install it on F17 (seemless). Import is now working for windows guest, though some more errors are to be treated manually (eth virtio errors), but harmless. -- Nicolas Ecarnot
On 05/02/2013 17:45, Nicolas Ecarnot wrote:
Le 04/02/2013 16:17, Nicolas Ecarnot a écrit :
Now, the problem comes with migrating windows vmachines. I read here at 3.3.1.2 : https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Virtualiza...
that I had to install three things, more or less optional : - virtio-win (this one seems mandatory, as I'm getting the error : virt-v2v: blah blah blah missing : /usr/share/virtio-win/drivers/i386/WinXP or whatever windows OS - I tried many) - libguestfs-winsupport (I don't know whether it is mandatory, as I'm hitting the bug above.It seems important as it seems related to the file system, so quite useful) - Guest Tools ISO (this one seems to be similar to VmWare tools, if I understood it well), so I don't know if it's an improvement only, neither where to find it for oVirt and Fedora.
Regards,
Hu ho, I think I hit this bug :
http://thr3ads.net/libguestfs/2011/11/1623975-Virtio-win-RPM and http://thr3ads.net/libguestfs/2011/11/1624040-Windows-P2V-migration-temporar...
I have a RHN account, so I was able to download the missing virtio-win rpm and install it on F17 (seemless). Import is now working for windows guest, though some more errors are to be treated manually (eth virtio errors), but harmless.
how about wiki-fying this thread for others? Thanks, Itamar
Le 06/02/2013 11:20, Itamar Heim a écrit :
Hu ho, I think I hit this bug :
http://thr3ads.net/libguestfs/2011/11/1623975-Virtio-win-RPM and http://thr3ads.net/libguestfs/2011/11/1624040-Windows-P2V-migration-temporar...
I have a RHN account, so I was able to download the missing virtio-win rpm and install it on F17 (seemless). Import is now working for windows guest, though some more errors are to be treated manually (eth virtio errors), but harmless.
how about wiki-fying this thread for others?
Thanks, Itamar
Hi Itamar, Hi people, I don't know if your proposal was directed to me, but I just *found* this thread, but never wrote anything into it, so you'd better ask concerned people about their writings. Regards, -- Nicolas Ecarnot
Hi, How can I install virtio-win and libguestfs-winsupport , it looks like a RHEV package not a ovirt package.
participants (5)
-
Itamar Heim -
Jakub Libosvar -
Jose -
Nicolas Ecarnot -
René Koch (ovido)