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/
Home Products Support Community News


Re: [Xen-devel] pci-passthrough and shared interrupts

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-devel] pci-passthrough and shared interrupts
From: Ritu kaur <ritu.kaur.us@xxxxxxxxx>
Date: Sun, 3 Oct 2010 09:41:55 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 03 Oct 2010 09:43:03 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=Bb48F07200Fo9uAd0zuoboezvrokFx6jHuciNU589sw=; b=OjPv1d2715/T7RnPy/NyKJoxA+gH4IFlmUglcNPzvDDHsKsCTpaGJs5FVLU254cF8j IslpGH+ZkJNSDrAoZrvbzxkDqjx+eferi9pMo91BJ04yhuC/+SE48lC2Q7Lo/17mkOPF EhLmvl+pb+5wnu/o4DdArkbVdDjcMgCg6TEqE=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=FpcIys8IfqUZ6XzI5NHh9HCZ64sU9ynqodhEQvSoELcaUwmanEcNQ72seleDmeTAO7 /HrCZi1U13BLu4/hqY6Wg02EZCWHQswpT0+IoZHp/8T1aulII/jT0DHAFl8bHGCheeRh qFDOOubg/tyRmqaXArRtl1qT1+NAYDm2zc2ww=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTikXvkqFw-y92URtGJJYjxktOaSHEAuOwYt30MWT@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: <AANLkTin8j7gFkt3x_+QFrJJ+iaP7dk2q6RH5Sm8aoa1Q@xxxxxxxxxxxxxx> <20100825223415.GA6326@xxxxxxxxxxxxxxxxxxx> <AANLkTim_Fn8ZMHvtVBLz453cC+C7g0pqMKKj7MS_kLAm@xxxxxxxxxxxxxx> <20100825234330.GA6588@xxxxxxxxxxxxxxxxxxx> <AANLkTi=vYDh0XoMo9p9e+2P+sVbqH5q+RJzpYB0E+vuV@xxxxxxxxxxxxxx> <20100827140347.GA4454@xxxxxxxxxxxxxxxxxxx> <AANLkTi=_m-=WDFSd3imunXAVUsYn2B1_rvCGyOrjDOKb@xxxxxxxxxxxxxx> <20101001134529.GA28639@xxxxxxxxxxxx> <AANLkTinZa6e3tmvcHUff_S19Djchi=LK5sT9my90T6uD@xxxxxxxxxxxxxx> <20101001155820.GA29323@xxxxxxxxxxxx> <AANLkTikXvkqFw-y92URtGJJYjxktOaSHEAuOwYt30MWT@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

Installation/compilation of xen source on fedora core went through fine. I am facing an issue when dom0_mem is set to 1024M. During boot I get the message

Panic on CPU 0
Not enough RAM for domain 0 allocation

Same thing happens when dom0_mem is set to 512M

when dom0_mem is set to 256M,  I get following message

Panic on CPU 0
Domain 0 allocation is too small for kernel image

Is 8GB ram mandatory? In my machine it is 2GB ram, inputs appreciated.


On Sun, Oct 3, 2010 at 9:07 AM, Ritu kaur <ritu.kaur.us@gmail.com> wrote:
Thanks Konrad, I checked my old emails(back in March 2010) to see if I had tried this combination when I was testing xcp. I did try this combination and the problem I had faced was configuration errors due to IDE_DISK. I couldn't get past this problem. Snippets below

Thanks Konrad.
>    I downloaded new code and still doesn't work(albeit different problem). I
>    will enumerate them below
>    (Please note 1, 2 and 3 are seen with old xen/next as well). What seemed
>    simple testing of pci passthrough via config changes doesn't seem to be
>    the case.
>    1. mkinitrd doesn't work in xcp ddk. I get below errors
>    mkinitrd -f ./initrd-2.6.32.ing 2.6.32
>    modinfo: could not find module ide-disk
>    No module ide-disk found for kernel 2.6.32, aborting.

On Fri, Oct 1, 2010 at 8:58 AM, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> wrote:
On Fri, Oct 01, 2010 at 08:36:03AM -0700, Ritu kaur wrote:
> Hi Konrad,
> Frankly, I am confused. XCP(which is similar to Citrix Xenserver but
> open-source and newer-kernel) requires DDK to build a kernel image. If I
> understand your suggestion correctly I should be able to
> 1. Take PVOPS kernel code, compile it in XCP DDK and load it into dom0
> 2. Take PVOPS kernel code, compile it in domU OS and load it into domU
> then, I should be able to get pci-passthrough + shared interrupts between
> devices working correctly?  Please clarify/confirm


Xen-devel mailing list