From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andy Burns <xen.lists@burns.me.uk>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Xen + DVB = not working. memory allocation issue?
Date: Wed, 19 Dec 2012 16:59:22 -0500 [thread overview]
Message-ID: <20121219215922.GB12292@phenom.dumpdata.com> (raw)
In-Reply-To: <CAE1-PRdFxJWTKp6Qiaagh_9B8eOtK3aF=-8AT2CnrrT+KS2F0A@mail.gmail.com>
On Thu, Oct 25, 2012 at 07:14:53PM +0100, Andy Burns wrote:
> On 25 September 2012 15:10, Konrad Rzeszutek Wilk <konrad@kernel.org> wrote:
>
> > So try also limiting how much memory the hypervisor has to eliminate
> > this being a 4GB issue. Meaning on the _hypervisor_ line add 'mem=4G'.
>
> I previously required that with xen 4.1.x but now I've upgraded to Xen
> 4.2 (and dom0 and domU to 3.6.x kernels) I no longer require it.
>
> Has the O/P got iommu=soft in the domU kernel command line if it's a PV domU?
>
> Also try 'pci=resource_alignment=BB:DD.F;BB:DD.F' etc on the
> hypervisor command line for your relevant PCI device(s)
>
> Those tweaks are all I need to use these days for PCI passthrough :-)
Sorry for the late response - walking through my mailbox. Did this thread ever get resolved?
prev parent reply other threads:[~2012-12-19 21:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+LkAa=RHJCtpncP8AUSeR8Te3ZLMvRctuZqnv_NwUkCQ-im8Q@mail.gmail.com>
2012-09-21 17:29 ` Xen + DVB = not working. memory allocation issue? Konrad Rzeszutek Wilk
2012-09-22 4:13 ` John Krstev
2012-09-25 0:49 ` John Krstev
2012-09-25 14:10 ` Konrad Rzeszutek Wilk
2012-09-26 1:02 ` John Krstev
2012-10-12 4:43 ` John Krstev
2012-10-25 3:39 ` John Krstev
2012-10-25 18:14 ` Andy Burns
2012-12-19 21:59 ` Konrad Rzeszutek Wilk [this message]
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=20121219215922.GB12292@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen.lists@burns.me.uk \
/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.