From: Steve Freitas <sflist@ihonk.com>
To: Don Slutz <dslutz@verizon.com>, xen-devel@lists.xen.org
Subject: Re: PCI hole resize support for 4.5? If not, workaround?
Date: Mon, 20 Oct 2014 10:14:54 -0700 [thread overview]
Message-ID: <5445430E.1050005@ihonk.com> (raw)
In-Reply-To: <544508B9.1070905@terremark.com>
On 10/20/2014 6:06, Don Slutz wrote:
> On 10/18/14 02:17, Steve Freitas wrote:
>> Hi all,
>>
>> I'm suffering from bug 28 [1], unable to assign more than 3.5 gigs of
>> RAM to my Windows VM while using VGA passthrough. This is a
>> showstopper for me.
>>
>> Since #28 is still listed as up for grabs for 4.5 [2], I assume a fix
>> is not likely to make it in. However, a message from Ian [3]
>> indicated that a workaround was available at some point. Will a
>> workaround be offered for 4.4 or 4.5?
>>
>
> Adding the patch:
>
> http://lists.xenproject.org/archives/html/xen-devel/2014-10/msg01447.html
>
> to 4.5-unstable
>
> and adding
>
> mmio_hole_size = 536870912
>
> to your .xfg should allow you to use more memory (the number above
> is .5 gig, which should work based on 3.5 gigs working).
Hi Don!
Thanks for your reply and the patch, my searches didn't turn up your
post. Any idea if I'll run into trouble trying to apply this to 4.4.1?
I'd like to stick with (minimally modified) distro packages if possible,
and Debian Jessie is on 4.4.1. And any feeling for whether this will
make it into 4.5? Sure would be nice to see this problem fixed for good.
Thanks again.
Steve
next prev parent reply other threads:[~2014-10-20 17:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-18 6:17 PCI hole resize support for 4.5? If not, workaround? Steve Freitas
2014-10-20 13:06 ` Don Slutz
2014-10-20 17:14 ` Steve Freitas [this message]
2014-10-21 13:14 ` Don Slutz
2014-10-21 17:33 ` Steve Freitas
2014-10-29 13:33 ` Slutz, Donald Christopher
2014-10-29 20:25 ` Konrad Rzeszutek Wilk
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=5445430E.1050005@ihonk.com \
--to=sflist@ihonk.com \
--cc=dslutz@verizon.com \
--cc=xen-devel@lists.xen.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 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.