From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@bugzilla.kernel.org Subject: [Bug 190211] New: memory ballooning doesn't take on boot since approx kernel 4.5.3 Date: Tue, 13 Dec 2016 00:43:20 +0000 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit To: kvm@vger.kernel.org Return-path: Received: from mail.kernel.org ([198.145.29.136]:48494 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753010AbcLMAnY (ORCPT ); Mon, 12 Dec 2016 19:43:24 -0500 Received: from mail.kernel.org (localhost [127.0.0.1]) by mail.kernel.org (Postfix) with ESMTP id BECE920456 for ; Tue, 13 Dec 2016 00:43:22 +0000 (UTC) Received: from bugzilla2.web.kernel.org (bugzilla2.web.kernel.org [172.20.200.52]) by mail.kernel.org (Postfix) with ESMTP id 7BC7A2043C for ; Tue, 13 Dec 2016 00:43:20 +0000 (UTC) Sender: kvm-owner@vger.kernel.org List-ID: https://bugzilla.kernel.org/show_bug.cgi?id=190211 Bug ID: 190211 Summary: memory ballooning doesn't take on boot since approx kernel 4.5.3 Product: Virtualization Version: unspecified Kernel Version: 4.9, 4.8.14, 4.8.1, 4.7.2, 4.6.2 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: kvm Assignee: virtualization_kvm@kernel-bugs.osdl.org Reporter: ap@zip.com.au Regression: No Just noticed that on restart or bootup memory ballooning stopped working. The guest boots with the maximum allowed memory rather than the "current" setting in libvirt. If I request a memory shrink after boot, the balloon works and memory available shrinks as requested. I went through the following guest kernels: 4.9, 4.8.14, 4.8.1, 4.7.2, 4.6.2, 4.5.3 (worked), 4.4.4 (worked). These were custom compiles. Debian official kernels for 4.8.0 and 4.7.0 also failed. I used libvirt 2.5.0, 2.4.0 and 1.2.20 Qemu versions: 2.5 and 2.7 Debian stretch for the guest, wheezy and stretch for the host. Host kernels 4.3.3, 4.8.6 and 4.8.14 The fact that dropping kernel versions made it work once I hit 4.5.3 makes me think there's an issue kernel-side. -- You are receiving this mail because: You are watching the assignee of the bug.