From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60625) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z9w1O-0004H2-MS for qemu-devel@nongnu.org; Tue, 30 Jun 2015 09:56:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z9w1K-0006wf-F2 for qemu-devel@nongnu.org; Tue, 30 Jun 2015 09:56:22 -0400 Received: from mail-wi0-f178.google.com ([209.85.212.178]:36058) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z9w1K-0006wL-9G for qemu-devel@nongnu.org; Tue, 30 Jun 2015 09:56:18 -0400 Received: by widjy10 with SMTP id jy10so31187312wid.1 for ; Tue, 30 Jun 2015 06:56:17 -0700 (PDT) Date: Tue, 30 Jun 2015 15:56:13 +0200 From: Eduardo Otubo Message-ID: <20150630135613.GB19986@vader> References: <20150630080752.GB22813@vader> <20150630111821.14e2bb54@nial.brq.redhat.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uQr8t48UFsdbeI+V" Content-Disposition: inline In-Reply-To: <20150630111821.14e2bb54@nial.brq.redhat.com> Subject: Re: [Qemu-devel] mem1 is in use, can not be deleted List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Igor Mammedov Cc: Qemu-devel --uQr8t48UFsdbeI+V Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 30, 2015 at 11=3D18=3D21AM +0200, Igor Mammedov wrote: > On Tue, 30 Jun 2015 10:07:52 +0200 > Eduardo Otubo wrote: >=20 > > Hello all, > >=20 > > I compiled the HEAD of the master branch and was testing memory > > hotunplug and got to this issue. Note: I followed exactly what's written > > on the docs/memory-hotplug.txt file. > >=20 > > QEMU 2.3.50 monitor - type 'help' for more information > > (qemu) object_add memory-backend-ram,id=3Dmem1,size=3D1G > > object_add memory-backend-ram,id=3Dmem1,size=3D1G > > (qemu) device_add pc-dimm,id=3Ddimm1,memdev=3Dmem1 > > device_add pc-dimm,id=3Ddimm1,memdev=3Dmem1 > > (qemu) device_del dimm1 > > device_del dimm1 > > (qemu) object_del mem1 > > object_del mem1 > > mem1 is in use, can not be deleted >=20 > probably because dimm1 isn't deleted, > you can check it in monitor using command "info memory-devices" Yes, you're right. The reason is surely because dimm1 wasn't deleted -- and I think I didn't make my point very clear -- my question was more about: Is there any reason for dimm1 not being deleted? The reason why I tested with the guest OS fully running and on GRUB is because I guessed the guest OS was using this memory and couldn't be deallocated. If that's the case, and qemu did a best effort to remove and couldn't because guest was using it, then Ok, I just need to adapt my tests. Other than that perhaps I hit a bug. Regards, --=20 Eduardo Otubo ProfitBricks GmbH --uQr8t48UFsdbeI+V Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVkp/9AAoJEP0M/1sS+L0v8ZUIAIBUujY2hPgBYW/j4kP+0xK6 mJ+3d+DCk2ELM3aqpALpjnpnHlZ7GTxjoAVeif5Tkmz8znj9qdmv3f8UITU8eslZ J45QBaiapKghKarTs1XgAI0w1Xmv63dmmpQP4SwxEAdOk9Z14ac8OkpLsldv/Yja 1wircoEwWXxJmERQumzg072Qh3QJYxU3dziJuG/Hrd/+Lb5qHqjWJJL/j0WzyGqW KlsPR2/O0GdHeBdn1J5OUmCU/Gp3U5f2LmC+MlGipCcPVlBXhDBMUVvSCBP80nYr X0tK4rfeQ33WJXI4YjIxEq45cwACUH8+cTEP9VKM7QnN9pT3266oo5bwt+3lbaY= =MbS2 -----END PGP SIGNATURE----- --uQr8t48UFsdbeI+V--