From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58119) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YuGEp-0007V6-JG for qemu-devel@nongnu.org; Mon, 18 May 2015 04:17:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YuGEm-0008MD-AQ for qemu-devel@nongnu.org; Mon, 18 May 2015 04:17:27 -0400 Received: from mail-wi0-f170.google.com ([209.85.212.170]:36963) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YuGEm-0008Lz-4Z for qemu-devel@nongnu.org; Mon, 18 May 2015 04:17:24 -0400 Received: by wibt6 with SMTP id t6so60060982wib.0 for ; Mon, 18 May 2015 01:17:23 -0700 (PDT) Date: Mon, 18 May 2015 10:17:20 +0200 From: Eduardo Otubo Message-ID: <20150518081719.GA5439@vader> References: <20150504162442.GA12825@francium.user.ytu.skyatlas.com> <1954990735.5679237.1430761748082.JavaMail.zimbra@oxygem.tv> <20150504183420.GA3127@caesium> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="SLDf9lqlvOQaIe6s" Content-Disposition: inline In-Reply-To: <20150504183420.GA3127@caesium> Subject: Re: [Qemu-devel] VCPU Hot-Unplug Feature List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Fahri Cihan Demirci Cc: Igor Mammedov , qemu-devel , Alexandre DERUMIER --SLDf9lqlvOQaIe6s Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 04, 2015 at 09=3D34=3D21PM +0300, Fahri Cihan Demirci wrote: > Hello Alexandre, >=20 > Thank you for your response. I came upon that patch on the Libvirt mailin= g list, too. However, the following comment makes me think that it's not li= kely to be merged: >=20 > https://www.redhat.com/archives/libvir-list/2015-February/msg00415.html >=20 > Also, later in the thread, the author of the patch seems to confirm that = the plan for hotplug in QEMU is not compatible with that patch: >=20 > https://www.redhat.com/archives/libvir-list/2015-March/msg01169.html >=20 > So, I think Libvirt developers have decided to wait until there is a gene= ralized groundwork for VCPU hot-unplug in the QEMU code base. That's why I = decided to inquire and offer help for QEMU developers, since the ball seems= to be in their court now. We're very interested in having this feature upstream as well. As Fahri stated above, I also would like to offer help to get it pushed. What's the current status? Regards, >=20 > Thanks a lot for your time. >=20 >=20 > On Mon, May 04, 2015 at 07:49:08PM +0200, Alexandre DERUMIER wrote: > > Hi, > >=20 > > they are a lot of patches sent on the mailing list recently, > >=20 > > cpu hotplug|unplug with device_add|del > >=20 > > https://www.redhat.com/archives/libvir-list/2015-February/msg00084.html > >=20 > >=20 > >=20 > > ----- Mail original ----- > > De: "Fahri Cihan Demirci" > > =C3=80: "qemu-devel" > > Envoy=C3=A9: Lundi 4 Mai 2015 18:24:43 > > Objet: [Qemu-devel] VCPU Hot-Unplug Feature > >=20 > > Hello,=20 > >=20 > > We are interested in being able to remove a VCPU from an active Libvirt= domain running under QEMU/KVM. However, currently that does not seem to be= possible because QEMU does not provide an interface for hot-unplugging a V= CPU. The corresponding feature page [1] on the QEMU wiki mentions the cpu-a= dd interface and the generalized device add/del interface. So, my question = is, is there someone working on a cpu-remove interface or making progress i= n the generalized device add/del interface to hot-unplug VCPUS? If you are = in any way interested in or planning such a feature, we may provide feedbac= k, testing or help in the development effort. Any other input, guidance or = corrections would be also most welcome. Thank you.=20 > >=20 > > [1] http://wiki.qemu.org/Features/CPUHotplug=20 > >=20 > >=20 > > Best regards,=20 > > Fahri Cihan Demirci=20 >=20 --=20 Eduardo Otubo ProfitBricks GmbH --SLDf9lqlvOQaIe6s Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVWaAFAAoJEP0M/1sS+L0v3YAH/0j8b1pEF/x5SFkryyRSjwCb EH0ZyJvTYJHhqhgNOe3g9E3v6+uiuP45W2bxJC34iU7X28pumdKtxrhi1tiKrT3v kuCLG8y0agW3JC3VcFDOv8J1kwIm6gxEg3AkPaZiTKOwWKdb+UrR82hnwWipW2zw XU5MzQtkCNzkJ9wM9tF8Yer2eNl6IWtZdk2NkrKsJvC0K0K+cAJmG+HuYP25OJms VKS18A8xePFiY6Xh9V4cFvmetEx7dFAJ7kpRAiw73gnAedxDMlawL3vEHz/fSTM6 4PrwznBvs5qM9COh3AsJt39gVhSmjeVN9a7JVKM2L6ZlYNGOzi0Md6u+2Rd7DXc= =SuUp -----END PGP SIGNATURE----- --SLDf9lqlvOQaIe6s--