qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Korolev <alexey.korolev@endace.com>
To: yamahata@valinux.co.jp
Cc: sfd@endace.com, seabios@seabios.org, qemu-devel@nongnu.org,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [BUG] [Seabios] PCI 64bit BARs on Win2008 - unable to start the device. (ACPI lacks the _DSM method)
Date: Thu, 1 Dec 2011 18:49:54 +1300	[thread overview]
Message-ID: <4ED71582.3000107@endace.com> (raw)
In-Reply-To: <20111130074903.GD17781@redhat.com>

Isaku san,

I've just added you to discussion.
There are some issues with PCI 64bit support in Windows. Windows fails 
to assign the resource if it doesn't fit in first 4GB window.

I really don't know why it happens.
One of the possibilities is related to lack of _DSM method in ACPI.

Another guesse could be related to the fact that 440FX only supports 
32bit PCI bus interface and windows may limit PCI address range to first 
4GB for PCI devices under this bridge.
I remember you were working on Q35 chipset simulation, I wonder if it is 
working and would it be possible to try?

Thanks,
Alexey
> On Wed, Nov 30, 2011 at 02:04:08PM +1300, Alexey Korolev wrote:
>> Hi,
>>
>> We have got some issues with 64bit PCI devices support under Windows guests.
>> Windows fails to start any PCI devices with 64bit BARs when size
>> exceeds 512MB with error code 12 (can't allocate resources). In
>> other words it fails when the PCI memory region is located above
>> 4GB.
>>
>> I tried to investigate this problem and found document from Microsoft:
>> http://msdn.microsoft.com/en-us/windows/hardware/gg462986
>>
>> It states that the _DSM method must be implemented to support
>> devices above 4GB.
> That's not how I read it:
> 	Windows Vista always respects the boot configuration of devices above
> 	4 GB, considering the processor’s addressing capability and the version
> 	of the Windows operating system that is running.
>
>> Unfortunately I'm not familiar with ACPI code of seabios, so can't
>> implement the _DSM method. May be you have other ideas what needs to
>> be done to fix it? Any help is appreciated.
>>
>> Thanks,
>> Alexey
> Could you share some more detail about your setup?
>

  parent reply	other threads:[~2011-12-01  5:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-30  1:04 [Qemu-devel] [BUG] [Seabios] PCI 64bit BARs on Win2008 - unable to start the device. (ACPI lacks the _DSM method) Alexey Korolev
2011-11-30  7:49 ` Michael S. Tsirkin
2011-12-01  5:19   ` Alexey Korolev
2011-12-01 11:25     ` Gerd Hoffmann
2011-12-01 11:41       ` Gerd Hoffmann
2011-12-05  4:29         ` Alexey Korolev
2011-12-12  8:10           ` Gerd Hoffmann
2011-12-13  4:19             ` Alexey Korolev
2011-12-14  4:30               ` Alexey Korolev
2011-12-14  5:10                 ` Kevin O'Connor
2011-12-15  8:48                 ` Gerd Hoffmann
2011-12-16  4:41                   ` Alexey Korolev
2011-12-16  9:23                     ` Gerd Hoffmann
2011-12-01  5:49   ` Alexey Korolev [this message]
2011-12-01 10:17     ` Michael S. Tsirkin
2011-12-05  4:20       ` Alexey Korolev
2011-12-05  6:31         ` Michael S. Tsirkin
2011-12-06  4:23           ` Alexey Korolev
2011-12-13 11:11             ` [Qemu-devel] [SeaBIOS] " Gerd Hoffmann
2011-12-14  4:31               ` Alexey Korolev

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=4ED71582.3000107@endace.com \
    --to=alexey.korolev@endace.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=seabios@seabios.org \
    --cc=sfd@endace.com \
    --cc=yamahata@valinux.co.jp \
    /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).