All of lore.kernel.org
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: linzhecheng <linzhecheng@huawei.com>
Cc: QEMU <qemu-devel@nongnu.org>, "mst@redhat.com" <mst@redhat.com>,
	"wangxin (U)" <wangxinxin.wang@huawei.com>,
	"robert.moore@intel.com" <robert.moore@intel.com>,
	lidonglin <lidonglin@huawei.com>,
	"Gonglei (Arei)" <arei.gonglei@huawei.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	"lersek@redhat.com" <lersek@redhat.com>
Subject: Re: [Qemu-devel] Some issues of hotpluging memory and cpus
Date: Wed, 27 Jun 2018 16:08:59 +0200	[thread overview]
Message-ID: <20180627160859.3733036d@redhat.com> (raw)
In-Reply-To: <D9DE8DBB19F2A24080482022C1DE758302C971CE@dggemm509-mbx.china.huawei.com>

On Mon, 25 Jun 2018 13:30:10 +0000
linzhecheng <linzhecheng@huawei.com> wrote:

> Hi, all,
> I had some problems when doing memory hot plugging. After a lot of tests, I was able to stably reproduce the following issues with Windows 2012 R2:
> 
> 1. If I hot-plug the memory immediately after hot-plugging the CPUs, these memory devices will not be detected by windows OS because I cannot see them in the device manager.
> 2. If I add a certain delay (for example, 2s or more) between the hot-plugging memory and the CPU, the memory devices will be detected but some of them may not be online.
> And Memory Module Properties displaying the following contents:
> 
> This device cannot start. (Code 10)
> {Conflicting Address Range}
> The specified address range conflicts with the address space.
it could help if you can find in device manger what it conflicts with


> 3. usb tablet mouse would not work probability after hot adding memory.
> 
> Due to the closed nature of windows OS, I can't know what's going on inside.
> Is it related to acpi tables exposure?
> I hope you can give me some advice, thank you.

you also can try running QEMU with cphp_* and mhp_* trace events enabled [*],
it should show ACPI interaction os Windows with QEMU including address assignment.


*) docs/devel/tracing.txt

      reply	other threads:[~2018-06-27 14:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-25 13:30 [Qemu-devel] Some issues of hotpluging memory and cpus linzhecheng
2018-06-27 14:08 ` 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=20180627160859.3733036d@redhat.com \
    --to=imammedo@redhat.com \
    --cc=arei.gonglei@huawei.com \
    --cc=lersek@redhat.com \
    --cc=lidonglin@huawei.com \
    --cc=linzhecheng@huawei.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=robert.moore@intel.com \
    --cc=wangxinxin.wang@huawei.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.