Created attachment 1164035 [details] import vm using virtual appliance vmware OVA Description of problem: rhevm-image-uploader document should be more precise as to what kind of OVA appliances can be imported to RHEV. Version-Release number of selected component (if applicable): 3.6.0 How reproducible: 01643354 & 01637397 cases are opened for asking process on how to import as new VM in RHEV using Virtual appliance (VMware OVA) as it fails to import and we do not have documentation available in RHEV 3.6. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
We will be moving to the UI\REST image uploader in 4.0 the tool will be deprecated. Please make sure to include the types of images you can import using that.
In the upload\download API we support RAM\QCOW2. For v2v, Arik can you please answer?
(In reply to Yaniv Dary from comment #2) > In the upload\download API we support RAM\QCOW2. > For v2v, Arik can you please answer? Since we tested only OVAs with VMDK disks, I believe that's what should be stated in the documentation.
(In reply to Yaniv Dary from comment #2) Correction: > In the upload\download API we support RAW\QCOW2.
Assigning to Emma for review. Emma, let's look at adding this information in 4.1 and 4.0 if possible.
In the Admin Guide, 11.6.7. Uploading and Downloading a Disk Image to a Storage Domain clearly states that only RAW and QCOW2 are supported. https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html-single/administration_guide/#Uploading_a_Disk_Image_to_a_Storage_Domain Therefore, the only documentation that needs to be clarified is the v2v section in the Virtual Machine Management Guide.
Hey Nisim This bug is in order to document what formats the various import methods support. For vmware, Arik told me v2v was only tested on vmdk for VMWare but he wasn't sure about Xen. Could you please let me know what disk format you tested to import vms from Xen using v2v?
Hi Emma Xen disk formats tested for v2v from Xen are raw, qcow and qcow2
Hi Richard and Martin, Nisim suggested I ask you whether v2v is meant to support importing VMs with vmdk disk format from Xen. Currently he has tested qcow qcow2 and raw, but vmdk doesn't work.
(In reply to Emma Heftman from comment #15) > Hi Richard and Martin, Nisim suggested I ask you whether v2v is meant to > support importing VMs with vmdk disk format from Xen. We only support RHEL 5 Xen, which generates neither OVAs nor VMDK. So I'm guessing you're talking about some other (not supported) version of Xen. There is a bug to support other versions of Xen (bug 1253593) Also when reporting a bug, please collect the full ‘virt-v2v -v -x’ output. For RHV 4.1, see: http://libguestfs.org/virt-v2v.1.html#debugging-rhv-m-import-failures
(In reply to Richard W.M. Jones from comment #16) > (In reply to Emma Heftman from comment #15) > > Hi Richard and Martin, Nisim suggested I ask you whether v2v is meant to > > support importing VMs with vmdk disk format from Xen. > > We only support RHEL 5 Xen, which generates neither OVAs nor VMDK. > > So I'm guessing you're talking about some other (not supported) > version of Xen. There is a bug to support other versions of Xen > (bug 1253593) > > Also when reporting a bug, please collect the full ‘virt-v2v -v -x’ > output. For RHV 4.1, see: > http://libguestfs.org/virt-v2v.1.html#debugging-rhv-m-import-failures Hi Richard, I am indeed talking about RHEL 5 Xen. So assuming the following is correct, I would like to add Nisim's findings which is that we can currently successfully import RAW, QCOW and QCOW2. Is this correct? This is what is currently documented: 6.12.5. Importing a Virtual Machine from a Xen Host Import virtual machines from Xen on Red Hat Enterprise Linux 5 to your Red Hat Virtualization environment. Red Hat Virtualization uses V2V to import virtual machines. The virt-v2v package must be installed on at least one host (referred to in this procedure as the proxy host). The virt-v2v package is available by default on Red Hat Virtualization Hosts (RHVH) and is installed on Red Hat Enterprise Linux hosts as a dependency of VDSM when added to the Red Hat Virtualization environment. Red Hat Enterprise Linux hosts must be Red Hat Enterprise Linux 7.2 or later. Note The virt-v2v package is not available on the ppc64le architecture and these hosts cannot be used as proxy hosts.
(In reply to Emma Heftman from comment #17) > Hi Richard, I am indeed talking about RHEL 5 Xen. So assuming the following > is correct, I would like to add Nisim's findings which is that we can > currently successfully import RAW, QCOW and QCOW2. Is this correct? I checked the source of v2v and on the RHEL 5 Xen path it basically takes whatever source format is declared by Xen and tries to use it without interpreting it. Developers have only tested raw format, so it's good to know that (old) qcow and qcow2 also work. I also checked RHEL 5 Xen itself to see what formats were supported. There were other formats that in theory could have been used, including "vmdk" (but note this driver was known to be very broken, Red Hat rewrote and fixed that driver extensively, long after RHEL 5 was released). If we need to document this at all, then maybe we should only mention raw and qcow2 (not old qcow which was also a semi-broken format). Can we simply not document it? > Note > The virt-v2v package is not available on the ppc64le architecture and these > hosts cannot be used as proxy hosts. This is going to be fixed in Pegas 1.1, hopefully ...
Yaniv/Martin Please let me know what you would like me to document for Xen, if at all. QCOW2 and RAW?
Martin, can you please reply based on what is supported and tested in the platform Virt QE?
Hi Yaniv, Emma, (In reply to Yaniv Lavi (Dary) from comment #21) > Martin, can you please reply based on what is supported and tested in the > platform Virt QE? as already said by Richard in comment #18 v2v from RHEL5 XEN does take whatever disk is there and does not try interpreting it. So RAW format is the only tested one, but I would expect that qcow2 works as well esp. as Nisim seems to have tested it successfully according to comment #14. I would not document support for qcow due to the reasons mentioned by Richard earlier. Thanks! Martin
Please document both RAW\QCOW in the same pragmatic language that Martin used.
Now published at https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/virtual_machine_management_guide/sect-exporting_and_importing_virtual_machines_and_templates#Importing_a_Virtual_Machine_from_a_VMware_Provider and https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.0/html/virtual_machine_management_guide/sect-exporting_and_importing_virtual_machines_and_templates#Importing_a_Virtual_Machine_from_a_VMware_Provider