WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: PCI passthrough stopped working, brainache!

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: PCI passthrough stopped working, brainache!
From: Andy Burns <xen.lists@xxxxxxxxxxx>
Date: Mon, 24 Oct 2011 12:30:18 +0100
Delivery-date: Mon, 24 Oct 2011 04:31:21 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=OcZUZTuwv51RSpwqgOxhJPJCERoI0ot7wgD20nGedSY=; b=du7YBKAP6Rnra3lt/s9Z3MwCqNkjXmfD5X0zU42uyMwx7GHnXJVu9NHtybx/L3ZCRH aBlyM9REy/CWb7jSXWeFQjRyV9dyvfrBmmxT5ClSnY7UndxKaC55xuavbnLRPzNkT/WJ IKV7BkPFG0Usyegt+z3xyHs1AuqgD90HM7a0w=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <CAE1-PRe3FZknxdCLkhkGbzd-i=y5eGMAwY+yoa36j61oHNcRSw@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <CAE1-PReH55X375oSb_gx4K_2iTTo67xpFfS8r7zv3KPtiOxj_A@xxxxxxxxxxxxxx> <CAE1-PRc9LqO07TjH3TnfSnEB8gLkBhw2211syeA04XPWts62Xg@xxxxxxxxxxxxxx> <CAE1-PRfg3fkMMSQyPO+y8dqxcE-KNJc--6bx84aouaQorOF27w@xxxxxxxxxxxxxx> <20111012035032.GB26092@xxxxxxxxxxxxxxxxx> <CAE1-PRfuo10T2iKJUNoY=Aj4S_TjUbiPT1jARv+iD7g+1qWuNg@xxxxxxxxxxxxxx> <CAE1-PRd9Kicm=dRtDmPKGXM8-fp62NyvDdpww38jA3Afwrt8+g@xxxxxxxxxxxxxx> <20111013181543.GF15499@xxxxxxxxxxxxxxxxx> <CAE1-PRfGTxeQ59jmHfB6bKKk2+B5bNnKhAvXoV-5P__+nkhgKQ@xxxxxxxxxxxxxx> <1318674976.11016.24.camel@xxxxxxxxxxxxxxxxxxxx> <CAE1-PRe3FZknxdCLkhkGbzd-i=y5eGMAwY+yoa36j61oHNcRSw@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 15 October 2011 12:27, Andy Burns <xen.lists@xxxxxxxxxxx> wrote:

> On 15 October 2011 11:36, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
>
>> I think you've got 8G of RAM so one thing which might be worth trying is
>> to give "mem=2G"
>
> A coconut for the gentleman!

I can see that the devs have been busy getting their ducks in a row
for when the 3.2 merge window opens (3.1 is released now) so not
wanted to pester about this as it's OK for now with the workarounds.

Initially I tried mem=2G, with dom0_mem=512M and two domUs of 512M and
1G respectively, I presume this caused a bit of ballooning in dom0 as
I caught it with 400M'ish at one point and I had a little instability.

I pushed it up to mem=3G and at the same time added irqpoll for dom0
and the pci domU (because I was seeing a few "nobody cared" messages
in the domU at bootup and in the dom0 after shutting down the domU)
those changes so far have resulted in a stable setup.

Not wanting to reboot the dom0 just yet (would like to see how stable
it really is) but want to think about things to try when I *do* reboot
it,
I'm assuming the DMA problem will rear its head again if I try mem >=
4G, I haven't tried anything with dma_bits yet either, anything other
suggestions or logging that might help?

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel