qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre DERUMIER <aderumier@odiso.com>
To: Andrey Korolyov <andrey@xdel.ru>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] cpu hotplug and windows guest (win2012r2)
Date: Mon, 19 Jan 2015 18:12:19 +0100 (CET)	[thread overview]
Message-ID: <1838738523.4548105.1421687539965.JavaMail.zimbra@oxygem.tv> (raw)
In-Reply-To: <CABYiri9vOjPH6RJPs8uvGj50Gcn8gvTz=+szhoZs-6dnw7EquA@mail.gmail.com>

>> I *need* to specify non-zero amount of memory for each numa node
>>to be seen, if each CPU belongs to different node for example but
>>everything else is just fine.

Ok, thanks I'll try to enable numa to see if it's helping

(I known that numa is mandatory for memory hotplug, maybe for cpu too)

----- Mail original -----
De: "Andrey Korolyov" <andrey@xdel.ru>
À: "aderumier" <aderumier@odiso.com>
Cc: "qemu-devel" <qemu-devel@nongnu.org>
Envoyé: Mercredi 14 Janvier 2015 17:07:41
Objet: Re: [Qemu-devel] cpu hotplug and windows guest (win2012r2)

On Fri, Jan 9, 2015 at 4:35 PM, Andrey Korolyov <andrey@xdel.ru> wrote: 
> On Fri, Jan 9, 2015 at 1:26 PM, Alexandre DERUMIER <aderumier@odiso.com> wrote: 
>> Hi, 
>> 
>> I'm currently testing cpu hotplug with a windows 2012R2 standard guest, 
>> 
>> and I can't get it too work. (works fine with linux guest). 
>> 
>> host kernel : rhel7 3.10 kernel 
>> qemu 2.2 
>> 
>> 
>> qemu command line : -smp cpus=1,sockets=2,cores=1,maxcpus=2 
>> 
>> Started with 1cpu, topogoly is 2sockets with 1cores. 
>> 
>> 
>> Then 
>> 
>> qmp# cpu-add 1 
>> 
>> 
>> I can see a new cpu is windows device manager, and event log in the device said that it's online. 
>> 
>> So it should be ok, but. 
>> 
>> I can't see new processor in taskmanager or perfmon. (I had tried to relaunch them to be sure.). 
>> 
>> 
>> So, it is a windows bug ? Does I need to do something else ? 
>> 
> 
> Did you populated appropriate topology in arguments? As far as I can 
> remember from pre-1.1 era CPU hotplug not worked with windows, so it 
> should be neither lack of configured NUMA or a simply OS-specific 
> issue. 

Just to let anyone know that it works well: 

http://xdel.ru/downloads/windows-hotplugged-cpu.png 

Topology is a bit rotten (I have two sockets with single CPU in each) 
and I *need* to specify non-zero amount of memory for each numa node 
to be seen, if each CPU belongs to different node for example but 
everything else is just fine. 

  reply	other threads:[~2015-01-19 17:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09 10:26 [Qemu-devel] cpu hotplug and windows guest (win2012r2) Alexandre DERUMIER
2015-01-09 13:35 ` Andrey Korolyov
2015-01-14 16:07   ` Andrey Korolyov
2015-01-19 17:12     ` Alexandre DERUMIER [this message]
2015-01-19 17:15       ` Andrey Korolyov
     [not found]     ` <1789085063.4708770.1421780811020.JavaMail.zimbra@oxygem.tv>
2015-01-20 19:06       ` Alexandre DERUMIER
2015-01-20 23:16         ` Andrey Korolyov
     [not found]           ` <860823709.4718817.1421808140331.JavaMail.zimbra@oxygem.tv>
2015-01-21  2:43             ` Alexandre DERUMIER
2015-01-19 16:06 ` Igor Mammedov
2015-01-19 17:13   ` Alexandre DERUMIER

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1838738523.4548105.1421687539965.JavaMail.zimbra@oxygem.tv \
    --to=aderumier@odiso.com \
    --cc=andrey@xdel.ru \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).