From: Alexey Korolev <alexey.korolev@endace.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: sfd@endace.com, yamahata@valinux.co.jp, seabios@seabios.org,
qemu-devel@nongnu.org, gleb@redhat.com
Subject: Re: [Qemu-devel] [BUG] [Seabios] PCI 64bit BARs on Win2008 - unable to start the device. (ACPI lacks the _DSM method)
Date: Tue, 6 Dec 2011 17:23:28 +1300 [thread overview]
Message-ID: <4EDD98C0.6040808@endace.com> (raw)
In-Reply-To: <20111205063151.GE22501@redhat.com>
On 05/12/11 19:31, Michael S. Tsirkin wrote:
> On Mon, Dec 05, 2011 at 05:20:32PM +1300, Alexey Korolev wrote:
>> Hi Michael,
>>
>> Thank you for good advice, you are right. When I added new range
>> above 4GB in _CRS the problem has gone.
>> QWordMemory (ResourceProducer, PosDecode, MinFixed, MaxFixed,
>> NonCacheable, ReadWrite,
>> 0x00000000, // Address Space Granularity
>> 0x100000000, // Address Range Minimum
>> 0x3FFFFFFFF, // Address Range Maximum
>> 0x00000000, // Address Translation Offset
>> 0x400000000, // Address Length
>> ,, , AddressRangeMemory, TypeStatic)
>>
>> The only big problem with this range - as soon as I have more than
>> 3GB of RAM, windows will boot in BSOD. The problem relates to memory
>> range intersection.
>> Unfortunately it is not possible to predict how many GB of RAM the
>> virtual machine could have - so it's difficult to specify a
>> particular region.
>> Do you have any ideas what can be done to solve this problem?
>>
>> Regards,
>> Alexey
> Two possible ideas:
> 1. Pass the value in from qemu
Do you mean to create the 64bit region dynamically? I've tried to obtain
RAM size somehow inside DSL code, but the ACPI spec doesn't tell how to
do that.
> 2. Get a range toward the upper end of the memory, around 1<<40
>
Yes. This solution works great. And this is very simple as well. Just
wondering if it will be good as a complete solution?
next prev parent reply other threads:[~2011-12-06 4:23 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
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 [this message]
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=4EDD98C0.6040808@endace.com \
--to=alexey.korolev@endace.com \
--cc=gleb@redhat.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).