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] pci-passthrough and shared interrupts

To: 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 10:12:58 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Sun, 03 Oct 2010 10:13:49 -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=ZW6EnJrUiH2Nz6DaJqLq5VYRV98ATX3wZkL12SMxRvI=; b=PFzmWXpZsWPil1WzCzSgw0aH87qBpE0JpnTWZzWenUcVXjDk7y2c5kO+9p/xtWnfXM G9ZDafRL5/DjyLow+TQPZAshgM805cYbqVHLKX7DS9KM92PeqAUXKU6f3O+prnK7iJrH MZTiStfKceRYWCdv92LSilmSq7hZYqvPeubqY=
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=aRU7VsN6iHOlwk22BBuvo+uMpzQBXZXwaU1cQsGzsibZUag/B8rNgzLPuGeEIHbFqo lWkQsi6kcKfkKz8UElO/2shwwQOGlUAWI3ci9tifMRA0JHN9O1yqmbpc5Y1DvBVhDzXe MeczoMllN7uscgasWqDHbcQpiRIjnUznpLlHU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20101003165438.GT2804@xxxxxxxxxxx>
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: <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> <AANLkTimwWCpYCtGc_HviF0he1v7RLppk5RrxVKjmR6RA@xxxxxxxxxxxxxx> <20101003165438.GT2804@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Pasi,

I do have it as dom0_mem=256M, following is my grub.conf....

/**********************************************************
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/mapper/vg_f13-lv_root
#          initrd /initrd-[generic-]version.img
#boot=/dev/sda
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
#hiddenmenu
title Fedora (2.6.34.7-56.fc13.x86_64)
        root (hd0,0)
        kernel /vmlinuz-2.6.34.7-56.fc13.x86_64 ro root=/dev/mapper/vg_f13-lv_root rd_LVM_LV=vg_f13/lv_root rd_LVM_LV=vg_f13/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
        initrd /initramfs-2.6.34.7-56.fc13.x86_64.img
title Fedora (2.6.33.3-85.fc13.x86_64)
        root (hd0,0)
        kernel /vmlinuz-2.6.33.3-85.fc13.x86_64 ro root=/dev/mapper/vg_f13-lv_root rd_LVM_LV=vg_f13/lv_root rd_LVM_LV=vg_f13/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
        initrd /initramfs-2.6.33.3-85.fc13.x86_64.img
title Fedora Xen 4.0 with Linux 2.6.32.23 pvops dom0
        root (hd0,0)
        kernel /xen.gz dom0_mem=256M loglvl=all guest_loglvl=all
        module /vmlinuz-2.6.32.23 ro root=/dev/mapper/vg_f13-lv_root nomodeset
        module /initramfs-2.6.32.23.img
************************************************************************************************************/

Thanks

On Sun, Oct 3, 2010 at 9:54 AM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
On Sun, Oct 03, 2010 at 09:41:55AM -0700, Ritu kaur wrote:
>    Pasi,
>
>    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.
>

It sounds like you wrote the value wrong, ie. you didn't specify 'M' to make it megabytes,
so you got kilobytes.. and thus it's too small to fit the dom0 kernel image there.

-- Pasi

>    Thanks
>
>    On Sun, Oct 3, 2010 at 9:07 AM, Ritu kaur <[1]ritu.kaur.us@[2]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
>      <[3]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
>
>        Yes.
>
> References
>
>    Visible links
>    1. http://ritu.kaur.us/
>    2. http://gmail.com/
>    3. mailto:konrad.wilk@xxxxxxxxxx

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