From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ritu kaur Subject: Re: domU guest for xcp 0.1.1 Date: Sun, 21 Mar 2010 10:22:06 -0700 Message-ID: <29b32d341003211022k43817d37h6ed23913cf2b85af@mail.gmail.com> References: <29b32d341003151904m2a992be5s74697d6047b864c6@mail.gmail.com> <29b32d341003171144k628a7741x17b6658731f96e4b@mail.gmail.com> <1268903824.10129.38718.camel@zakaz.uk.xensource.com> <29b32d341003180643o326f7f43h97c25bd104f3b658@mail.gmail.com> <1268921503.10129.39640.camel@zakaz.uk.xensource.com> <20100318143906.GH14445@phenom.dumpdata.com> <29b32d341003180828j3b606b2bh8267a6cadd889240@mail.gmail.com> <20100318162641.GA24175@phenom.dumpdata.com> <29b32d341003190827yf3cddcdgc7d4713cae41cbde@mail.gmail.com> <29b32d341003201850v6328f6afp1183c16ae6771cb1@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1521706281==" Return-path: In-Reply-To: <29b32d341003201850v6328f6afp1183c16ae6771cb1@mail.gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============1521706281== Content-Type: multipart/alternative; boundary=000e0cd1b124daa73d048252d1b0 --000e0cd1b124daa73d048252d1b0 Content-Type: text/plain; charset=ISO-8859-1 Hi, I am running out of options to test pci passthrough with shared interrupts, since xen/next kernel doesn't work with xcp0.1.1 dom0. I tried couple of combinations 1. xen 3.4.3 with xen/next kernel, dom0 continuous reboot, boot messages goes off pretty fast so not sure what's going wrong here. 2. xen 3.4.3 with 2.6.27.42-0.1.1.xs0.1.1.737.1065xen(i.e which comes with xcp 0.1.1 default) system boots fine. 3. Assuming "1" is related to wrong .config file, copied kernel-2.6.27.42-0.1.1.xs0.1.1.737.1065-i686-xen.config which comes with dom0 kernel code, compiled and still same result as "1". Note: All 3, I tested by copying just xen3.4.3.gz, tools and stubdom is not copied. If there is any viable options left to try out let me know. Thanks On Sat, Mar 20, 2010 at 6:50 PM, Ritu kaur wrote: > with 3.4.3 xen and kernel code from Jeremy's xen/next puts dom0 into > continuous reboot mode. > > 1. downloaded xen/next code into DDK and generated tar-pkg, it generates > linux-2.6.32.tar. Copied this tar file into root directory of dom0 and > extracted the file. > > 2. Copied xen code from http://xenbits.xensource.com/xen-3.4-testing.hginto DDK and did "make xen", copied xen.3.4.3.gz into /boot of dom0. > > modified extlinux.conf to point to new vmlinuz and xen. dom0 is in > continuous reboot mode, let me know what am I doing wrong? > > Thanks > > > On Fri, Mar 19, 2010 at 8:27 AM, Ritu kaur wrote: > >> Thanks Konrad. I downloaded kernel code from xen/next. I believe this >> requires 3.4.3 or 4.0.0 xen hypervisor code, I downloaded xen hypervisor >> from xenbits.xensource.com/xen-unstable.hg. For xcp dom0 all compilation >> happens in DDK and no make utility is available and as I understand I need >> to execute make install-* in dom0. For install-xen probably I can copy >> xen.gz into /boot and modify files to reflect that but I am not sure what's >> the needed to install tools and stubdom in xcp dom0? >> >> make xen >> make tools >> make stubdom >> >> make install-xen >> make install-tools >> make install-stubdom >> >> Thanks >> >> >> On Thu, Mar 18, 2010 at 9:26 AM, Konrad Rzeszutek Wilk < >> konrad.wilk@oracle.com> wrote: >> >>> On Thu, Mar 18, 2010 at 08:28:18AM -0700, Ritu kaur wrote: >>> > Thanks Ian for clarification on interrupt handling mechanism. >>> > >>> > Thanks Konrad. Should I use xen/next in dom0 or domU? >>> >>> Both. >>> >> >> > --000e0cd1b124daa73d048252d1b0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

I am running out of options to test pci passthrough with shared = interrupts, since xen/next kernel doesn't work with xcp0.1.1 dom0. I tr= ied couple of combinations

1. xen 3.4.3 with xen/next kernel, dom0 c= ontinuous reboot, boot messages goes off pretty fast so not sure what's= going wrong here.

2. xen 3.4.3 with 2.6.27.42-0.1.1.xs0.1.1.737.1065xen(i.e which comes w= ith xcp 0.1.1 default) system boots fine.

3. Assuming "1" = is related to wrong .config file, copied kernel-2.6.27.42-0.1.1.xs0.1.1.737= .1065-i686-xen.config which comes with dom0 kernel code, compiled and still= same result as "1".

Note: All 3, I tested by copying just xen3.4.3.gz, tools and stubdom is= not copied. If there is any viable options left to try out let me know.
Thanks

On Sat, Mar 20, 2010 at 6:50 = PM, Ritu kaur <ritu.ka= ur.us@gmail.com> wrote:
with 3.4.3 xen an= d kernel code from Jeremy's xen/next puts dom0 into continuous reboot m= ode.

1. downloaded xen/next code into DDK and generated tar-pkg, it generate= s linux-2.6.32.tar. Copied this tar file into root directory of dom0 and ex= tracted the file.

2. Copied xen code from http://xenbits.xensource.com/xen-3.4-testing= .hg into DDK and did "make xen", copied xen.3.4.3.gz into /bo= ot of dom0.

modified extlinux.conf to point to new vmlinuz and xen. dom0 is in continuo= us reboot mode, let me know what am I doing wrong?

Thanks
=


On Fri, Mar 19, = 2010 at 8:27 AM, Ritu kaur <ritu.kaur.us@gmail.com> wrote:
Thanks Konrad. I = downloaded kernel code from=A0 xen/next. I believe this requires 3.4.3 or 4= .0.0 xen hypervisor code, I downloaded xen hypervisor from xenbits.xensourc= e.com/xen-unstable.hg. For xcp dom0 all compilation happens in DDK and = no make utility is available and as I understand I need to execute make ins= tall-* in dom0. For install-xen probably I can copy xen.gz into /boot and m= odify files to reflect that but I am not sure what's the needed to inst= all tools and stubdom in xcp dom0?

make xen
make tools
make stubdom

make install-xen
make= =20 install-tools
make install-stubdom

Thanks

On Thu, Mar 18, 2010 at 9:26 AM, Konrad Rze= szutek Wilk <konrad.wilk@oracle.com> wrote:
On Thu, Mar = 18, 2010 at 08:28:18AM -0700, Ritu kaur wrote:
> Thanks Ian for clarification on interrupt handling mechanism.
>
> Thanks Konrad. Should I use xen/next in dom0 or domU?

Both.



--000e0cd1b124daa73d048252d1b0-- --===============1521706281== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============1521706281==--