qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: Eduardo Otubo <eduardo.otubo@profitbricks.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] CPU hotplug on Windows 2016 as guest
Date: Thu, 22 Dec 2016 14:04:51 +0100	[thread overview]
Message-ID: <20161222140451.4fa67eac@nial.brq.redhat.com> (raw)
In-Reply-To: <20161222094029.GA1571@vader>

On Thu, 22 Dec 2016 10:40:29 +0100
Eduardo Otubo <eduardo.otubo@profitbricks.com> wrote:

> Hi guys,
> 
> I'm just trying Qemu 2.7 and 2.8 and Windows 2016 as guest and cpu
> hotplug doesn't seem to be working. CPU appears on qemu device tree, but
> doesn't appear inside the guest (nor control panel, performance monitor
> or device manager)
> 
> Anyone going through this?
> 

It's MS regression we've found in September,
workaround is to remove wrong driver bindings in the guest
see: https://bugzilla.redhat.com/show_bug.cgi?id=1377155#c17

And complain to MS support so that they'd fix it.

      reply	other threads:[~2016-12-22 13:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-22  9:40 [Qemu-devel] CPU hotplug on Windows 2016 as guest Eduardo Otubo
2016-12-22 13:04 ` Igor Mammedov [this message]

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=20161222140451.4fa67eac@nial.brq.redhat.com \
    --to=imammedo@redhat.com \
    --cc=eduardo.otubo@profitbricks.com \
    --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).