1. To test this feature, one needs to first set up a KVM Host. This may be performed via the Virtual Machine Manager which can connect to a remote machine for saving KVM VMs.
One can check the Volume and Disk size of the VM image file via the following command:
qemu-img info <file Image>
One can find the image file here:
A sample output is as follows:
[root@sla-leonard ~]# qemu-img info /var/lib/libvirt/images/generic.qcow2
file format: qcow2
virtual size: 20G (21474836480 bytes)
disk size: 3.3M
Format specific information:
lazy refcounts: true
refcount bits: 16
2. Enter the WebAdmin oVirt Open Visualization Manager. Enter the Compute >> Virtual Machines tab. At the far right on the screen after the Create Snapshot button are three vertical dots. Please press on the button with the three vertical dots and choose Import on the drop down list. Choose the Data Center, Change the Source Drop Down List to KVM (Via Libvirt). Enter the URI, User and Password of the KVM Host and click on the Load button.
Note: at least one VM has to be running in the Data Center.
The URI should be in the following format (replacing HostName with the IP Address or Host Name of the KVM Host):
3. One should see the list of virtual machines available in the “Virtual Machines on Source” List Box on the left side. Please choose the VMs to be imported to oVirt, press the right arrow button so that the VMs chosen appear in the “Virtual Machines to Import” List Box on the right side and press the Next button.
4. Ensure the Allocation Policy is set to “Thin Provision” and choose the OK button.
5. Wait for the Import to succeed.
6. One can check the file on the storage domain to verify the Disk Size matches the original.
*** Bug 1587892 has been marked as a duplicate of this bug. ***
Polarion TC added to external trackers.
INFO: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:
[Project 'vdsm'/Component 'ovirt-engine' mismatch]
For more info please contact: firstname.lastname@example.org
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.