From: Don Slutz <dslutz@verizon.com>
To: Steve Freitas <sflist@ihonk.com>, Xen-devel@lists.xen.org
Subject: Re: PCI hole resize support for 4.5? If not, workaround?
Date: Mon, 20 Oct 2014 09:06:01 -0400 [thread overview]
Message-ID: <544508B9.1070905@terremark.com> (raw)
In-Reply-To: <544205F4.60609@ihonk.com>
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).
-Don Slutz
> I'm using Xen 4.4.1 on Debian Jessie (official distro packages),
> kernel 3.16, Xeon 5660, Intel 5500 chipset (rev 22), Nvidia Quadro FX
> 4800 GPU.
>
> Thanks,
>
> Steve
>
> [1] http://bugs.xenproject.org/xen/bug/28
> [2] http://marc.info/?l=xen-devel&m=141356622719233
> [3] http://marc.info/?l=xen-devel&m=138918385728185
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-10-20 13:06 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 [this message]
2014-10-20 17:14 ` Steve Freitas
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=544508B9.1070905@terremark.com \
--to=dslutz@verizon.com \
--cc=Xen-devel@lists.xen.org \
--cc=sflist@ihonk.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.