importing a qcow2 disk into ovirt 3.5?
On 21/10/14 02:27, Paul Jansen wrote: >>>I've just been doing some search= ing to try and work out how to get a >>>vmware windows VM into ovirt. >>>It= seems that the newest virtv2v has dropped support for importing >>>from an= ESXi standalone machine - and now only works with vcenter. I >>>didn't ha= ve any success with using the current virt-v2v attaching to >>>an ESXi host= . >>>>>>I've prepared the VM by first removing the vmware tools and have >>= installled the various virtio drivers, as well as running the >>>'mergeide= ' registry file to enable IDE. I've used 'qemu-img' to >>>convirt this VMD= K file to QCOW2. It does not appear that there is a >>>straightforward way= for me to import this new qcow2 disk into ovirt. >>>>>>It seems my best op= tion at the moment is to export the VMware VM as >>>an OVA and then try and= use a newer virt-v2v to import this into ovirt. >>>Alternatively I could c= onstruct a VM in virt-manager and attach the >>>converted qcow2 disk to it, and then use virt-v2v to import this into >>>ovirt. >>>>>>Can someo= ne suggest an alternative course of action? It seems >>>strange that I can= 't just import a disk into ovirt, construct a VM >>>and attach the disk. >=
Is there anything int he works to make this process easier? >>>>>>Than= ks, >>>Paul >>>=0A>Wrote this awhile back as a quick qcow to ovf implementa= tion to import =0A>into ovirt-engine/rhevm. There are newer options but thi= s does the job =0A>really quick. Will wrap the qcow image into an exploded = ova structure or =0A>zipped. You can then import it directly into engine wi=
--653554528-719396241-1414055098=:11942 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable th =0A>engine-image-uploader.=0A> >https://jboggs.fedorapeople.org/guest-im= age-ovf-creator.py =0AThanks for all the replies with suggestions on how to= tackle this.=0A=0AI've tried Joey's script above and it does the trick nic= ely.=0AHaving 'qemu-img', Joey's script referenced above plus engine-image-= uploader on a machine allowed me to convert a VMDK file to QCOW2 and then p= ush the resulant QCOW2 disk - wrapped in a basic VM - up to my ovirt export= domain.=0AFrom there I was able to import it as a template, and then creat= e a machine based on that template.=0AThis was relatively simple.=0A=0AI'm = looking forward to seeing some integration in the oVirt UI that may handle = this in future.=0AI have a VMware vcenter installation and often use the 'd= eploy from OVF template' menu item - which I just pass a http URI with the = OVF/OVA and have it deploy a VM on my cluster. This would be great to see = in ovirt. --653554528-719396241-1414055098=:11942 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><body><div style=3D"color:#000; background-color:#fff; font-family:He= lveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, Sans-Serif;fo= nt-size:12px"><pre style=3D"" class=3D"">>><i style=3D"" class=3D""> = On 21/10/14 02:27, Paul Jansen wrote:=0A</i>>>><i style=3D"" class= =3D""> I've just been doing some searching to try and work out how to get a= =0A</i>>>><i style=3D"" class=3D""> vmware windows VM into ovirt.= =0A</i>>>><i style=3D"" class=3D""> It seems that the newest virtv= 2v has dropped support for importing =0A</i>>>><i style=3D"" class= =3D""> from an ESXi standalone machine - and now only works with vcenter. = I =0A</i>>>><i style=3D"" class=3D""> didn't have any success with= using the current virt-v2v attaching to =0A</i>>>><i style=3D"" c= lass=3D""> an ESXi host.=0A</i>>>><i style=3D"" class=3D"">=0A</i>= >>><i style=3D"" class=3D""> I've prepared the VM by first removin= g the vmware tools and have =0A</i>>>><i style=3D"" class=3D""> in= stallled the various virtio drivers, as well as running the =0A</i>>>= ><i style=3D"" class=3D""> 'mergeide' registry file to enable IDE. I've= used 'qemu-img' to =0A</i>>>><i style=3D"" class=3D""> convirt th= is VMDK file to QCOW2. It does not appear that there is a =0A</i>>>&= gt;<i style=3D"" class=3D""> straightforward way for me to import this new = qcow2 disk into ovirt.=0A</i>>>><i style=3D"" class=3D"">=0A</i>&g= t;>><i style=3D"" class=3D""> It seems my best option at the moment i= s to export the VMware VM as =0A</i>>>><i style=3D"" class=3D""> a= n OVA and then try and use a newer virt-v2v to import this into ovirt.=0A</= i>>>><i style=3D"" class=3D""> Alternatively I could construct a V= M in virt-manager and attach the =0A</i>>>><i style=3D"" class=3D"= "> converted qcow2 disk to it, and then use virt-v2v to import this into = =0A</i>>>><i style=3D"" class=3D""> ovirt.=0A</i>>>><i st= yle=3D"" class=3D"">=0A</i>>>><i style=3D"" class=3D""> Can someon= e suggest an alternative course of action? It seems =0A</i>>>><i = style=3D"" class=3D""> strange that I can't just import a disk into ovirt, = construct a VM =0A</i>>>><i style=3D"" class=3D""> and attach the= disk.=0A</i>>>><i style=3D"" class=3D"">=0A</i>>>><i sty= le=3D"" class=3D""> Is there anything int he works to make this process eas= ier?=0A</i>>>><i style=3D"" class=3D"">=0A</i>>>><i style= =3D"" class=3D""> Thanks,=0A</i>>>><i style=3D"" class=3D""> Paul= =0A</i>>>><br style=3D"">>Wrote this awhile back as a quick qco= w to ovf implementation to import =0A>into ovirt-engine/rhevm. There are= newer options but this does the job =0A>really quick. Will wrap the qco= w image into an exploded ova structure or =0A>zipped. You can then impor= t it directly into engine with =0A>engine-image-uploader.=0A>=0A<a st= yle=3D"" class=3D"" href=3D"https://jboggs.fedorapeople.org/guest-image-ovf= -creator.py">>https://jboggs.fedorapeople.org/guest-image-ovf-creator.py= </a>=0A<br>Thanks for all the replies with suggestions on how to tackle thi= s.<br style=3D"" class=3D""></pre><pre style=3D"" class=3D"">I've tried Joe= y's script above and it does the trick nicely.<br>Having 'qemu-img', Joey's= script referenced above plus engine-image-uploader on a machine allowed me= to convert a VMDK file to QCOW2 and then push the resulant QCOW2 disk - wr= apped in a basic VM - up to my ovirt export domain.<br>From there I was abl= e to import it as a template, and then create a machine based on that templ= ate.<br>This was relatively simple.<br><br>I'm looking forward to seeing so= me integration in the oVirt UI that may handle this in future.<br>I have a = VMware vcenter installation and often use the 'deploy from OVF template' me= nu item - which I just pass a http URI with the OVF/OVA and have it deploy = a VM on my cluster. This would be great to see in ovirt.<br><br></pre></di= v></body></html> --653554528-719396241-1414055098=:11942--
participants (1)
-
Paul Jansen