RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 498870 [details]
rhevm.log

Description of problem:
The VM gets inflated after several migrations.

Version-Release number of selected component (if applicable):
RHEVM ic114
vdsm-4.9-64.el6.x86_64
libvirt-0.8.7-18.el6.x86_64
qemu-kvm-0.12.1.2-2.161.el6.x86_64
lvm2-2.02.83-3.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Have two hosts and VM with 2GB thin provisioned disk.
2. Migrate the VM. VM usually gets paused.
2. Migrate more times.
  
Actual results:
VM inflates from 1GB to 2GB and more, until the storage domain is full.

Expected results:
VM doesn't grow after migration.

Additional info:
Note there are some bugs possibly related in the see also.
Note that that is currently a bug #701671 causing a missing lvs entries on my host 10.34.57.206

Created attachment 498871 [details]
vdsm.log for host .206

Created attachment 498872 [details]
vdsm.log for host .213

Jaroslav , this is probably not a VDSM bug since it does not have influence on the guest image. Please explain what does your guests are doing during the migration time.

(In reply to comment #4)
> Please explain what does your guests are doing during the migration time.

The machine was running (I forgot to mention that in the Steps to Reproduce.), or Paused. It got Paused by the migration -- I think this is another bug that I should open.

There was no OS installed on the machine used for reproducing this bug. The machine was very probably in the Grub menu waiting for user input, CPU around 0% or machine paused.

May be related (and solved) by BZ#708022

http://gerrit.usersys.redhat.com/535

Verified
vdsm-4.9-79.el6.x86_64

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.

http://rhn.redhat.com/errata/RHEA-2011-1782.html