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 826736 [details]
pmap -xp

Description of problem:
virt-manager allocates over 1.5GiB of virtual memory after two or more virtual machines are created: Network install (http), ram 1800MB, storage LVM lv
guest os: rhel-7 "latest"

Version-Release number of selected component (if applicable):
virt-manager-0.10.0-7.el7.noarch
python-2.7.5-10.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. choose network install
2. specify http URL (rhel-7 in my case)
3. set RAM 1800MB
4. I've used LVM
5. install os, don't turn it off, remove it (without disk if you want)
6. repeat at least once (with disk from step 5 if you have it)

Actual results:
virt-manager uses over 1.5GiB of virtual memory

Expected results:
considerably lower memory consumption

Additional info:
VM specs after installation:
  ...
  <memory unit='KiB'>1843200</memory>
  <currentMemory unit='KiB'>1843200</currentMemory>
  <vcpu placement='static'>1</vcpu>
  <os>
    <type arch='x86_64' machine='pc-i440fx-rhel7.0.0'>hvm</type>
    <boot dev='hd'/>
  </os>
  ...

I can reproduce this issue with:
virt-manager-0.10.0-8.el7.noarch.

Steps are the same as description.

*** Bug 1139125 has been marked as a duplicate of this bug. ***

can it still be reproduced on RHEL-7.1 with the latest pygobject version? I am going to move it to 7.2

Since there were no response, whether the issue is still there and I've tested it right now and the memory usage by virt-manager after several network install is consistent, I'm closing this bug as fixed by rebase.

One more thing to add, the usage of virtual memory will be always significantly larger, because it contains all shared libraries.  The RES (Resident Memory Size) is the value you should check, because that's the current memory usage.

I've just looked at the attachment and actually this wasn't bug at all, because the real usage is about 216 MiB, which isn't that much.  I'm closing this as not a bug.