Bug 1625543
| Summary: | After importing KVM VM the actual size is bigger than the virtual size | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Steven Rosenberg <srosenbe> | |
| Component: | vdsm | Assignee: | Dan Kenigsberg <danken> | |
| Status: | CLOSED ERRATA | QA Contact: | Nisim Simsolo <nsimsolo> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 4.2.0 | CC: | bigsow, eblake, emarcus, eshenitz, jsuchane, lsurette, mavital, michal.skrivanek, mprivozn, mtessun, nsimsolo, nsoffer, pvilayat, rbarry, rdlugyhe, Rhev-m-bugs, rjones, srevivo, srosenbe, tburke, tnisan, ycui | |
| Target Milestone: | ovirt-4.3.0 | Keywords: | ZStream | |
| Target Release: | --- | Flags: | mavital:
needinfo+
lsvaty: testing_plan_complete- |
|
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Enhancement | ||
| Doc Text: |
When Importing KVM VMs and Sparseness is specified, the actual Disk Size should be preserved to improve the performance of the Import as well as to conserve disk space on the Destination Storage Domain. Previously, when you set thin provisioning for importing a KVM-based VM into a Red Hat Virtualization environment, the disk size of the VM within the Red Hat Virtualization storage domain was inflated to the volume size or larger, even when the original KVM-based VM was much smaller.
KVM Sparseness is now supported so that when you import a virtual machine with thin provisioning enabled into a Red Hat Virtualization environment, the disk size of the original virtual machine image is preserved. However, KVM Sparseness is not supported for Block Storage Domains.
|
Story Points: | --- | |
| Clone Of: | 1587892 | |||
| : | 1628477 (view as bug list) | Environment: | ||
| Last Closed: | 2019-05-08 12:38:08 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 1587892, 1628477 | |||
| Bug Blocks: | ||||
flags,please *** Bug 1587892 has been marked as a duplicate of this bug. *** verified_upstream: ovirt-engine-4.3.0-0.0.master.20181023141116.gitc92ccb5.el7 vdsm-4.30.1-25.gitce9e416.el7.x86_64 libvirt-client-4.5.0-10.el7.x86_64 qemu-kvm-ev-2.10.0-21.el7_5.7.1.x86_64 sanlock-3.6.0-1.el7.x86_64 Verification scenario: 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: rhv-devops 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. https://access.redhat.com/errata/RHEA-2019:1085 sync2jira sync2jira |
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: /var/lib/libvirt/images A sample output is as follows: [root@sla-leonard ~]# qemu-img info /var/lib/libvirt/images/generic.qcow2 image: /var/lib/libvirt/images/generic.qcow2 file format: qcow2 virtual size: 20G (21474836480 bytes) disk size: 3.3M cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: true refcount bits: 16 corrupt: false 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): qemu+ssh://root@HostName/system 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.