From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Gordan Bobic <gordan@bobich.net>
Cc: Xen Developers <xen-devel@lists.xen.org>,
Ian Campbell <Ian.Campbell@citrix.com>,
Andrea Brugiolo <andrea@cab.unipd.it>
Subject: Re: Xen pciback not working: "address space collision: [mem ...] conflicts with System RAM [mem ...]"
Date: Fri, 2 Aug 2013 08:44:09 -0400 [thread overview]
Message-ID: <20130802124409.GL24540@konrad-lan.dumpdata.com> (raw)
In-Reply-To: <a3de3388bb055da44816eb326ec1d9b5@mail.shatteredsilicon.net>
> >>>>The RAM region is pretty much all of the memory. This looks like
> >>>>the 'e820_hole'
> >>>>parameter is not being used? (It only works for xl btw).
> >>
> >>Where is the e820_hole option documented and what does it do?
> >
> >It should be in the manpage (man xl.cfg). Here is a copy-n-paste:
> > e820_host=BOOLEAN
.. snip..
>
> Ah, so this was a typo above. s/e820_hole/e820_host/
Yes. It is suppose to be 'e820_host=1'. Thank you for helping me realize
my mistake. <sigh>
next prev parent reply other threads:[~2013-08-02 12:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 10:32 Xen pciback not working: "address space collision: [mem ...] conflicts with System RAM [mem ...]" Andrea Brugiolo
2013-07-29 9:02 ` Ian Campbell
2013-07-29 16:01 ` Andrea Brugiolo
2013-07-29 17:55 ` Konrad Rzeszutek Wilk
2013-07-30 9:11 ` Ian Campbell
2013-08-02 9:07 ` Andrea Brugiolo
2013-08-02 9:27 ` Gordan Bobic
2013-08-02 12:06 ` Konrad Rzeszutek Wilk
2013-08-02 12:19 ` Gordan Bobic
2013-08-02 12:44 ` Konrad Rzeszutek Wilk [this message]
2013-08-02 12:04 ` Konrad Rzeszutek Wilk
2013-08-02 12:30 ` Andrea Brugiolo
2013-08-02 12:43 ` Konrad Rzeszutek Wilk
2013-08-20 14:56 ` Andrea Brugiolo
2013-08-23 18:54 ` Konrad Rzeszutek Wilk
2013-08-27 21:03 ` Andrea Brugiolo
2013-08-28 15:45 ` Konrad Rzeszutek Wilk
2013-08-28 16:44 ` Andrea Brugiolo
2013-08-30 16:08 ` Konrad Rzeszutek Wilk
2013-09-04 17:22 ` Andrea Brugiolo
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=20130802124409.GL24540@konrad-lan.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=andrea@cab.unipd.it \
--cc=gordan@bobich.net \
--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.