All of lore.kernel.org
 help / color / mirror / Atom feed
From: Don Slutz <dslutz@verizon.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>,
	"Stephen Oberholtzer" <stevie@qrpff.net>
Cc: xen-users@lists.xen.org, xen-devel@lists.xen.org
Subject: Re: [Xen-users] HVM PCI Passthrough: Code 12: Undersized PCI MMIO region?
Date: Tue, 06 Jan 2015 13:44:27 -0500	[thread overview]
Message-ID: <54AC2D0B.1070709@terremark.com> (raw)
In-Reply-To: <20150106130046.GU19091@reaktio.net>

On 01/06/15 08:00, Pasi Kärkkäinen wrote:
> On Tue, Dec 02, 2014 at 10:08:35PM -0500, Stephen Oberholtzer wrote:
>> All,
>>
> 
> Hello,
> 
>> Please bear with me.  I don't fully understand all of the mechanisms
>> involved here, so this message contains a large quantity of data,
>> including some links to even larger quantities of data.
>> The short version is: I think something isn't reserving enough (GPFN)
>> address space for MMIO.
>>

...

>>
>> Now, I don't fully understand how this stuff all works, but here's
>> what appears to be happening: Xen isn't reserving enough contiguous
>> GPFN (virtual machine address space) for all of the devices on the
>> virtual PCI bus -- in particular, for what is probably a big honkin'
>> window into the card's onboard RAM.
>>
>> So my two questions are:
>> (1) Is my guess correct?  Or at least close?

I think so.

>> (2) What the heck do I do about it? I don't see any options in
>> xl.cfg(5) for specifying the size of the MMIO region for the virtual
>> PCI bus, or anything similar to that.
>>

There is a new feature in xen 4.5 (soon to be released) that you can
add to the config file (xl.cfg):

   Memory layout
    mmio_hole=MBYTES
        Specifies the size the MMIO hole below 4GiB will be. Only valid for
        device_model_version = "qemu-xen".

        Cannot be smaller than 256. Cannot be larger than 3840.

        Known good large value is 3072.


Subject: [Xen-devel] Xen Project 4.5 RC4 is Ready Today; Test Day is
Wednesday
Date: Mon, 15 Dec 2014 14:33:33 -0500
From: Russ Pavlicek <russell.pavlicek@xenproject.org>
To: xen-devel@lists.xen.org, xen-users@lists.xen.org
<xen-users@lists.xen.org>, xen-announce@lists.xenproject.org,
xs-devel@lists.xenserver.org, mirageos-devel@lists.xenproject.org,
xen-api@lists.xen.org

Folks,

This Wednesday, December 17, is our fourth and FINAL Test Day
for the 4.5 release cycle (barring any changes which may result from
Wednesday's Test Day). Release Candidate 4 is available for
assessment today.

If you've held off testing the new release until it matures, delay no
longer!  Test and state your concerns now or the next release you
see could be the official one

Information about testing this release can be found here:
http://wiki.xenproject.org/wiki/Xen_4.5_RC4_test_instructions

To learn more about Test Days, including the scheduled date
for the final release, check out:
http://wiki.xenproject.org/wiki/Xen_Project_Test_Days

   -Don Slutz

>>
>> NOTE: If I assign 2048MB or less RAM to this VM, the VM crashes at
>> bootup, and has a nasty tendency to take the host with it (lockup).
>>
>> -- 
>> -- Stevie-O
>> Real programmers use COPY CON PROGRAM.EXE
>>
> 
> 
> -- Pasi
> 
> 
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xen.org
>> http://lists.xen.org/xen-users
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
> 

  reply	other threads:[~2015-01-06 18:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAD_xR9d-_JfnP0X0ttsM0q=0ChdGz_Li5p-tWUzeMXhX=z2uBw@mail.gmail.com>
2015-01-06 13:00 ` [Xen-users] HVM PCI Passthrough: Code 12: Undersized PCI MMIO region? Pasi Kärkkäinen
2015-01-06 18:44   ` Don Slutz [this message]
2015-01-07  9:44   ` Jan Beulich

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=54AC2D0B.1070709@terremark.com \
    --to=dslutz@verizon.com \
    --cc=pasik@iki.fi \
    --cc=stevie@qrpff.net \
    --cc=xen-devel@lists.xen.org \
    --cc=xen-users@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.