From owner-freebsd-virtualization@freebsd.org  Thu May  5 16:17:05 2016
Return-Path: <owner-freebsd-virtualization@freebsd.org>
Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1200CB2EC3A
 for <freebsd-virtualization@mailman.ysv.freebsd.org>;
 Thu,  5 May 2016 16:17:05 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 028C712D7
 for <freebsd-virtualization@FreeBSD.org>; Thu,  5 May 2016 16:17:05 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u45GH3Kc077669
 for <freebsd-virtualization@FreeBSD.org>; Thu, 5 May 2016 16:17:04 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-virtualization@FreeBSD.org
Subject: [Bug 198344] [virtio] virtio-balloon does not work
Date: Thu, 05 May 2016 16:17:04 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.2-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: vivek@khera.org
X-Bugzilla-Status: Open
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-198344-27103-aL1idXetyg@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-198344-27103@https.bugs.freebsd.org/bugzilla/>
References: <bug-198344-27103@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 05 May 2016 16:17:05 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D198344

--- Comment #8 from Vick Khera <vivek@khera.org> ---
Created attachment 169998
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D169998&action=
=3Dedit
graph of memory usage of my VM

I've been watching my 10.3 VM for a while now, and I finally found evidence
that it did release some memory. The VM environment is Proxmox VE, which is
basically a fancy pants GUI on top of Debian linux + KVM.

The memory usage graph is attached.

--=20
You are receiving this mail because:
You are the assignee for the bug.=