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.
Bug 1139125 - huge memory consumption leading to vm killing
Summary: huge memory consumption leading to vm killing
Keywords:
Status: CLOSED DUPLICATE of bug 1015413
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pygobject3
Version: 7.1
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Matthew Barnes
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-08 06:57 UTC by Vladimir Benes
Modified: 2014-09-16 07:41 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-08 09:31:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Vladimir Benes 2014-09-08 06:57:20 UTC 
Description of problem:
after several hours (maybe day+) my vm was killed overnight. When I tried to power it on again I see:
Error starting domain: internal error: process exited while connecting to monitor: Cannot set up guest memory 'pc.ram': Cannot allocate memory

looking to top says:
17815 vbenes    20   0 2718640 1.606g  13648 S   2.3 21.8  30:19.98 virt-manag+ 

^^^ this is pretty ugly as newly started virt-manager eats a lot less.

25338 vbenes    20   0  991348  54516  17376 S   2.0  0.7   0:01.20 virt-manager

Version-Release number of selected component (if applicable):


How reproducible:
virt-manager-0.10.0-20.el7.noarch

Steps to Reproduce:
1.open virt-manager and start some machines
2.let it be over night with machine on

Actual results:
huge memory consumption

Expected results:
low mem consumption

Additional info:
Comment 1 Giuseppe Scrivano 2014-09-08 09:31:45 UTC 

*** This bug has been marked as a duplicate of bug 1032720 ***
Comment 2 Giuseppe Scrivano 2014-09-16 07:41:48 UTC 

*** This bug has been marked as a duplicate of bug 1015413 ***
Note You need to log in before you can comment on or make changes to this bug.