Using=20 Xen/paravirt_ops

Building with domU support

Get a curre= nt=20 kernel. The latest kernel.org kernel is = generally a good choice.

Configure as normal; you can start with your current .config file

If building 32 bit kernel make sure you have CONFIG_X86_PAE enabled (which is set by selecting CONFIG_HIGHMEM64G)

non-PAE mode doesn't work in 2.6.25, and has been dropped altogether from 2.6.26 and newer kernel versions.

Enable these core=20 options:

CO= NFIG_PARAVIRT_GUEST
CONFIG_XEN

And Xen pv device=20 support

CON= FIG_HVC_DRIVER and CONFIG_HVC_XEN
C= ONFIG_XEN_BLKDEV_FRONTEND
CONFIG_XEN_NETDEV_FR= ONTEND

And build= =20 as usual

kernel.org

On Fri, Mar 12, 20= 10 at 9:51 AM, Pasi K=E4rkk=E4inen <pasik@iki.fi> wrote:

On Fri, Mar 12, 2010 at 09:10:31AM -0800, Ritu kaur wrote= :
> =A0 =A0Hi,
>
> =A0 =A0I am expanding my question to developers forum to get some quic= k help on
> =A0 =A0pci passthrough. I am using xcp 0.1.1 as a dom0 and installed D= ebian Lenny
> =A0 =A0as a domU(as mentioned in

> =A0 =A0[1]http://wiki.xensource.com/xenwiki/Command_= Line_Interface).

> =A0 =A0Unfortunately, Debian Lenny which the wiki po= ints to doesn't come with PV

> =A0 =A0drivers(I need pcifront driver). I looked up in [2]wiki.debian.org/Xen = and

> =A0 =A0I found following snippets
>
> =A0 =A0/***The default Lenny kernel is the newer paravirt_ops version = (2.6.26),
> =A0 =A0which does not function as a dom0 (except for the -xen variants= , which
> =A0 =A0have dom0 support but also some issues running as domU (please = clarify?).
> =A0 =A0It will also not support PCI passthrough in a domU. For PCI pas= sthrough,
> =A0 =A0you have to run the 2.6.18 etch kernel as both dom0 and domU. *= **/
>

I don't know if there are pre-packaged kernels for lenny with pci= front driver.

Links to kernel sources that have the pcifront driver:

=A0 =A0 =A0 =A0- http://xenbits.xen.org/linux-2.6.18-xen.hg
=A0 =A0 =A0 =A0- pv_ops xen.git xen/stable 2.6.32.9 and xen/master 2.6.31.= 6
=A0 =A0 =A0 =A0 =A0(See: http://wiki.xensource.com/xenwiki/XenParavirt= Ops)
=A0 =A0 =A0 =A0- Kernels with the forward-ported Novell/opensuse Xen patch= es (2.6.29, 2.6.31, 2.6.33)
=A0 =A0 =A0 =A0 =A0(See: http://wiki.xensource.com/xenwiki/XenDom0Kern= els)

> =A0 =A0Can someone let me know what domU has been tested with XCP 0.1.= 1 for pci
> =A0 =A0passthrough and any pointers to that domU kernel binary or sour= ce will
> =A0 =A0help me out.
>

Unfortunately I don't know what kernel has been tested.

-- Pasi

Subject: Re: domU guest for xcp 0.1.1 Date: Sat, 13 Mar 2010 13:18:57 +0200 Message-ID: <20100313111857.GS1878@reaktio.net> References: <29b32d341003120910l5340bc01tcada3ca2adbaf763@mail.gmail.com> <20100312175135.GK1878@reaktio.net> <29b32d341003121751s517ea28qbdb78e8cc69243ac@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <29b32d341003121751s517ea28qbdb78e8cc69243ac@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: Ritu kaur Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Fri, Mar 12, 2010 at 05:51:20PM -0800, Ritu kaur wrote: > Thanks Pasi. I looked at > [1]http://wiki.xensource.com/xenwiki/XenParavirtOps(my foray into li= nux is > via xen, so please pardon by silly questions) >=20 > Using Xen/paravirt_ops >=20 > Building with domU support >=20 > 1. Get a current kernel. The latest [2]kernel.org kernel is general= ly a > good choice. > 2. Configure as normal; you can start with your current .config fil= e > 3. If building 32 bit kernel make sure you have CONFIG_X86_PAE enab= led > (which is set by selecting CONFIG_HIGHMEM64G) >=20 > * non-PAE mode doesn't work in 2.6.25, and has been dropped > altogether from 2.6.26 and newer kernel versions. >=20 > 4. Enable these core options: >=20 > 1. CONFIG_PARAVIRT_GUEST > 2. CONFIG_XEN >=20 > 5. And Xen pv device support >=20 > 1. CONFIG_HVC_DRIVER and CONFIG_HVC_XEN > 2. CONFIG_XEN_BLKDEV_FRONTEND > 3. CONFIG_XEN_NETDEV_FRONTEND >=20 > 6. And build as usual >=20 > Config doesn't have pcifront in it? don't I need it for pci passthro= ugh? I > have copied linux 2.6.33 source from [3]kernel.org and started build= ing > kernel(irrespective of above questions), but what distribution is th= is > kernel associated with i.e I thought I should first install linux fr= om a > distribution and rebuild kernel for any modification, but in this ca= se I > don't understand what distribution this is associated with. Inputs m= uch > appreciated. >=20 You need to check out Jeremy's xen.git, and possibly xen/stable branch fr= om there, to have the pcifront driver. It's not yet in the upstream kernel.org kern= el. -- Pasi > Thanks >=20 > On Fri, Mar 12, 2010 at 9:51 AM, Pasi K=E4rkk=E4inen <[4]pasik@iki.f= i> wrote: >=20 > On Fri, Mar 12, 2010 at 09:10:31AM -0800, Ritu kaur wrote: > > Hi, > > > > I am expanding my question to developers forum to get some qu= ick > help on > > pci passthrough. I am using xcp 0.1.1 as a dom0 and installed > Debian Lenny > > as a domU(as mentioned in > > [1][5]http://wiki.xensource.com/xenwiki/Command_Line_Interfac= e). > > Unfortunately, Debian Lenny which the wiki points to doesn't = come > with PV > > drivers(I need pcifront driver). I looked up in > [2][6]wiki.debian.org/Xen and > > I found following snippets > > > > /***The default Lenny kernel is the newer paravirt_ops versio= n > (2.6.26), > > which does not function as a dom0 (except for the -xen varian= ts, > which > > have dom0 support but also some issues running as domU (pleas= e > clarify?). > > It will also not support PCI passthrough in a domU. For PCI > passthrough, > > you have to run the 2.6.18 etch kernel as both dom0 and domU.= ***/ > > >=20 > I don't know if there are pre-packaged kernels for lenny with pcif= ront > driver. >=20 > Links to kernel sources that have the pcifront driver: >=20 > - [7]http://xenbits.xen.org/linux-2.6.18-xen.hg > - pv_ops xen.git xen/stable 2.6.32.9 and xen/master 2.6.31.= 6 > (See: [8]http://wiki.xensource.com/xenwiki/XenParavirtOps= ) > - Kernels with the forward-ported Novell/opensuse Xen patch= es > (2.6.29, 2.6.31, 2.6.33) > (See: [9]http://wiki.xensource.com/xenwiki/XenDom0Kernels= ) > > Can someone let me know what domU has been tested with XCP 0.= 1.1 > for pci > > passthrough and any pointers to that domU kernel binary or so= urce > will > > help me out. > > >=20 > Unfortunately I don't know what kernel has been tested. > -- Pasi >=20 > References >=20 > Visible links > 1. http://wiki.xensource.com/xenwiki/XenParavirtOps(my > 2. http://kernel.org/ > 3. http://kernel.org/ > 4. mailto:pasik@iki.fi > 5. http://wiki.xensource.com/xenwiki/Command_Line_Interface > 6. http://wiki.debian.org/Xen > 7. http://xenbits.xen.org/linux-2.6.18-xen.hg > 8. http://wiki.xensource.com/xenwiki/XenParavirtOps > 9. http://wiki.xensource.com/xenwiki/XenDom0Kernels From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ritu kaur Subject: Re: domU guest for xcp 0.1.1 Date: Sat, 13 Mar 2010 08:09:36 -0800 Message-ID: <29b32d341003130809u49d1edcas234fdca4c3d70ed@mail.gmail.com> References: <29b32d341003120910l5340bc01tcada3ca2adbaf763@mail.gmail.com> <20100312175135.GK1878@reaktio.net> <29b32d341003121751s517ea28qbdb78e8cc69243ac@mail.gmail.com> <20100313111857.GS1878@reaktio.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0359337520==" Return-path: In-Reply-To: <20100313111857.GS1878@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============0359337520== Content-Type: multipart/alternative; boundary=000e0cd242a0d2c6330481b0dfe9 --000e0cd242a0d2c6330481b0dfe9 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thanks again. As I understand from wiki page, Jeremy's xen.git and xen/stable code are for building dom0 kernel. Can dom0 kernel be used as a domU? At least last time I checked I was told I cannot use it. Thanks On Sat, Mar 13, 2010 at 3:18 AM, Pasi K=E4rkk=E4inen wrote: > On Fri, Mar 12, 2010 at 05:51:20PM -0800, Ritu kaur wrote: > > Thanks Pasi. I looked at > > [1]http://wiki.xensource.com/xenwiki/XenParavirtOps(myforay into linux is > > via xen, so please pardon by silly questions) > > > > Using Xen/paravirt_ops > > > > Building with domU support > > > > 1. Get a current kernel. The latest [2]kernel.org kernel is > generally a > > good choice. > > 2. Configure as normal; you can start with your current .config fil= e > > 3. If building 32 bit kernel make sure you have CONFIG_X86_PAE > enabled > > (which is set by selecting CONFIG_HIGHMEM64G) > > > > * non-PAE mode doesn't work in 2.6.25, and has been dropped > > altogether from 2.6.26 and newer kernel versions. > > > > 4. Enable these core options: > > > > 1. CONFIG_PARAVIRT_GUEST > > 2. CONFIG_XEN > > > > 5. And Xen pv device support > > > > 1. CONFIG_HVC_DRIVER and CONFIG_HVC_XEN > > 2. CONFIG_XEN_BLKDEV_FRONTEND > > 3. CONFIG_XEN_NETDEV_FRONTEND > > > > 6. And build as usual > > > > Config doesn't have pcifront in it? don't I need it for pci > passthrough? I > > have copied linux 2.6.33 source from [3]kernel.org and started > building > > kernel(irrespective of above questions), but what distribution is th= is > > kernel associated with i.e I thought I should first install linux fr= om > a > > distribution and rebuild kernel for any modification, but in this ca= se > I > > don't understand what distribution this is associated with. Inputs > much > > appreciated. > > > > You need to check out Jeremy's xen.git, and possibly xen/stable branch fr= om > there, > to have the pcifront driver. It's not yet in the upstream kernel.orgkerne= l. > > -- Pasi > > > Thanks > > > > On Fri, Mar 12, 2010 at 9:51 AM, Pasi K=E4rkk=E4inen <[4]pasik@iki.f= i> > wrote: > > > > On Fri, Mar 12, 2010 at 09:10:31AM -0800, Ritu kaur wrote: > > > Hi, > > > > > > I am expanding my question to developers forum to get some > quick > > help on > > > pci passthrough. I am using xcp 0.1.1 as a dom0 and installed > > Debian Lenny > > > as a domU(as mentioned in > > > [1][5]http://wiki.xensource.com/xenwiki/Command_Line_Interfac= e > ). > > > Unfortunately, Debian Lenny which the wiki points to doesn't > come > > with PV > > > drivers(I need pcifront driver). I looked up in > > [2][6]wiki.debian.org/Xen and > > > I found following snippets > > > > > > /***The default Lenny kernel is the newer paravirt_ops versio= n > > (2.6.26), > > > which does not function as a dom0 (except for the -xen > variants, > > which > > > have dom0 support but also some issues running as domU (pleas= e > > clarify?). > > > It will also not support PCI passthrough in a domU. For PCI > > passthrough, > > > you have to run the 2.6.18 etch kernel as both dom0 and domU. > ***/ > > > > > > > I don't know if there are pre-packaged kernels for lenny with > pcifront > > driver. > > > > Links to kernel sources that have the pcifront driver: > > > > - [7]http://xenbits.xen.org/linux-2.6.18-xen.hg > > - pv_ops xen.git xen/stable 2.6.32.9 and xen/master 2.6.31.= 6 > > (See: [8]http://wiki.xensource.com/xenwiki/XenParavirtOps= ) > > - Kernels with the forward-ported Novell/opensuse Xen patch= es > > (2.6.29, 2.6.31, 2.6.33) > > (See: [9]http://wiki.xensource.com/xenwiki/XenDom0Kernels= ) > > > Can someone let me know what domU has been tested with XCP > 0.1.1 > > for pci > > > passthrough and any pointers to that domU kernel binary or > source > > will > > > help me out. > > > > > > > Unfortunately I don't know what kernel has been tested. > > -- Pasi > > > > References > > > > Visible links > > 1. http://wiki.xensource.com/xenwiki/XenParavirtOps(my > > 2. http://kernel.org/ > > 3. http://kernel.org/ > > 4. mailto:pasik@iki.fi > > 5. http://wiki.xensource.com/xenwiki/Command_Line_Interface > > 6. http://wiki.debian.org/Xen > > 7. http://xenbits.xen.org/linux-2.6.18-xen.hg > > 8. http://wiki.xensource.com/xenwiki/XenParavirtOps > > 9. http://wiki.xensource.com/xenwiki/XenDom0Kernels > --000e0cd242a0d2c6330481b0dfe9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thanks again. As I understand from wiki page, Jeremy's xen.git and xen/= stable code are for building dom0 kernel. Can dom0 kernel be used as a domU= ? At least last time I checked I was told I cannot use it.

Thanks

On Sat, Mar 13, 2010 at 3:18 AM, Pasi K=E4rk= k=E4inen <pasik@iki.fi= > wrote:

On Fri, Mar 12, 2010 at 05:51:20PM -0800, Ritu kaur wrote= :
> =A0 =A0Thanks Pasi. I looked at

> =A0 =A0[1]http://wiki.xensource.com/xenwiki/XenParavirt= Ops(my foray into linux is

> =A0 =A0via xen, so please pardon by silly questions)=
>
> Using Xen/paravirt_ops
>
> =A0 Building with domU support
>

> =A0 =A0 1. Get a current kernel. The latest [2]kernel.org kernel is generally a
> =A0 =A0 =A0 =A0good choice.
> =A0 =A0 2. Configure as normal; you can start with your current .confi= g file
> =A0 =A0 3. If building 32 bit kernel make sure you have CONFIG_X86_PAE= enabled

> =A0 =A0 =A0 =A0(which is set by selecting CONFIG_HIG= HMEM64G)
>
> =A0 =A0 =A0 =A0 =A0 * non-PAE mode doesn't work in 2.6.25, and has= been dropped
> =A0 =A0 =A0 =A0 =A0 =A0 altogether from 2.6.26 and newer kernel versio= ns.
>

> =A0 =A0 4. Enable these core options:
>
> =A0 =A0 =A0 =A0 =A01. CONFIG_PARAVIRT_GUEST
> =A0 =A0 =A0 =A0 =A02. CONFIG_XEN
>
> =A0 =A0 5. And Xen pv device support
>
> =A0 =A0 =A0 =A0 =A01. CONFIG_HVC_DRIVER and CONFIG_HVC_XEN
> =A0 =A0 =A0 =A0 =A02. CONFIG_XEN_BLKDEV_FRONTEND
> =A0 =A0 =A0 =A0 =A03. CONFIG_XEN_NETDEV_FRONTEND
>
> =A0 =A0 6. And build as usual

>
> =A0 =A0Config doesn't have pcifront in it? don't I need it for= pci passthrough? I

> =A0 =A0have copied linux 2.6.33 source from [3]kernel.org and started building

> =A0 =A0kernel(irrespective of above questions), but = what distribution is this
> =A0 =A0kernel associated with i.e I thought I should first install lin= ux from a
> =A0 =A0distribution and rebuild kernel for any modification, but in th= is case I
> =A0 =A0don't understand what distribution this is associated with.= Inputs much
> =A0 =A0appreciated.
>

You need to check out Jeremy's xen.git, and possibly xen/stable b= ranch from there,
to have the pcifront driver. It's not yet in the upstream kernel.org kernel.

-- Pasi

> =A0 =A0Thanks

>
> =A0 =A0On Fri, Mar 12, 2010 at 9:51 AM, Pasi K=E4rkk=E4inen <[4]pasik@iki.fi> wrote:
>
> =A0 =A0 =A0On Fri, Mar 12, 2010 at 09:10:31AM -0800, Ritu kaur wrote:<= br> > =A0 =A0 =A0> =A0 =A0Hi,
> =A0 =A0 =A0>
> =A0 =A0 =A0> =A0 =A0I am expanding my question to developers forum = to get some quick
> =A0 =A0 =A0help on
> =A0 =A0 =A0> =A0 =A0pci passthrough. I am using xcp 0.1.1 as a dom0= and installed
> =A0 =A0 =A0Debian Lenny
> =A0 =A0 =A0> =A0 =A0as a domU(as mentioned in

> =A0 =A0 =A0> =A0 =A0[1][5]http://wiki.xensource.c= om/xenwiki/Command_Line_Interface).

> =A0 =A0 =A0> =A0 =A0Unfortunately, Debian Lenny w= hich the wiki points to doesn't come
> =A0 =A0 =A0with PV
> =A0 =A0 =A0> =A0 =A0drivers(I need pcifront driver). I looked up in=

> =A0 =A0 =A0[2][6]wiki.debian.org/Xen and

> =A0 =A0 =A0> =A0 =A0I found following snippets > =A0 =A0 =A0>
> =A0 =A0 =A0> =A0 =A0/***The default Lenny kernel is the newer parav= irt_ops version
> =A0 =A0 =A0(2.6.26),
> =A0 =A0 =A0> =A0 =A0which does not function as a dom0 (except for t= he -xen variants,
> =A0 =A0 =A0which
> =A0 =A0 =A0> =A0 =A0have dom0 support but also some issues running = as domU (please
> =A0 =A0 =A0clarify?).
> =A0 =A0 =A0> =A0 =A0It will also not support PCI passthrough in a d= omU. For PCI
> =A0 =A0 =A0passthrough,
> =A0 =A0 =A0> =A0 =A0you have to run the 2.6.18 etch kernel as both = dom0 and domU. ***/
> =A0 =A0 =A0>
>
> =A0 =A0 =A0I don't know if there are pre-packaged kernels for lenn= y with pcifront
> =A0 =A0 =A0driver.
>
> =A0 =A0 =A0Links to kernel sources that have the pcifront driver:
>

> =A0 =A0 =A0 =A0 =A0 =A0 - [7]http://xenbits.xen.org/linux-2.6.18-x= en.hg

> =A0 =A0 =A0 =A0 =A0 =A0 - pv_ops xen.git xen/stable = 2.6.32.9 and xen/master 2.6.31.6

> =A0 =A0 =A0 =A0 =A0 =A0 =A0 (See: [8]http://wiki.xensource.c= om/xenwiki/XenParavirtOps)

> =A0 =A0 =A0 =A0 =A0 =A0 - Kernels with the forward-p= orted Novell/opensuse Xen patches
> =A0 =A0 =A0(2.6.29, 2.6.31, 2.6.33)

> =A0 =A0 =A0 =A0 =A0 =A0 =A0 (See: [9]http://wiki.xensource.c= om/xenwiki/XenDom0Kernels)

> =A0 =A0 =A0> =A0 =A0Can someone let me know what = domU has been tested with XCP 0.1.1
> =A0 =A0 =A0for pci
> =A0 =A0 =A0> =A0 =A0passthrough and any pointers to that domU kerne= l binary or source
> =A0 =A0 =A0will
> =A0 =A0 =A0> =A0 =A0help me out.
> =A0 =A0 =A0>
>
> =A0 =A0 =A0Unfortunately I don't know what kernel has been tested.=
> =A0 =A0 =A0-- Pasi
>

> References
>
> =A0 =A0Visible links
> =A0 =A01. http://wiki.xensource.com/xenwiki/XenParavirtOps(my=
> =A0 =A02. http://kern= el.org/
> =A0 =A03. http://kern= el.org/
> =A0 =A04. mailto:pasik@iki.fi
> =A0 =A05. http://wiki.xensource.com/xenwiki/Command_Line_I= nterface
> =A0 =A06. htt= p://wiki.debian.org/Xen
> =A0 =A07. http://xenbits.xen.org/linux-2.6.18-xen.hg
> =A0 =A08. http://wiki.xensource.com/xenwiki/XenParavirtOps
> =A0 =A09. http://wiki.xensource.com/xenwiki/XenDom0Kernels

--000e0cd242a0d2c6330481b0dfe9-- --===============0359337520== 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 --===============0359337520==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: domU guest for xcp 0.1.1 Date: Sat, 13 Mar 2010 18:41:02 +0200 Message-ID: <20100313164102.GZ1878@reaktio.net> References: <29b32d341003120910l5340bc01tcada3ca2adbaf763@mail.gmail.com> <20100312175135.GK1878@reaktio.net> <29b32d341003121751s517ea28qbdb78e8cc69243ac@mail.gmail.com> <20100313111857.GS1878@reaktio.net> <29b32d341003130809u49d1edcas234fdca4c3d70ed@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <29b32d341003130809u49d1edcas234fdca4c3d70ed@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: Ritu kaur Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Sat, Mar 13, 2010 at 08:09:36AM -0800, Ritu kaur wrote: > Thanks again. As I understand from wiki page, Jeremy's xen.git and > xen/stable code are for building dom0 kernel. Can dom0 kernel be use= d as a > domU? At least last time I checked I was told I cannot use it. >=20 Yes, you can use the dom0 kernel also as domU, just make sure you build=20 the frontend drivers aswell. Actually you've been able to use the same kernel for both dom0 and domU f= or years, this is how distributions like RHEL5/CentOS5, Debian etch/lenny, Fedora 6= /7/8, SLES10/11, OpenSUSE, etc ship their kernels. The same kernel image works = for=20 both dom0 and domU. Actually pvops makes it possible to boot the exact same kernel image on b= aremetal (non-Xen), Xen dom0 and domU! -- Pasi > Thanks >=20 > On Sat, Mar 13, 2010 at 3:18 AM, Pasi K=E4rkk=E4inen <[1]pasik@iki.f= i> wrote: >=20 > On Fri, Mar 12, 2010 at 05:51:20PM -0800, Ritu kaur wrote: > > Thanks Pasi. I looked at > > [1][2]http://wiki.xensource.com/xenwiki/XenParavirtOps(my for= ay > into linux is > > via xen, so please pardon by silly questions) > > > > Using Xen/paravirt_ops > > > > Building with domU support > > > > 1. Get a current kernel. The latest [2][3]kernel.org kernel = is > generally a > > good choice. > > 2. Configure as normal; you can start with your current .con= fig > file > > 3. If building 32 bit kernel make sure you have CONFIG_X86_P= AE > enabled > > (which is set by selecting CONFIG_HIGHMEM64G) > > > > * non-PAE mode doesn't work in 2.6.25, and has been dr= opped > > altogether from 2.6.26 and newer kernel versions. > > > > 4. Enable these core options: > > > > 1. CONFIG_PARAVIRT_GUEST > > 2. CONFIG_XEN > > > > 5. And Xen pv device support > > > > 1. CONFIG_HVC_DRIVER and CONFIG_HVC_XEN > > 2. CONFIG_XEN_BLKDEV_FRONTEND > > 3. CONFIG_XEN_NETDEV_FRONTEND > > > > 6. And build as usual > > > > Config doesn't have pcifront in it? don't I need it for pci > passthrough? I > > have copied linux 2.6.33 source from [3][4]kernel.org and sta= rted > building > > kernel(irrespective of above questions), but what distributio= n is > this > > kernel associated with i.e I thought I should first install l= inux > from a > > distribution and rebuild kernel for any modification, but in = this > case I > > don't understand what distribution this is associated with. I= nputs > much > > appreciated. > > >=20 > You need to check out Jeremy's xen.git, and possibly xen/stable br= anch > from there, > to have the pcifront driver. It's not yet in the upstream [5]kerne= l.org > kernel. >=20 > -- Pasi >=20 > > Thanks > > > > On Fri, Mar 12, 2010 at 9:51 AM, Pasi K=E4rkk=E4inen > <[4][6]pasik@iki.fi> wrote: > > > > On Fri, Mar 12, 2010 at 09:10:31AM -0800, Ritu kaur wrote: > > > Hi, > > > > > > I am expanding my question to developers forum to get = some > quick > > help on > > > pci passthrough. I am using xcp 0.1.1 as a dom0 and > installed > > Debian Lenny > > > as a domU(as mentioned in > > > > [1][5][7]http://wiki.xensource.com/xenwiki/Command_Line_Interface= ). > > > Unfortunately, Debian Lenny which the wiki points to d= oesn't > come > > with PV > > > drivers(I need pcifront driver). I looked up in > > [2][6][8]wiki.debian.org/Xen and > > > I found following snippets > > > > > > /***The default Lenny kernel is the newer paravirt_ops > version > > (2.6.26), > > > which does not function as a dom0 (except for the -xen > variants, > > which > > > have dom0 support but also some issues running as domU > (please > > clarify?). > > > It will also not support PCI passthrough in a domU. Fo= r PCI > > passthrough, > > > you have to run the 2.6.18 etch kernel as both dom0 an= d > domU. ***/ > > > > > > > I don't know if there are pre-packaged kernels for lenny wi= th > pcifront > > driver. > > > > Links to kernel sources that have the pcifront driver: > > > > - [7][9]http://xenbits.xen.org/linux-2.6.18-xen.hg > > - pv_ops xen.git xen/stable 2.6.32.9 and xen/master > 2.6.31.6 > > (See: > [8][10]http://wiki.xensource.com/xenwiki/XenParavirtOps) > > - Kernels with the forward-ported Novell/opensuse Xe= n > patches > > (2.6.29, 2.6.31, 2.6.33) > > (See: > [9][11]http://wiki.xensource.com/xenwiki/XenDom0Kernels) > > > Can someone let me know what domU has been tested with= XCP > 0.1.1 > > for pci > > > passthrough and any pointers to that domU kernel binar= y or > source > > will > > > help me out. > > > > > > > Unfortunately I don't know what kernel has been tested. > > -- Pasi > > > > References > > > > Visible links > > 1. [12]http://wiki.xensource.com/xenwiki/XenParavirtOps(my > > 2. [13]http://kernel.org/ > > 3. [14]http://kernel.org/ > > 4. mailto:[15]pasik@iki.fi > > 5. [16]http://wiki.xensource.com/xenwiki/Command_Line_Interfa= ce > > 6. [17]http://wiki.debian.org/Xen > > 7. [18]http://xenbits.xen.org/linux-2.6.18-xen.hg > > 8. [19]http://wiki.xensource.com/xenwiki/XenParavirtOps > > 9. [20]http://wiki.xensource.com/xenwiki/XenDom0Kernels >=20 > References >=20 > Visible links > 1. mailto:pasik@iki.fi > 2. http://wiki.xensource.com/xenwiki/XenParavirtOps%28my > 3. http://kernel.org/ > 4. http://kernel.org/ > 5. http://kernel.org/ > 6. mailto:pasik@iki.fi > 7. http://wiki.xensource.com/xenwiki/Command_Line_Interface > 8. http://wiki.debian.org/Xen > 9. http://xenbits.xen.org/linux-2.6.18-xen.hg > 10. http://wiki.xensource.com/xenwiki/XenParavirtOps > 11. http://wiki.xensource.com/xenwiki/XenDom0Kernels > 12. http://wiki.xensource.com/xenwiki/XenParavirtOps%28my > 13. http://kernel.org/ > 14. http://kernel.org/ > 15. mailto:pasik@iki.fi > 16. http://wiki.xensource.com/xenwiki/Command_Line_Interface > 17. http://wiki.debian.org/Xen > 18. http://xenbits.xen.org/linux-2.6.18-xen.hg > 19. http://wiki.xensource.com/xenwiki/XenParavirtOps > 20. http://wiki.xensource.com/xenwiki/XenDom0Kernels From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ritu kaur Subject: Re: domU guest for xcp 0.1.1 Date: Sat, 13 Mar 2010 17:43:23 -0800 Message-ID: <29b32d341003131743j6ae271d6of486a3c1a4858513@mail.gmail.com> References: <29b32d341003120910l5340bc01tcada3ca2adbaf763@mail.gmail.com> <20100312175135.GK1878@reaktio.net> <29b32d341003121751s517ea28qbdb78e8cc69243ac@mail.gmail.com> <20100313111857.GS1878@reaktio.net> <29b32d341003130809u49d1edcas234fdca4c3d70ed@mail.gmail.com> <20100313164102.GZ1878@reaktio.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1543345690==" Return-path: In-Reply-To: <20100313164102.GZ1878@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============1543345690== Content-Type: multipart/alternative; boundary=000e0cd242a0dc04a30481b8e37c --000e0cd242a0dc04a30481b8e37c Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable I followed the steps mentioned in wiki to pull xen code to compile domU kernel from 1. xen/master, I get following compilation errors. I do see in xen-devel forum someone else has reported similar issue but no solution yet(patch provided by Konrad has followup errors) CC [M] drivers/watchdog/machzwd.o CC [M] drivers/watchdog/sbc_epx_c3.o CC [M] drivers/watchdog/softdog.o CC drivers/xen/grant-table.o CC drivers/xen/features.o CC drivers/xen/events.o drivers/xen/events.c:605: error: redefinition of =E2=80=98xen_destroy_irq= =E2=80=99 /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29: error: previous definition of =E2=80=98xen_destroy_irq=E2=80=99 was here drivers/xen/events.c:637: error: redefinition of =E2=80=98xen_create_msi_ir= q=E2=80=99 /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25: error: previous definition of =E2=80=98xen_create_msi_irq=E2=80=99 was here make[2]: *** [drivers/xen/events.o] Error 1 make[1]: *** [drivers/xen] Error 2 make: *** [drivers] Error 2 2. xen/stable, I get following errors CC drivers/pci/xen-pcifront.o drivers/pci/xen-pcifront.c:373: error: variable =E2=80=98pci_frontend_ops= =E2=80=99 has initializut incomplete type drivers/pci/xen-pcifront.c:374: error: unknown field =E2=80=98enable_msi=E2= =80=99 specified in ializer drivers/pci/xen-pcifront.c:374: warning: excess elements in struct initializer drivers/pci/xen-pcifront.c:374: warning: (near initialization for =E2=80=98pci_frontend_op)=E2=80=99 drivers/pci/xen-pcifront.c:375: error: unknown field =E2=80=98disable_msi= =E2=80=99 specified in ializer drivers/pci/xen-pcifront.c:375: warning: excess elements in struct initializer drivers/pci/xen-pcifront.c:375: warning: (near initialization for =E2=80=98pci_frontend_op)=E2=80=99 drivers/pci/xen-pcifront.c:376: error: unknown field =E2=80=98enable_msix= =E2=80=99 specified in ializer drivers/pci/xen-pcifront.c:376: warning: excess elements in struct initializer drivers/pci/xen-pcifront.c:376: warning: (near initialization for =E2=80=98pci_frontend_op)=E2=80=99 drivers/pci/xen-pcifront.c:377: error: unknown field =E2=80=98disable_msix= =E2=80=99 specified intializer drivers/pci/xen-pcifront.c:377: warning: excess elements in struct initializer drivers/pci/xen-pcifront.c:377: warning: (near initialization for =E2=80=98pci_frontend_op)=E2=80=99 drivers/pci/xen-pcifront.c: In function =E2=80=98pci_frontend_registrar=E2= =80=99: drivers/pci/xen-pcifront.c:383: error: =E2=80=98xen_pci_frontend=E2=80=99 u= ndeclared (first use his function) drivers/pci/xen-pcifront.c:383: error: (Each undeclared identifier is reported only once drivers/pci/xen-pcifront.c:383: error: for each function it appears in.) make[2]: *** [drivers/pci/xen-pcifront.o] Error 1 make[1]: *** [drivers/pci] Error 2 make: *** [drivers] Error 2 Kindly let me know how to proceed on this. Thanks --000e0cd242a0dc04a30481b8e37c Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable I followed the steps mentioned in=A0 wiki to pull xen code to compile domU = kernel from

1. xen/master, I get following compilation errors. I do = see in xen-devel forum someone else has reported similar issue but no solut= ion yet(patch provided by Konrad has followup errors)

CC [M]=A0 drivers/watchdog/machzwd.o
=A0 CC [M]=A0 drivers/watchdog/= sbc_epx_c3.o
=A0 CC [M]=A0 drivers/watchdog/softdog.o
=A0 CC=A0=A0=A0= =A0=A0 drivers/xen/grant-table.o
=A0 CC=A0=A0=A0=A0=A0 drivers/xen/featu= res.o
=A0 CC=A0=A0=A0=A0=A0 drivers/xen/events.o
drivers/xen/events.c:605: error: redefinition of =E2=80=98xen_destroy_irq= =E2=80=99
/root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29: = error: previous definition of =E2=80=98xen_destroy_irq=E2=80=99 was heredrivers/xen/events.c:637: error: redefinition of =E2=80=98xen_create_msi_i= rq=E2=80=99
/root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25: error: previo= us definition of =E2=80=98xen_create_msi_irq=E2=80=99 was here
make[2]: = *** [drivers/xen/events.o] Error 1
make[1]: *** [drivers/xen] Error 2make: *** [drivers] Error 2

2. xen/stable, I get following errors

=A0CC=A0=A0=A0=A0=A0 drive= rs/pci/xen-pcifront.o
drivers/pci/xen-pcifront.c:373: error: variable = =E2=80=98pci_frontend_ops=E2=80=99 has initializut incomplete type
drive= rs/pci/xen-pcifront.c:374: error: unknown field =E2=80=98enable_msi=E2=80= =99 specified in ializer
drivers/pci/xen-pcifront.c:374: warning: excess elements in struct initiali= zer
drivers/pci/xen-pcifront.c:374: warning: (near initialization for = =E2=80=98pci_frontend_op)=E2=80=99
drivers/pci/xen-pcifront.c:375: erro= r: unknown field =E2=80=98disable_msi=E2=80=99 specified in ializer
drivers/pci/xen-pcifront.c:375: warning: excess elements in struct initiali= zer
drivers/pci/xen-pcifront.c:375: warning: (near initialization for = =E2=80=98pci_frontend_op)=E2=80=99
drivers/pci/xen-pcifront.c:376: erro= r: unknown field =E2=80=98enable_msix=E2=80=99 specified in ializer
drivers/pci/xen-pcifront.c:376: warning: excess elements in struct initiali= zer
drivers/pci/xen-pcifront.c:376: warning: (near initialization for = =E2=80=98pci_frontend_op)=E2=80=99
drivers/pci/xen-pcifront.c:377: erro= r: unknown field =E2=80=98disable_msix=E2=80=99 specified intializer
drivers/pci/xen-pcifront.c:377: warning: excess elements in struct initiali= zer
drivers/pci/xen-pcifront.c:377: warning: (near initialization for = =E2=80=98pci_frontend_op)=E2=80=99
drivers/pci/xen-pcifront.c: In funct= ion =E2=80=98pci_frontend_registrar=E2=80=99:
drivers/pci/xen-pcifront.c:383: error: =E2=80=98xen_pci_frontend=E2=80=99 u= ndeclared (first use his function)
drivers/pci/xen-pcifront.c:383: error= : (Each undeclared identifier is reported only once
drivers/pci/xen-pcif= ront.c:383: error: for each function it appears in.)
make[2]: *** [drivers/pci/xen-pcifront.o] Error 1
make[1]: *** [drivers/= pci] Error 2
make: *** [drivers] Error 2

Kindly let me know how t= o proceed on this.

Thanks

--000e0cd242a0dc04a30481b8e37c-- --===============1543345690== 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 --===============1543345690==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: pvops xen/master and xen/stable domU kernel compilation errors Date: Sun, 14 Mar 2010 11:04:53 +0200 Message-ID: <20100314090453.GA1878@reaktio.net> References: <29b32d341003120910l5340bc01tcada3ca2adbaf763@mail.gmail.com> <20100312175135.GK1878@reaktio.net> <29b32d341003121751s517ea28qbdb78e8cc69243ac@mail.gmail.com> <20100313111857.GS1878@reaktio.net> <29b32d341003130809u49d1edcas234fdca4c3d70ed@mail.gmail.com> <20100313164102.GZ1878@reaktio.net> <29b32d341003131743j6ae271d6of486a3c1a4858513@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <29b32d341003131743j6ae271d6of486a3c1a4858513@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: Ritu kaur Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Sat, Mar 13, 2010 at 05:43:23PM -0800, Ritu kaur wrote: > I followed the steps mentioned in wiki to pull xen code to compile = domU > kernel from >=20 > 1. xen/master, I get following compilation errors. I do see in xen-d= evel > forum someone else has reported similar issue but no solution yet(pa= tch > provided by Konrad has followup errors) >=20 Hmm.. the error below seems pretty easy to solve. Maybe Konrad already ha= s a patch for this. > CC [M] drivers/watchdog/machzwd.o > CC [M] drivers/watchdog/sbc_epx_c3.o > CC [M] drivers/watchdog/softdog.o > CC drivers/xen/grant-table.o > CC drivers/xen/features.o > CC drivers/xen/events.o > drivers/xen/events.c:605: error: redefinition of =E2**xen_destroy_ir= q=E2** > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29: error: > previous definition of =E2**xen_destroy_irq=E2** was here > drivers/xen/events.c:637: error: redefinition of =E2**xen_create_msi= _irq=E2** > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25: error: > previous definition of =E2**xen_create_msi_irq=E2** was here > make[2]: *** [drivers/xen/events.o] Error 1 > make[1]: *** [drivers/xen] Error 2 > make: *** [drivers] Error 2 >=20 > 2. xen/stable, I get following errors >=20 Ok so some extra patches needed here aswell. -- Pasi > CC drivers/pci/xen-pcifront.o > drivers/pci/xen-pcifront.c:373: error: variable =E2**pci_frontend_op= s=E2** has > initializut incomplete type > drivers/pci/xen-pcifront.c:374: error: unknown field =E2**enable_msi= =E2** > specified in ializer > drivers/pci/xen-pcifront.c:374: warning: excess elements in struct > initializer > drivers/pci/xen-pcifront.c:374: warning: (near initialization for > =E2**pci_frontend_op)=E2** > drivers/pci/xen-pcifront.c:375: error: unknown field =E2**disable_ms= i=E2** > specified in ializer > drivers/pci/xen-pcifront.c:375: warning: excess elements in struct > initializer > drivers/pci/xen-pcifront.c:375: warning: (near initialization for > =E2**pci_frontend_op)=E2** > drivers/pci/xen-pcifront.c:376: error: unknown field =E2**enable_msi= x=E2** > specified in ializer > drivers/pci/xen-pcifront.c:376: warning: excess elements in struct > initializer > drivers/pci/xen-pcifront.c:376: warning: (near initialization for > =E2**pci_frontend_op)=E2** > drivers/pci/xen-pcifront.c:377: error: unknown field =E2**disable_ms= ix=E2** > specified intializer > drivers/pci/xen-pcifront.c:377: warning: excess elements in struct > initializer > drivers/pci/xen-pcifront.c:377: warning: (near initialization for > =E2**pci_frontend_op)=E2** > drivers/pci/xen-pcifront.c: In function =E2**pci_frontend_registrar=E2= **: > drivers/pci/xen-pcifront.c:383: error: =E2**xen_pci_frontend=E2** un= declared > (first use his function) > drivers/pci/xen-pcifront.c:383: error: (Each undeclared identifier i= s > reported only once > drivers/pci/xen-pcifront.c:383: error: for each function it appears = in.) > make[2]: *** [drivers/pci/xen-pcifront.o] Error 1 > make[1]: *** [drivers/pci] Error 2 > make: *** [drivers] Error 2 >=20 > Kindly let me know how to proceed on this. >=20 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sander Eikelenboom Subject: Re: domU guest for xcp 0.1.1 Date: Sun, 14 Mar 2010 12:15:40 +0100 Message-ID: <112460240.20100314121540@eikelenboom.it> References: <29b32d341003120910l5340bc01tcada3ca2adbaf763@mail.gmail.com> <20100312175135.GK1878@reaktio.net> <29b32d341003121751s517ea28qbdb78e8cc69243ac@mail.gmail.com> <20100313111857.GS1878@reaktio.net> <29b32d341003130809u49d1edcas234fdca4c3d70ed@mail.gmail.com> <20100313164102.GZ1878@reaktio.net> <29b32d341003131743j6ae271d6of486a3c1a4858513@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <29b32d341003131743j6ae271d6of486a3c1a4858513@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: Ritu kaur Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Hello Ritu, There are some problems with pci.h, i have also reported this to Konrad. As a workaround you can enable dom0 support in these kernels, then they com= pile fine in my case. -- Sander Sunday, March 14, 2010, 2:43:23 AM, you wrote: > I followed the steps mentioned in wiki to pull xen code to compile domU > kernel from > 1. xen/master, I get following compilation errors. I do see in xen-devel > forum someone else has reported similar issue but no solution yet(patch > provided by Konrad has followup errors) > CC [M] drivers/watchdog/machzwd.o > CC [M] drivers/watchdog/sbc_epx_c3.o > CC [M] drivers/watchdog/softdog.o > CC drivers/xen/grant-table.o > CC drivers/xen/features.o > CC drivers/xen/events.o > drivers/xen/events.c:605: error: redefinition of =E2=80=98xen_destroy_irq= =E2=80=99 > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29: error: > previous definition of =E2=80=98xen_destroy_irq=E2=80=99 was here > drivers/xen/events.c:637: error: redefinition of =E2=80=98xen_create_msi_= irq=E2=80=99 > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25: error: > previous definition of =E2=80=98xen_create_msi_irq=E2=80=99 was here > make[2]: *** [drivers/xen/events.o] Error 1 > make[1]: *** [drivers/xen] Error 2 > make: *** [drivers] Error 2 > 2. xen/stable, I get following errors > CC drivers/pci/xen-pcifront.o > drivers/pci/xen-pcifront.c:373: error: variable =E2=80=98pci_frontend_ops= =E2=80=99 has > initializut incomplete type > drivers/pci/xen-pcifront.c:374: error: unknown field =E2=80=98enable_msi= =E2=80=99 > specified in ializer > drivers/pci/xen-pcifront.c:374: warning: excess elements in struct > initializer > drivers/pci/xen-pcifront.c:374: warning: (near initialization for > =E2=80=98pci_frontend_op)=E2=80=99 > drivers/pci/xen-pcifront.c:375: error: unknown field =E2=80=98disable_msi= =E2=80=99 > specified in ializer > drivers/pci/xen-pcifront.c:375: warning: excess elements in struct > initializer > drivers/pci/xen-pcifront.c:375: warning: (near initialization for > =E2=80=98pci_frontend_op)=E2=80=99 > drivers/pci/xen-pcifront.c:376: error: unknown field =E2=80=98enable_msix= =E2=80=99 > specified in ializer > drivers/pci/xen-pcifront.c:376: warning: excess elements in struct > initializer > drivers/pci/xen-pcifront.c:376: warning: (near initialization for > =E2=80=98pci_frontend_op)=E2=80=99 > drivers/pci/xen-pcifront.c:377: error: unknown field =E2=80=98disable_msi= x=E2=80=99 > specified intializer > drivers/pci/xen-pcifront.c:377: warning: excess elements in struct > initializer > drivers/pci/xen-pcifront.c:377: warning: (near initialization for > =E2=80=98pci_frontend_op)=E2=80=99 > drivers/pci/xen-pcifront.c: In function =E2=80=98pci_frontend_registrar= =E2=80=99: > drivers/pci/xen-pcifront.c:383: error: =E2=80=98xen_pci_frontend=E2=80=99= undeclared > (first use his function) > drivers/pci/xen-pcifront.c:383: error: (Each undeclared identifier is > reported only once > drivers/pci/xen-pcifront.c:383: error: for each function it appears in.) > make[2]: *** [drivers/pci/xen-pcifront.o] Error 1 > make[1]: *** [drivers/pci] Error 2 > make: *** [drivers] Error 2 > Kindly let me know how to proceed on this. > Thanks --=20 Best regards, Sander mailto:linux@eikelenboom.it From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ritu kaur Subject: Re: domU guest for xcp 0.1.1 Date: Sun, 14 Mar 2010 13:29:29 -0700 Message-ID: <29b32d341003141329v3c6a73c0y8030cf3c6736634c@mail.gmail.com> References: <29b32d341003120910l5340bc01tcada3ca2adbaf763@mail.gmail.com> <20100312175135.GK1878@reaktio.net> <29b32d341003121751s517ea28qbdb78e8cc69243ac@mail.gmail.com> <20100313111857.GS1878@reaktio.net> <29b32d341003130809u49d1edcas234fdca4c3d70ed@mail.gmail.com> <20100313164102.GZ1878@reaktio.net> <29b32d341003131743j6ae271d6of486a3c1a4858513@mail.gmail.com> <112460240.20100314121540@eikelenboom.it> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1716000356==" Return-path: In-Reply-To: <112460240.20100314121540@eikelenboom.it> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Sander Eikelenboom Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============1716000356== Content-Type: multipart/alternative; boundary=000e0cd17e7c12596a0481c89f64 --000e0cd17e7c12596a0481c89f64 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Sander, Thanks, I enabled DOM0 and other backend drivers along with pci frontend in .config file. I am able to get it build. However, I having additional questions, inputs appreciated. 1. can this kernel be used in any linux distribution? I have Debian Lenny a= s DomU? 2. In Debian Lenny /boot/grub/menu.lst, I have title Debian GNU/Linux, kernel 2.6.26-2-686-bigmem root (hd0,0) kernel /boot/vmlinuz-2.6.26-2-686-bigmem root=3D/dev/xvda1 ro console=3Dhvc0 quiet initrd /boot/initrd.img-2.6.26-2-686-bigmem but the kernel image built in arch/i386/boot is bzImage. Does "make modules_install" and "make install" take care of it, since I am not sure I haven't tried it. Basically, my question boils down to 1. Can I use bzImage in debian lenny, 2. does make install take care of configuring it Thanks On Sun, Mar 14, 2010 at 4:15 AM, Sander Eikelenboom w= rote: > Hello Ritu, > > There are some problems with pci.h, i have also reported this to Konrad. > As a workaround you can enable dom0 support in these kernels, then they > compile fine in my case. > > -- > > Sander > > > Sunday, March 14, 2010, 2:43:23 AM, you wrote: > > > I followed the steps mentioned in wiki to pull xen code to compile dom= U > > kernel from > > > 1. xen/master, I get following compilation errors. I do see in xen-deve= l > > forum someone else has reported similar issue but no solution yet(patch > > provided by Konrad has followup errors) > > > CC [M] drivers/watchdog/machzwd.o > > CC [M] drivers/watchdog/sbc_epx_c3.o > > CC [M] drivers/watchdog/softdog.o > > CC drivers/xen/grant-table.o > > CC drivers/xen/features.o > > CC drivers/xen/events.o > > drivers/xen/events.c:605: error: redefinition of =E2=80=98xen_destroy_i= rq=E2=80=99 > > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29: error: > > previous definition of =E2=80=98xen_destroy_irq=E2=80=99 was here > > drivers/xen/events.c:637: error: redefinition of =E2=80=98xen_create_ms= i_irq=E2=80=99 > > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25: error: > > previous definition of =E2=80=98xen_create_msi_irq=E2=80=99 was here > > make[2]: *** [drivers/xen/events.o] Error 1 > > make[1]: *** [drivers/xen] Error 2 > > make: *** [drivers] Error 2 > > > 2. xen/stable, I get following errors > > > CC drivers/pci/xen-pcifront.o > > drivers/pci/xen-pcifront.c:373: error: variable =E2=80=98pci_frontend_o= ps=E2=80=99 > has > > initializut incomplete type > > drivers/pci/xen-pcifront.c:374: error: unknown field =E2=80=98enable_ms= i=E2=80=99 > > specified in ializer > > drivers/pci/xen-pcifront.c:374: warning: excess elements in struct > > initializer > > drivers/pci/xen-pcifront.c:374: warning: (near initialization for > > =E2=80=98pci_frontend_op)=E2=80=99 > > drivers/pci/xen-pcifront.c:375: error: unknown field =E2=80=98disable_m= si=E2=80=99 > > specified in ializer > > drivers/pci/xen-pcifront.c:375: warning: excess elements in struct > > initializer > > drivers/pci/xen-pcifront.c:375: warning: (near initialization for > > =E2=80=98pci_frontend_op)=E2=80=99 > > drivers/pci/xen-pcifront.c:376: error: unknown field =E2=80=98enable_ms= ix=E2=80=99 > > specified in ializer > > drivers/pci/xen-pcifront.c:376: warning: excess elements in struct > > initializer > > drivers/pci/xen-pcifront.c:376: warning: (near initialization for > > =E2=80=98pci_frontend_op)=E2=80=99 > > drivers/pci/xen-pcifront.c:377: error: unknown field =E2=80=98disable_m= six=E2=80=99 > > specified intializer > > drivers/pci/xen-pcifront.c:377: warning: excess elements in struct > > initializer > > drivers/pci/xen-pcifront.c:377: warning: (near initialization for > > =E2=80=98pci_frontend_op)=E2=80=99 > > drivers/pci/xen-pcifront.c: In function =E2=80=98pci_frontend_registrar= =E2=80=99: > > drivers/pci/xen-pcifront.c:383: error: =E2=80=98xen_pci_frontend=E2=80= =99 undeclared > > (first use his function) > > drivers/pci/xen-pcifront.c:383: error: (Each undeclared identifier is > > reported only once > > drivers/pci/xen-pcifront.c:383: error: for each function it appears in.= ) > > make[2]: *** [drivers/pci/xen-pcifront.o] Error 1 > > make[1]: *** [drivers/pci] Error 2 > > make: *** [drivers] Error 2 > > > Kindly let me know how to proceed on this. > > > Thanks > > > > -- > Best regards, > Sander mailto:linux@eikelenboom.it > > --000e0cd17e7c12596a0481c89f64 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Sander,

Thanks, I enabled DOM0 and other backend drivers along w= ith pci frontend in .config file. I am able to get it build. However, I hav= ing additional questions, inputs appreciated.

1. can this kernel be = used in any linux distribution? I have Debian Lenny as DomU?

2. In Debian Lenny /boot/grub/menu.lst, I have
title=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0 Debian GNU/Linux, kernel 2.6.26-2-686-bigmem
root=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0 (hd0,0)
kernel=A0=A0=A0=A0=A0=A0=A0=A0=A0 /b= oot/vmlinuz-2.6.26-2-686-bigmem root=3D/dev/xvda1 ro console=3Dhvc0 quiet initrd=A0=A0=A0=A0=A0=A0=A0=A0=A0 /boot/initrd.img-2.6.26-2-686-bigmem
<= br>but the kernel image built in arch/i386/boot is bzImage. Does "make= modules_install" and "make install" take care of it, since = I am not sure I haven't tried it.

Basically, my question boils down to

1. Can I use bzImage in de= bian lenny,
2. does make install take care of configuring it

Thanks

On Sun, Mar 14, 2010 at 4:15 AM, = Sander Eikelenboom <linux@eikelenboom.it> wrote:

Hello Ritu,

There are some problems with pci.h, i have also reported this to Konrad. As a workaround you can enable dom0 support in these kernels, then they com= pile fine in my case.

--

Sander

Sunday, March 14, 2010, 2:43:23 AM, you wrote:

> I followed the steps mentioned in =A0wiki to pull xen code to compile = domU
> kernel from

> 1. xen/master, I get following compilation errors. I do see in xen-dev= el
> forum someone else has reported similar issue but no solution yet(patc= h
> provided by Konrad has followup errors)

> CC [M] =A0drivers/watchdog/machzwd.o
> =A0 CC [M] =A0drivers/watchdog/sbc_epx_c3.o
> =A0 CC [M] =A0drivers/watchdog/softdog.o
> =A0 CC =A0 =A0 =A0drivers/xen/grant-table.o
> =A0 CC =A0 =A0 =A0drivers/xen/features.o
> =A0 CC =A0 =A0 =A0drivers/xen/events.o
> drivers/xen/events.c:605: error: redefinition of =E2=80=98xen_destroy_= irq=E2=80=99
> /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29: error: > previous definition of =E2=80=98xen_destroy_irq=E2=80=99 was here
> drivers/xen/events.c:637: error: redefinition of =E2=80=98xen_create_m= si_irq=E2=80=99
> /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25: error: > previous definition of =E2=80=98xen_create_msi_irq=E2=80=99 was here > make[2]: *** [drivers/xen/events.o] Error 1
> make[1]: *** [drivers/xen] Error 2
> make: *** [drivers] Error 2

> 2. xen/stable, I get following errors

> =A0CC =A0 =A0 =A0drivers/pci/xen-pcifront.o
> drivers/pci/xen-pcifront.c:373: error: variable =E2=80=98pci_frontend_= ops=E2=80=99 has
> initializut incomplete type
> drivers/pci/xen-pcifront.c:374: error: unknown field =E2=80=98enable_m= si=E2=80=99
> specified in ializer
> drivers/pci/xen-pcifront.c:374: warning: excess elements in struct
> initializer
> drivers/pci/xen-pcifront.c:374: warning: (near initialization for
> =E2=80=98pci_frontend_op)=E2=80=99
> drivers/pci/xen-pcifront.c:375: error: unknown field =E2=80=98disable_= msi=E2=80=99
> specified in ializer
> drivers/pci/xen-pcifront.c:375: warning: excess elements in struct
> initializer
> drivers/pci/xen-pcifront.c:375: warning: (near initialization for
> =E2=80=98pci_frontend_op)=E2=80=99
> drivers/pci/xen-pcifront.c:376: error: unknown field =E2=80=98enable_m= six=E2=80=99
> specified in ializer
> drivers/pci/xen-pcifront.c:376: warning: excess elements in struct
> initializer
> drivers/pci/xen-pcifront.c:376: warning: (near initialization for
> =E2=80=98pci_frontend_op)=E2=80=99
> drivers/pci/xen-pcifront.c:377: error: unknown field =E2=80=98disable_= msix=E2=80=99
> specified intializer
> drivers/pci/xen-pcifront.c:377: warning: excess elements in struct
> initializer
> drivers/pci/xen-pcifront.c:377: warning: (near initialization for
> =E2=80=98pci_frontend_op)=E2=80=99
> drivers/pci/xen-pcifront.c: In function =E2=80=98pci_frontend_registra= r=E2=80=99:
> drivers/pci/xen-pcifront.c:383: error: =E2=80=98xen_pci_frontend=E2=80= =99 undeclared
> (first use his function)
> drivers/pci/xen-pcifront.c:383: error: (Each undeclared identifier is<= br> > reported only once
> drivers/pci/xen-pcifront.c:383: error: for each function it appears in= .)
> make[2]: *** [drivers/pci/xen-pcifront.o] Error 1
> make[1]: *** [drivers/pci] Error 2
> make: *** [drivers] Error 2

> Kindly let me know how to proceed on this.

> Thanks

--
Best regards,
=A0Sander =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0mailto:linux@eikelenboom.it

--000e0cd17e7c12596a0481c89f64-- --===============1716000356== 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 --===============1716000356==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sander Eikelenboom Subject: Re: domU guest for xcp 0.1.1 Date: Sun, 14 Mar 2010 21:52:24 +0100 Message-ID: <1056770753.20100314215224@eikelenboom.it> References: <29b32d341003120910l5340bc01tcada3ca2adbaf763@mail.gmail.com> <20100312175135.GK1878@reaktio.net> <29b32d341003121751s517ea28qbdb78e8cc69243ac@mail.gmail.com> <20100313111857.GS1878@reaktio.net> <29b32d341003130809u49d1edcas234fdca4c3d70ed@mail.gmail.com> <20100313164102.GZ1878@reaktio.net> <29b32d341003131743j6ae271d6of486a3c1a4858513@mail.gmail.com> <112460240.20100314121540@eikelenboom.it> <29b32d341003141329v3c6a73c0y8030cf3c6736634c@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <29b32d341003141329v3c6a73c0y8030cf3c6736634c@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: Ritu kaur Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Hello Ritu, I don't have experience with XCP specifically, but normal compiled pvops-ke= rnels work fine for me with Debian lenny domU's. -- Sander Sunday, March 14, 2010, 9:29:29 PM, you wrote: > Hi Sander, > Thanks, I enabled DOM0 and other backend drivers along with pci frontend = in > .config file. I am able to get it build. However, I having additional > questions, inputs appreciated. > 1. can this kernel be used in any linux distribution? I have Debian Lenny= as > DomU? > 2. In Debian Lenny /boot/grub/menu.lst, I have > title Debian GNU/Linux, kernel 2.6.26-2-686-bigmem > root (hd0,0) > kernel /boot/vmlinuz-2.6.26-2-686-bigmem root=3D/dev/xvda1 ro > console=3Dhvc0 quiet > initrd /boot/initrd.img-2.6.26-2-686-bigmem > but the kernel image built in arch/i386/boot is bzImage. Does "make > modules_install" and "make install" take care of it, since I am not sure I > haven't tried it. > Basically, my question boils down to > 1. Can I use bzImage in debian lenny, > 2. does make install take care of configuring it > Thanks > On Sun, Mar 14, 2010 at 4:15 AM, Sander Eikelenboom wrote: >> Hello Ritu, >> >> There are some problems with pci.h, i have also reported this to Konrad. >> As a workaround you can enable dom0 support in these kernels, then they >> compile fine in my case. >> >> -- >> >> Sander >> >> >> Sunday, March 14, 2010, 2:43:23 AM, you wrote: >> >> > I followed the steps mentioned in wiki to pull xen code to compile do= mU >> > kernel from >> >> > 1. xen/master, I get following compilation errors. I do see in xen-dev= el >> > forum someone else has reported similar issue but no solution yet(patch >> > provided by Konrad has followup errors) >> >> > CC [M] drivers/watchdog/machzwd.o >> > CC [M] drivers/watchdog/sbc_epx_c3.o >> > CC [M] drivers/watchdog/softdog.o >> > CC drivers/xen/grant-table.o >> > CC drivers/xen/features.o >> > CC drivers/xen/events.o >> > drivers/xen/events.c:605: error: redefinition of =E2=80=98xen_destroy_= irq=E2=80=99 >> > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29: error: >> > previous definition of =E2=80=98xen_destroy_irq=E2=80=99 was here >> > drivers/xen/events.c:637: error: redefinition of =E2=80=98xen_create_m= si_irq=E2=80=99 >> > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25: error: >> > previous definition of =E2=80=98xen_create_msi_irq=E2=80=99 was here >> > make[2]: *** [drivers/xen/events.o] Error 1 >> > make[1]: *** [drivers/xen] Error 2 >> > make: *** [drivers] Error 2 >> >> > 2. xen/stable, I get following errors >> >> > CC drivers/pci/xen-pcifront.o >> > drivers/pci/xen-pcifront.c:373: error: variable =E2=80=98pci_frontend_= ops=E2=80=99 >> has >> > initializut incomplete type >> > drivers/pci/xen-pcifront.c:374: error: unknown field =E2=80=98enable_m= si=E2=80=99 >> > specified in ializer >> > drivers/pci/xen-pcifront.c:374: warning: excess elements in struct >> > initializer >> > drivers/pci/xen-pcifront.c:374: warning: (near initialization for >> > =E2=80=98pci_frontend_op)=E2=80=99 >> > drivers/pci/xen-pcifront.c:375: error: unknown field =E2=80=98disable_= msi=E2=80=99 >> > specified in ializer >> > drivers/pci/xen-pcifront.c:375: warning: excess elements in struct >> > initializer >> > drivers/pci/xen-pcifront.c:375: warning: (near initialization for >> > =E2=80=98pci_frontend_op)=E2=80=99 >> > drivers/pci/xen-pcifront.c:376: error: unknown field =E2=80=98enable_m= six=E2=80=99 >> > specified in ializer >> > drivers/pci/xen-pcifront.c:376: warning: excess elements in struct >> > initializer >> > drivers/pci/xen-pcifront.c:376: warning: (near initialization for >> > =E2=80=98pci_frontend_op)=E2=80=99 >> > drivers/pci/xen-pcifront.c:377: error: unknown field =E2=80=98disable_= msix=E2=80=99 >> > specified intializer >> > drivers/pci/xen-pcifront.c:377: warning: excess elements in struct >> > initializer >> > drivers/pci/xen-pcifront.c:377: warning: (near initialization for >> > =E2=80=98pci_frontend_op)=E2=80=99 >> > drivers/pci/xen-pcifront.c: In function =E2=80=98pci_frontend_registra= r=E2=80=99: >> > drivers/pci/xen-pcifront.c:383: error: =E2=80=98xen_pci_frontend=E2=80= =99 undeclared >> > (first use his function) >> > drivers/pci/xen-pcifront.c:383: error: (Each undeclared identifier is >> > reported only once >> > drivers/pci/xen-pcifront.c:383: error: for each function it appears in= .) >> > make[2]: *** [drivers/pci/xen-pcifront.o] Error 1 >> > make[1]: *** [drivers/pci] Error 2 >> > make: *** [drivers] Error 2 >> >> > Kindly let me know how to proceed on this. >> >> > Thanks >> >> >> >> -- >> Best regards, >> Sander mailto:linux@eikelenboom.it >> >> --=20 Best regards, Sander mailto:linux@eikelenboom.it From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ritu kaur Subject: Re: domU guest for xcp 0.1.1 Date: Sun, 14 Mar 2010 18:40:33 -0700 Message-ID: <29b32d341003141840x5a55e74sfb2eda56005e4f84@mail.gmail.com> References: <29b32d341003120910l5340bc01tcada3ca2adbaf763@mail.gmail.com> <20100312175135.GK1878@reaktio.net> <29b32d341003121751s517ea28qbdb78e8cc69243ac@mail.gmail.com> <20100313111857.GS1878@reaktio.net> <29b32d341003130809u49d1edcas234fdca4c3d70ed@mail.gmail.com> <20100313164102.GZ1878@reaktio.net> <29b32d341003131743j6ae271d6of486a3c1a4858513@mail.gmail.com> <112460240.20100314121540@eikelenboom.it> <29b32d341003141329v3c6a73c0y8030cf3c6736634c@mail.gmail.com> <1056770753.20100314215224@eikelenboom.it> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1788313506==" Return-path: In-Reply-To: <1056770753.20100314215224@eikelenboom.it> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============1788313506== Content-Type: multipart/alternative; boundary=000e0cd242a08eeda10481ccf75a --000e0cd242a08eeda10481ccf75a Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Pasi, I am able to use xen/stable kernel in domU(debian lenny) and lspci lists th= e device(i am testing pci passthrough). however, when I compile my driver in domU I get struct net_device has no member named open struct net_device has no member named stop struct net_device has no member named hard_start_xmit ... I need to compile my driver in domU and load it in order to use the nic fro= m domU. Inputs appreciated. Thanks On Sun, Mar 14, 2010 at 1:52 PM, Sander Eikelenboom w= rote: > Hello Ritu, > > I don't have experience with XCP specifically, but normal compiled > pvops-kernels work fine for me with Debian lenny domU's. > > -- > Sander > > Sunday, March 14, 2010, 9:29:29 PM, you wrote: > > > Hi Sander, > > > Thanks, I enabled DOM0 and other backend drivers along with pci fronten= d > in > > .config file. I am able to get it build. However, I having additional > > questions, inputs appreciated. > > > 1. can this kernel be used in any linux distribution? I have Debian Len= ny > as > > DomU? > > > 2. In Debian Lenny /boot/grub/menu.lst, I have > > title Debian GNU/Linux, kernel 2.6.26-2-686-bigmem > > root (hd0,0) > > kernel /boot/vmlinuz-2.6.26-2-686-bigmem root=3D/dev/xvda1 ro > > console=3Dhvc0 quiet > > initrd /boot/initrd.img-2.6.26-2-686-bigmem > > > but the kernel image built in arch/i386/boot is bzImage. Does "make > > modules_install" and "make install" take care of it, since I am not sur= e > I > > haven't tried it. > > > Basically, my question boils down to > > > 1. Can I use bzImage in debian lenny, > > 2. does make install take care of configuring it > > > > Thanks > > > On Sun, Mar 14, 2010 at 4:15 AM, Sander Eikelenboom < > linux@eikelenboom.it>wrote: > > >> Hello Ritu, > >> > >> There are some problems with pci.h, i have also reported this to Konra= d. > >> As a workaround you can enable dom0 support in these kernels, then the= y > >> compile fine in my case. > >> > >> -- > >> > >> Sander > >> > >> > >> Sunday, March 14, 2010, 2:43:23 AM, you wrote: > >> > >> > I followed the steps mentioned in wiki to pull xen code to compile > domU > >> > kernel from > >> > >> > 1. xen/master, I get following compilation errors. I do see in > xen-devel > >> > forum someone else has reported similar issue but no solution > yet(patch > >> > provided by Konrad has followup errors) > >> > >> > CC [M] drivers/watchdog/machzwd.o > >> > CC [M] drivers/watchdog/sbc_epx_c3.o > >> > CC [M] drivers/watchdog/softdog.o > >> > CC drivers/xen/grant-table.o > >> > CC drivers/xen/features.o > >> > CC drivers/xen/events.o > >> > drivers/xen/events.c:605: error: redefinition of =E2=80=98xen_destro= y_irq=E2=80=99 > >> > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29: error: > >> > previous definition of =E2=80=98xen_destroy_irq=E2=80=99 was here > >> > drivers/xen/events.c:637: error: redefinition of > =E2=80=98xen_create_msi_irq=E2=80=99 > >> > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25: error: > >> > previous definition of =E2=80=98xen_create_msi_irq=E2=80=99 was here > >> > make[2]: *** [drivers/xen/events.o] Error 1 > >> > make[1]: *** [drivers/xen] Error 2 > >> > make: *** [drivers] Error 2 > >> > >> > 2. xen/stable, I get following errors > >> > >> > CC drivers/pci/xen-pcifront.o > >> > drivers/pci/xen-pcifront.c:373: error: variable =E2=80=98pci_fronten= d_ops=E2=80=99 > >> has > >> > initializut incomplete type > >> > drivers/pci/xen-pcifront.c:374: error: unknown field =E2=80=98enable= _msi=E2=80=99 > >> > specified in ializer > >> > drivers/pci/xen-pcifront.c:374: warning: excess elements in struct > >> > initializer > >> > drivers/pci/xen-pcifront.c:374: warning: (near initialization for > >> > =E2=80=98pci_frontend_op)=E2=80=99 > >> > drivers/pci/xen-pcifront.c:375: error: unknown field =E2=80=98disabl= e_msi=E2=80=99 > >> > specified in ializer > >> > drivers/pci/xen-pcifront.c:375: warning: excess elements in struct > >> > initializer > >> > drivers/pci/xen-pcifront.c:375: warning: (near initialization for > >> > =E2=80=98pci_frontend_op)=E2=80=99 > >> > drivers/pci/xen-pcifront.c:376: error: unknown field =E2=80=98enable= _msix=E2=80=99 > >> > specified in ializer > >> > drivers/pci/xen-pcifront.c:376: warning: excess elements in struct > >> > initializer > >> > drivers/pci/xen-pcifront.c:376: warning: (near initialization for > >> > =E2=80=98pci_frontend_op)=E2=80=99 > >> > drivers/pci/xen-pcifront.c:377: error: unknown field > =E2=80=98disable_msix=E2=80=99 > >> > specified intializer > >> > drivers/pci/xen-pcifront.c:377: warning: excess elements in struct > >> > initializer > >> > drivers/pci/xen-pcifront.c:377: warning: (near initialization for > >> > =E2=80=98pci_frontend_op)=E2=80=99 > >> > drivers/pci/xen-pcifront.c: In function =E2=80=98pci_frontend_regist= rar=E2=80=99: > >> > drivers/pci/xen-pcifront.c:383: error: =E2=80=98xen_pci_frontend=E2= =80=99 > undeclared > >> > (first use his function) > >> > drivers/pci/xen-pcifront.c:383: error: (Each undeclared identifier i= s > >> > reported only once > >> > drivers/pci/xen-pcifront.c:383: error: for each function it appears > in.) > >> > make[2]: *** [drivers/pci/xen-pcifront.o] Error 1 > >> > make[1]: *** [drivers/pci] Error 2 > >> > make: *** [drivers] Error 2 > >> > >> > Kindly let me know how to proceed on this. > >> > >> > Thanks > >> > >> > >> > >> -- > >> Best regards, > >> Sander mailto:linux@eikelenboom.it > >> > >> > > > > -- > Best regards, > Sander mailto:linux@eikelenboom.it > > --000e0cd242a08eeda10481ccf75a Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Pasi,

I am able to use xen/stable kernel in domU(debian lenny) an= d lspci lists the device(i am testing pci passthrough). however, when I com= pile my driver in domU I get

struct net_device has no member named = open
struct net_device has no member named stop
struct net_device has no memb= er named hard_start_xmit
...

I need to compile my driver in domU = and load it in order to use the nic from domU. Inputs appreciated.

Thanks

On Sun, Mar 14, 2010 at 1:52 PM, S= ander Eikelenboom <linux@eikelenboom.it> wrote:

Hello Ritu,

I don't have experience with XCP specifically, but normal compiled pvop= s-kernels work fine for me with Debian lenny domU's.

--
Sander

Sunday, March 14, 2010, 9:29:29 PM, you wrote:

> Hi Sander,

> Thanks, I enabled DOM0 and other backend drivers along with pci fronte= nd in
> .config file. I am able to get it build. However, I having additional<= br> > questions, inputs appreciated.

> 1. can this kernel be used in any linux distribution? I have Debian Le= nny as
> DomU?

> 2. In Debian Lenny /boot/grub/menu.lst, I have
> title =A0 =A0 =A0 =A0 =A0 Debian GNU/Linux, kernel 2.6.26-2-686-bigmem=
> root =A0 =A0 =A0 =A0 =A0 =A0(hd0,0)
> kernel =A0 =A0 =A0 =A0 =A0/boot/vmlinuz-2.6.26-2-686-bigmem root=3D/de= v/xvda1 ro
> console=3Dhvc0 quiet
> initrd =A0 =A0 =A0 =A0 =A0/boot/initrd.img-2.6.26-2-686-bigmem

> but the kernel image built in arch/i386/boot is bzImage. Does "ma= ke
> modules_install" and "make install" take care of it, si= nce I am not sure I
> haven't tried it.

> Basically, my question boils down to

> 1. Can I use bzImage in debian lenny,
> 2. does make install take care of configuring it

> Thanks

> On Sun, Mar 14, 2010 at 4:15 AM, Sander Eikelenboom <linux@eikelenboom.it>wrote:

>> Hello Ritu,
>>
>> There are some problems with pci.h, i have also reported this to K= onrad.
>> As a workaround you can enable dom0 support in these kernels, then= they
>> compile fine in my case.
>>
>> --
>>
>> Sander
>>
>>
>> Sunday, March 14, 2010, 2:43:23 AM, you wrote:
>>
>> > I followed the steps mentioned in =A0wiki to pull xen code to= compile domU
>> > kernel from
>>
>> > 1. xen/master, I get following compilation errors. I do see i= n xen-devel
>> > forum someone else has reported similar issue but no solution= yet(patch
>> > provided by Konrad has followup errors)
>>
>> > CC [M] =A0drivers/watchdog/machzwd.o
>> > =A0 CC [M] =A0drivers/watchdog/sbc_epx_c3.o
>> > =A0 CC [M] =A0drivers/watchdog/softdog.o
>> > =A0 CC =A0 =A0 =A0drivers/xen/grant-table.o
>> > =A0 CC =A0 =A0 =A0drivers/xen/features.o
>> > =A0 CC =A0 =A0 =A0drivers/xen/events.o
>> > drivers/xen/events.c:605: error: redefinition of =E2=80=98xen= _destroy_irq=E2=80=99
>> > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29:= error:
>> > previous definition of =E2=80=98xen_destroy_irq=E2=80=99 was = here
>> > drivers/xen/events.c:637: error: redefinition of =E2=80=98xen= _create_msi_irq=E2=80=99
>> > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25:= error:
>> > previous definition of =E2=80=98xen_create_msi_irq=E2=80=99 w= as here
>> > make[2]: *** [drivers/xen/events.o] Error 1
>> > make[1]: *** [drivers/xen] Error 2
>> > make: *** [drivers] Error 2
>>
>> > 2. xen/stable, I get following errors
>>
>> > =A0CC =A0 =A0 =A0drivers/pci/xen-pcifront.o
>> > drivers/pci/xen-pcifront.c:373: error: variable =E2=80=98pci_= frontend_ops=E2=80=99
>> has
>> > initializut incomplete type
>> > drivers/pci/xen-pcifront.c:374: error: unknown field =E2=80= =98enable_msi=E2=80=99
>> > specified in ializer
>> > drivers/pci/xen-pcifront.c:374: warning: excess elements in s= truct
>> > initializer
>> > drivers/pci/xen-pcifront.c:374: warning: (near initialization= for
>> > =E2=80=98pci_frontend_op)=E2=80=99
>> > drivers/pci/xen-pcifront.c:375: error: unknown field =E2=80= =98disable_msi=E2=80=99
>> > specified in ializer
>> > drivers/pci/xen-pcifront.c:375: warning: excess elements in s= truct
>> > initializer
>> > drivers/pci/xen-pcifront.c:375: warning: (near initialization= for
>> > =E2=80=98pci_frontend_op)=E2=80=99
>> > drivers/pci/xen-pcifront.c:376: error: unknown field =E2=80= =98enable_msix=E2=80=99
>> > specified in ializer
>> > drivers/pci/xen-pcifront.c:376: warning: excess elements in s= truct
>> > initializer
>> > drivers/pci/xen-pcifront.c:376: warning: (near initialization= for
>> > =E2=80=98pci_frontend_op)=E2=80=99
>> > drivers/pci/xen-pcifront.c:377: error: unknown field =E2=80= =98disable_msix=E2=80=99
>> > specified intializer
>> > drivers/pci/xen-pcifront.c:377: warning: excess elements in s= truct
>> > initializer
>> > drivers/pci/xen-pcifront.c:377: warning: (near initialization= for
>> > =E2=80=98pci_frontend_op)=E2=80=99
>> > drivers/pci/xen-pcifront.c: In function =E2=80=98pci_frontend= _registrar=E2=80=99:
>> > drivers/pci/xen-pcifront.c:383: error: =E2=80=98xen_pci_front= end=E2=80=99 undeclared
>> > (first use his function)
>> > drivers/pci/xen-pcifront.c:383: error: (Each undeclared ident= ifier is
>> > reported only once
>> > drivers/pci/xen-pcifront.c:383: error: for each function it a= ppears in.)
>> > make[2]: *** [drivers/pci/xen-pcifront.o] Error 1
>> > make[1]: *** [drivers/pci] Error 2
>> > make: *** [drivers] Error 2
>>
>> > Kindly let me know how to proceed on this.
>>
>> > Thanks
>>
>>
>>
>> --
>> Best regards,
>> =A0Sander =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0m= ailto:linux@eikelenboom.it
>>
>>

--

Best regards,
=A0Sander =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0mailto:linux@eikelenboom.it

--000e0cd242a08eeda10481ccf75a-- --===============1788313506== 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 --===============1788313506==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ritu kaur Subject: Re: domU guest for xcp 0.1.1 Date: Sun, 14 Mar 2010 20:30:46 -0700 Message-ID: <29b32d341003142030p1fe511d2ke30b8483ff8cc368@mail.gmail.com> References: <29b32d341003120910l5340bc01tcada3ca2adbaf763@mail.gmail.com> <29b32d341003121751s517ea28qbdb78e8cc69243ac@mail.gmail.com> <20100313111857.GS1878@reaktio.net> <29b32d341003130809u49d1edcas234fdca4c3d70ed@mail.gmail.com> <20100313164102.GZ1878@reaktio.net> <29b32d341003131743j6ae271d6of486a3c1a4858513@mail.gmail.com> <112460240.20100314121540@eikelenboom.it> <29b32d341003141329v3c6a73c0y8030cf3c6736634c@mail.gmail.com> <1056770753.20100314215224@eikelenboom.it> <29b32d341003141840x5a55e74sfb2eda56005e4f84@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2134394969==" Return-path: In-Reply-To: <29b32d341003141840x5a55e74sfb2eda56005e4f84@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: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============2134394969== Content-Type: multipart/alternative; boundary=000e0cd1a9a0bfb7380481ce8186 --000e0cd1a9a0bfb7380481ce8186 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Just to add, this driver compiles fine in other linux flavors(Debian Lenny 5.0, Citrix Xenserver...) so it has to do with Xen/stable. Didn't see anything related to this in xen-devel, inputs appreciated. Thanks On Sun, Mar 14, 2010 at 6:40 PM, Ritu kaur wrote: > Hi Pasi, > > I am able to use xen/stable kernel in domU(debian lenny) and lspci lists > the device(i am testing pci passthrough). however, when I compile my driv= er > in domU I get > > struct net_device has no member named open > struct net_device has no member named stop > struct net_device has no member named hard_start_xmit > ... > > I need to compile my driver in domU and load it in order to use the nic > from domU. Inputs appreciated. > > Thanks > > > On Sun, Mar 14, 2010 at 1:52 PM, Sander Eikelenboom wrote: > >> Hello Ritu, >> >> I don't have experience with XCP specifically, but normal compiled >> pvops-kernels work fine for me with Debian lenny domU's. >> >> -- >> Sander >> >> Sunday, March 14, 2010, 9:29:29 PM, you wrote: >> >> > Hi Sander, >> >> > Thanks, I enabled DOM0 and other backend drivers along with pci fronte= nd >> in >> > .config file. I am able to get it build. However, I having additional >> > questions, inputs appreciated. >> >> > 1. can this kernel be used in any linux distribution? I have Debian >> Lenny as >> > DomU? >> >> > 2. In Debian Lenny /boot/grub/menu.lst, I have >> > title Debian GNU/Linux, kernel 2.6.26-2-686-bigmem >> > root (hd0,0) >> > kernel /boot/vmlinuz-2.6.26-2-686-bigmem root=3D/dev/xvda1 ro >> > console=3Dhvc0 quiet >> > initrd /boot/initrd.img-2.6.26-2-686-bigmem >> >> > but the kernel image built in arch/i386/boot is bzImage. Does "make >> > modules_install" and "make install" take care of it, since I am not su= re >> I >> > haven't tried it. >> >> > Basically, my question boils down to >> >> > 1. Can I use bzImage in debian lenny, >> > 2. does make install take care of configuring it >> >> >> > Thanks >> >> > On Sun, Mar 14, 2010 at 4:15 AM, Sander Eikelenboom < >> linux@eikelenboom.it>wrote: >> >> >> Hello Ritu, >> >> >> >> There are some problems with pci.h, i have also reported this to >> Konrad. >> >> As a workaround you can enable dom0 support in these kernels, then th= ey >> >> compile fine in my case. >> >> >> >> -- >> >> >> >> Sander >> >> >> >> >> >> Sunday, March 14, 2010, 2:43:23 AM, you wrote: >> >> >> >> > I followed the steps mentioned in wiki to pull xen code to compile >> domU >> >> > kernel from >> >> >> >> > 1. xen/master, I get following compilation errors. I do see in >> xen-devel >> >> > forum someone else has reported similar issue but no solution >> yet(patch >> >> > provided by Konrad has followup errors) >> >> >> >> > CC [M] drivers/watchdog/machzwd.o >> >> > CC [M] drivers/watchdog/sbc_epx_c3.o >> >> > CC [M] drivers/watchdog/softdog.o >> >> > CC drivers/xen/grant-table.o >> >> > CC drivers/xen/features.o >> >> > CC drivers/xen/events.o >> >> > drivers/xen/events.c:605: error: redefinition of >> =E2=80=98xen_destroy_irq=E2=80=99 >> >> > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29: error= : >> >> > previous definition of =E2=80=98xen_destroy_irq=E2=80=99 was here >> >> > drivers/xen/events.c:637: error: redefinition of >> =E2=80=98xen_create_msi_irq=E2=80=99 >> >> > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25: error= : >> >> > previous definition of =E2=80=98xen_create_msi_irq=E2=80=99 was her= e >> >> > make[2]: *** [drivers/xen/events.o] Error 1 >> >> > make[1]: *** [drivers/xen] Error 2 >> >> > make: *** [drivers] Error 2 >> >> >> >> > 2. xen/stable, I get following errors >> >> >> >> > CC drivers/pci/xen-pcifront.o >> >> > drivers/pci/xen-pcifront.c:373: error: variable >> =E2=80=98pci_frontend_ops=E2=80=99 >> >> has >> >> > initializut incomplete type >> >> > drivers/pci/xen-pcifront.c:374: error: unknown field =E2=80=98enabl= e_msi=E2=80=99 >> >> > specified in ializer >> >> > drivers/pci/xen-pcifront.c:374: warning: excess elements in struct >> >> > initializer >> >> > drivers/pci/xen-pcifront.c:374: warning: (near initialization for >> >> > =E2=80=98pci_frontend_op)=E2=80=99 >> >> > drivers/pci/xen-pcifront.c:375: error: unknown field >> =E2=80=98disable_msi=E2=80=99 >> >> > specified in ializer >> >> > drivers/pci/xen-pcifront.c:375: warning: excess elements in struct >> >> > initializer >> >> > drivers/pci/xen-pcifront.c:375: warning: (near initialization for >> >> > =E2=80=98pci_frontend_op)=E2=80=99 >> >> > drivers/pci/xen-pcifront.c:376: error: unknown field >> =E2=80=98enable_msix=E2=80=99 >> >> > specified in ializer >> >> > drivers/pci/xen-pcifront.c:376: warning: excess elements in struct >> >> > initializer >> >> > drivers/pci/xen-pcifront.c:376: warning: (near initialization for >> >> > =E2=80=98pci_frontend_op)=E2=80=99 >> >> > drivers/pci/xen-pcifront.c:377: error: unknown field >> =E2=80=98disable_msix=E2=80=99 >> >> > specified intializer >> >> > drivers/pci/xen-pcifront.c:377: warning: excess elements in struct >> >> > initializer >> >> > drivers/pci/xen-pcifront.c:377: warning: (near initialization for >> >> > =E2=80=98pci_frontend_op)=E2=80=99 >> >> > drivers/pci/xen-pcifront.c: In function =E2=80=98pci_frontend_regis= trar=E2=80=99: >> >> > drivers/pci/xen-pcifront.c:383: error: =E2=80=98xen_pci_frontend=E2= =80=99 >> undeclared >> >> > (first use his function) >> >> > drivers/pci/xen-pcifront.c:383: error: (Each undeclared identifier = is >> >> > reported only once >> >> > drivers/pci/xen-pcifront.c:383: error: for each function it appears >> in.) >> >> > make[2]: *** [drivers/pci/xen-pcifront.o] Error 1 >> >> > make[1]: *** [drivers/pci] Error 2 >> >> > make: *** [drivers] Error 2 >> >> >> >> > Kindly let me know how to proceed on this. >> >> >> >> > Thanks >> >> >> >> >> >> >> >> -- >> >> Best regards, >> >> Sander mailto:linux@eikelenboom.it >> >> >> >> >> >> >> >> -- >> Best regards, >> Sander mailto:linux@eikelenboom.it >> >> > --000e0cd1a9a0bfb7380481ce8186 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Just to add, this driver compiles fine in other linux flavors(Debian Lenny = 5.0, Citrix Xenserver...) so it has to do with Xen/stable. Didn't see a= nything related to this in xen-devel, inputs appreciated.

Thanks

On Sun, Mar 14, 2010 at 6:40 PM, Ritu kaur <= span dir=3D"ltr"><ritu.kaur.us@gmail.com> wrote:

Hi Pasi,

I am able to use xen/stable kernel in domU(debian lenny) an= d lspci lists the device(i am testing pci passthrough). however, when I com= pile my driver in domU I get

struct net_device has no member named = open
struct net_device has no member named stop
struct net_device has no memb= er named hard_start_xmit
...

I need to compile my driver in domU = and load it in order to use the nic from domU. Inputs appreciated.

Thanks

= On Sun, Mar 14, 2010 at 1:52 PM, Sander Eikelenboom <<= a href=3D"mailto:linux@eikelenboom.it" target=3D"_blank">linux@eikelenboom.= it> wrote:

Hello Ritu,

I don't have experience with XCP specifically, but normal compiled pvop= s-kernels work fine for me with Debian lenny domU's.

--
Sander

Sunday, March 14, 2010, 9:29:29 PM, you wrote:

> Hi Sander,

> Thanks, I enabled DOM0 and other backend drivers along with pci fronte= nd in
> .config file. I am able to get it build. However, I having additional<= br> > questions, inputs appreciated.

> 1. can this kernel be used in any linux distribution? I have Debian Le= nny as
> DomU?

> 2. In Debian Lenny /boot/grub/menu.lst, I have
> title =A0 =A0 =A0 =A0 =A0 Debian GNU/Linux, kernel 2.6.26-2-686-bigmem=
> root =A0 =A0 =A0 =A0 =A0 =A0(hd0,0)
> kernel =A0 =A0 =A0 =A0 =A0/boot/vmlinuz-2.6.26-2-686-bigmem root=3D/de= v/xvda1 ro
> console=3Dhvc0 quiet
> initrd =A0 =A0 =A0 =A0 =A0/boot/initrd.img-2.6.26-2-686-bigmem

> but the kernel image built in arch/i386/boot is bzImage. Does "ma= ke
> modules_install" and "make install" take care of it, si= nce I am not sure I
> haven't tried it.

> Basically, my question boils down to

> 1. Can I use bzImage in debian lenny,
> 2. does make install take care of configuring it

> Thanks

> On Sun, Mar 14, 2010 at 4:15 AM, Sander Eikelenboom <linux@eikelenboom.it>wro= te:

>> Hello Ritu,
>>
>> There are some problems with pci.h, i have also reported this to K= onrad.
>> As a workaround you can enable dom0 support in these kernels, then= they
>> compile fine in my case.
>>
>> --
>>
>> Sander
>>
>>
>> Sunday, March 14, 2010, 2:43:23 AM, you wrote:
>>
>> > I followed the steps mentioned in =A0wiki to pull xen code to= compile domU
>> > kernel from
>>
>> > 1. xen/master, I get following compilation errors. I do see i= n xen-devel
>> > forum someone else has reported similar issue but no solution= yet(patch
>> > provided by Konrad has followup errors)
>>
>> > CC [M] =A0drivers/watchdog/machzwd.o
>> > =A0 CC [M] =A0drivers/watchdog/sbc_epx_c3.o
>> > =A0 CC [M] =A0drivers/watchdog/softdog.o
>> > =A0 CC =A0 =A0 =A0drivers/xen/grant-table.o
>> > =A0 CC =A0 =A0 =A0drivers/xen/features.o
>> > =A0 CC =A0 =A0 =A0drivers/xen/events.o
>> > drivers/xen/events.c:605: error: redefinition of =E2=80=98xen= _destroy_irq=E2=80=99
>> > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29:= error:
>> > previous definition of =E2=80=98xen_destroy_irq=E2=80=99 was = here
>> > drivers/xen/events.c:637: error: redefinition of =E2=80=98xen= _create_msi_irq=E2=80=99
>> > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25:= error:
>> > previous definition of =E2=80=98xen_create_msi_irq=E2=80=99 w= as here
>> > make[2]: *** [drivers/xen/events.o] Error 1
>> > make[1]: *** [drivers/xen] Error 2
>> > make: *** [drivers] Error 2
>>
>> > 2. xen/stable, I get following errors
>>
>> > =A0CC =A0 =A0 =A0drivers/pci/xen-pcifront.o
>> > drivers/pci/xen-pcifront.c:373: error: variable =E2=80=98pci_= frontend_ops=E2=80=99
>> has
>> > initializut incomplete type
>> > drivers/pci/xen-pcifront.c:374: error: unknown field =E2=80= =98enable_msi=E2=80=99
>> > specified in ializer
>> > drivers/pci/xen-pcifront.c:374: warning: excess elements in s= truct
>> > initializer
>> > drivers/pci/xen-pcifront.c:374: warning: (near initialization= for
>> > =E2=80=98pci_frontend_op)=E2=80=99
>> > drivers/pci/xen-pcifront.c:375: error: unknown field =E2=80= =98disable_msi=E2=80=99
>> > specified in ializer
>> > drivers/pci/xen-pcifront.c:375: warning: excess elements in s= truct
>> > initializer
>> > drivers/pci/xen-pcifront.c:375: warning: (near initialization= for
>> > =E2=80=98pci_frontend_op)=E2=80=99
>> > drivers/pci/xen-pcifront.c:376: error: unknown field =E2=80= =98enable_msix=E2=80=99
>> > specified in ializer
>> > drivers/pci/xen-pcifront.c:376: warning: excess elements in s= truct
>> > initializer
>> > drivers/pci/xen-pcifront.c:376: warning: (near initialization= for
>> > =E2=80=98pci_frontend_op)=E2=80=99
>> > drivers/pci/xen-pcifront.c:377: error: unknown field =E2=80= =98disable_msix=E2=80=99
>> > specified intializer
>> > drivers/pci/xen-pcifront.c:377: warning: excess elements in s= truct
>> > initializer
>> > drivers/pci/xen-pcifront.c:377: warning: (near initialization= for
>> > =E2=80=98pci_frontend_op)=E2=80=99
>> > drivers/pci/xen-pcifront.c: In function =E2=80=98pci_frontend= _registrar=E2=80=99:
>> > drivers/pci/xen-pcifront.c:383: error: =E2=80=98xen_pci_front= end=E2=80=99 undeclared
>> > (first use his function)
>> > drivers/pci/xen-pcifront.c:383: error: (Each undeclared ident= ifier is
>> > reported only once
>> > drivers/pci/xen-pcifront.c:383: error: for each function it a= ppears in.)
>> > make[2]: *** [drivers/pci/xen-pcifront.o] Error 1
>> > make[1]: *** [drivers/pci] Error 2
>> > make: *** [drivers] Error 2
>>
>> > Kindly let me know how to proceed on this.
>>
>> > Thanks
>>
>>
>>
>> --
>> Best regards,
>> =A0Sander =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0m= ailto:linux@eikel= enboom.it
>>
>>

--

Best regards,
=A0Sander =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0mailto:linux@eikelenboom.it=

--000e0cd1a9a0bfb7380481ce8186-- --===============2134394969== 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 --===============2134394969==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: domU guest for xcp 0.1.1 Date: Mon, 15 Mar 2010 08:44:48 +0000 Message-ID: <1268642688.8652.2792.camel@localhost.localdomain> References: <29b32d341003120910l5340bc01tcada3ca2adbaf763@mail.gmail.com> <29b32d341003121751s517ea28qbdb78e8cc69243ac@mail.gmail.com> <20100313111857.GS1878@reaktio.net> <29b32d341003130809u49d1edcas234fdca4c3d70ed@mail.gmail.com> <20100313164102.GZ1878@reaktio.net> <29b32d341003131743j6ae271d6of486a3c1a4858513@mail.gmail.com> <112460240.20100314121540@eikelenboom.it> <29b32d341003141329v3c6a73c0y8030cf3c6736634c@mail.gmail.com> <1056770753.20100314215224@eikelenboom.it> <29b32d341003141840x5a55e74sfb2eda56005e4f84@mail.gmail.com> <29b32d341003142030p1fe511d2ke30b8483ff8cc368@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <29b32d341003142030p1fe511d2ke30b8483ff8cc368@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: Ritu kaur Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Mon, 2010-03-15 at 03:30 +0000, Ritu kaur wrote: > Just to add, this driver compiles fine in other linux flavors(Debian > Lenny 5.0, Citrix Xenserver...) so it has to do with Xen/stable. > Didn't see anything related to this in xen-devel, inputs appreciated. This is because the pvops kernel is based on a much newer upstream kernel (2.6.31 or 32) than that found in Lenny (2.6.26) or Citrix XenServer (2.6.18/27) and some of the kernel's internal interfaces must have changed. This has nothing to do with Xen per-se but rather compatibility with different Linux kernels. Ian. >=20 > Thanks >=20 > On Sun, Mar 14, 2010 at 6:40 PM, Ritu kaur > wrote: > Hi Pasi, > =20 > I am able to use xen/stable kernel in domU(debian lenny) and > lspci lists the device(i am testing pci passthrough). however, > when I compile my driver in domU I get=20 > =20 > struct net_device has no member named open > struct net_device has no member named stop > struct net_device has no member named hard_start_xmit > ... > =20 > I need to compile my driver in domU and load it in order to > use the nic from domU. Inputs appreciated. > =20 > Thanks=20 > =20 > =20 > =20 > On Sun, Mar 14, 2010 at 1:52 PM, Sander Eikelenboom > wrote: > Hello Ritu, > =20 > I don't have experience with XCP specifically, but > normal compiled pvops-kernels work fine for me with > Debian lenny domU's. > =20 > -- > Sander=20 > =20 > =20 > Sunday, March 14, 2010, 9:29:29 PM, you wrote: > =20 > > Hi Sander, > =20 > > Thanks, I enabled DOM0 and other backend drivers > along with pci frontend in > > .config file. I am able to get it build. However, I > having additional > > questions, inputs appreciated. > =20 > > 1. can this kernel be used in any linux > distribution? I have Debian Lenny as > > DomU? > =20 > > 2. In Debian Lenny /boot/grub/menu.lst, I have > > title Debian GNU/Linux, kernel > 2.6.26-2-686-bigmem > > root (hd0,0) > > kernel /boot/vmlinuz-2.6.26-2-686-bigmem > root=3D/dev/xvda1 ro > > console=3Dhvc0 quiet > > initrd /boot/initrd.img-2.6.26-2-686-bigmem > =20 > > but the kernel image built in arch/i386/boot is > bzImage. Does "make > > modules_install" and "make install" take care of it, > since I am not sure I > > haven't tried it. > =20 > > Basically, my question boils down to > =20 > > 1. Can I use bzImage in debian lenny, > > 2. does make install take care of configuring it > =20 > =20 > > Thanks > =20 > > On Sun, Mar 14, 2010 at 4:15 AM, Sander Eikelenboom > wrote: > =20 > >> Hello Ritu, > >> > >> There are some problems with pci.h, i have also > reported this to Konrad. > >> As a workaround you can enable dom0 support in > these kernels, then they > >> compile fine in my case. > >> > >> -- > >> > >> Sander > >> > >> > >> Sunday, March 14, 2010, 2:43:23 AM, you wrote: > >> > >> > I followed the steps mentioned in wiki to pull > xen code to compile domU > >> > kernel from > >> > >> > 1. xen/master, I get following compilation > errors. I do see in xen-devel > >> > forum someone else has reported similar issue but > no solution yet(patch > >> > provided by Konrad has followup errors) > >> > >> > CC [M] drivers/watchdog/machzwd.o > >> > CC [M] drivers/watchdog/sbc_epx_c3.o > >> > CC [M] drivers/watchdog/softdog.o > >> > CC drivers/xen/grant-table.o > >> > CC drivers/xen/features.o > >> > CC drivers/xen/events.o > >> > drivers/xen/events.c:605: error: redefinition of > =C3=A2=E2=82=AC=CB=9Cxen_destroy_irq=C3=A2=E2=82=AC=E2=84= =A2 > >> > > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/p= ci.h:29: error: > >> > previous definition of =C3=A2=E2=82=AC=CB=9Cxen_de= stroy_irq=C3=A2=E2=82=AC=E2=84=A2 was > here > >> > drivers/xen/events.c:637: error: redefinition of > =C3=A2=E2=82=AC=CB=9Cxen_create_msi_irq=C3=A2=E2=82=AC=E2= =84=A2 > >> > > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/p= ci.h:25: error: > >> > previous definition of =C3=A2=E2=82=AC=CB=9Cxen_cr= eate_msi_irq=C3=A2=E2=82=AC=E2=84=A2 > was here > >> > make[2]: *** [drivers/xen/events.o] Error 1 > >> > make[1]: *** [drivers/xen] Error 2 > >> > make: *** [drivers] Error 2 > >> > >> > 2. xen/stable, I get following errors > >> > >> > CC drivers/pci/xen-pcifront.o > >> > drivers/pci/xen-pcifront.c:373: error: variable =C3= =A2 > =E2=82=AC=CB=9Cpci_frontend_ops=C3=A2=E2=82=AC=E2=84=A2 > >> has > >> > initializut incomplete type > >> > drivers/pci/xen-pcifront.c:374: error: unknown > field =C3=A2=E2=82=AC=CB=9Cenable_msi=C3=A2=E2=82=AC=E2= =84=A2 > >> > specified in ializer > >> > drivers/pci/xen-pcifront.c:374: warning: excess > elements in struct > >> > initializer > >> > drivers/pci/xen-pcifront.c:374: warning: (near > initialization for > >> > =C3=A2=E2=82=AC=CB=9Cpci_frontend_op)=C3=A2=E2=82=AC= =E2=84=A2 > >> > drivers/pci/xen-pcifront.c:375: error: unknown > field =C3=A2=E2=82=AC=CB=9Cdisable_msi=C3=A2=E2=82=AC=E2= =84=A2 > >> > specified in ializer > >> > drivers/pci/xen-pcifront.c:375: warning: excess > elements in struct > >> > initializer > >> > drivers/pci/xen-pcifront.c:375: warning: (near > initialization for > >> > =C3=A2=E2=82=AC=CB=9Cpci_frontend_op)=C3=A2=E2=82=AC= =E2=84=A2 > >> > drivers/pci/xen-pcifront.c:376: error: unknown > field =C3=A2=E2=82=AC=CB=9Cenable_msix=C3=A2=E2=82=AC=E2= =84=A2 > >> > specified in ializer > >> > drivers/pci/xen-pcifront.c:376: warning: excess > elements in struct > >> > initializer > >> > drivers/pci/xen-pcifront.c:376: warning: (near > initialization for > >> > =C3=A2=E2=82=AC=CB=9Cpci_frontend_op)=C3=A2=E2=82=AC= =E2=84=A2 > >> > drivers/pci/xen-pcifront.c:377: error: unknown > field =C3=A2=E2=82=AC=CB=9Cdisable_msix=C3=A2=E2=82=AC=E2= =84=A2 > >> > specified intializer > >> > drivers/pci/xen-pcifront.c:377: warning: excess > elements in struct > >> > initializer > >> > drivers/pci/xen-pcifront.c:377: warning: (near > initialization for > >> > =C3=A2=E2=82=AC=CB=9Cpci_frontend_op)=C3=A2=E2=82=AC= =E2=84=A2 > >> > drivers/pci/xen-pcifront.c: In function =C3=A2 > =E2=82=AC=CB=9Cpci_frontend_registrar=C3=A2=E2=82=AC=E2= =84=A2: > >> > drivers/pci/xen-pcifront.c:383: error: =C3=A2 > =E2=82=AC=CB=9Cxen_pci_frontend=C3=A2=E2=82=AC=E2=84=A2= undeclared > >> > (first use his function) > >> > drivers/pci/xen-pcifront.c:383: error: (Each > undeclared identifier is > >> > reported only once > >> > drivers/pci/xen-pcifront.c:383: error: for each > function it appears in.) > >> > make[2]: *** [drivers/pci/xen-pcifront.o] Error 1 > >> > make[1]: *** [drivers/pci] Error 2 > >> > make: *** [drivers] Error 2 > >> > >> > Kindly let me know how to proceed on this. > >> > >> > Thanks > >> > >> > >> > >> -- > >> Best regards, > >> Sander > mailto:linux@eikelenboom.it > >> > >> > =20 > =20 > =20 > =20 > --=20 > =20 > Best regards, > Sander > mailto:linux@eikelenboom.it > =20 > =20 > =20 > =20 >=20 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ritu kaur Subject: Re: domU guest for xcp 0.1.1 Date: Mon, 15 Mar 2010 06:42:30 -0700 Message-ID: <29b32d341003150642o4e2620edsf154b19d78aa7f42@mail.gmail.com> References: <29b32d341003120910l5340bc01tcada3ca2adbaf763@mail.gmail.com> <29b32d341003130809u49d1edcas234fdca4c3d70ed@mail.gmail.com> <20100313164102.GZ1878@reaktio.net> <29b32d341003131743j6ae271d6of486a3c1a4858513@mail.gmail.com> <112460240.20100314121540@eikelenboom.it> <29b32d341003141329v3c6a73c0y8030cf3c6736634c@mail.gmail.com> <1056770753.20100314215224@eikelenboom.it> <29b32d341003141840x5a55e74sfb2eda56005e4f84@mail.gmail.com> <29b32d341003142030p1fe511d2ke30b8483ff8cc368@mail.gmail.com> <1268642688.8652.2792.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1567620191==" Return-path: In-Reply-To: <1268642688.8652.2792.camel@localhost.localdomain> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Campbell Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org --===============1567620191== Content-Type: multipart/alternative; boundary=000e0cd13bca7957c70481d70ddc --000e0cd13bca7957c70481d70ddc Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Ian, Thanks. Should I use DDK to compile my drivers? I have pci device listed in domU and drivers are not compilable there hence wondering how do I use the it? Thanks On Mon, Mar 15, 2010 at 1:44 AM, Ian Campbell wrot= e: > On Mon, 2010-03-15 at 03:30 +0000, Ritu kaur wrote: > > Just to add, this driver compiles fine in other linux flavors(Debian > > Lenny 5.0, Citrix Xenserver...) so it has to do with Xen/stable. > > Didn't see anything related to this in xen-devel, inputs appreciated. > > This is because the pvops kernel is based on a much newer upstream > kernel (2.6.31 or 32) than that found in Lenny (2.6.26) or Citrix > XenServer (2.6.18/27) and some of the kernel's internal interfaces must > have changed. > > This has nothing to do with Xen per-se but rather compatibility with > different Linux kernels. > > Ian. > > > > > Thanks > > > > On Sun, Mar 14, 2010 at 6:40 PM, Ritu kaur > > wrote: > > Hi Pasi, > > > > I am able to use xen/stable kernel in domU(debian lenny) and > > lspci lists the device(i am testing pci passthrough). however, > > when I compile my driver in domU I get > > > > struct net_device has no member named open > > struct net_device has no member named stop > > struct net_device has no member named hard_start_xmit > > ... > > > > I need to compile my driver in domU and load it in order to > > use the nic from domU. Inputs appreciated. > > > > Thanks > > > > > > > > On Sun, Mar 14, 2010 at 1:52 PM, Sander Eikelenboom > > wrote: > > Hello Ritu, > > > > I don't have experience with XCP specifically, but > > normal compiled pvops-kernels work fine for me with > > Debian lenny domU's. > > > > -- > > Sander > > > > > > Sunday, March 14, 2010, 9:29:29 PM, you wrote: > > > > > Hi Sander, > > > > > Thanks, I enabled DOM0 and other backend drivers > > along with pci frontend in > > > .config file. I am able to get it build. However, I > > having additional > > > questions, inputs appreciated. > > > > > 1. can this kernel be used in any linux > > distribution? I have Debian Lenny as > > > DomU? > > > > > 2. In Debian Lenny /boot/grub/menu.lst, I have > > > title Debian GNU/Linux, kernel > > 2.6.26-2-686-bigmem > > > root (hd0,0) > > > kernel /boot/vmlinuz-2.6.26-2-686-bigmem > > root=3D/dev/xvda1 ro > > > console=3Dhvc0 quiet > > > initrd /boot/initrd.img-2.6.26-2-686-bigmem > > > > > but the kernel image built in arch/i386/boot is > > bzImage. Does "make > > > modules_install" and "make install" take care of it, > > since I am not sure I > > > haven't tried it. > > > > > Basically, my question boils down to > > > > > 1. Can I use bzImage in debian lenny, > > > 2. does make install take care of configuring it > > > > > > > Thanks > > > > > On Sun, Mar 14, 2010 at 4:15 AM, Sander Eikelenboom > > wrote: > > > > >> Hello Ritu, > > >> > > >> There are some problems with pci.h, i have also > > reported this to Konrad. > > >> As a workaround you can enable dom0 support in > > these kernels, then they > > >> compile fine in my case. > > >> > > >> -- > > >> > > >> Sander > > >> > > >> > > >> Sunday, March 14, 2010, 2:43:23 AM, you wrote: > > >> > > >> > I followed the steps mentioned in wiki to pull > > xen code to compile domU > > >> > kernel from > > >> > > >> > 1. xen/master, I get following compilation > > errors. I do see in xen-devel > > >> > forum someone else has reported similar issue but > > no solution yet(patch > > >> > provided by Konrad has followup errors) > > >> > > >> > CC [M] drivers/watchdog/machzwd.o > > >> > CC [M] drivers/watchdog/sbc_epx_c3.o > > >> > CC [M] drivers/watchdog/softdog.o > > >> > CC drivers/xen/grant-table.o > > >> > CC drivers/xen/features.o > > >> > CC drivers/xen/events.o > > >> > drivers/xen/events.c:605: error: redefinition of > > =E2=80=98xen_destroy_irq=E2=80=99 > > >> > > > > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29: error: > > >> > previous definition of =E2=80=98xen_destroy_irq=E2= =80=99 was > > here > > >> > drivers/xen/events.c:637: error: redefinition of > > =E2=80=98xen_create_msi_irq=E2=80=99 > > >> > > > > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25: error: > > >> > previous definition of =E2=80=98xen_create_msi_irq= =E2=80=99 > > was here > > >> > make[2]: *** [drivers/xen/events.o] Error 1 > > >> > make[1]: *** [drivers/xen] Error 2 > > >> > make: *** [drivers] Error 2 > > >> > > >> > 2. xen/stable, I get following errors > > >> > > >> > CC drivers/pci/xen-pcifront.o > > >> > drivers/pci/xen-pcifront.c:373: error: variable = =E2 > > =80=98pci_frontend_ops=E2=80=99 > > >> has > > >> > initializut incomplete type > > >> > drivers/pci/xen-pcifront.c:374: error: unknown > > field =E2=80=98enable_msi=E2=80=99 > > >> > specified in ializer > > >> > drivers/pci/xen-pcifront.c:374: warning: excess > > elements in struct > > >> > initializer > > >> > drivers/pci/xen-pcifront.c:374: warning: (near > > initialization for > > >> > =E2=80=98pci_frontend_op)=E2=80=99 > > >> > drivers/pci/xen-pcifront.c:375: error: unknown > > field =E2=80=98disable_msi=E2=80=99 > > >> > specified in ializer > > >> > drivers/pci/xen-pcifront.c:375: warning: excess > > elements in struct > > >> > initializer > > >> > drivers/pci/xen-pcifront.c:375: warning: (near > > initialization for > > >> > =E2=80=98pci_frontend_op)=E2=80=99 > > >> > drivers/pci/xen-pcifront.c:376: error: unknown > > field =E2=80=98enable_msix=E2=80=99 > > >> > specified in ializer > > >> > drivers/pci/xen-pcifront.c:376: warning: excess > > elements in struct > > >> > initializer > > >> > drivers/pci/xen-pcifront.c:376: warning: (near > > initialization for > > >> > =E2=80=98pci_frontend_op)=E2=80=99 > > >> > drivers/pci/xen-pcifront.c:377: error: unknown > > field =E2=80=98disable_msix=E2=80=99 > > >> > specified intializer > > >> > drivers/pci/xen-pcifront.c:377: warning: excess > > elements in struct > > >> > initializer > > >> > drivers/pci/xen-pcifront.c:377: warning: (near > > initialization for > > >> > =E2=80=98pci_frontend_op)=E2=80=99 > > >> > drivers/pci/xen-pcifront.c: In function =E2 > > =80=98pci_frontend_registrar=E2=80=99: > > >> > drivers/pci/xen-pcifront.c:383: error: =E2 > > =80=98xen_pci_frontend=E2=80=99 undeclared > > >> > (first use his function) > > >> > drivers/pci/xen-pcifront.c:383: error: (Each > > undeclared identifier is > > >> > reported only once > > >> > drivers/pci/xen-pcifront.c:383: error: for each > > function it appears in.) > > >> > make[2]: *** [drivers/pci/xen-pcifront.o] Error 1 > > >> > make[1]: *** [drivers/pci] Error 2 > > >> > make: *** [drivers] Error 2 > > >> > > >> > Kindly let me know how to proceed on this. > > >> > > >> > Thanks > > >> > > >> > > >> > > >> -- > > >> Best regards, > > >> Sander > > mailto:linux@eikelenboom.it > > >> > > >> > > > > > > > > > > -- > > > > Best regards, > > Sander > > mailto:linux@eikelenboom.it > > > > > > > > > > > > > --000e0cd13bca7957c70481d70ddc Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Ian,

Thanks. Should I use DDK to compile my drivers? I have pci d= evice listed in domU and drivers are not compilable there hence wondering h= ow do I use the it?

Thanks

On Mon= , Mar 15, 2010 at 1:44 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:=

On Mon, 2010-03-15 at 03:30 +0000, Ritu kaur wrote:
> Just to add, this driver compiles fine in other linux flavors(Debian > Lenny 5.0, Citrix Xenserver...) so it has to do with Xen/stable.
> Didn't see anything related to this in xen-devel, inputs appreciat= ed.

This is because the pvops kernel is based on a much newer upstream kernel (2.6.31 or 32) than that found in Lenny (2.6.26) or Citrix
XenServer (2.6.18/27) and some of the kernel's internal interfaces must=
have changed.

This has nothing to do with Xen per-se but rather compatibility with
different Linux kernels.

Ian.

>
> Thanks
>
> On Sun, Mar 14, 2010 at 6:40 PM, Ritu kaur <ritu.kaur.us@gmail.com>
> wrote:
> =A0 =A0 =A0 =A0 Hi Pasi,
>
> =A0 =A0 =A0 =A0 I am able to use xen/stable kernel in domU(debian lenn= y) and
> =A0 =A0 =A0 =A0 lspci lists the device(i am testing pci passthrough). = however,
> =A0 =A0 =A0 =A0 when I compile my driver in domU I get
>
> =A0 =A0 =A0 =A0 struct net_device has no member named open
> =A0 =A0 =A0 =A0 struct net_device has no member named stop
> =A0 =A0 =A0 =A0 struct net_device has no member named hard_start_xmit<= br> > =A0 =A0 =A0 =A0 ...
>
> =A0 =A0 =A0 =A0 I need to compile my driver in domU and load it in ord= er to
> =A0 =A0 =A0 =A0 use the nic from domU. Inputs appreciated.
>
> =A0 =A0 =A0 =A0 Thanks
>
>
>
> =A0 =A0 =A0 =A0 On Sun, Mar 14, 2010 at 1:52 PM, Sander Eikelenboom > =A0 =A0 =A0 =A0 <linux@eike= lenboom.it> wrote:
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Hello Ritu,
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 I don't have experience with XCP s= pecifically, but
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 normal compiled pvops-kernels work fin= e for me with
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Debian lenny domU's.
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 --
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Sander
>
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Sunday, March 14, 2010, 9:29:29 PM, yo= u wrote:
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > Hi Sander,
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > Thanks, I enabled DOM0 and other = backend drivers
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 along with pci frontend in
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > .config file. I am able to get it= build. However, I
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 having additional
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > questions, inputs appreciated. >
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > 1. can this kernel be used in any= linux
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 distribution? I have Debian Lenny as > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > DomU?
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > 2. In Debian Lenny /boot/grub/men= u.lst, I have
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > title =A0 =A0 =A0 =A0 =A0 Debian = GNU/Linux, kernel
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 2.6.26-2-686-bigmem
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > root =A0 =A0 =A0 =A0 =A0 =A0(hd0,= 0)
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > kernel =A0 =A0 =A0 =A0 =A0/boot/v= mlinuz-2.6.26-2-686-bigmem
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 root=3D/dev/xvda1 ro
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > console=3Dhvc0 quiet
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > initrd =A0 =A0 =A0 =A0 =A0/boot/i= nitrd.img-2.6.26-2-686-bigmem
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > but the kernel image built in arc= h/i386/boot is
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 bzImage. Does "make
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > modules_install" and "m= ake install" take care of it,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 since I am not sure I
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > haven't tried it.
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > Basically, my question boils down= to
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > 1. Can I use bzImage in debian le= nny,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > 2. does make install take care of= configuring it
>
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > Thanks
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > On Sun, Mar 14, 2010 at 4:15 AM, = Sander Eikelenboom
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <linux@eikelenboom.it>wrote:
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> Hello Ritu,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> There are some problems with = pci.h, i have also
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 reported this to Konrad.
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> As a workaround you can enabl= e dom0 support in
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 these kernels, then they
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> compile fine in my case.
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> --
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> Sander
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> Sunday, March 14, 2010, 2:43:= 23 AM, you wrote:
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > I followed the steps men= tioned in =A0wiki to pull
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 xen code to compile domU
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > kernel from
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > 1. xen/master, I get fol= lowing compilation
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 errors. I do see in xen-devel
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > forum someone else has r= eported similar issue but
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 no solution yet(patch
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > provided by Konrad has f= ollowup errors)
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > CC [M] =A0drivers/watchd= og/machzwd.o
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =A0 CC [M] =A0drivers/wa= tchdog/sbc_epx_c3.o
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =A0 CC [M] =A0drivers/wa= tchdog/softdog.o
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =A0 CC =A0 =A0 =A0driver= s/xen/grant-table.o
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =A0 CC =A0 =A0 =A0driver= s/xen/features.o
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =A0 CC =A0 =A0 =A0driver= s/xen/events.o
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/xen/events.c:605= : error: redefinition of
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =E2=80=98xen_destroy_irq=E2=80=99
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > /root/kernel/linux.2-6.xen/arch/x= 86/include/asm/xen/pci.h:29: error:
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > previous definition of = =E2=80=98xen_destroy_irq=E2=80=99 was
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 here
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/xen/events.c:637= : error: redefinition of
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =E2=80=98xen_create_msi_irq=E2=80=99 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > /root/kernel/linux.2-6.xen/arch/x= 86/include/asm/xen/pci.h:25: error:
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > previous definition of = =E2=80=98xen_create_msi_irq=E2=80=99
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 was here
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > make[2]: *** [drivers/xe= n/events.o] Error 1
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > make[1]: *** [drivers/xe= n] Error 2
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > make: *** [drivers] Erro= r 2
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > 2. xen/stable, I get fol= lowing errors
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =A0CC =A0 =A0 =A0drivers= /pci/xen-pcifront.o
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:373: error: variable =E2
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =80=98pci_frontend_ops=E2=80=99
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> has
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > initializut incomplete t= ype
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:374: error: unknown
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 field =E2=80=98enable_msi=E2=80=99
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > specified in ializer
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:374: warning: excess
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 elements in struct
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > initializer
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:374: warning: (near
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 initialization for
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =E2=80=98pci_frontend_op= )=E2=80=99
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:375: error: unknown
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 field =E2=80=98disable_msi=E2=80=99 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > specified in ializer
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:375: warning: excess
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 elements in struct
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > initializer
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:375: warning: (near
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 initialization for
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =E2=80=98pci_frontend_op= )=E2=80=99
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:376: error: unknown
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 field =E2=80=98enable_msix=E2=80=99 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > specified in ializer
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:376: warning: excess
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 elements in struct
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > initializer
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:376: warning: (near
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 initialization for
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =E2=80=98pci_frontend_op= )=E2=80=99
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:377: error: unknown
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 field =E2=80=98disable_msix=E2=80=99 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > specified intializer
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:377: warning: excess
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 elements in struct
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > initializer
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:377: warning: (near
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 initialization for
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =E2=80=98pci_frontend_op= )=E2=80=99
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c: In function =E2
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =80=98pci_frontend_registrar=E2=80=99:=
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:383: error: =E2
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =80=98xen_pci_frontend=E2=80=99 undecl= ared
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > (first use his function)=
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:383: error: (Each
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 undeclared identifier is
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > reported only once
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:383: error: for each
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 function it appears in.)
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > make[2]: *** [drivers/pc= i/xen-pcifront.o] Error 1
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > make[1]: *** [drivers/pc= i] Error 2
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > make: *** [drivers] Erro= r 2
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > Kindly let me know how t= o proceed on this.
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > Thanks
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> --
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> Best regards,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> =A0Sander
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0mailto:linux@eikelenboom.it
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
>
>
>
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 --
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Best regards,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Sander
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0mailto:linux@eikelenboom.it
>
>
>
>
>

--000e0cd13bca7957c70481d70ddc-- --===============1567620191== 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 --===============1567620191==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: domU guest for xcp 0.1.1 Date: Mon, 15 Mar 2010 13:44:05 +0000 Message-ID: <1268660645.10129.25070.camel@zakaz.uk.xensource.com> References: <29b32d341003120910l5340bc01tcada3ca2adbaf763@mail.gmail.com> <29b32d341003130809u49d1edcas234fdca4c3d70ed@mail.gmail.com> <20100313164102.GZ1878@reaktio.net> <29b32d341003131743j6ae271d6of486a3c1a4858513@mail.gmail.com> <112460240.20100314121540@eikelenboom.it> <29b32d341003141329v3c6a73c0y8030cf3c6736634c@mail.gmail.com> <1056770753.20100314215224@eikelenboom.it> <29b32d341003141840x5a55e74sfb2eda56005e4f84@mail.gmail.com> <29b32d341003142030p1fe511d2ke30b8483ff8cc368@mail.gmail.com> <1268642688.8652.2792.camel@localhost.localdomain> <29b32d341003150642o4e2620edsf154b19d78aa7f42@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <29b32d341003150642o4e2620edsf154b19d78aa7f42@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: Ritu kaur Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Mon, 2010-03-15 at 13:42 +0000, Ritu kaur wrote: > Hi Ian, >=20 > Thanks. Should I use DDK to compile my drivers? I have pci device > listed in domU and drivers are not compilable there hence wondering > how do I use the it?=20 You must compile your driver against the kernel used in the domU. This is not a Xen specific requirement -- you must always compile your driver against the kernel you want to use it with. Note that this may involve porting your driver to work with the kernel you are using in your domU. Ian. >=20 > Thanks >=20 > On Mon, Mar 15, 2010 at 1:44 AM, Ian Campbell > wrote: > On Mon, 2010-03-15 at 03:30 +0000, Ritu kaur wrote: > > Just to add, this driver compiles fine in other linux > flavors(Debian > > Lenny 5.0, Citrix Xenserver...) so it has to do with > Xen/stable. > > Didn't see anything related to this in xen-devel, inputs > appreciated. > =20 > =20 > This is because the pvops kernel is based on a much newer > upstream > kernel (2.6.31 or 32) than that found in Lenny (2.6.26) or > Citrix > XenServer (2.6.18/27) and some of the kernel's internal > interfaces must > have changed. > =20 > This has nothing to do with Xen per-se but rather > compatibility with > different Linux kernels. > =20 > Ian. > =20 > =20 > > > > Thanks > > > > On Sun, Mar 14, 2010 at 6:40 PM, Ritu kaur > > > wrote: > > Hi Pasi, > > > > I am able to use xen/stable kernel in domU(debian > lenny) and > > lspci lists the device(i am testing pci > passthrough). however, > > when I compile my driver in domU I get > > > > struct net_device has no member named open > > struct net_device has no member named stop > > struct net_device has no member named > hard_start_xmit > > ... > > > > I need to compile my driver in domU and load it in > order to > > use the nic from domU. Inputs appreciated. > > > > Thanks > > > > > > > > On Sun, Mar 14, 2010 at 1:52 PM, Sander Eikelenboom > > wrote: > > Hello Ritu, > > > > I don't have experience with XCP > specifically, but > > normal compiled pvops-kernels work fine for > me with > > Debian lenny domU's. > > > > -- > > Sander > > > > > > Sunday, March 14, 2010, 9:29:29 PM, you > wrote: > > > > > Hi Sander, > > > > > Thanks, I enabled DOM0 and other backend > drivers > > along with pci frontend in > > > .config file. I am able to get it build. > However, I > > having additional > > > questions, inputs appreciated. > > > > > 1. can this kernel be used in any linux > > distribution? I have Debian Lenny as > > > DomU? > > > > > 2. In Debian Lenny /boot/grub/menu.lst, I > have > > > title Debian GNU/Linux, kernel > > 2.6.26-2-686-bigmem > > > root (hd0,0) > > > kernel > /boot/vmlinuz-2.6.26-2-686-bigmem > > root=3D/dev/xvda1 ro > > > console=3Dhvc0 quiet > > > initrd > /boot/initrd.img-2.6.26-2-686-bigmem > > > > > but the kernel image built in > arch/i386/boot is > > bzImage. Does "make > > > modules_install" and "make install" take > care of it, > > since I am not sure I > > > haven't tried it. > > > > > Basically, my question boils down to > > > > > 1. Can I use bzImage in debian lenny, > > > 2. does make install take care of > configuring it > > > > > > > Thanks > > > > > On Sun, Mar 14, 2010 at 4:15 AM, Sander > Eikelenboom > > wrote: > > > > >> Hello Ritu, > > >> > > >> There are some problems with pci.h, i > have also > > reported this to Konrad. > > >> As a workaround you can enable dom0 > support in > > these kernels, then they > > >> compile fine in my case. > > >> > > >> -- > > >> > > >> Sander > > >> > > >> > > >> Sunday, March 14, 2010, 2:43:23 AM, you > wrote: > > >> > > >> > I followed the steps mentioned in wiki > to pull > > xen code to compile domU > > >> > kernel from > > >> > > >> > 1. xen/master, I get following > compilation > > errors. I do see in xen-devel > > >> > forum someone else has reported similar > issue but > > no solution yet(patch > > >> > provided by Konrad has followup errors) > > >> > > >> > CC [M] drivers/watchdog/machzwd.o > > >> > CC [M] drivers/watchdog/sbc_epx_c3.o > > >> > CC [M] drivers/watchdog/softdog.o > > >> > CC drivers/xen/grant-table.o > > >> > CC drivers/xen/features.o > > >> > CC drivers/xen/events.o > > >> > drivers/xen/events.c:605: error: > redefinition of > > =C3=A2=E2=82=AC=CB=9Cxen_destroy_irq=C3=A2=E2= =82=AC=E2=84=A2 > > >> > > > > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29:= error: > > >> > previous definition of =C3=A2 > =E2=82=AC=CB=9Cxen_destroy_irq=C3=A2=E2=82=AC=E2=84=A2 was > > here > > >> > drivers/xen/events.c:637: error: > redefinition of > > =C3=A2=E2=82=AC=CB=9Cxen_create_msi_irq=C3=A2= =E2=82=AC=E2=84=A2 > > >> > > > > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25:= error: > > >> > previous definition of =C3=A2 > =E2=82=AC=CB=9Cxen_create_msi_irq=C3=A2=E2=82=AC=E2=84=A2 > > was here > > >> > make[2]: *** [drivers/xen/events.o] > Error 1 > > >> > make[1]: *** [drivers/xen] Error 2 > > >> > make: *** [drivers] Error 2 > > >> > > >> > 2. xen/stable, I get following errors > > >> > > >> > CC drivers/pci/xen-pcifront.o > > >> > drivers/pci/xen-pcifront.c:373: error: > variable =C3=A2 > > =E2=82=AC=CB=9Cpci_frontend_ops=C3=A2=E2=82=AC= =E2=84=A2 > > >> has > > >> > initializut incomplete type > > >> > drivers/pci/xen-pcifront.c:374: error: > unknown > > field =C3=A2=E2=82=AC=CB=9Cenable_msi=C3=A2=E2= =82=AC=E2=84=A2 > > >> > specified in ializer > > >> > drivers/pci/xen-pcifront.c:374: > warning: excess > > elements in struct > > >> > initializer > > >> > drivers/pci/xen-pcifront.c:374: > warning: (near > > initialization for > > >> > =C3=A2=E2=82=AC=CB=9Cpci_frontend_op)=C3= =A2=E2=82=AC=E2=84=A2 > > >> > drivers/pci/xen-pcifront.c:375: error: > unknown > > field =C3=A2=E2=82=AC=CB=9Cdisable_msi=C3=A2=E2= =82=AC=E2=84=A2 > > >> > specified in ializer > > >> > drivers/pci/xen-pcifront.c:375: > warning: excess > > elements in struct > > >> > initializer > > >> > drivers/pci/xen-pcifront.c:375: > warning: (near > > initialization for > > >> > =C3=A2=E2=82=AC=CB=9Cpci_frontend_op)=C3= =A2=E2=82=AC=E2=84=A2 > > >> > drivers/pci/xen-pcifront.c:376: error: > unknown > > field =C3=A2=E2=82=AC=CB=9Cenable_msix=C3=A2=E2= =82=AC=E2=84=A2 > > >> > specified in ializer > > >> > drivers/pci/xen-pcifront.c:376: > warning: excess > > elements in struct > > >> > initializer > > >> > drivers/pci/xen-pcifront.c:376: > warning: (near > > initialization for > > >> > =C3=A2=E2=82=AC=CB=9Cpci_frontend_op)=C3= =A2=E2=82=AC=E2=84=A2 > > >> > drivers/pci/xen-pcifront.c:377: error: > unknown > > field =C3=A2=E2=82=AC=CB=9Cdisable_msix=C3=A2= =E2=82=AC=E2=84=A2 > > >> > specified intializer > > >> > drivers/pci/xen-pcifront.c:377: > warning: excess > > elements in struct > > >> > initializer > > >> > drivers/pci/xen-pcifront.c:377: > warning: (near > > initialization for > > >> > =C3=A2=E2=82=AC=CB=9Cpci_frontend_op)=C3= =A2=E2=82=AC=E2=84=A2 > > >> > drivers/pci/xen-pcifront.c: In function > =C3=A2 > > =E2=82=AC=CB=9Cpci_frontend_registrar=C3=A2=E2= =82=AC=E2=84=A2: > > >> > drivers/pci/xen-pcifront.c:383: error: > =C3=A2 > > =E2=82=AC=CB=9Cxen_pci_frontend=C3=A2=E2=82=AC= =E2=84=A2 undeclared > > >> > (first use his function) > > >> > drivers/pci/xen-pcifront.c:383: error: > (Each > > undeclared identifier is > > >> > reported only once > > >> > drivers/pci/xen-pcifront.c:383: error: > for each > > function it appears in.) > > >> > make[2]: *** > [drivers/pci/xen-pcifront.o] Error 1 > > >> > make[1]: *** [drivers/pci] Error 2 > > >> > make: *** [drivers] Error 2 > > >> > > >> > Kindly let me know how to proceed on > this. > > >> > > >> > Thanks > > >> > > >> > > >> > > >> -- > > >> Best regards, > > >> Sander > > mailto:linux@eikelenboom.it > > >> > > >> > > > > > > > > > > -- > > > > Best regards, > > Sander > > mailto:linux@eikelenboom.it > > > > > > > > > > > =20 > =20 > =20 >=20 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ritu kaur Subject: Re: domU guest for xcp 0.1.1 Date: Mon, 15 Mar 2010 06:46:09 -0700 Message-ID: <29b32d341003150646o4d215dfel1c2a2bc6d287edc@mail.gmail.com> References: <29b32d341003120910l5340bc01tcada3ca2adbaf763@mail.gmail.com> <29b32d341003131743j6ae271d6of486a3c1a4858513@mail.gmail.com> <112460240.20100314121540@eikelenboom.it> <29b32d341003141329v3c6a73c0y8030cf3c6736634c@mail.gmail.com> <1056770753.20100314215224@eikelenboom.it> <29b32d341003141840x5a55e74sfb2eda56005e4f84@mail.gmail.com> <29b32d341003142030p1fe511d2ke30b8483ff8cc368@mail.gmail.com> <1268642688.8652.2792.camel@localhost.localdomain> <29b32d341003150642o4e2620edsf154b19d78aa7f42@mail.gmail.com> <1268660645.10129.25070.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1131156903==" Return-path: In-Reply-To: <1268660645.10129.25070.camel@zakaz.uk.xensource.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: Ian Campbell Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org --===============1131156903== Content-Type: multipart/alternative; boundary=000e0cd109568180de0481d71a02 --000e0cd109568180de0481d71a02 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Thanks Ian, I will take a look at it. On Mon, Mar 15, 2010 at 6:44 AM, Ian Campbell wrot= e: > On Mon, 2010-03-15 at 13:42 +0000, Ritu kaur wrote: > > Hi Ian, > > > > Thanks. Should I use DDK to compile my drivers? I have pci device > > listed in domU and drivers are not compilable there hence wondering > > how do I use the it? > > You must compile your driver against the kernel used in the domU. This > is not a Xen specific requirement -- you must always compile your driver > against the kernel you want to use it with. Note that this may involve > porting your driver to work with the kernel you are using in your domU. > > Ian. > > > > > Thanks > > > > On Mon, Mar 15, 2010 at 1:44 AM, Ian Campbell > > wrote: > > On Mon, 2010-03-15 at 03:30 +0000, Ritu kaur wrote: > > > Just to add, this driver compiles fine in other linux > > flavors(Debian > > > Lenny 5.0, Citrix Xenserver...) so it has to do with > > Xen/stable. > > > Didn't see anything related to this in xen-devel, inputs > > appreciated. > > > > > > This is because the pvops kernel is based on a much newer > > upstream > > kernel (2.6.31 or 32) than that found in Lenny (2.6.26) or > > Citrix > > XenServer (2.6.18/27) and some of the kernel's internal > > interfaces must > > have changed. > > > > This has nothing to do with Xen per-se but rather > > compatibility with > > different Linux kernels. > > > > Ian. > > > > > > > > > > Thanks > > > > > > On Sun, Mar 14, 2010 at 6:40 PM, Ritu kaur > > > > > wrote: > > > Hi Pasi, > > > > > > I am able to use xen/stable kernel in domU(debian > > lenny) and > > > lspci lists the device(i am testing pci > > passthrough). however, > > > when I compile my driver in domU I get > > > > > > struct net_device has no member named open > > > struct net_device has no member named stop > > > struct net_device has no member named > > hard_start_xmit > > > ... > > > > > > I need to compile my driver in domU and load it in > > order to > > > use the nic from domU. Inputs appreciated. > > > > > > Thanks > > > > > > > > > > > > On Sun, Mar 14, 2010 at 1:52 PM, Sander Eikelenboom > > > wrote: > > > Hello Ritu, > > > > > > I don't have experience with XCP > > specifically, but > > > normal compiled pvops-kernels work fine for > > me with > > > Debian lenny domU's. > > > > > > -- > > > Sander > > > > > > > > > Sunday, March 14, 2010, 9:29:29 PM, you > > wrote: > > > > > > > Hi Sander, > > > > > > > Thanks, I enabled DOM0 and other backend > > drivers > > > along with pci frontend in > > > > .config file. I am able to get it build. > > However, I > > > having additional > > > > questions, inputs appreciated. > > > > > > > 1. can this kernel be used in any linux > > > distribution? I have Debian Lenny as > > > > DomU? > > > > > > > 2. In Debian Lenny /boot/grub/menu.lst, I > > have > > > > title Debian GNU/Linux, kernel > > > 2.6.26-2-686-bigmem > > > > root (hd0,0) > > > > kernel > > /boot/vmlinuz-2.6.26-2-686-bigmem > > > root=3D/dev/xvda1 ro > > > > console=3Dhvc0 quiet > > > > initrd > > /boot/initrd.img-2.6.26-2-686-bigmem > > > > > > > but the kernel image built in > > arch/i386/boot is > > > bzImage. Does "make > > > > modules_install" and "make install" take > > care of it, > > > since I am not sure I > > > > haven't tried it. > > > > > > > Basically, my question boils down to > > > > > > > 1. Can I use bzImage in debian lenny, > > > > 2. does make install take care of > > configuring it > > > > > > > > > > Thanks > > > > > > > On Sun, Mar 14, 2010 at 4:15 AM, Sander > > Eikelenboom > > > wrote: > > > > > > >> Hello Ritu, > > > >> > > > >> There are some problems with pci.h, i > > have also > > > reported this to Konrad. > > > >> As a workaround you can enable dom0 > > support in > > > these kernels, then they > > > >> compile fine in my case. > > > >> > > > >> -- > > > >> > > > >> Sander > > > >> > > > >> > > > >> Sunday, March 14, 2010, 2:43:23 AM, you > > wrote: > > > >> > > > >> > I followed the steps mentioned in wiki > > to pull > > > xen code to compile domU > > > >> > kernel from > > > >> > > > >> > 1. xen/master, I get following > > compilation > > > errors. I do see in xen-devel > > > >> > forum someone else has reported similar > > issue but > > > no solution yet(patch > > > >> > provided by Konrad has followup errors) > > > >> > > > >> > CC [M] drivers/watchdog/machzwd.o > > > >> > CC [M] drivers/watchdog/sbc_epx_c3.o > > > >> > CC [M] drivers/watchdog/softdog.o > > > >> > CC drivers/xen/grant-table.o > > > >> > CC drivers/xen/features.o > > > >> > CC drivers/xen/events.o > > > >> > drivers/xen/events.c:605: error: > > redefinition of > > > =E2=80=98xen_destroy_irq=E2=80=99 > > > >> > > > > > > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29: > error: > > > >> > previous definition of =E2 > > =80=98xen_destroy_irq=E2=80=99 was > > > here > > > >> > drivers/xen/events.c:637: error: > > redefinition of > > > =E2=80=98xen_create_msi_irq=E2=80=99 > > > >> > > > > > > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25: > error: > > > >> > previous definition of =E2 > > =80=98xen_create_msi_irq=E2=80=99 > > > was here > > > >> > make[2]: *** [drivers/xen/events.o] > > Error 1 > > > >> > make[1]: *** [drivers/xen] Error 2 > > > >> > make: *** [drivers] Error 2 > > > >> > > > >> > 2. xen/stable, I get following errors > > > >> > > > >> > CC drivers/pci/xen-pcifront.o > > > >> > drivers/pci/xen-pcifront.c:373: error: > > variable =E2 > > > =80=98pci_frontend_ops=E2=80=99 > > > >> has > > > >> > initializut incomplete type > > > >> > drivers/pci/xen-pcifront.c:374: error: > > unknown > > > field =E2=80=98enable_msi=E2=80=99 > > > >> > specified in ializer > > > >> > drivers/pci/xen-pcifront.c:374: > > warning: excess > > > elements in struct > > > >> > initializer > > > >> > drivers/pci/xen-pcifront.c:374: > > warning: (near > > > initialization for > > > >> > =E2=80=98pci_frontend_op)=E2=80=99 > > > >> > drivers/pci/xen-pcifront.c:375: error: > > unknown > > > field =E2=80=98disable_msi=E2=80=99 > > > >> > specified in ializer > > > >> > drivers/pci/xen-pcifront.c:375: > > warning: excess > > > elements in struct > > > >> > initializer > > > >> > drivers/pci/xen-pcifront.c:375: > > warning: (near > > > initialization for > > > >> > =E2=80=98pci_frontend_op)=E2=80=99 > > > >> > drivers/pci/xen-pcifront.c:376: error: > > unknown > > > field =E2=80=98enable_msix=E2=80=99 > > > >> > specified in ializer > > > >> > drivers/pci/xen-pcifront.c:376: > > warning: excess > > > elements in struct > > > >> > initializer > > > >> > drivers/pci/xen-pcifront.c:376: > > warning: (near > > > initialization for > > > >> > =E2=80=98pci_frontend_op)=E2=80=99 > > > >> > drivers/pci/xen-pcifront.c:377: error: > > unknown > > > field =E2=80=98disable_msix=E2=80=99 > > > >> > specified intializer > > > >> > drivers/pci/xen-pcifront.c:377: > > warning: excess > > > elements in struct > > > >> > initializer > > > >> > drivers/pci/xen-pcifront.c:377: > > warning: (near > > > initialization for > > > >> > =E2=80=98pci_frontend_op)=E2=80=99 > > > >> > drivers/pci/xen-pcifront.c: In function > > =E2 > > > =80=98pci_frontend_registrar=E2=80=99: > > > >> > drivers/pci/xen-pcifront.c:383: error: > > =E2 > > > =80=98xen_pci_frontend=E2=80=99 undeclared > > > >> > (first use his function) > > > >> > drivers/pci/xen-pcifront.c:383: error: > > (Each > > > undeclared identifier is > > > >> > reported only once > > > >> > drivers/pci/xen-pcifront.c:383: error: > > for each > > > function it appears in.) > > > >> > make[2]: *** > > [drivers/pci/xen-pcifront.o] Error 1 > > > >> > make[1]: *** [drivers/pci] Error 2 > > > >> > make: *** [drivers] Error 2 > > > >> > > > >> > Kindly let me know how to proceed on > > this. > > > >> > > > >> > Thanks > > > >> > > > >> > > > >> > > > >> -- > > > >> Best regards, > > > >> Sander > > > mailto:linux@eikelenboom.it > > > >> > > > >> > > > > > > > > > > > > > > > -- > > > > > > Best regards, > > > Sander > > > mailto:linux@eikelenboom.it > > > > > > > > > > > > > > > > > > > > > > > > > > --000e0cd109568180de0481d71a02 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Thanks Ian, I will take a look at it.

On = Mon, Mar 15, 2010 at 6:44 AM, Ian Campbell <Ian.Campbell@citrix.com> wro= te:

On Mon, 2010-03-15 at 13:42 +0000, Ritu kaur wrote:
> Hi Ian,
>
> Thanks. Should I use DDK to compile my drivers? I have pci device
> listed in domU and drivers are not compilable there hence wondering > how do I use the it?

You must compile your driver against the kernel used in the domU. Thi= s
is not a Xen specific requirement -- you must always compile your driver against the kernel you want to use it with. Note that this may involve
porting your driver to work with the kernel you are using in your domU.

Ian.

>
> Thanks
>
> On Mon, Mar 15, 2010 at 1:44 AM, Ian Campbell
> <Ian.Campbell@citrix.com= > wrote:
> =A0 =A0 =A0 =A0 On Mon, 2010-03-15 at 03:30 +0000, Ritu kaur wrote: > =A0 =A0 =A0 =A0 > Just to add, this driver compiles fine in other l= inux
> =A0 =A0 =A0 =A0 flavors(Debian
> =A0 =A0 =A0 =A0 > Lenny 5.0, Citrix Xenserver...) so it has to do w= ith
> =A0 =A0 =A0 =A0 Xen/stable.
> =A0 =A0 =A0 =A0 > Didn't see anything related to this in xen-de= vel, inputs
> =A0 =A0 =A0 =A0 appreciated.
>
>
> =A0 =A0 =A0 =A0 This is because the pvops kernel is based on a much ne= wer
> =A0 =A0 =A0 =A0 upstream
> =A0 =A0 =A0 =A0 kernel (2.6.31 or 32) than that found in Lenny (2.6.26= ) or
> =A0 =A0 =A0 =A0 Citrix
> =A0 =A0 =A0 =A0 XenServer (2.6.18/27) and some of the kernel's int= ernal
> =A0 =A0 =A0 =A0 interfaces must
> =A0 =A0 =A0 =A0 have changed.
>
> =A0 =A0 =A0 =A0 This has nothing to do with Xen per-se but rather
> =A0 =A0 =A0 =A0 compatibility with
> =A0 =A0 =A0 =A0 different Linux kernels.
>
> =A0 =A0 =A0 =A0 Ian.
>
>
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > Thanks
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > On Sun, Mar 14, 2010 at 6:40 PM, Ritu kaur
> =A0 =A0 =A0 =A0 <= ritu.kaur.us@gmail.com>
> =A0 =A0 =A0 =A0 > wrote:
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 Hi Pasi,
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 I am able to use xen/stable kerne= l in domU(debian
> =A0 =A0 =A0 =A0 lenny) and
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 lspci lists the device(i am testi= ng pci
> =A0 =A0 =A0 =A0 passthrough). however,
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 when I compile my driver in domU = I get
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 struct net_device has no member n= amed open
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 struct net_device has no member n= amed stop
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 struct net_device has no member n= amed
> =A0 =A0 =A0 =A0 hard_start_xmit
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 ...
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 I need to compile my driver in do= mU and load it in
> =A0 =A0 =A0 =A0 order to
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 use the nic from domU. Inputs app= reciated.
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 Thanks
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 On Sun, Mar 14, 2010 at 1:52 PM, = Sander Eikelenboom
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 <linux@eikelenboom.it> wrote:
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Hello Ritu,
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 I don't have = experience with XCP
> =A0 =A0 =A0 =A0 specifically, but
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 normal compiled p= vops-kernels work fine for
> =A0 =A0 =A0 =A0 me with
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Debian lenny domU= 's.
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 --
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Sander
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Sunday, March 14,= 2010, 9:29:29 PM, you
> =A0 =A0 =A0 =A0 wrote:
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > Hi Sander, > =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > Thanks, I en= abled DOM0 and other backend
> =A0 =A0 =A0 =A0 drivers
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 along with pci fr= ontend in
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > .config file= . I am able to get it build.
> =A0 =A0 =A0 =A0 However, I
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 having additional=
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > questions, i= nputs appreciated.
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > 1. can this = kernel be used in any linux
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 distribution? I h= ave Debian Lenny as
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > DomU?
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > 2. In Debian= Lenny /boot/grub/menu.lst, I
> =A0 =A0 =A0 =A0 have
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > title =A0 = =A0 =A0 =A0 =A0 Debian GNU/Linux, kernel
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 2.6.26-2-686-bigm= em
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > root =A0 =A0= =A0 =A0 =A0 =A0(hd0,0)
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > kernel
> =A0 =A0 =A0 =A0 =A0/boot/vmlinuz-2.6.26-2-686-bigmem
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 root=3D/dev/xvda1= ro
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > console=3Dhv= c0 quiet
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > initrd
> =A0 =A0 =A0 =A0 =A0/boot/initrd.img-2.6.26-2-686-bigmem
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > but the kern= el image built in
> =A0 =A0 =A0 =A0 arch/i386/boot is
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 bzImage. Does &qu= ot;make
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > modules_inst= all" and "make install" take
> =A0 =A0 =A0 =A0 care of it,
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 since I am not su= re I
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > haven't = tried it.
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > Basically, m= y question boils down to
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > 1. Can I use= bzImage in debian lenny,
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > 2. does make= install take care of
> =A0 =A0 =A0 =A0 configuring it
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > Thanks
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > On Sun, Mar = 14, 2010 at 4:15 AM, Sander
> =A0 =A0 =A0 =A0 Eikelenboom
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <linux@eikelenboom.it>wrote:
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> Hello Ri= tu,
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> There ar= e some problems with pci.h, i
> =A0 =A0 =A0 =A0 have also
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 reported this to = Konrad.
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> As a wor= karound you can enable dom0
> =A0 =A0 =A0 =A0 support in
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 these kernels, th= en they
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> compile = fine in my case.
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> --
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> Sander > =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> Sunday, = March 14, 2010, 2:43:23 AM, you
> =A0 =A0 =A0 =A0 wrote:
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > I f= ollowed the steps mentioned in =A0wiki
> =A0 =A0 =A0 =A0 to pull
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 xen code to compi= le domU
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > ker= nel from
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > 1. = xen/master, I get following
> =A0 =A0 =A0 =A0 compilation
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 errors. I do see = in xen-devel
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > for= um someone else has reported similar
> =A0 =A0 =A0 =A0 issue but
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 no solution yet(p= atch
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > pro= vided by Konrad has followup errors)
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > CC = [M] =A0drivers/watchdog/machzwd.o
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =A0= CC [M] =A0drivers/watchdog/sbc_epx_c3.o
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =A0= CC [M] =A0drivers/watchdog/softdog.o
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =A0= CC =A0 =A0 =A0drivers/xen/grant-table.o
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =A0= CC =A0 =A0 =A0drivers/xen/features.o
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =A0= CC =A0 =A0 =A0drivers/xen/events.o
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/xen/events.c:605: error:
> =A0 =A0 =A0 =A0 redefinition of
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =E2=80=98xen_dest= roy_irq=E2=80=99
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > /root/kernel/linux.2-6.xen/arch/x86/include/asm/x= en/pci.h:29: error:
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > pre= vious definition of =E2
> =A0 =A0 =A0 =A0 =80=98xen_destroy_irq=E2=80=99 was
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 here
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/xen/events.c:637: error:
> =A0 =A0 =A0 =A0 redefinition of
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =E2=80=98xen_crea= te_msi_irq=E2=80=99
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > /root/kernel/linux.2-6.xen/arch/x86/include/asm/x= en/pci.h:25: error:
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > pre= vious definition of =E2
> =A0 =A0 =A0 =A0 =80=98xen_create_msi_irq=E2=80=99
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 was here
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > mak= e[2]: *** [drivers/xen/events.o]
> =A0 =A0 =A0 =A0 Error 1
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > mak= e[1]: *** [drivers/xen] Error 2
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > mak= e: *** [drivers] Error 2
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > 2. = xen/stable, I get following errors
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =A0= CC =A0 =A0 =A0drivers/pci/xen-pcifront.o
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:373: error:
> =A0 =A0 =A0 =A0 variable =E2
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =80=98pci_fronten= d_ops=E2=80=99
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> has
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > ini= tializut incomplete type
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:374: error:
> =A0 =A0 =A0 =A0 unknown
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 field =E2=80=98en= able_msi=E2=80=99
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > spe= cified in ializer
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:374:
> =A0 =A0 =A0 =A0 warning: excess
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 elements in struc= t
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > ini= tializer
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:374:
> =A0 =A0 =A0 =A0 warning: (near
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 initialization fo= r
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =E2= =80=98pci_frontend_op)=E2=80=99
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:375: error:
> =A0 =A0 =A0 =A0 unknown
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 field =E2=80=98di= sable_msi=E2=80=99
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > spe= cified in ializer
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:375:
> =A0 =A0 =A0 =A0 warning: excess
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 elements in struc= t
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > ini= tializer
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:375:
> =A0 =A0 =A0 =A0 warning: (near
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 initialization fo= r
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =E2= =80=98pci_frontend_op)=E2=80=99
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:376: error:
> =A0 =A0 =A0 =A0 unknown
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 field =E2=80=98en= able_msix=E2=80=99
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > spe= cified in ializer
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:376:
> =A0 =A0 =A0 =A0 warning: excess
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 elements in struc= t
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > ini= tializer
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:376:
> =A0 =A0 =A0 =A0 warning: (near
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 initialization fo= r
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =E2= =80=98pci_frontend_op)=E2=80=99
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:377: error:
> =A0 =A0 =A0 =A0 unknown
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 field =E2=80=98di= sable_msix=E2=80=99
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > spe= cified intializer
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:377:
> =A0 =A0 =A0 =A0 warning: excess
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 elements in struc= t
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > ini= tializer
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:377:
> =A0 =A0 =A0 =A0 warning: (near
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 initialization fo= r
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =E2= =80=98pci_frontend_op)=E2=80=99
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c: In function
> =A0 =A0 =A0 =A0 =E2
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =80=98pci_fronten= d_registrar=E2=80=99:
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:383: error:
> =A0 =A0 =A0 =A0 =E2
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =80=98xen_pci_fro= ntend=E2=80=99 undeclared
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > (fi= rst use his function)
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:383: error:
> =A0 =A0 =A0 =A0 (Each
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 undeclared identi= fier is
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > rep= orted only once
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:383: error:
> =A0 =A0 =A0 =A0 for each
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 function it appea= rs in.)
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > mak= e[2]: ***
> =A0 =A0 =A0 =A0 [drivers/pci/xen-pcifront.o] Error 1
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > mak= e[1]: *** [drivers/pci] Error 2
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > mak= e: *** [drivers] Error 2
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > Kin= dly let me know how to proceed on
> =A0 =A0 =A0 =A0 this.
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > Tha= nks
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> --
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> Best reg= ards,
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> =A0Sande= r
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0mailto:linux@eikelenboom.it
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 --
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Best regards,
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Sander
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0mailto:linux@eikelenboom.it
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 >
>
>
>
>

--000e0cd109568180de0481d71a02-- --===============1131156903== 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 --===============1131156903==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ritu kaur Subject: Re: domU guest for xcp 0.1.1 Date: Mon, 15 Mar 2010 19:04:54 -0700 Message-ID: <29b32d341003151904m2a992be5s74697d6047b864c6@mail.gmail.com> References: <29b32d341003120910l5340bc01tcada3ca2adbaf763@mail.gmail.com> <112460240.20100314121540@eikelenboom.it> <29b32d341003141329v3c6a73c0y8030cf3c6736634c@mail.gmail.com> <1056770753.20100314215224@eikelenboom.it> <29b32d341003141840x5a55e74sfb2eda56005e4f84@mail.gmail.com> <29b32d341003142030p1fe511d2ke30b8483ff8cc368@mail.gmail.com> <1268642688.8652.2792.camel@localhost.localdomain> <29b32d341003150642o4e2620edsf154b19d78aa7f42@mail.gmail.com> <1268660645.10129.25070.camel@zakaz.uk.xensource.com> <29b32d341003150646o4d215dfel1c2a2bc6d287edc@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0242862634==" Return-path: In-Reply-To: <29b32d341003150646o4d215dfel1c2a2bc6d287edc@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: Ian Campbell Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org --===============0242862634== Content-Type: multipart/alternative; boundary=000e0cd1b7fc7e85d70481e16cb1 --000e0cd1b7fc7e85d70481e16cb1 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Thanks Ian and Pasi, it took me much less time than I had thought to fix drivers and I am able to see nic interfaces via ifconfig. I am yet to test ping and other stuff. Had couple of questions 1. I used xe vm-param-clear uuid=3D param-name=3Dother-config o= n dom0 and rebooted domU assuming dom0 will get back pci device. It didn't. I had to reboot dom0 in order to unhook pci device from domU. Is this the way it is supposed to work? 2. Unrelated to pci passthrough, xen/stable code I downloaded doesn't seem to have netfront drivers or any front drivers, doesn't it come by default when you download from xen/stable? Thanks On Mon, Mar 15, 2010 at 6:46 AM, Ritu kaur wrote: > Thanks Ian, I will take a look at it. > > > On Mon, Mar 15, 2010 at 6:44 AM, Ian Campbell wr= ote: > >> On Mon, 2010-03-15 at 13:42 +0000, Ritu kaur wrote: >> > Hi Ian, >> > >> > Thanks. Should I use DDK to compile my drivers? I have pci device >> > listed in domU and drivers are not compilable there hence wondering >> > how do I use the it? >> >> You must compile your driver against the kernel used in the domU. This >> is not a Xen specific requirement -- you must always compile your driver >> against the kernel you want to use it with. Note that this may involve >> porting your driver to work with the kernel you are using in your domU. >> >> Ian. >> >> > >> > Thanks >> > >> > On Mon, Mar 15, 2010 at 1:44 AM, Ian Campbell >> > wrote: >> > On Mon, 2010-03-15 at 03:30 +0000, Ritu kaur wrote: >> > > Just to add, this driver compiles fine in other linux >> > flavors(Debian >> > > Lenny 5.0, Citrix Xenserver...) so it has to do with >> > Xen/stable. >> > > Didn't see anything related to this in xen-devel, inputs >> > appreciated. >> > >> > >> > This is because the pvops kernel is based on a much newer >> > upstream >> > kernel (2.6.31 or 32) than that found in Lenny (2.6.26) or >> > Citrix >> > XenServer (2.6.18/27) and some of the kernel's internal >> > interfaces must >> > have changed. >> > >> > This has nothing to do with Xen per-se but rather >> > compatibility with >> > different Linux kernels. >> > >> > Ian. >> > >> > >> > > >> > > Thanks >> > > >> > > On Sun, Mar 14, 2010 at 6:40 PM, Ritu kaur >> > >> > > wrote: >> > > Hi Pasi, >> > > >> > > I am able to use xen/stable kernel in domU(debian >> > lenny) and >> > > lspci lists the device(i am testing pci >> > passthrough). however, >> > > when I compile my driver in domU I get >> > > >> > > struct net_device has no member named open >> > > struct net_device has no member named stop >> > > struct net_device has no member named >> > hard_start_xmit >> > > ... >> > > >> > > I need to compile my driver in domU and load it in >> > order to >> > > use the nic from domU. Inputs appreciated. >> > > >> > > Thanks >> > > >> > > >> > > >> > > On Sun, Mar 14, 2010 at 1:52 PM, Sander Eikelenboom >> > > wrote: >> > > Hello Ritu, >> > > >> > > I don't have experience with XCP >> > specifically, but >> > > normal compiled pvops-kernels work fine for >> > me with >> > > Debian lenny domU's. >> > > >> > > -- >> > > Sander >> > > >> > > >> > > Sunday, March 14, 2010, 9:29:29 PM, you >> > wrote: >> > > >> > > > Hi Sander, >> > > >> > > > Thanks, I enabled DOM0 and other backend >> > drivers >> > > along with pci frontend in >> > > > .config file. I am able to get it build. >> > However, I >> > > having additional >> > > > questions, inputs appreciated. >> > > >> > > > 1. can this kernel be used in any linux >> > > distribution? I have Debian Lenny as >> > > > DomU? >> > > >> > > > 2. In Debian Lenny /boot/grub/menu.lst, I >> > have >> > > > title Debian GNU/Linux, kernel >> > > 2.6.26-2-686-bigmem >> > > > root (hd0,0) >> > > > kernel >> > /boot/vmlinuz-2.6.26-2-686-bigmem >> > > root=3D/dev/xvda1 ro >> > > > console=3Dhvc0 quiet >> > > > initrd >> > /boot/initrd.img-2.6.26-2-686-bigmem >> > > >> > > > but the kernel image built in >> > arch/i386/boot is >> > > bzImage. Does "make >> > > > modules_install" and "make install" take >> > care of it, >> > > since I am not sure I >> > > > haven't tried it. >> > > >> > > > Basically, my question boils down to >> > > >> > > > 1. Can I use bzImage in debian lenny, >> > > > 2. does make install take care of >> > configuring it >> > > >> > > >> > > > Thanks >> > > >> > > > On Sun, Mar 14, 2010 at 4:15 AM, Sander >> > Eikelenboom >> > > wrote: >> > > >> > > >> Hello Ritu, >> > > >> >> > > >> There are some problems with pci.h, i >> > have also >> > > reported this to Konrad. >> > > >> As a workaround you can enable dom0 >> > support in >> > > these kernels, then they >> > > >> compile fine in my case. >> > > >> >> > > >> -- >> > > >> >> > > >> Sander >> > > >> >> > > >> >> > > >> Sunday, March 14, 2010, 2:43:23 AM, you >> > wrote: >> > > >> >> > > >> > I followed the steps mentioned in wiki >> > to pull >> > > xen code to compile domU >> > > >> > kernel from >> > > >> >> > > >> > 1. xen/master, I get following >> > compilation >> > > errors. I do see in xen-devel >> > > >> > forum someone else has reported similar >> > issue but >> > > no solution yet(patch >> > > >> > provided by Konrad has followup errors) >> > > >> >> > > >> > CC [M] drivers/watchdog/machzwd.o >> > > >> > CC [M] drivers/watchdog/sbc_epx_c3.o >> > > >> > CC [M] drivers/watchdog/softdog.o >> > > >> > CC drivers/xen/grant-table.o >> > > >> > CC drivers/xen/features.o >> > > >> > CC drivers/xen/events.o >> > > >> > drivers/xen/events.c:605: error: >> > redefinition of >> > > =E2=80=98xen_destroy_irq=E2=80=99 >> > > >> >> > > >> > > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29= : >> error: >> > > >> > previous definition of =E2 >> > =80=98xen_destroy_irq=E2=80=99 was >> > > here >> > > >> > drivers/xen/events.c:637: error: >> > redefinition of >> > > =E2=80=98xen_create_msi_irq=E2=80=99 >> > > >> >> > > >> > > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25= : >> error: >> > > >> > previous definition of =E2 >> > =80=98xen_create_msi_irq=E2=80=99 >> > > was here >> > > >> > make[2]: *** [drivers/xen/events.o] >> > Error 1 >> > > >> > make[1]: *** [drivers/xen] Error 2 >> > > >> > make: *** [drivers] Error 2 >> > > >> >> > > >> > 2. xen/stable, I get following errors >> > > >> >> > > >> > CC drivers/pci/xen-pcifront.o >> > > >> > drivers/pci/xen-pcifront.c:373: error: >> > variable =E2 >> > > =80=98pci_frontend_ops=E2=80=99 >> > > >> has >> > > >> > initializut incomplete type >> > > >> > drivers/pci/xen-pcifront.c:374: error: >> > unknown >> > > field =E2=80=98enable_msi=E2=80=99 >> > > >> > specified in ializer >> > > >> > drivers/pci/xen-pcifront.c:374: >> > warning: excess >> > > elements in struct >> > > >> > initializer >> > > >> > drivers/pci/xen-pcifront.c:374: >> > warning: (near >> > > initialization for >> > > >> > =E2=80=98pci_frontend_op)=E2=80=99 >> > > >> > drivers/pci/xen-pcifront.c:375: error: >> > unknown >> > > field =E2=80=98disable_msi=E2=80=99 >> > > >> > specified in ializer >> > > >> > drivers/pci/xen-pcifront.c:375: >> > warning: excess >> > > elements in struct >> > > >> > initializer >> > > >> > drivers/pci/xen-pcifront.c:375: >> > warning: (near >> > > initialization for >> > > >> > =E2=80=98pci_frontend_op)=E2=80=99 >> > > >> > drivers/pci/xen-pcifront.c:376: error: >> > unknown >> > > field =E2=80=98enable_msix=E2=80=99 >> > > >> > specified in ializer >> > > >> > drivers/pci/xen-pcifront.c:376: >> > warning: excess >> > > elements in struct >> > > >> > initializer >> > > >> > drivers/pci/xen-pcifront.c:376: >> > warning: (near >> > > initialization for >> > > >> > =E2=80=98pci_frontend_op)=E2=80=99 >> > > >> > drivers/pci/xen-pcifront.c:377: error: >> > unknown >> > > field =E2=80=98disable_msix=E2=80=99 >> > > >> > specified intializer >> > > >> > drivers/pci/xen-pcifront.c:377: >> > warning: excess >> > > elements in struct >> > > >> > initializer >> > > >> > drivers/pci/xen-pcifront.c:377: >> > warning: (near >> > > initialization for >> > > >> > =E2=80=98pci_frontend_op)=E2=80=99 >> > > >> > drivers/pci/xen-pcifront.c: In function >> > =E2 >> > > =80=98pci_frontend_registrar=E2=80=99: >> > > >> > drivers/pci/xen-pcifront.c:383: error: >> > =E2 >> > > =80=98xen_pci_frontend=E2=80=99 undeclared >> > > >> > (first use his function) >> > > >> > drivers/pci/xen-pcifront.c:383: error: >> > (Each >> > > undeclared identifier is >> > > >> > reported only once >> > > >> > drivers/pci/xen-pcifront.c:383: error: >> > for each >> > > function it appears in.) >> > > >> > make[2]: *** >> > [drivers/pci/xen-pcifront.o] Error 1 >> > > >> > make[1]: *** [drivers/pci] Error 2 >> > > >> > make: *** [drivers] Error 2 >> > > >> >> > > >> > Kindly let me know how to proceed on >> > this. >> > > >> >> > > >> > Thanks >> > > >> >> > > >> >> > > >> >> > > >> -- >> > > >> Best regards, >> > > >> Sander >> > > mailto:linux@eikelenboom.it >> > > >> >> > > >> >> > > >> > > >> > > >> > > >> > > -- >> > > >> > > Best regards, >> > > Sander >> > > mailto:linux@eikelenboom.it >> > > >> > > >> > > >> > > >> > > >> > >> > >> > >> > >> >> >> > --000e0cd1b7fc7e85d70481e16cb1 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Thanks Ian and Pasi, it took me much less time than I had thought to fix dr= ivers and I am able to see nic interfaces via ifconfig. I am yet to test pi= ng and other stuff. Had couple of questions

1. I used xe vm-param-cl= ear uuid=3D<uuid-of-vm> param-name=3Dother-config on dom0 and reboote= d domU assuming dom0 will get back pci device. It didn't. I had to rebo= ot dom0 in order to unhook pci device from domU. Is this the way it is supp= osed to work?

2. Unrelated to pci passthrough, xen/stable code I downloaded doesn'= ;t seem to have netfront drivers or any front drivers, doesn't it come = by default when you download from xen/stable?

Thanks

On Mon, Mar 15, 2010 at 6:46 AM, Ritu kaur <ritu.kaur.us@gmail.com> wrote:

Thanks Ian, I will take a look at it.

=
On Mon, Mar 15, 2010 at 6:44 AM, Ian Campbel= l <Ian.Campbell@citrix.com> wrote:

On Mon, 2010= -03-15 at 13:42 +0000, Ritu kaur wrote:
> Hi Ian,
>
> Thanks. Should I use DDK to compile my drivers? I have pci device
> listed in domU and drivers are not compilable there hence wondering > how do I use the it?

You must compile your driver against the kernel used in the domU. Thi= s
is not a Xen specific requirement -- you must always compile your driver against the kernel you want to use it with. Note that this may involve
porting your driver to work with the kernel you are using in your domU.

Ian.

>
> Thanks
>
> On Mon, Mar 15, 2010 at 1:44 AM, Ian Campbell
> <Ian.C= ampbell@citrix.com> wrote:
> =A0 =A0 =A0 =A0 On Mon, 2010-03-15 at 03:30 +0000, Ritu kaur wrote: > =A0 =A0 =A0 =A0 > Just to add, this driver compiles fine in other l= inux
> =A0 =A0 =A0 =A0 flavors(Debian
> =A0 =A0 =A0 =A0 > Lenny 5.0, Citrix Xenserver...) so it has to do w= ith
> =A0 =A0 =A0 =A0 Xen/stable.
> =A0 =A0 =A0 =A0 > Didn't see anything related to this in xen-de= vel, inputs
> =A0 =A0 =A0 =A0 appreciated.
>
>
> =A0 =A0 =A0 =A0 This is because the pvops kernel is based on a much ne= wer
> =A0 =A0 =A0 =A0 upstream
> =A0 =A0 =A0 =A0 kernel (2.6.31 or 32) than that found in Lenny (2.6.26= ) or
> =A0 =A0 =A0 =A0 Citrix
> =A0 =A0 =A0 =A0 XenServer (2.6.18/27) and some of the kernel's int= ernal
> =A0 =A0 =A0 =A0 interfaces must
> =A0 =A0 =A0 =A0 have changed.
>
> =A0 =A0 =A0 =A0 This has nothing to do with Xen per-se but rather
> =A0 =A0 =A0 =A0 compatibility with
> =A0 =A0 =A0 =A0 different Linux kernels.
>
> =A0 =A0 =A0 =A0 Ian.
>
>
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > Thanks
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > On Sun, Mar 14, 2010 at 6:40 PM, Ritu kaur
> =A0 =A0 =A0 =A0 <= ritu.kaur.us@gmail.com>
> =A0 =A0 =A0 =A0 > wrote:
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 Hi Pasi,
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 I am able to use xen/stable kerne= l in domU(debian
> =A0 =A0 =A0 =A0 lenny) and
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 lspci lists the device(i am testi= ng pci
> =A0 =A0 =A0 =A0 passthrough). however,
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 when I compile my driver in domU = I get
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 struct net_device has no member n= amed open
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 struct net_device has no member n= amed stop
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 struct net_device has no member n= amed
> =A0 =A0 =A0 =A0 hard_start_xmit
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 ...
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 I need to compile my driver in do= mU and load it in
> =A0 =A0 =A0 =A0 order to
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 use the nic from domU. Inputs app= reciated.
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 Thanks
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 On Sun, Mar 14, 2010 at 1:52 PM, = Sander Eikelenboom
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 <linux@eikelenboom.it> wrote:
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Hello Ritu,
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 I don't have = experience with XCP
> =A0 =A0 =A0 =A0 specifically, but
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 normal compiled p= vops-kernels work fine for
> =A0 =A0 =A0 =A0 me with
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Debian lenny domU= 's.
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 --
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Sander
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Sunday, March 14,= 2010, 9:29:29 PM, you
> =A0 =A0 =A0 =A0 wrote:
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > Hi Sander, > =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > Thanks, I en= abled DOM0 and other backend
> =A0 =A0 =A0 =A0 drivers
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 along with pci fr= ontend in
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > .config file= . I am able to get it build.
> =A0 =A0 =A0 =A0 However, I
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 having additional=
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > questions, i= nputs appreciated.
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > 1. can this = kernel be used in any linux
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 distribution? I h= ave Debian Lenny as
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > DomU?
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > 2. In Debian= Lenny /boot/grub/menu.lst, I
> =A0 =A0 =A0 =A0 have
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > title =A0 = =A0 =A0 =A0 =A0 Debian GNU/Linux, kernel
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 2.6.26-2-686-bigm= em
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > root =A0 =A0= =A0 =A0 =A0 =A0(hd0,0)
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > kernel
> =A0 =A0 =A0 =A0 =A0/boot/vmlinuz-2.6.26-2-686-bigmem
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 root=3D/dev/xvda1= ro
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > console=3Dhv= c0 quiet
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > initrd
> =A0 =A0 =A0 =A0 =A0/boot/initrd.img-2.6.26-2-686-bigmem
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > but the kern= el image built in
> =A0 =A0 =A0 =A0 arch/i386/boot is
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 bzImage. Does &qu= ot;make
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > modules_inst= all" and "make install" take
> =A0 =A0 =A0 =A0 care of it,
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 since I am not su= re I
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > haven't = tried it.
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > Basically, m= y question boils down to
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > 1. Can I use= bzImage in debian lenny,
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > 2. does make= install take care of
> =A0 =A0 =A0 =A0 configuring it
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > Thanks
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > On Sun, Mar = 14, 2010 at 4:15 AM, Sander
> =A0 =A0 =A0 =A0 Eikelenboom
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <linux@eikelenboom.it>wr= ote:
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> Hello Ri= tu,
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> There ar= e some problems with pci.h, i
> =A0 =A0 =A0 =A0 have also
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 reported this to = Konrad.
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> As a wor= karound you can enable dom0
> =A0 =A0 =A0 =A0 support in
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 these kernels, th= en they
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> compile = fine in my case.
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> --
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> Sander > =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> Sunday, = March 14, 2010, 2:43:23 AM, you
> =A0 =A0 =A0 =A0 wrote:
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > I f= ollowed the steps mentioned in =A0wiki
> =A0 =A0 =A0 =A0 to pull
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 xen code to compi= le domU
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > ker= nel from
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > 1. = xen/master, I get following
> =A0 =A0 =A0 =A0 compilation
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 errors. I do see = in xen-devel
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > for= um someone else has reported similar
> =A0 =A0 =A0 =A0 issue but
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 no solution yet(p= atch
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > pro= vided by Konrad has followup errors)
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > CC = [M] =A0drivers/watchdog/machzwd.o
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =A0= CC [M] =A0drivers/watchdog/sbc_epx_c3.o
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =A0= CC [M] =A0drivers/watchdog/softdog.o
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =A0= CC =A0 =A0 =A0drivers/xen/grant-table.o
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =A0= CC =A0 =A0 =A0drivers/xen/features.o
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =A0= CC =A0 =A0 =A0drivers/xen/events.o
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/xen/events.c:605: error:
> =A0 =A0 =A0 =A0 redefinition of
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =E2=80=98xen_dest= roy_irq=E2=80=99
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > /root/kernel/linux.2-6.xen/arch/x86/include/asm/x= en/pci.h:29: error:
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > pre= vious definition of =E2
> =A0 =A0 =A0 =A0 =80=98xen_destroy_irq=E2=80=99 was
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 here
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/xen/events.c:637: error:
> =A0 =A0 =A0 =A0 redefinition of
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =E2=80=98xen_crea= te_msi_irq=E2=80=99
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > /root/kernel/linux.2-6.xen/arch/x86/include/asm/x= en/pci.h:25: error:
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > pre= vious definition of =E2
> =A0 =A0 =A0 =A0 =80=98xen_create_msi_irq=E2=80=99
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 was here
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > mak= e[2]: *** [drivers/xen/events.o]
> =A0 =A0 =A0 =A0 Error 1
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > mak= e[1]: *** [drivers/xen] Error 2
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > mak= e: *** [drivers] Error 2
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > 2. = xen/stable, I get following errors
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =A0= CC =A0 =A0 =A0drivers/pci/xen-pcifront.o
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:373: error:
> =A0 =A0 =A0 =A0 variable =E2
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =80=98pci_fronten= d_ops=E2=80=99
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> has
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > ini= tializut incomplete type
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:374: error:
> =A0 =A0 =A0 =A0 unknown
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 field =E2=80=98en= able_msi=E2=80=99
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > spe= cified in ializer
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:374:
> =A0 =A0 =A0 =A0 warning: excess
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 elements in struc= t
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > ini= tializer
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:374:
> =A0 =A0 =A0 =A0 warning: (near
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 initialization fo= r
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =E2= =80=98pci_frontend_op)=E2=80=99
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:375: error:
> =A0 =A0 =A0 =A0 unknown
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 field =E2=80=98di= sable_msi=E2=80=99
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > spe= cified in ializer
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:375:
> =A0 =A0 =A0 =A0 warning: excess
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 elements in struc= t
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > ini= tializer
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:375:
> =A0 =A0 =A0 =A0 warning: (near
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 initialization fo= r
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =E2= =80=98pci_frontend_op)=E2=80=99
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:376: error:
> =A0 =A0 =A0 =A0 unknown
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 field =E2=80=98en= able_msix=E2=80=99
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > spe= cified in ializer
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:376:
> =A0 =A0 =A0 =A0 warning: excess
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 elements in struc= t
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > ini= tializer
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:376:
> =A0 =A0 =A0 =A0 warning: (near
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 initialization fo= r
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =E2= =80=98pci_frontend_op)=E2=80=99
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:377: error:
> =A0 =A0 =A0 =A0 unknown
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 field =E2=80=98di= sable_msix=E2=80=99
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > spe= cified intializer
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:377:
> =A0 =A0 =A0 =A0 warning: excess
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 elements in struc= t
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > ini= tializer
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:377:
> =A0 =A0 =A0 =A0 warning: (near
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 initialization fo= r
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =E2= =80=98pci_frontend_op)=E2=80=99
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c: In function
> =A0 =A0 =A0 =A0 =E2
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =80=98pci_fronten= d_registrar=E2=80=99:
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:383: error:
> =A0 =A0 =A0 =A0 =E2
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =80=98xen_pci_fro= ntend=E2=80=99 undeclared
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > (fi= rst use his function)
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:383: error:
> =A0 =A0 =A0 =A0 (Each
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 undeclared identi= fier is
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > rep= orted only once
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > dri= vers/pci/xen-pcifront.c:383: error:
> =A0 =A0 =A0 =A0 for each
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 function it appea= rs in.)
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > mak= e[2]: ***
> =A0 =A0 =A0 =A0 [drivers/pci/xen-pcifront.o] Error 1
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > mak= e[1]: *** [drivers/pci] Error 2
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > mak= e: *** [drivers] Error 2
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > Kin= dly let me know how to proceed on
> =A0 =A0 =A0 =A0 this.
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > Tha= nks
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> --
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> Best reg= ards,
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> =A0Sande= r
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0mailto:linux@eikelenboom.it=
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 --
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Best regards,
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Sander
> =A0 =A0 =A0 =A0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0mailto:linux@eikelenboom.it=
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 >
> =A0 =A0 =A0 =A0 >
>
>
>
>

--000e0cd1b7fc7e85d70481e16cb1-- --===============0242862634== 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 --===============0242862634==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: domU guest for xcp 0.1.1 Date: Tue, 16 Mar 2010 07:37:49 +0000 Message-ID: <1268725069.8652.4179.camel@localhost.localdomain> References: <29b32d341003120910l5340bc01tcada3ca2adbaf763@mail.gmail.com> <112460240.20100314121540@eikelenboom.it> <29b32d341003141329v3c6a73c0y8030cf3c6736634c@mail.gmail.com> <1056770753.20100314215224@eikelenboom.it> <29b32d341003141840x5a55e74sfb2eda56005e4f84@mail.gmail.com> <29b32d341003142030p1fe511d2ke30b8483ff8cc368@mail.gmail.com> <1268642688.8652.2792.camel@localhost.localdomain> <29b32d341003150642o4e2620edsf154b19d78aa7f42@mail.gmail.com> <1268660645.10129.25070.camel@zakaz.uk.xensource.com> <29b32d341003150646o4d215dfel1c2a2bc6d287edc@mail.gmail.com> <29b32d341003151904m2a992be5s74697d6047b864c6@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <29b32d341003151904m2a992be5s74697d6047b864c6@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: Ritu kaur Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Tue, 2010-03-16 at 02:04 +0000, Ritu kaur wrote: > Thanks Ian and Pasi, it took me much less time than I had thought to > fix drivers and I am able to see nic interfaces via ifconfig. I am yet > to test ping and other stuff. Had couple of questions > > 1. I used xe vm-param-clear uuid= param-name=other-config > on dom0 and rebooted domU assuming dom0 will get back pci device. It > didn't. I had to reboot dom0 in order to unhook pci device from domU. > Is this the way it is supposed to work? Aside: you need "param-key=pci" in the above or I think you will clear all keys in other-config which is unlikely to be what you want. You could also have used vm-param-set other-config:pci="". The NIC will remain bound to the pciback driver until you explicitly unbind it and rebind to another driver in domain 0 and won't be available until you do this. You can rebind the driver echo'ing the PCI BDF of the device into the "unbind" and "bind" nodes under the appropriate drivers in sysfs. e.g. for pcidev=0000:00:08.0: echo -n "$pcidev" > /sys/bus/pci/devices/"$pcidev"/driver/unbind echo -n "$pcidev" > /sys/bus/pci/drivers/$mydriver/bind > 2. Unrelated to pci passthrough, xen/stable code I downloaded doesn't > seem to have netfront drivers or any front drivers, doesn't it come by > default when you download from xen/stable? It should do. The modules have different names though, xen-netfront and xen-blkfront IIRC. Ian. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: domU guest for xcp 0.1.1 Date: Tue, 16 Mar 2010 17:23:00 +0200 Message-ID: <20100316152259.GO1878@reaktio.net> References: <29b32d341003141329v3c6a73c0y8030cf3c6736634c@mail.gmail.com> <1056770753.20100314215224@eikelenboom.it> <29b32d341003141840x5a55e74sfb2eda56005e4f84@mail.gmail.com> <29b32d341003142030p1fe511d2ke30b8483ff8cc368@mail.gmail.com> <1268642688.8652.2792.camel@localhost.localdomain> <29b32d341003150642o4e2620edsf154b19d78aa7f42@mail.gmail.com> <1268660645.10129.25070.camel@zakaz.uk.xensource.com> <29b32d341003150646o4d215dfel1c2a2bc6d287edc@mail.gmail.com> <29b32d341003151904m2a992be5s74697d6047b864c6@mail.gmail.com> <1268725069.8652.4179.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1268725069.8652.4179.camel@localhost.localdomain> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Campbell Cc: Ritu kaur , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Tue, Mar 16, 2010 at 07:37:49AM +0000, Ian Campbell wrote: > > > 2. Unrelated to pci passthrough, xen/stable code I downloaded doesn't > > seem to have netfront drivers or any front drivers, doesn't it come by > > default when you download from xen/stable? > > It should do. The modules have different names though, xen-netfront and > xen-blkfront IIRC. > Also make sure you have the correct 'requirements' enabled in the .config, xen options won't show up in menuconfig until you have the correct cpu type chosen, PAE enabled (if building 32bit kernel), ACPI enabled etc.. -- Pasi From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ritu kaur Subject: Re: domU guest for xcp 0.1.1 Date: Tue, 16 Mar 2010 16:25:17 -0700 Message-ID: <29b32d341003161625w2969f2daib3408561920793d3@mail.gmail.com> References: <29b32d341003141329v3c6a73c0y8030cf3c6736634c@mail.gmail.com> <29b32d341003141840x5a55e74sfb2eda56005e4f84@mail.gmail.com> <29b32d341003142030p1fe511d2ke30b8483ff8cc368@mail.gmail.com> <1268642688.8652.2792.camel@localhost.localdomain> <29b32d341003150642o4e2620edsf154b19d78aa7f42@mail.gmail.com> <1268660645.10129.25070.camel@zakaz.uk.xensource.com> <29b32d341003150646o4d215dfel1c2a2bc6d287edc@mail.gmail.com> <29b32d341003151904m2a992be5s74697d6047b864c6@mail.gmail.com> <1268725069.8652.4179.camel@localhost.localdomain> <20100316152259.GO1878@reaktio.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0264597520==" Return-path: In-Reply-To: <20100316152259.GO1878@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: "xen-devel@lists.xensource.com" , Ian Campbell List-Id: xen-devel@lists.xenproject.org --===============0264597520== Content-Type: multipart/alternative; boundary=000e0cd17e7c7ab6030481f34f46 --000e0cd17e7c7ab6030481f34f46 Content-Type: text/plain; charset=ISO-8859-1 Thanks Pasi. Back to pci passthrough debugging. I enabled nic interface via ifconfig and it doesn't receive any interrupts. Driver in domU experiences tx timeout and if I try to write to a disk in domU(i.e cat /proc/interrupts > /root/debugs) system never recovers. From dom0 cannot execute reboot/shutdown... have to use magic way to reboot the system. I looked into xen-devel forum for any possible soln(patch mentioned in the forum are all present in xen code I have). Inputs appreciated. 1. when dom0 is booted, device has irq 11 assigned lspci -v on dom0 Ethernet controller: Unknown device dead:face Subsystem: Unknown device dead:face Flags: bus master, medium devsel, latency 32, IRQ 11 Memory at d0000000 (32-bit, non-prefetchable) [size=128M] 2. After domU boots up, irq is reassigned to 17 and it shares with usb/ide disk and other devices lspci -v on dom0 Ethernet controller: Unknown device dead:face Subsystem: Unknown device dead:face Flags: bus master, medium devsel, latency 32, IRQ 17 Memory at d0000000 (32-bit, non-prefetchable) [size=128M] lspci -v on domU 00:00.0 Ethernet controller: Device dead:face Subsystem: Device dead:face Flags: bus master, medium devsel, latency 32, IRQ 17 Memory at d0000000 (32-bit, non-prefetchable) [size=128M] Kernel driver in use: ncr2f Kernel modules: ncr2f cat /proc/interrupts from domU # cat /proc/interrupts CPU0 17: 0 xen-pirq-pcifront ncr2f0 502: 6336 xen-dyn-event eth0 503: 2951 xen-dyn-event blkif 504: 105 xen-dyn-event hvc_console 505: 52 xen-dyn-event pcifront 506: 351 xen-dyn-event xenbus 507: 0 xen-dyn-ipi callfuncsingle0 508: 0 xen-dyn-virq debug0 509: 0 xen-dyn-ipi callfunc0 510: 0 xen-dyn-ipi resched0 511: 5949 xen-dyn-virq timer0 NMI: 0 Non-maskable interrupts LOC: 0 Local timer interrupts SPU: 0 Spurious interrupts PMI: 0 Performance monitoring interrupts PND: 0 Performance pending work RES: 0 Rescheduling interrupts CAL: 0 Function call interrupts TLB: 0 TLB shootdowns TRM: 0 Thermal event interrupts THR: 0 Threshold APIC interrupts MCE: 0 Machine check exceptions MCP: 0 Machine check polls ERR: 0 MIS: 0 After around 50 secs... # cat /proc/interrupts CPU0 17: 0 xen-pirq-pcifront ncr2f0 502: 7283 xen-dyn-event eth0 503: 2951 xen-dyn-event blkif 504: 121 xen-dyn-event hvc_console 505: 52 xen-dyn-event pcifront 506: 351 xen-dyn-event xenbus 507: 0 xen-dyn-ipi callfuncsingle0 508: 0 xen-dyn-virq debug0 509: 0 xen-dyn-ipi callfunc0 510: 0 xen-dyn-ipi resched0 511: 6237 xen-dyn-virq timer0 NMI: 0 Non-maskable interrupts LOC: 0 Local timer interrupts SPU: 0 Spurious interrupts PMI: 0 Performance monitoring interrupts PND: 0 Performance pending work RES: 0 Rescheduling interrupts CAL: 0 Function call interrupts TLB: 0 TLB shootdowns TRM: 0 Thermal event interrupts THR: 0 Threshold APIC interrupts MCE: 0 Machine check exceptions MCP: 0 Machine check polls ERR: 0 MIS: 0 --000e0cd17e7c7ab6030481f34f46 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: base64 VGhhbmtzIFBhc2kuIEJhY2sgdG8gcGNpIHBhc3N0aHJvdWdoIGRlYnVnZ2luZy48YnI+PGJyPkkg ZW5hYmxlZCBuaWMgaW50ZXJmYWNlIHZpYSBpZmNvbmZpZyBhbmQgaXQgZG9lc24mIzM5O3QgcmVj ZWl2ZSBhbnkgaW50ZXJydXB0cy4gRHJpdmVyIGluIGRvbVUgZXhwZXJpZW5jZXMgdHggdGltZW91 dKAgYW5kIGlmIEkgdHJ5IHRvIHdyaXRlIHRvIGEgZGlzayBpbiBkb21VKGkuZSBjYXQgL3Byb2Mv aW50ZXJydXB0cyAmZ3Q7IC9yb290L2RlYnVncykgc3lzdGVtIG5ldmVyIHJlY292ZXJzLiBGcm9t IGRvbTAgY2Fubm90IGV4ZWN1dGUgcmVib290L3NodXRkb3duLi4uIGhhdmUgdG8gdXNlIG1hZ2lj IHdheSB0byByZWJvb3QgdGhlIHN5c3RlbS4gSSBsb29rZWQgaW50byB4ZW4tZGV2ZWwgZm9ydW0g Zm9yIGFueSBwb3NzaWJsZSBzb2xuKHBhdGNoIG1lbnRpb25lZCBpbiB0aGUgZm9ydW0gYXJlIGFs bCBwcmVzZW50IGluIHhlbiBjb2RlIEkgaGF2ZSkuIElucHV0cyBhcHByZWNpYXRlZC48YnI+Cjxi cj4xLiB3aGVuIGRvbTAgaXMgYm9vdGVkLCBkZXZpY2UgaGFzIGlycSAxMSBhc3NpZ25lZDxicj48 YnI+bHNwY2kgLXYgb24gZG9tMDxicj48YnI+oEV0aGVybmV0IGNvbnRyb2xsZXI6IFVua25vd24g ZGV2aWNlIGRlYWQ6ZmFjZTxicj6goKCgoKCgIFN1YnN5c3RlbTogVW5rbm93biBkZXZpY2UgZGVh ZDpmYWNlPGJyPqCgoKCgoKAgRmxhZ3M6IGJ1cyBtYXN0ZXIsIG1lZGl1bSBkZXZzZWwsIGxhdGVu Y3kgMzIsIElSUSAxMTxicj4KoKCgoKCgoCBNZW1vcnkgYXQgZDAwMDAwMDAgKDMyLWJpdCwgbm9u LXByZWZldGNoYWJsZSkgW3NpemU9MTI4TV08YnI+PGJyPjIuIEFmdGVyIGRvbVUgYm9vdHMgdXAs IGlycSBpcyByZWFzc2lnbmVkIHRvIDE3IGFuZCBpdCBzaGFyZXMgd2l0aCB1c2IvaWRlIGRpc2sg YW5kIG90aGVyIGRldmljZXM8YnI+bHNwY2kgLXYgb24gZG9tMDxicj48YnI+oEV0aGVybmV0IGNv bnRyb2xsZXI6IFVua25vd24gZGV2aWNlIGRlYWQ6ZmFjZTxicj4KCqCgoKCgoKAgU3Vic3lzdGVt OiBVbmtub3duIGRldmljZSBkZWFkOmZhY2U8YnI+CqCgoKCgoKAgRmxhZ3M6IGJ1cyBtYXN0ZXIs IG1lZGl1bSBkZXZzZWwsIGxhdGVuY3kgMzIsIElSUSAxNzxicj4KoKCgoKCgoCBNZW1vcnkgYXQg ZDAwMDAwMDAgKDMyLWJpdCwgbm9uLXByZWZldGNoYWJsZSkgW3NpemU9MTI4TV08YnI+PGJyPmxz cGNpIC12IG9uIGRvbVU8YnI+PGJyPjAwOjAwLjAgRXRoZXJuZXQgY29udHJvbGxlcjogRGV2aWNl IGRlYWQ6ZmFjZTxicj6goKCgoKCgIFN1YnN5c3RlbTogRGV2aWNlIGRlYWQ6ZmFjZTxicj6goKCg oKCgIEZsYWdzOiBidXMgbWFzdGVyLCBtZWRpdW0gZGV2c2VsLCBsYXRlbmN5IDMyLCBJUlEgMTc8 YnI+CqCgoKCgoKAgTWVtb3J5IGF0IGQwMDAwMDAwICgzMi1iaXQsIG5vbi1wcmVmZXRjaGFibGUp IFtzaXplPTEyOE1dPGJyPqCgoKCgoKAgS2VybmVsIGRyaXZlciBpbiB1c2U6IG5jcjJmPGJyPqCg oKCgoKAgS2VybmVsIG1vZHVsZXM6IG5jcjJmPGJyPjxicj5jYXQgL3Byb2MvaW50ZXJydXB0cyBm cm9tIGRvbVU8YnI+PGJyPiMgY2F0IC9wcm9jL2ludGVycnVwdHMgPGJyPqCgoKCgoKCgoKAgQ1BV MKCgoKCgoCA8YnI+CqAxNzqgoKCgoKCgoKAgMKAgeGVuLXBpcnEtcGNpZnJvbnSgIG5jcjJmMDxi cj41MDI6oKCgoKCgIDYzMzagoCB4ZW4tZHluLWV2ZW50oKCgoCBldGgwPGJyPjUwMzqgoKCgoKAg Mjk1MaCgIHhlbi1keW4tZXZlbnSgoKCgIGJsa2lmPGJyPjUwNDqgoKCgoKCgIDEwNaCgIHhlbi1k eW4tZXZlbnSgoKCgIGh2Y19jb25zb2xlPGJyPjUwNTqgoKCgoKCgoCA1MqCgIHhlbi1keW4tZXZl bnSgoKCgIHBjaWZyb250PGJyPgo1MDY6oKCgoKCgoCAzNTGgoCB4ZW4tZHluLWV2ZW50oKCgoCB4 ZW5idXM8YnI+NTA3OqCgoKCgoKCgoCAwoKAgeGVuLWR5bi1pcGmgoKCgoKAgY2FsbGZ1bmNzaW5n bGUwPGJyPjUwODqgoKCgoKCgoKAgMKCgIHhlbi1keW4tdmlycaCgoKCgIGRlYnVnMDxicj41MDk6 oKCgoKCgoKCgIDCgoCB4ZW4tZHluLWlwaaCgoKCgoCBjYWxsZnVuYzA8YnI+NTEwOqCgoKCgoKCg oCAwoKAgeGVuLWR5bi1pcGmgoKCgoKAgcmVzY2hlZDA8YnI+CjUxMTqgoKCgoKAgNTk0OaCgIHhl bi1keW4tdmlycaCgoKCgIHRpbWVyMDxicj5OTUk6oKCgoKCgoKCgIDCgoCBOb24tbWFza2FibGUg aW50ZXJydXB0czxicj5MT0M6oKCgoKCgoKCgIDCgoCBMb2NhbCB0aW1lciBpbnRlcnJ1cHRzPGJy PlNQVTqgoKCgoKCgoKAgMKCgIFNwdXJpb3VzIGludGVycnVwdHM8YnI+UE1JOqCgoKCgoKCgoCAw oKAgUGVyZm9ybWFuY2UgbW9uaXRvcmluZyBpbnRlcnJ1cHRzPGJyPgpQTkQ6oKCgoKCgoKCgIDCg oCBQZXJmb3JtYW5jZSBwZW5kaW5nIHdvcms8YnI+UkVTOqCgoKCgoKCgoCAwoKAgUmVzY2hlZHVs aW5nIGludGVycnVwdHM8YnI+Q0FMOqCgoKCgoKCgoCAwoKAgRnVuY3Rpb24gY2FsbCBpbnRlcnJ1 cHRzPGJyPlRMQjqgoKCgoKCgoKAgMKCgIFRMQiBzaG9vdGRvd25zPGJyPlRSTTqgoKCgoKCgoKAg MKCgIFRoZXJtYWwgZXZlbnQgaW50ZXJydXB0czxicj5USFI6oKCgoKCgoKCgIDCgoCBUaHJlc2hv bGQgQVBJQyBpbnRlcnJ1cHRzPGJyPgpNQ0U6oKCgoKCgoKCgIDCgoCBNYWNoaW5lIGNoZWNrIGV4 Y2VwdGlvbnM8YnI+TUNQOqCgoKCgoKCgoCAwoKAgTWFjaGluZSBjaGVjayBwb2xsczxicj5FUlI6 oKCgoKCgoKCgIDA8YnI+TUlTOqCgoKCgoKCgoCAwPGJyPjxicj5BZnRlciBhcm91bmQgNTAgc2Vj cy4uLjxicj48YnI+IyBjYXQgL3Byb2MvaW50ZXJydXB0cyA8YnI+oKCgoKCgoKCgoCBDUFUwoKCg oKCgIDxicj6gMTc6oKCgoKCgoKCgIDCgIHhlbi1waXJxLXBjaWZyb250oCBuY3IyZjA8YnI+CjUw MjqgoKCgoKAgNzI4M6CgIHhlbi1keW4tZXZlbnSgoKCgIGV0aDA8YnI+NTAzOqCgoKCgoCAyOTUx oKAgeGVuLWR5bi1ldmVudKCgoKAgYmxraWY8YnI+NTA0OqCgoKCgoKAgMTIxoKAgeGVuLWR5bi1l dmVudKCgoKAgaHZjX2NvbnNvbGU8YnI+NTA1OqCgoKCgoKCgIDUyoKAgeGVuLWR5bi1ldmVudKCg oKAgcGNpZnJvbnQ8YnI+NTA2OqCgoKCgoKAgMzUxoKAgeGVuLWR5bi1ldmVudKCgoKAgeGVuYnVz PGJyPgo1MDc6oKCgoKCgoKCgIDCgoCB4ZW4tZHluLWlwaaCgoKCgoCBjYWxsZnVuY3NpbmdsZTA8 YnI+NTA4OqCgoKCgoKCgoCAwoKAgeGVuLWR5bi12aXJxoKCgoKAgZGVidWcwPGJyPjUwOTqgoKCg oKCgoKAgMKCgIHhlbi1keW4taXBpoKCgoKCgIGNhbGxmdW5jMDxicj41MTA6oKCgoKCgoKCgIDCg oCB4ZW4tZHluLWlwaaCgoKCgoCByZXNjaGVkMDxicj41MTE6oKCgoKCgIDYyMzegoCB4ZW4tZHlu LXZpcnGgoKCgoCB0aW1lcjA8YnI+Ck5NSTqgoKCgoKCgoKAgMKCgIE5vbi1tYXNrYWJsZSBpbnRl cnJ1cHRzPGJyPkxPQzqgoKCgoKCgoKAgMKCgIExvY2FsIHRpbWVyIGludGVycnVwdHM8YnI+U1BV OqCgoKCgoKCgoCAwoKAgU3B1cmlvdXMgaW50ZXJydXB0czxicj5QTUk6oKCgoKCgoKCgIDCgoCBQ ZXJmb3JtYW5jZSBtb25pdG9yaW5nIGludGVycnVwdHM8YnI+UE5EOqCgoKCgoKCgoCAwoKAgUGVy Zm9ybWFuY2UgcGVuZGluZyB3b3JrPGJyPgpSRVM6oKCgoKCgoKCgIDCgoCBSZXNjaGVkdWxpbmcg aW50ZXJydXB0czxicj5DQUw6oKCgoKCgoKCgIDCgoCBGdW5jdGlvbiBjYWxsIGludGVycnVwdHM8 YnI+VExCOqCgoKCgoKCgoCAwoKAgVExCIHNob290ZG93bnM8YnI+VFJNOqCgoKCgoKCgoCAwoKAg VGhlcm1hbCBldmVudCBpbnRlcnJ1cHRzPGJyPlRIUjqgoKCgoKCgoKAgMKCgIFRocmVzaG9sZCBB UElDIGludGVycnVwdHM8YnI+TUNFOqCgoKCgoKCgoCAwoKAgTWFjaGluZSBjaGVjayBleGNlcHRp b25zPGJyPgpNQ1A6oKCgoKCgoKCgIDCgoCBNYWNoaW5lIGNoZWNrIHBvbGxzPGJyPkVSUjqgoKCg oKCgoKAgMDxicj5NSVM6oKCgoKCgoKCgIDA8YnI+PGJyPgo= --000e0cd17e7c7ab6030481f34f46-- --===============0264597520== 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 --===============0264597520==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ritu kaur Subject: Re: domU guest for xcp 0.1.1 Date: Wed, 17 Mar 2010 11:44:08 -0700 Message-ID: <29b32d341003171144k628a7741x17b6658731f96e4b@mail.gmail.com> References: <29b32d341003141329v3c6a73c0y8030cf3c6736634c@mail.gmail.com> <29b32d341003142030p1fe511d2ke30b8483ff8cc368@mail.gmail.com> <1268642688.8652.2792.camel@localhost.localdomain> <29b32d341003150642o4e2620edsf154b19d78aa7f42@mail.gmail.com> <1268660645.10129.25070.camel@zakaz.uk.xensource.com> <29b32d341003150646o4d215dfel1c2a2bc6d287edc@mail.gmail.com> <29b32d341003151904m2a992be5s74697d6047b864c6@mail.gmail.com> <1268725069.8652.4179.camel@localhost.localdomain> <20100316152259.GO1878@reaktio.net> <29b32d341003161625w2969f2daib3408561920793d3@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1480831413==" Return-path: In-Reply-To: <29b32d341003161625w2969f2daib3408561920793d3@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: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: "xen-devel@lists.xensource.com" , Ian Campbell List-Id: xen-devel@lists.xenproject.org --===============1480831413== Content-Type: multipart/alternative; boundary=000e0cd2de02d9155d0482037f4e --000e0cd2de02d9155d0482037f4e Content-Type: text/plain; charset=ISO-8859-1 Pasi, Ian I debugged this further with the assumption that IRQ follows the path IDT->Hypervisor->pciback->pcifront->actual_device. I added printk message while binding to a event-chnl and event-chnl callback function in pcifront. I do see my printk message(while binding to event-chnl in domU) so I know kernel has correct module. After nic device is enabled via ifconfig in domU, I do not see messages (added in event-chnl callback function) from pcifront so I believe interrupt is not delivered to pcifront itself. static inline void schedule_pcifront_aer_op(struct pcifront_device *pdev) { if (test_bit(_XEN_PCIB_active, (unsigned long *)&pdev->sh_info->flags) && !test_and_set_bit(_PDEVB_op_active, &pdev->flags)) { dev_dbg(&pdev->xdev->dev, "schedule aer frontend job\n"); printk(KERN_DEBUG "schedule aer frontend job %d\n", pdev->irq); <<<<<<< never seen in dmesg in domU schedule_work(&pdev->op_work); } } dmesg on dom0 says "nobody cared...", forum has some old discussions around 2006 and hence didn't look into it in detail. Inputs will be very much appreciated. dmesg in dom0 and domU follows. Thanks /**********************dmesg on dom0***************************************/ pciback 0000:08:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 irq 17: nobody cared (try booting with the "irqpoll" option) Pid: 0, comm: swapper Tainted: G 2.6.27.42-0.1.1.xs0.1.1.737.1065xen #1 [] __report_bad_irq+0x27/0x90 [] note_interrupt+0x2fc/0x330 [] ? usb_hcd_irq+0x4d/0xe0 [usbcore] [] ? handle_IRQ_event+0x31/0x90 [] handle_level_irq+0xe4/0x110 [] do_IRQ+0x43/0x90 [] ? ktime_get+0x19/0x40 [] evtchn_do_upcall+0xdf/0x1f0 [] hypervisor_callback+0x41/0x49 [] ? xen_safe_halt+0x8b/0xc0 [] xen_idle+0x1e/0x50 [] cpu_idle+0x58/0xa0 [] rest_init+0x4e/0x60 ======================= handlers: [] (usb_hcd_irq+0x0/0xe0 [usbcore]) Disabling IRQ #17 ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen ata1.00: cmd ca/00:08:31:08:14/00:00:00:00:00/e0 tag 0 dma 4096 out res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) ata1.00: status: { DRDY } ata1: soft resetting link ata1.00: qc timeout (cmd 0x27) ata1.00: failed to read native max address (err_mask=0x4) ata1.00: revalidation failed (errno=-5) ata1: soft resetting link ata1.00: qc timeout (cmd 0x27) ata1.00: failed to read native max address (err_mask=0x4) ata1.00: revalidation failed (errno=-5) ata1: soft resetting link ata1.00: qc timeout (cmd 0x27) ata1.00: failed to read native max address (err_mask=0x4) ata1.00: revalidation failed (errno=-5) ata1.00: disabled ata1.00: device reported invalid CHS sector 0 ata1: soft resetting link ata1: EH complete sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK end_request: I/O error, dev sda, sector 1312817 Buffer I/O error on device sda1, logical block 164102 lost page write due to I/O error on sda1 /**************************dmesg on domU*********************************************/ [ 5.994657] EXT3 FS on xvda1, internal journal [ 8.431645] loop: module loaded [ 10.043554] NET: Registered protocol family 10 [ 10.044013] lo: Disabled Privacy Extensions [ 11.859410] lp: driver loaded but no devices found [ 11.965333] ppdev: user-space parallel port driver [ 20.076012] eth0: no IPv6 routers present [ 170.192510] ncr 0000:00:00.0: enabling device (0000 -> 0002) [ 170.192551] ncr 0000:00:00.0: Xen PCI enabling IRQ: 17 [ 170.192571] ncr: Found an ncr device (cfg revision 0)... [ 287.816020] ------------[ cut here ]------------ [ 287.816031] WARNING: at net/sched/sch_generic.c:261 dev_watchdog+0xf8/0x188() [ 287.816037] NETDEV WATCHDOG: ncr (): transmit queue 0 timed out [ 287.816041] Modules linked in: ncr ppdev parport_pc lp parport acpi_cpufreq processor cpufreq_powersave cpufreq_stats cpufreq_ondemand freq_table cpufreq_userspace cpufreq_conservative ipv6 loop evdev pcspkr xen_netfront ext3 jbd mbcache xen_blkfront thermal_sys [ 287.816113] Pid: 0, comm: swapper Not tainted 2.6.32.9 #4 [ 287.816118] Call Trace: [ 287.816127] [] ? dev_watchdog+0xf8/0x188 [ 287.816135] [] ? dev_watchdog+0xf8/0x188 [ 287.816143] [] ? warn_slowpath_common+0x5e/0x8a [ 287.816151] [] ? warn_slowpath_fmt+0x26/0x2a [ 287.816159] [] ? dev_watchdog+0xf8/0x188 [ 287.816168] [] ? check_events+0x8/0xc [ 287.816175] [] ? xen_force_evtchn_callback+0xc/0x10 [ 287.816183] [] ? check_events+0x8/0xc [ 287.816191] [] ? xen_restore_fl_direct_end+0x0/0x1 [ 287.816200] [] ? _spin_unlock_irqrestore+0xe/0x10 [ 287.816209] [] ? mod_timer+0x15f/0x168 [ 287.816217] [] ? dev_watchdog+0x0/0x188 [ 287.816224] [] ? run_timer_softirq+0x195/0x217 [ 287.816232] [] ? __do_softirq+0xaa/0x151 [ 287.816240] [] ? do_softirq+0x31/0x3c [ 287.816247] [] ? irq_exit+0x26/0x58 [ 287.816256] [] ? xen_evtchn_do_upcall+0x13f/0x151 [ 287.816264] [] ? xen_do_upcall+0x7/0xc [ 287.816272] [] ? hypercall_page+0x3a7/0x1001 [ 287.816280] [] ? xen_safe_halt+0xf/0x1b [ 287.816287] [] ? xen_idle+0x23/0x30 [ 287.816295] [] ? cpu_idle+0x46/0x62 [ 287.816303] [] ? start_kernel+0x2c7/0x2ca [ 287.816310] [] ? xen_start_kernel+0x5e6/0x5ee [ 287.816315] ---[ end trace 00c16cce2318c073 ]--- [ 287.816320] ncr: Transmit timeout on ncr at 4294964250, latency 583 [ 291.816017] ncr: Transmit timeout on ncr at 4294965250, latency 1000 ... [ 412.673801] end_request: I/O error, dev xvda, sector 7608215 [ 412.673826] end_request: I/O error, dev xvda, sector 7608223 [ 412.673837] end_request: I/O error, dev xvda, sector 7608231 [ 480.052035] INFO: task kjournald:565 blocked for more than 120 seconds. [ 480.052047] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 480.052057] kjournald D 121f1575 0 565 2 0x00000000 [ 480.052069] cf864d80 00000246 c136b7c0 121f1575 c1c25040 c13ce460 c13ce460 cf864f38 [ 480.052091] c26fb460 00000000 5737fa96 00000045 c136b7c0 121f1e2a c1052d6d 6c3e6a53 [ 480.052111] 00000000 121f1e2a 00000000 cf894690 cf864f38 cf864d80 c26fb894 c26fb460 [ 480.052131] Call Trace: [ 480.052143] [] ? ktime_get_ts+0xd7/0xdf [ 480.052154] [] ? io_schedule+0x5f/0x98 [ 480.052162] [] ? sync_buffer+0x30/0x33 [ 480.052169] [] ? __wait_on_bit+0x33/0x58 [ 480.052176] [] ? sync_buffer+0x0/0x33 [ 480.052183] [] ? out_of_line_wait_on_bit+0xb6/0xbe [ 480.052190] [] ? sync_buffer+0x0/0x33 [ 480.052198] [] ? wake_bit_function+0x0/0x3c [ 480.052205] [] ? __wait_on_buffer+0x16/0x18 [ 480.052223] [] ? journal_commit_transaction+0x85a/0xd6d [jbd] [ 480.052235] [] ? finish_task_switch+0x3d/0x9c [ 480.052243] [] ? check_events+0x8/0xc [ 480.052250] [] ? xen_restore_fl_direct_end+0x0/0x1 [ 480.052258] [] ? _spin_unlock_irqrestore+0xe/0x10 [ 480.052267] [] ? try_to_del_timer_sync+0x79/0x80 [ 480.052276] [] ? kjournald+0xbb/0x1e5 [jbd] [ 480.052283] [] ? autoremove_wake_function+0x0/0x2d [ 480.052292] [] ? kjournald+0x0/0x1e5 [jbd] [ 480.052299] [] ? kthread+0x61/0x66 [ 480.052305] [] ? kthread+0x0/0x66 [ 480.052313] [] ? kernel_thread_helper+0x7/0x10 [ 480.052320] INFO: task rsyslogd:1929 blocked for more than 120 seconds. [ 480.052328] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 480.052337] rsyslogd D 00001000 0 1929 1 0x00000000 [ 480.052346] c1c20d40 00000286 d0877650 00001000 c1c25200 c13ce460 c13ce460 c1c20ef8 [ 480.052367] c26fb460 00000000 c1cd5600 c1cf02c0 cf4693ec cf576518 c1005ff4 c26f0a5c [ 480.052387] cf99fd98 cf99fdac c100665c c26f025c c1c20ef8 c26f0a5c cf99fd98 cf99fdac [ 480.052407] Call Trace: [ 480.052418] [] ? __ext3_get_inode_loc+0xc7/0x275 [ext3] [ 480.052426] [] ? xen_force_evtchn_callback+0xc/0x10 [ 480.052434] [] ? check_events+0x8/0xc [ 480.052442] [] ? do_get_write_access+0x1f8/0x3b5 [jbd] [ 480.052450] [] ? wake_bit_function+0x0/0x3c [ 480.052459] [] ? journal_get_write_access+0x18/0x26 [jbd] [ 480.052469] [] ? __ext3_journal_get_write_access+0x13/0x32 [ext3] [ 480.052479] [] ? ext3_reserve_inode_write+0x2d/0x5d [ext3] [ 480.052489] [] ? ext3_mark_inode_dirty+0x11/0x27 [ext3] [ 480.052499] [] ? ext3_dirty_inode+0x50/0x63 [ext3] [ 480.052507] [] ? __mark_inode_dirty+0x20/0x10c [ 480.052515] [] ? file_update_time+0xbe/0xdf [ 480.052523] [] ? __generic_file_aio_write+0x2f7/0x452 [ 480.052531] [] ? xen_restore_fl_direct_end+0x0/0x1 [ 480.052539] [] ? _spin_unlock_irqrestore+0xe/0x10 [ 480.052546] [] ? hrtimer_try_to_cancel+0x6e/0x83 [ 480.052554] [] ? hrtimer_try_to_cancel+0x7c/0x83 [ 480.052561] [] ? generic_file_aio_write+0x51/0x93 [ 480.052571] [] ? do_sync_write+0xc0/0x107 [ 480.052578] [] ? autoremove_wake_function+0x0/0x2d [ 480.052586] [] ? pick_next_task_fair+0x95/0x9c [ 480.052593] [] ? schedule+0x5ea/0x671 [ 480.052601] [] ? security_file_permission+0xc/0xd [ 480.052609] [] ? do_sync_write+0x0/0x107 [ 480.052616] [] ? vfs_write+0x84/0x12f [ 480.052623] [] ? sys_write+0x3c/0x63 [ 480.052630] [] ? sysenter_do_call+0x12/0x28 --000e0cd2de02d9155d0482037f4e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Pasi, Ian

I debugged this further with the assumption that IRQ follo= ws the path IDT->Hypervisor->pciback->pcifront->actual_device. = I added printk message while binding to a event-chnl=A0 and event-chnl call= back function in pcifront. I do see my printk message(while binding to even= t-chnl in domU) so I know kernel has correct module. After nic device is en= abled via ifconfig in domU, I do not see messages (added in event-chnl call= back function) from pcifront so I believe interrupt is not delivered to pci= front itself.

static inline void schedule_pcifront_aer_op(struct pcifront_device *pde= v)
{
=A0=A0=A0=A0=A0=A0=A0 if (test_bit(_XEN_PCIB_active, (unsigned l= ong *)&pdev->sh_info->flags)
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0 && !test_and_set_bit(_PDEVB_op_active, &pdev->f= lags)) {
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 dev_dbg(&pdev->xdev-&g= t;dev, "schedule aer frontend job\n");
=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0 printk(KERN_DEBUG "schedule aer frontend job = %d\n", pdev->irq); <<<<<<< never seen in dmesg= in domU
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 schedule_work(&pdev->o= p_work);
=A0=A0=A0=A0=A0=A0=A0 }
}

dmesg on dom0 says "no= body cared...", forum has some old discussions around 2006 and hence d= idn't look into it in detail.

Inputs will be very much appreciated.

dmesg in dom0 and domU follows= .

Thanks
/**********************dmesg on dom0********************= *******************/
pciback 0000:08:01.0: PCI INT A -> GSI 17 (level= , low) -> IRQ 17
irq 17: nobody cared (try booting with the "irqpoll" option)
P= id: 0, comm: swapper Tainted: G=A0=A0=A0=A0=A0=A0=A0=A0=A0 2.6.27.42-0.1.1.= xs0.1.1.737.1065xen #1
=A0[<c01544f7>] __report_bad_irq+0x27/0x90<= br>=A0[<c015485c>] note_interrupt+0x2fc/0x330
=A0[<f01df92d>] ? usb_hcd_irq+0x4d/0xe0 [usbcore]
=A0[<c0153931= >] ? handle_IRQ_event+0x31/0x90
=A0[<c01551e4>] handle_level_ir= q+0xe4/0x110
=A0[<c0107733>] do_IRQ+0x43/0x90
=A0[<c01413b9&= gt;] ? ktime_get+0x19/0x40
=A0[<c026cfcf>] evtchn_do_upcall+0xdf/0x1f0
=A0[<c0105565>] = hypervisor_callback+0x41/0x49
=A0[<c010797b>] ? xen_safe_halt+0x8b= /0xc0
=A0[<c010afde>] xen_idle+0x1e/0x50
=A0[<c0103728>] = cpu_idle+0x58/0xa0
=A0[<c0338f4e>] rest_init+0x4e/0x60
=A0=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
handlers:
[<f01df8e0>= ;] (usb_hcd_irq+0x0/0xe0 [usbcore])
Disabling IRQ #17
ata1.00: except= ion Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: cmd ca/00:08:31:08:14/00:00:00:00:00/e0 tag 0 dma 4096 out
=A0= =A0=A0=A0=A0=A0=A0=A0 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (ti= meout)
ata1.00: status: { DRDY }
ata1: soft resetting link
ata1.00= : qc timeout (cmd 0x27)
ata1.00: failed to read native max address (err_mask=3D0x4)
ata1.00: rev= alidation failed (errno=3D-5)
ata1: soft resetting link
ata1.00: qc t= imeout (cmd 0x27)
ata1.00: failed to read native max address (err_mask= =3D0x4)
ata1.00: revalidation failed (errno=3D-5)
ata1: soft resetting link
a= ta1.00: qc timeout (cmd 0x27)
ata1.00: failed to read native max address= (err_mask=3D0x4)
ata1.00: revalidation failed (errno=3D-5)
ata1.00: = disabled
ata1.00: device reported invalid CHS sector 0
ata1: soft resetting link<= br>ata1: EH complete
sd 0:0:0:0: [sda] Result: hostbyte=3DDID_BAD_TARGET= driverbyte=3DDRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sda, sect= or 1312817
Buffer I/O error on device sda1, logical block 164102
lost page write du= e to I/O error on sda1

/**************************dmesg on domU*= ********************************************/
[=A0=A0=A0 5.994657] EXT3 = FS on xvda1, internal journal
[=A0=A0=A0 8.431645] loop: module loaded
[=A0=A0 10.043554] NET: Registe= red protocol family 10
[=A0=A0 10.044013] lo: Disabled Privacy Extension= s
[=A0=A0 11.859410] lp: driver loaded but no devices found
[=A0=A0 1= 1.965333] ppdev: user-space parallel port driver
[=A0=A0 20.076012] eth0: no IPv6 routers present
[=A0 170.192510] ncr 00= 00:00:00.0: enabling device (0000 -> 0002)
[=A0 170.192551] ncr 0000:= 00:00.0: Xen PCI enabling IRQ: 17
[=A0 170.192571] ncr: Found an ncr dev= ice (cfg revision 0)...
[=A0 287.816020] ------------[ cut here ]------------
[=A0 287.816031] W= ARNING: at net/sched/sch_generic.c:261 dev_watchdog+0xf8/0x188()
[=A0 28= 7.816037] NETDEV WATCHDOG: ncr (): transmit queue 0 timed out
[=A0 287.8= 16041] Modules linked in: ncr ppdev parport_pc lp parport acpi_cpufreq proc= essor cpufreq_powersave cpufreq_stats cpufreq_ondemand freq_table cpufreq_u= serspace cpufreq_conservative ipv6 loop evdev pcspkr xen_netfront ext3 jbd = mbcache xen_blkfront thermal_sys
[=A0 287.816113] Pid: 0, comm: swapper Not tainted 2.6.32.9 #4
[=A0 287.= 816118] Call Trace:
[=A0 287.816127]=A0 [<c11f2db1>] ? dev_watchdo= g+0xf8/0x188
[=A0 287.816135]=A0 [<c11f2db1>] ? dev_watchdog+0xf8/= 0x188
[=A0 287.816143]=A0 [<c1037a1b>] ? warn_slowpath_common+0x5e/0x8a
= [=A0 287.816151]=A0 [<c1037a79>] ? warn_slowpath_fmt+0x26/0x2a
[= =A0 287.816159]=A0 [<c11f2db1>] ? dev_watchdog+0xf8/0x188
[=A0 287= .816168]=A0 [<c100665c>] ? check_events+0x8/0xc
[=A0 287.816175]=A0 [<c1005ff4>] ? xen_force_evtchn_callback+0xc/0x10=
[=A0 287.816183]=A0 [<c100665c>] ? check_events+0x8/0xc
[=A0 2= 87.816191]=A0 [<c1006653>] ? xen_restore_fl_direct_end+0x0/0x1
[= =A0 287.816200]=A0 [<c124f4ea>] ? _spin_unlock_irqrestore+0xe/0x10 [=A0 287.816209]=A0 [<c1042a74>] ? mod_timer+0x15f/0x168
[=A0 287.= 816217]=A0 [<c11f2cb9>] ? dev_watchdog+0x0/0x188
[=A0 287.816224]= =A0 [<c104263c>] ? run_timer_softirq+0x195/0x217
[=A0 287.816232]= =A0 [<c103cb18>] ? __do_softirq+0xaa/0x151
[=A0 287.816240]=A0 [<c103cbf0>] ? do_softirq+0x31/0x3c
[=A0 287.8= 16247]=A0 [<c103ccc6>] ? irq_exit+0x26/0x58
[=A0 287.816256]=A0 [&= lt;c118f14b>] ? xen_evtchn_do_upcall+0x13f/0x151
[=A0 287.816264]=A0 = [<c1009087>] ? xen_do_upcall+0x7/0xc
[=A0 287.816272]=A0 [<c10023a7>] ? hypercall_page+0x3a7/0x1001
[= =A0 287.816280]=A0 [<c1006075>] ? xen_safe_halt+0xf/0x1b
[=A0 287.= 816287]=A0 [<c1004083>] ? xen_idle+0x23/0x30
[=A0 287.816295]=A0 [= <c100773c>] ? cpu_idle+0x46/0x62
[=A0 287.816303]=A0 [<c136e7e0>] ? start_kernel+0x2c7/0x2ca
[=A0 2= 87.816310]=A0 [<c1370d33>] ? xen_start_kernel+0x5e6/0x5ee
[=A0 287= .816315] ---[ end trace 00c16cce2318c073 ]---
[=A0 287.816320] ncr: Tran= smit timeout on ncr at 4294964250, latency 583
[=A0 291.816017] ncr: Transmit timeout on ncr at 4294965250, latency 1000...

[=A0 412.673801] end_request: I/O error, dev xvda, sector 7608= 215
[=A0 412.673826] end_request: I/O error, dev xvda, sector 7608223[=A0 412.673837] end_request: I/O error, dev xvda, sector 7608231
[=A0 480.052035] INFO: task kjournald:565 blocked for more than 120 seconds= .
[=A0 480.052047] "echo 0 > /proc/sys/kernel/hung_task_timeout_= secs" disables this message.
[=A0 480.052057] kjournald=A0=A0=A0=A0= D 121f1575=A0=A0=A0=A0 0=A0=A0 565=A0=A0=A0=A0=A0 2 0x00000000
[=A0 480.052069]=A0 cf864d80 00000246 c136b7c0 121f1575 c1c25040 c13ce460 c= 13ce460 cf864f38
[=A0 480.052091]=A0 c26fb460 00000000 5737fa96 00000045= c136b7c0 121f1e2a c1052d6d 6c3e6a53
[=A0 480.052111]=A0 00000000 121f1e= 2a 00000000 cf894690 cf864f38 cf864d80 c26fb894 c26fb460
[=A0 480.052131] Call Trace:
[=A0 480.052143]=A0 [<c1052d6d>] ? kt= ime_get_ts+0xd7/0xdf
[=A0 480.052154]=A0 [<c124e1eb>] ? io_schedul= e+0x5f/0x98
[=A0 480.052162]=A0 [<c10d49a2>] ? sync_buffer+0x30/0x= 33
[=A0 480.052169]=A0 [<c124e645>] ? __wait_on_bit+0x33/0x58
[=A0 480.052176]=A0 [<c10d4972>] ? sync_buffer+0x0/0x33
[=A0 480.0= 52183]=A0 [<c124e720>] ? out_of_line_wait_on_bit+0xb6/0xbe
[=A0 48= 0.052190]=A0 [<c10d4972>] ? sync_buffer+0x0/0x33
[=A0 480.052198]= =A0 [<c104b97f>] ? wake_bit_function+0x0/0x3c
[=A0 480.052205]=A0 [<c10d493f>] ? __wait_on_buffer+0x16/0x18
[=A0= 480.052223]=A0 [<d084622d>] ? journal_commit_transaction+0x85a/0xd6d= [jbd]
[=A0 480.052235]=A0 [<c10323bf>] ? finish_task_switch+0x3d/= 0x9c
[=A0 480.052243]=A0 [<c100665c>] ? check_events+0x8/0xc
[=A0 480.0= 52250]=A0 [<c1006653>] ? xen_restore_fl_direct_end+0x0/0x1
[=A0 48= 0.052258]=A0 [<c124f4ea>] ? _spin_unlock_irqrestore+0xe/0x10
[=A0 = 480.052267]=A0 [<c1042c5a>] ? try_to_del_timer_sync+0x79/0x80
[=A0 480.052276]=A0 [<d0848b6f>] ? kjournald+0xbb/0x1e5 [jbd]
[=A0= 480.052283]=A0 [<c104b952>] ? autoremove_wake_function+0x0/0x2d
[= =A0 480.052292]=A0 [<d0848ab4>] ? kjournald+0x0/0x1e5 [jbd]
[=A0 4= 80.052299]=A0 [<c104b71e>] ? kthread+0x61/0x66
[=A0 480.052305]=A0 [<c104b6bd>] ? kthread+0x0/0x66
[=A0 480.05231= 3]=A0 [<c1009037>] ? kernel_thread_helper+0x7/0x10
[=A0 480.052320= ] INFO: task rsyslogd:1929 blocked for more than 120 seconds.
[=A0 480.0= 52328] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disa= bles this message.
[=A0 480.052337] rsyslogd=A0=A0=A0=A0=A0 D 00001000=A0=A0=A0=A0 0=A0 1929= =A0=A0=A0=A0=A0 1 0x00000000
[=A0 480.052346]=A0 c1c20d40 00000286 d0877= 650 00001000 c1c25200 c13ce460 c13ce460 c1c20ef8
[=A0 480.052367]=A0 c26= fb460 00000000 c1cd5600 c1cf02c0 cf4693ec cf576518 c1005ff4 c26f0a5c
[=A0 480.052387]=A0 cf99fd98 cf99fdac c100665c c26f025c c1c20ef8 c26f0a5c c= f99fd98 cf99fdac
[=A0 480.052407] Call Trace:
[=A0 480.052418]=A0 [&l= t;d0877650>] ? __ext3_get_inode_loc+0xc7/0x275 [ext3]
[=A0 480.052426= ]=A0 [<c1005ff4>] ? xen_force_evtchn_callback+0xc/0x10
[=A0 480.052434]=A0 [<c100665c>] ? check_events+0x8/0xc
[=A0 480.0= 52442]=A0 [<d0845072>] ? do_get_write_access+0x1f8/0x3b5 [jbd]
[= =A0 480.052450]=A0 [<c104b97f>] ? wake_bit_function+0x0/0x3c
[=A0 = 480.052459]=A0 [<d0845247>] ? journal_get_write_access+0x18/0x26 [jbd= ]
[=A0 480.052469]=A0 [<d0882caf>] ? __ext3_journal_get_write_access+0x= 13/0x32 [ext3]
[=A0 480.052479]=A0 [<d0877baf>] ? ext3_reserve_ino= de_write+0x2d/0x5d [ext3]
[=A0 480.052489]=A0 [<d0877bf0>] ? ext3_= mark_inode_dirty+0x11/0x27 [ext3]
[=A0 480.052499]=A0 [<d0877d05>] ? ext3_dirty_inode+0x50/0x63 [ext3]<= br>[=A0 480.052507]=A0 [<c10cf541>] ? __mark_inode_dirty+0x20/0x10c[=A0 480.052515]=A0 [<c10c7bc5>] ? file_update_time+0xbe/0xdf
[= =A0 480.052523]=A0 [<c109107b>] ? __generic_file_aio_write+0x2f7/0x45= 2
[=A0 480.052531]=A0 [<c1006653>] ? xen_restore_fl_direct_end+0x0/0x1<= br>[=A0 480.052539]=A0 [<c124f4ea>] ? _spin_unlock_irqrestore+0xe/0x1= 0
[=A0 480.052546]=A0 [<c104e617>] ? hrtimer_try_to_cancel+0x6e/0x= 83
[=A0 480.052554]=A0 [<c104e625>] ? hrtimer_try_to_cancel+0x7c/0= x83
[=A0 480.052561]=A0 [<c1091227>] ? generic_file_aio_write+0x51/0x93[=A0 480.052571]=A0 [<c10b8680>] ? do_sync_write+0xc0/0x107
[=A0= 480.052578]=A0 [<c104b952>] ? autoremove_wake_function+0x0/0x2d
[= =A0 480.052586]=A0 [<c102dd9e>] ? pick_next_task_fair+0x95/0x9c
[=A0 480.052593]=A0 [<c124e105>] ? schedule+0x5ea/0x671
[=A0 480.0= 52601]=A0 [<c1107ae8>] ? security_file_permission+0xc/0xd
[=A0 480= .052609]=A0 [<c10b85c0>] ? do_sync_write+0x0/0x107
[=A0 480.052616= ]=A0 [<c10b900b>] ? vfs_write+0x84/0x12f
[=A0 480.052623]=A0 [<c10b914e>] ? sys_write+0x3c/0x63
[=A0 480.05= 2630]=A0 [<c10084b4>] ? sysenter_do_call+0x12/0x28

--000e0cd2de02d9155d0482037f4e-- --===============1480831413== 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 --===============1480831413==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: domU guest for xcp 0.1.1 Date: Thu, 18 Mar 2010 09:17:04 +0000 Message-ID: <1268903824.10129.38718.camel@zakaz.uk.xensource.com> References: <29b32d341003141329v3c6a73c0y8030cf3c6736634c@mail.gmail.com> <29b32d341003142030p1fe511d2ke30b8483ff8cc368@mail.gmail.com> <1268642688.8652.2792.camel@localhost.localdomain> <29b32d341003150642o4e2620edsf154b19d78aa7f42@mail.gmail.com> <1268660645.10129.25070.camel@zakaz.uk.xensource.com> <29b32d341003150646o4d215dfel1c2a2bc6d287edc@mail.gmail.com> <29b32d341003151904m2a992be5s74697d6047b864c6@mail.gmail.com> <1268725069.8652.4179.camel@localhost.localdomain> <20100316152259.GO1878@reaktio.net> <29b32d341003161625w2969f2daib3408561920793d3@mail.gmail.com> <29b32d341003171144k628a7741x17b6658731f96e4b@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <29b32d341003171144k628a7741x17b6658731f96e4b@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: Ritu kaur Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org I thought AER stuff was only called on error conditions and isn't in the normal pci passthrough paths so I don't think you would expect to see any messages from schedule_pcifront_aer_op in normal operation. I'm not sure about your actual problem (we're pushing the boundaries of my immediate knowledge of pcifront/back here), it looks as if it might relate to the interrupt being shared with other devices in domain 0? What does /proc/interrupts say on both ends? Which devices are you trying to passthrough, only 0000:08:01.0? Does 0000:08:01.0 share an interrupt with your USB controller and/or ATA controller in domain 0? Ian. On Wed, 2010-03-17 at 18:44 +0000, Ritu kaur wrote: > Pasi, Ian > > I debugged this further with the assumption that IRQ follows the path > IDT->Hypervisor->pciback->pcifront->actual_device. I added printk > message while binding to a event-chnl and event-chnl callback > function in pcifront. I do see my printk message(while binding to > event-chnl in domU) so I know kernel has correct module. After nic > device is enabled via ifconfig in domU, I do not see messages (added > in event-chnl callback function) from pcifront so I believe interrupt > is not delivered to pcifront itself. > > static inline void schedule_pcifront_aer_op(struct pcifront_device > *pdev) > { > if (test_bit(_XEN_PCIB_active, (unsigned long > *)&pdev->sh_info->flags) > && !test_and_set_bit(_PDEVB_op_active, &pdev->flags)) > { > dev_dbg(&pdev->xdev->dev, "schedule aer frontend job > \n"); > printk(KERN_DEBUG "schedule aer frontend job %d\n", > pdev->irq); <<<<<<< never seen in dmesg in domU > schedule_work(&pdev->op_work); > } > } > > dmesg on dom0 says "nobody cared...", forum has some old discussions > around 2006 and hence didn't look into it in detail. > > Inputs will be very much appreciated. > > dmesg in dom0 and domU follows. > > Thanks > /**********************dmesg on > dom0***************************************/ > pciback 0000:08:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 > irq 17: nobody cared (try booting with the "irqpoll" option) > Pid: 0, comm: swapper Tainted: G > 2.6.27.42-0.1.1.xs0.1.1.737.1065xen #1 > [] __report_bad_irq+0x27/0x90 > [] note_interrupt+0x2fc/0x330 > [] ? usb_hcd_irq+0x4d/0xe0 [usbcore] > [] ? handle_IRQ_event+0x31/0x90 > [] handle_level_irq+0xe4/0x110 > [] do_IRQ+0x43/0x90 > [] ? ktime_get+0x19/0x40 > [] evtchn_do_upcall+0xdf/0x1f0 > [] hypervisor_callback+0x41/0x49 > [] ? xen_safe_halt+0x8b/0xc0 > [] xen_idle+0x1e/0x50 > [] cpu_idle+0x58/0xa0 > [] rest_init+0x4e/0x60 > ======================= > handlers: > [] (usb_hcd_irq+0x0/0xe0 [usbcore]) > Disabling IRQ #17 > ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen > ata1.00: cmd ca/00:08:31:08:14/00:00:00:00:00/e0 tag 0 dma 4096 out > res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > ata1.00: status: { DRDY } > ata1: soft resetting link > ata1.00: qc timeout (cmd 0x27) > ata1.00: failed to read native max address (err_mask=0x4) > ata1.00: revalidation failed (errno=-5) > ata1: soft resetting link > ata1.00: qc timeout (cmd 0x27) > ata1.00: failed to read native max address (err_mask=0x4) > ata1.00: revalidation failed (errno=-5) > ata1: soft resetting link > ata1.00: qc timeout (cmd 0x27) > ata1.00: failed to read native max address (err_mask=0x4) > ata1.00: revalidation failed (errno=-5) > ata1.00: disabled > ata1.00: device reported invalid CHS sector 0 > ata1: soft resetting link > ata1: EH complete > sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET > driverbyte=DRIVER_OK,SUGGEST_OK > end_request: I/O error, dev sda, sector 1312817 > Buffer I/O error on device sda1, logical block 164102 > lost page write due to I/O error on sda1 > > > /**************************dmesg on > domU*********************************************/ > [ 5.994657] EXT3 FS on xvda1, internal journal > [ 8.431645] loop: module loaded > [ 10.043554] NET: Registered protocol family 10 > [ 10.044013] lo: Disabled Privacy Extensions > [ 11.859410] lp: driver loaded but no devices found > [ 11.965333] ppdev: user-space parallel port driver > [ 20.076012] eth0: no IPv6 routers present > [ 170.192510] ncr 0000:00:00.0: enabling device (0000 -> 0002) > [ 170.192551] ncr 0000:00:00.0: Xen PCI enabling IRQ: 17 > [ 170.192571] ncr: Found an ncr device (cfg revision 0)... > [ 287.816020] ------------[ cut here ]------------ > [ 287.816031] WARNING: at net/sched/sch_generic.c:261 dev_watchdog > +0xf8/0x188() > [ 287.816037] NETDEV WATCHDOG: ncr (): transmit queue 0 timed out > [ 287.816041] Modules linked in: ncr ppdev parport_pc lp parport > acpi_cpufreq processor cpufreq_powersave cpufreq_stats > cpufreq_ondemand freq_table cpufreq_userspace cpufreq_conservative > ipv6 loop evdev pcspkr xen_netfront ext3 jbd mbcache xen_blkfront > thermal_sys > [ 287.816113] Pid: 0, comm: swapper Not tainted 2.6.32.9 #4 > [ 287.816118] Call Trace: > [ 287.816127] [] ? dev_watchdog+0xf8/0x188 > [ 287.816135] [] ? dev_watchdog+0xf8/0x188 > [ 287.816143] [] ? warn_slowpath_common+0x5e/0x8a > [ 287.816151] [] ? warn_slowpath_fmt+0x26/0x2a > [ 287.816159] [] ? dev_watchdog+0xf8/0x188 > [ 287.816168] [] ? check_events+0x8/0xc > [ 287.816175] [] ? xen_force_evtchn_callback+0xc/0x10 > [ 287.816183] [] ? check_events+0x8/0xc > [ 287.816191] [] ? xen_restore_fl_direct_end+0x0/0x1 > [ 287.816200] [] ? _spin_unlock_irqrestore+0xe/0x10 > [ 287.816209] [] ? mod_timer+0x15f/0x168 > [ 287.816217] [] ? dev_watchdog+0x0/0x188 > [ 287.816224] [] ? run_timer_softirq+0x195/0x217 > [ 287.816232] [] ? __do_softirq+0xaa/0x151 > [ 287.816240] [] ? do_softirq+0x31/0x3c > [ 287.816247] [] ? irq_exit+0x26/0x58 > [ 287.816256] [] ? xen_evtchn_do_upcall+0x13f/0x151 > [ 287.816264] [] ? xen_do_upcall+0x7/0xc > [ 287.816272] [] ? hypercall_page+0x3a7/0x1001 > [ 287.816280] [] ? xen_safe_halt+0xf/0x1b > [ 287.816287] [] ? xen_idle+0x23/0x30 > [ 287.816295] [] ? cpu_idle+0x46/0x62 > [ 287.816303] [] ? start_kernel+0x2c7/0x2ca > [ 287.816310] [] ? xen_start_kernel+0x5e6/0x5ee > [ 287.816315] ---[ end trace 00c16cce2318c073 ]--- > [ 287.816320] ncr: Transmit timeout on ncr at 4294964250, latency 583 > [ 291.816017] ncr: Transmit timeout on ncr at 4294965250, latency > 1000 > ... > > [ 412.673801] end_request: I/O error, dev xvda, sector 7608215 > [ 412.673826] end_request: I/O error, dev xvda, sector 7608223 > [ 412.673837] end_request: I/O error, dev xvda, sector 7608231 > [ 480.052035] INFO: task kjournald:565 blocked for more than 120 > seconds. > [ 480.052047] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" > disables this message. > [ 480.052057] kjournald D 121f1575 0 565 2 0x00000000 > [ 480.052069] cf864d80 00000246 c136b7c0 121f1575 c1c25040 c13ce460 > c13ce460 cf864f38 > [ 480.052091] c26fb460 00000000 5737fa96 00000045 c136b7c0 121f1e2a > c1052d6d 6c3e6a53 > [ 480.052111] 00000000 121f1e2a 00000000 cf894690 cf864f38 cf864d80 > c26fb894 c26fb460 > [ 480.052131] Call Trace: > [ 480.052143] [] ? ktime_get_ts+0xd7/0xdf > [ 480.052154] [] ? io_schedule+0x5f/0x98 > [ 480.052162] [] ? sync_buffer+0x30/0x33 > [ 480.052169] [] ? __wait_on_bit+0x33/0x58 > [ 480.052176] [] ? sync_buffer+0x0/0x33 > [ 480.052183] [] ? out_of_line_wait_on_bit+0xb6/0xbe > [ 480.052190] [] ? sync_buffer+0x0/0x33 > [ 480.052198] [] ? wake_bit_function+0x0/0x3c > [ 480.052205] [] ? __wait_on_buffer+0x16/0x18 > [ 480.052223] [] ? journal_commit_transaction+0x85a/0xd6d > [jbd] > [ 480.052235] [] ? finish_task_switch+0x3d/0x9c > [ 480.052243] [] ? check_events+0x8/0xc > [ 480.052250] [] ? xen_restore_fl_direct_end+0x0/0x1 > [ 480.052258] [] ? _spin_unlock_irqrestore+0xe/0x10 > [ 480.052267] [] ? try_to_del_timer_sync+0x79/0x80 > [ 480.052276] [] ? kjournald+0xbb/0x1e5 [jbd] > [ 480.052283] [] ? autoremove_wake_function+0x0/0x2d > [ 480.052292] [] ? kjournald+0x0/0x1e5 [jbd] > [ 480.052299] [] ? kthread+0x61/0x66 > [ 480.052305] [] ? kthread+0x0/0x66 > [ 480.052313] [] ? kernel_thread_helper+0x7/0x10 > [ 480.052320] INFO: task rsyslogd:1929 blocked for more than 120 > seconds. > [ 480.052328] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" > disables this message. > [ 480.052337] rsyslogd D 00001000 0 1929 1 0x00000000 > [ 480.052346] c1c20d40 00000286 d0877650 00001000 c1c25200 c13ce460 > c13ce460 c1c20ef8 > [ 480.052367] c26fb460 00000000 c1cd5600 c1cf02c0 cf4693ec cf576518 > c1005ff4 c26f0a5c > [ 480.052387] cf99fd98 cf99fdac c100665c c26f025c c1c20ef8 c26f0a5c > cf99fd98 cf99fdac > [ 480.052407] Call Trace: > [ 480.052418] [] ? __ext3_get_inode_loc+0xc7/0x275 [ext3] > [ 480.052426] [] ? xen_force_evtchn_callback+0xc/0x10 > [ 480.052434] [] ? check_events+0x8/0xc > [ 480.052442] [] ? do_get_write_access+0x1f8/0x3b5 [jbd] > [ 480.052450] [] ? wake_bit_function+0x0/0x3c > [ 480.052459] [] ? journal_get_write_access+0x18/0x26 > [jbd] > [ 480.052469] [] ? __ext3_journal_get_write_access > +0x13/0x32 [ext3] > [ 480.052479] [] ? ext3_reserve_inode_write+0x2d/0x5d > [ext3] > [ 480.052489] [] ? ext3_mark_inode_dirty+0x11/0x27 [ext3] > [ 480.052499] [] ? ext3_dirty_inode+0x50/0x63 [ext3] > [ 480.052507] [] ? __mark_inode_dirty+0x20/0x10c > [ 480.052515] [] ? file_update_time+0xbe/0xdf > [ 480.052523] [] ? __generic_file_aio_write+0x2f7/0x452 > [ 480.052531] [] ? xen_restore_fl_direct_end+0x0/0x1 > [ 480.052539] [] ? _spin_unlock_irqrestore+0xe/0x10 > [ 480.052546] [] ? hrtimer_try_to_cancel+0x6e/0x83 > [ 480.052554] [] ? hrtimer_try_to_cancel+0x7c/0x83 > [ 480.052561] [] ? generic_file_aio_write+0x51/0x93 > [ 480.052571] [] ? do_sync_write+0xc0/0x107 > [ 480.052578] [] ? autoremove_wake_function+0x0/0x2d > [ 480.052586] [