From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36556) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YDlGP-0001kR-2d for qemu-devel@nongnu.org; Tue, 20 Jan 2015 21:43:26 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YDlGJ-0002Tm-Cs for qemu-devel@nongnu.org; Tue, 20 Jan 2015 21:43:25 -0500 Received: from mailpro.odiso.net ([89.248.209.98]:57538) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YDlGJ-0002Th-7K for qemu-devel@nongnu.org; Tue, 20 Jan 2015 21:43:19 -0500 Date: Wed, 21 Jan 2015 03:43:17 +0100 (CET) From: Alexandre DERUMIER Message-ID: <38239859.4718818.1421808197120.JavaMail.zimbra@oxygem.tv> In-Reply-To: <860823709.4718817.1421808140331.JavaMail.zimbra@oxygem.tv> References: <1274806254.3641413.1420799168297.JavaMail.zimbra@oxygem.tv> <1789085063.4708770.1421780811020.JavaMail.zimbra@oxygem.tv> <918972069.4708771.1421780817584.JavaMail.zimbra@oxygem.tv> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] cpu hotplug and windows guest (win2012r2) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Andrey Korolyov Cc: qemu-devel Ok, I think it's a windows bug, I have the same topology than you, I don't work. (I see the new vcpu in device manager, but not in taskmgr or perform) Rebooting the os make the new vcpu display, so it's seem to be ok on qemu s= ide. (Just to known, which version of win2012r2 do you use ? standard or datacen= ter ?) Thanks for your help! Regards, Alexandre ----- Mail original ----- De: "Andrey Korolyov" =C3=80: "aderumier" Cc: "qemu-devel" Envoy=C3=A9: Mercredi 21 Janvier 2015 00:16:45 Objet: Re: [Qemu-devel] cpu hotplug and windows guest (win2012r2) On Tue, Jan 20, 2015 at 10:06 PM, Alexandre DERUMIER=20 wrote:=20 > Hi,=20 >=20 > I have tried with numa enabled, and it's still don't work.=20 > Can you send me your vm qemu command line ?=20 >=20 >=20 > Also, with numa I have notice something strange with "info numa" command.= =20 >=20 > starting with -smp socket=3D2,cores=3D1=20 >=20 > # info numa=20 > 2 nodes=20 > node 0 cpus: 0=20 > node 0 size: 2048 MB=20 > node 1 cpus: 1=20 > node 1 size: 2048 MB=20 >=20 > ok=20 >=20 >=20 > now:=20 >=20 > starting with -smp 1,socket=3D2,cores=3D1,maxcpus=3D2=20 >=20 > # info numa=20 > 2 nodes=20 > node 0 cpus: 0=20 > node 0 size: 2048 MB=20 > node 1 cpus:=20 > node 1 size: 2048 MB=20 >=20 > ok=20 >=20 >=20 > now hotplug cpu=20 >=20 > # cpu-add 1=20 > # info numa=20 > 2 nodes=20 > node 0 cpus: 0 1=20 > node 0 size: 2048 MB=20 > node 1 cpus:=20 > node 1 size: 2048 MB=20 >=20 >=20 > cpu1 has been hotplugged on numa node0 ??????=20 >=20 >=20 http://lists.gnu.org/archive/html/qemu-devel/2015-01/msg02240.html=20 here are working examples. Yes, everything goes to the node0 unless=20 specified (you can see an example for bounded sockets in this url=20 too).=20