domU guest for xcp 0.1.1

domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 936 bytes --]

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
http://wiki.xensource.com/xenwiki/Command_Line_Interface). Unfortunately,
Debian Lenny which the wiki points to doesn't come with PV drivers(I need
pcifront driver). I looked up in 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. For PCI passthrough, you have to
run the 2.6.18 etch kernel as both dom0 and domU. ***/

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.

Thanks

[-- Attachment #1.2: Type: text/html, Size: 1105 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Pasi Kärkkäinen]

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]http://wiki.xensource.com/xenwiki/Command_Line_Interface).
>    Unfortunately, Debian Lenny which the wiki points to doesn't come with PV
>    drivers(I need pcifront driver). I looked up in [2]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. 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:

	- 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: http://wiki.xensource.com/xenwiki/XenParavirtOps)
	- Kernels with the forward-ported Novell/opensuse Xen patches (2.6.29, 2.6.31, 2.6.33)
	  (See: 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

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 3194 bytes --]

Thanks Pasi. I looked at
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 kernel.org kernel is generally a good
   choice.
   2. Configure as normal; you can start with your current .config file
   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 kernel.org and started building
kernel(irrespective of above questions), but what distribution is this
kernel associated with i.e I thought I should first install linux from a
distribution and rebuild kernel for any modification, but in this case I
don't understand what distribution this is associated with. Inputs much
appreciated.

Thanks




On Fri, Mar 12, 2010 at 9:51 AM, Pasi Kärkkäinen <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]http://wiki.xensource.com/xenwiki/Command_Line_Interface).
> >    Unfortunately, Debian Lenny which the wiki points to doesn't come with
> PV
> >    drivers(I need pcifront driver). I looked up in [2]
> 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. 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:
>
>        - 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: http://wiki.xensource.com/xenwiki/XenParavirtOps)
>        - Kernels with the forward-ported Novell/opensuse Xen patches
> (2.6.29, 2.6.31, 2.6.33)
>          (See: 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
>
>

[-- Attachment #1.2: Type: text/html, Size: 4970 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Pasi Kärkkäinen]

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 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 file
>     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 this
>    kernel associated with i.e I thought I should first install linux from a
>    distribution and rebuild kernel for any modification, but in this case 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 from there,
to have the pcifront driver. It's not yet in the upstream kernel.org kernel.

-- Pasi

>    Thanks
> 
>    On Fri, Mar 12, 2010 at 9:51 AM, Pasi Kärkkäinen <[4]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]http://wiki.xensource.com/xenwiki/Command_Line_Interface).
>      >    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 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. 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 patches
>      (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

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 4942 bytes --]

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ärkkäinen <pasik@iki.fi> 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(my<http://wiki.xensource.com/xenwiki/XenParavirtOps%28my>foray 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 file
> >     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 this
> >    kernel associated with i.e I thought I should first install linux from
> a
> >    distribution and rebuild kernel for any modification, but in this case
> 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 from
> there,
> to have the pcifront driver. It's not yet in the upstream kernel.orgkernel.
>
> -- Pasi
>
> >    Thanks
> >
> >    On Fri, Mar 12, 2010 at 9:51 AM, Pasi Kärkkäinen <[4]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]http://wiki.xensource.com/xenwiki/Command_Line_Interface
> ).
> >      >    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 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. 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 patches
> >      (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<http://wiki.xensource.com/xenwiki/XenParavirtOps%28my>
> >    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
>

[-- Attachment #1.2: Type: text/html, Size: 7129 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Pasi Kärkkäinen]

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 used as a
>    domU? At least last time I checked I was told I cannot use it.
> 

Yes, you can use the dom0 kernel also as domU, just make sure you build 
the frontend drivers aswell.

Actually you've been able to use the same kernel for both dom0 and domU for 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 
both dom0 and domU.

Actually pvops makes it possible to boot the exact same kernel image on baremetal (non-Xen),
Xen dom0 and domU!

-- Pasi

>    Thanks
> 
>    On Sat, Mar 13, 2010 at 3:18 AM, Pasi Kärkkäinen <[1]pasik@iki.fi> wrote:
> 
>      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 foray
>      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 .config
>      file
>      >     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][4]kernel.org and started
>      building
>      >    kernel(irrespective of above questions), but what distribution is
>      this
>      >    kernel associated with i.e I thought I should first install linux
>      from a
>      >    distribution and rebuild kernel for any modification, but in this
>      case 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
>      from there,
>      to have the pcifront driver. It's not yet in the upstream [5]kernel.org
>      kernel.
> 
>      -- Pasi
> 
>      >    Thanks
>      >
>      >    On Fri, Mar 12, 2010 at 9:51 AM, Pasi Kärkkäinen
>      <[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 doesn'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. 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][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 Xen
>      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 binary 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_Interface
>      >    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
> 
> References
> 
>    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

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 2764 bytes --]

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 ‘xen_destroy_irq’
/root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29: error:
previous definition of ‘xen_destroy_irq’ was here
drivers/xen/events.c:637: error: redefinition of ‘xen_create_msi_irq’
/root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25: error:
previous definition of ‘xen_create_msi_irq’ 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 ‘pci_frontend_ops’ has
initializut incomplete type
drivers/pci/xen-pcifront.c:374: error: unknown field ‘enable_msi’
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
‘pci_frontend_op)’
drivers/pci/xen-pcifront.c:375: error: unknown field ‘disable_msi’
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
‘pci_frontend_op)’
drivers/pci/xen-pcifront.c:376: error: unknown field ‘enable_msix’
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
‘pci_frontend_op)’
drivers/pci/xen-pcifront.c:377: error: unknown field ‘disable_msix’
specified intializer
drivers/pci/xen-pcifront.c:377: warning: excess elements in struct
initializer
drivers/pci/xen-pcifront.c:377: warning: (near initialization for
‘pci_frontend_op)’
drivers/pci/xen-pcifront.c: In function ‘pci_frontend_registrar’:
drivers/pci/xen-pcifront.c:383: error: ‘xen_pci_frontend’ 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

[-- Attachment #1.2: Type: text/html, Size: 2868 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: pvops xen/master and xen/stable domU kernel compilation errors

[Pasi Kärkkäinen]

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
> 
>    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)
> 

Hmm.. the error below seems pretty easy to solve. Maybe Konrad already has
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 â**xen_destroy_irqâ**
>    /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29: error:
>    previous definition of â**xen_destroy_irqâ** was here
>    drivers/xen/events.c:637: error: redefinition of â**xen_create_msi_irqâ**
>    /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25: error:
>    previous definition of â**xen_create_msi_irqâ** 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
> 

Ok so some extra patches needed here aswell.

-- Pasi

>     CC      drivers/pci/xen-pcifront.o
>    drivers/pci/xen-pcifront.c:373: error: variable â**pci_frontend_opsâ** has
>    initializut incomplete type
>    drivers/pci/xen-pcifront.c:374: error: unknown field â**enable_msiâ**
>    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
>    â**pci_frontend_op)â**
>    drivers/pci/xen-pcifront.c:375: error: unknown field â**disable_msiâ**
>    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
>    â**pci_frontend_op)â**
>    drivers/pci/xen-pcifront.c:376: error: unknown field â**enable_msixâ**
>    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
>    â**pci_frontend_op)â**
>    drivers/pci/xen-pcifront.c:377: error: unknown field â**disable_msixâ**
>    specified intializer
>    drivers/pci/xen-pcifront.c:377: warning: excess elements in struct
>    initializer
>    drivers/pci/xen-pcifront.c:377: warning: (near initialization for
>    â**pci_frontend_op)â**
>    drivers/pci/xen-pcifront.c: In function â**pci_frontend_registrarâ**:
>    drivers/pci/xen-pcifront.c:383: error: â**xen_pci_frontendâ** 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.
> 

Re: domU guest for xcp 0.1.1

[Sander Eikelenboom]

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 ‘xen_destroy_irq’
> /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29: error:
> previous definition of ‘xen_destroy_irq’ was here
> drivers/xen/events.c:637: error: redefinition of ‘xen_create_msi_irq’
> /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25: error:
> previous definition of ‘xen_create_msi_irq’ 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 ‘pci_frontend_ops’ has
> initializut incomplete type
> drivers/pci/xen-pcifront.c:374: error: unknown field ‘enable_msi’
> 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
> ‘pci_frontend_op)’
> drivers/pci/xen-pcifront.c:375: error: unknown field ‘disable_msi’
> 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
> ‘pci_frontend_op)’
> drivers/pci/xen-pcifront.c:376: error: unknown field ‘enable_msix’
> 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
> ‘pci_frontend_op)’
> drivers/pci/xen-pcifront.c:377: error: unknown field ‘disable_msix’
> specified intializer
> drivers/pci/xen-pcifront.c:377: warning: excess elements in struct
> initializer
> drivers/pci/xen-pcifront.c:377: warning: (near initialization for
> ‘pci_frontend_op)’
> drivers/pci/xen-pcifront.c: In function ‘pci_frontend_registrar’:
> drivers/pci/xen-pcifront.c:383: error: ‘xen_pci_frontend’ 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

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 4348 bytes --]

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=/dev/xvda1 ro
console=hvc0 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 <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
> 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 ‘xen_destroy_irq’
> > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29: error:
> > previous definition of ‘xen_destroy_irq’ was here
> > drivers/xen/events.c:637: error: redefinition of ‘xen_create_msi_irq’
> > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25: error:
> > previous definition of ‘xen_create_msi_irq’ 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 ‘pci_frontend_ops’
> has
> > initializut incomplete type
> > drivers/pci/xen-pcifront.c:374: error: unknown field ‘enable_msi’
> > 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
> > ‘pci_frontend_op)’
> > drivers/pci/xen-pcifront.c:375: error: unknown field ‘disable_msi’
> > 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
> > ‘pci_frontend_op)’
> > drivers/pci/xen-pcifront.c:376: error: unknown field ‘enable_msix’
> > 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
> > ‘pci_frontend_op)’
> > drivers/pci/xen-pcifront.c:377: error: unknown field ‘disable_msix’
> > specified intializer
> > drivers/pci/xen-pcifront.c:377: warning: excess elements in struct
> > initializer
> > drivers/pci/xen-pcifront.c:377: warning: (near initialization for
> > ‘pci_frontend_op)’
> > drivers/pci/xen-pcifront.c: In function ‘pci_frontend_registrar’:
> > drivers/pci/xen-pcifront.c:383: error: ‘xen_pci_frontend’ 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
>
>

[-- Attachment #1.2: Type: text/html, Size: 5141 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Sander Eikelenboom]

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=/dev/xvda1 ro
> console=hvc0 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 <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
>> 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 ‘xen_destroy_irq’
>> > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29: error:
>> > previous definition of ‘xen_destroy_irq’ was here
>> > drivers/xen/events.c:637: error: redefinition of ‘xen_create_msi_irq’
>> > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25: error:
>> > previous definition of ‘xen_create_msi_irq’ 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 ‘pci_frontend_ops’
>> has
>> > initializut incomplete type
>> > drivers/pci/xen-pcifront.c:374: error: unknown field ‘enable_msi’
>> > 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
>> > ‘pci_frontend_op)’
>> > drivers/pci/xen-pcifront.c:375: error: unknown field ‘disable_msi’
>> > 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
>> > ‘pci_frontend_op)’
>> > drivers/pci/xen-pcifront.c:376: error: unknown field ‘enable_msix’
>> > 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
>> > ‘pci_frontend_op)’
>> > drivers/pci/xen-pcifront.c:377: error: unknown field ‘disable_msix’
>> > specified intializer
>> > drivers/pci/xen-pcifront.c:377: warning: excess elements in struct
>> > initializer
>> > drivers/pci/xen-pcifront.c:377: warning: (near initialization for
>> > ‘pci_frontend_op)’
>> > drivers/pci/xen-pcifront.c: In function ‘pci_frontend_registrar’:
>> > drivers/pci/xen-pcifront.c:383: error: ‘xen_pci_frontend’ 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

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 5591 bytes --]

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 <linux@eikelenboom.it>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=/dev/xvda1 ro
> > console=hvc0 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 <
> 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
> >> 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 ‘xen_destroy_irq’
> >> > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29: error:
> >> > previous definition of ‘xen_destroy_irq’ was here
> >> > drivers/xen/events.c:637: error: redefinition of
> ‘xen_create_msi_irq’
> >> > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25: error:
> >> > previous definition of ‘xen_create_msi_irq’ 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 ‘pci_frontend_ops’
> >> has
> >> > initializut incomplete type
> >> > drivers/pci/xen-pcifront.c:374: error: unknown field ‘enable_msi’
> >> > 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
> >> > ‘pci_frontend_op)’
> >> > drivers/pci/xen-pcifront.c:375: error: unknown field ‘disable_msi’
> >> > 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
> >> > ‘pci_frontend_op)’
> >> > drivers/pci/xen-pcifront.c:376: error: unknown field ‘enable_msix’
> >> > 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
> >> > ‘pci_frontend_op)’
> >> > drivers/pci/xen-pcifront.c:377: error: unknown field
> ‘disable_msix’
> >> > specified intializer
> >> > drivers/pci/xen-pcifront.c:377: warning: excess elements in struct
> >> > initializer
> >> > drivers/pci/xen-pcifront.c:377: warning: (near initialization for
> >> > ‘pci_frontend_op)’
> >> > drivers/pci/xen-pcifront.c: In function ‘pci_frontend_registrar’:
> >> > drivers/pci/xen-pcifront.c:383: error: ‘xen_pci_frontend’
> 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
>
>

[-- Attachment #1.2: Type: text/html, Size: 7156 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 6090 bytes --]

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 <ritu.kaur.us@gmail.com> 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 <linux@eikelenboom.it>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=/dev/xvda1 ro
>> > console=hvc0 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 <
>> 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
>> >> 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
>> ‘xen_destroy_irq’
>> >> > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29: error:
>> >> > previous definition of ‘xen_destroy_irq’ was here
>> >> > drivers/xen/events.c:637: error: redefinition of
>> ‘xen_create_msi_irq’
>> >> > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25: error:
>> >> > previous definition of ‘xen_create_msi_irq’ 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
>> ‘pci_frontend_ops’
>> >> has
>> >> > initializut incomplete type
>> >> > drivers/pci/xen-pcifront.c:374: error: unknown field ‘enable_msi’
>> >> > 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
>> >> > ‘pci_frontend_op)’
>> >> > drivers/pci/xen-pcifront.c:375: error: unknown field
>> ‘disable_msi’
>> >> > 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
>> >> > ‘pci_frontend_op)’
>> >> > drivers/pci/xen-pcifront.c:376: error: unknown field
>> ‘enable_msix’
>> >> > 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
>> >> > ‘pci_frontend_op)’
>> >> > drivers/pci/xen-pcifront.c:377: error: unknown field
>> ‘disable_msix’
>> >> > specified intializer
>> >> > drivers/pci/xen-pcifront.c:377: warning: excess elements in struct
>> >> > initializer
>> >> > drivers/pci/xen-pcifront.c:377: warning: (near initialization for
>> >> > ‘pci_frontend_op)’
>> >> > drivers/pci/xen-pcifront.c: In function ‘pci_frontend_registrar’:
>> >> > drivers/pci/xen-pcifront.c:383: error: ‘xen_pci_frontend’
>> 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
>>
>>
>

[-- Attachment #1.2: Type: text/html, Size: 7832 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Ian Campbell]

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 <ritu.kaur.us@gmail.com>
> 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
>         <linux@eikelenboom.it> 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=/dev/xvda1 ro
>                 > console=hvc0 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
>                 <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
>                 >> 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
>                 ‘xen_destroy_irq’
>                 >>
>                 > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29: error:
>                 >> > previous definition of ‘xen_destroy_irq’ was
>                 here
>                 >> > drivers/xen/events.c:637: error: redefinition of
>                 ‘xen_create_msi_irq’
>                 >>
>                 > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25: error:
>                 >> > previous definition of ‘xen_create_msi_irq’
>                 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 â
>                 €˜pci_frontend_ops’
>                 >> has
>                 >> > initializut incomplete type
>                 >> > drivers/pci/xen-pcifront.c:374: error: unknown
>                 field ‘enable_msi’
>                 >> > 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
>                 >> > ‘pci_frontend_op)’
>                 >> > drivers/pci/xen-pcifront.c:375: error: unknown
>                 field ‘disable_msi’
>                 >> > 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
>                 >> > ‘pci_frontend_op)’
>                 >> > drivers/pci/xen-pcifront.c:376: error: unknown
>                 field ‘enable_msix’
>                 >> > 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
>                 >> > ‘pci_frontend_op)’
>                 >> > drivers/pci/xen-pcifront.c:377: error: unknown
>                 field ‘disable_msix’
>                 >> > specified intializer
>                 >> > drivers/pci/xen-pcifront.c:377: warning: excess
>                 elements in struct
>                 >> > initializer
>                 >> > drivers/pci/xen-pcifront.c:377: warning: (near
>                 initialization for
>                 >> > ‘pci_frontend_op)’
>                 >> > drivers/pci/xen-pcifront.c: In function â
>                 €˜pci_frontend_registrar’:
>                 >> > drivers/pci/xen-pcifront.c:383: error: â
>                 €˜xen_pci_frontend’ 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
>                 
>                 
>         
>         
> 

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 9673 bytes --]

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 <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 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 <ritu.kaur.us@gmail.com>
> > 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
> >         <linux@eikelenboom.it> 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=/dev/xvda1 ro
> >                 > console=hvc0 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
> >                 <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
> >                 >> 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
> >                 ‘xen_destroy_irq’
> >                 >>
> >                 >
> /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29: error:
> >                 >> > previous definition of ‘xen_destroy_irq’ was
> >                 here
> >                 >> > drivers/xen/events.c:637: error: redefinition of
> >                 ‘xen_create_msi_irq’
> >                 >>
> >                 >
> /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25: error:
> >                 >> > previous definition of ‘xen_create_msi_irq’
> >                 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 â
> >                 €˜pci_frontend_ops’
> >                 >> has
> >                 >> > initializut incomplete type
> >                 >> > drivers/pci/xen-pcifront.c:374: error: unknown
> >                 field ‘enable_msi’
> >                 >> > 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
> >                 >> > ‘pci_frontend_op)’
> >                 >> > drivers/pci/xen-pcifront.c:375: error: unknown
> >                 field ‘disable_msi’
> >                 >> > 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
> >                 >> > ‘pci_frontend_op)’
> >                 >> > drivers/pci/xen-pcifront.c:376: error: unknown
> >                 field ‘enable_msix’
> >                 >> > 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
> >                 >> > ‘pci_frontend_op)’
> >                 >> > drivers/pci/xen-pcifront.c:377: error: unknown
> >                 field ‘disable_msix’
> >                 >> > specified intializer
> >                 >> > drivers/pci/xen-pcifront.c:377: warning: excess
> >                 elements in struct
> >                 >> > initializer
> >                 >> > drivers/pci/xen-pcifront.c:377: warning: (near
> >                 initialization for
> >                 >> > ‘pci_frontend_op)’
> >                 >> > drivers/pci/xen-pcifront.c: In function â
> >                 €˜pci_frontend_registrar’:
> >                 >> > drivers/pci/xen-pcifront.c:383: error: â
> >                 €˜xen_pci_frontend’ 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
> >
> >
> >
> >
> >
>
>
>

[-- Attachment #1.2: Type: text/html, Size: 12182 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Ian Campbell]

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
> <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
>         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
>         <ritu.kaur.us@gmail.com>
>         > 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
>         >         <linux@eikelenboom.it> 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=/dev/xvda1 ro
>         >                 > console=hvc0 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
>         >                 <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
>         >                 >> 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
>         >                 ‘xen_destroy_irq’
>         >                 >>
>         >
>         > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29: error:
>         >                 >> > previous definition of â
>         €˜xen_destroy_irq’ was
>         >                 here
>         >                 >> > drivers/xen/events.c:637: error:
>         redefinition of
>         >                 ‘xen_create_msi_irq’
>         >                 >>
>         >
>         > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25: error:
>         >                 >> > previous definition of â
>         €˜xen_create_msi_irq’
>         >                 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 â
>         >                 €˜pci_frontend_ops’
>         >                 >> has
>         >                 >> > initializut incomplete type
>         >                 >> > drivers/pci/xen-pcifront.c:374: error:
>         unknown
>         >                 field ‘enable_msi’
>         >                 >> > 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
>         >                 >> > ‘pci_frontend_op)’
>         >                 >> > drivers/pci/xen-pcifront.c:375: error:
>         unknown
>         >                 field ‘disable_msi’
>         >                 >> > 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
>         >                 >> > ‘pci_frontend_op)’
>         >                 >> > drivers/pci/xen-pcifront.c:376: error:
>         unknown
>         >                 field ‘enable_msix’
>         >                 >> > 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
>         >                 >> > ‘pci_frontend_op)’
>         >                 >> > drivers/pci/xen-pcifront.c:377: error:
>         unknown
>         >                 field ‘disable_msix’
>         >                 >> > specified intializer
>         >                 >> > drivers/pci/xen-pcifront.c:377:
>         warning: excess
>         >                 elements in struct
>         >                 >> > initializer
>         >                 >> > drivers/pci/xen-pcifront.c:377:
>         warning: (near
>         >                 initialization for
>         >                 >> > ‘pci_frontend_op)’
>         >                 >> > drivers/pci/xen-pcifront.c: In function
>         â
>         >                 €˜pci_frontend_registrar’:
>         >                 >> > drivers/pci/xen-pcifront.c:383: error:
>         â
>         >                 €˜xen_pci_frontend’ 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
>         >
>         >
>         >
>         >
>         >
>         
>         
>         
> 

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 13083 bytes --]

Thanks Ian, I will take a look at it.

On Mon, Mar 15, 2010 at 6:44 AM, Ian Campbell <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. 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
> > <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
> >         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
> >         <ritu.kaur.us@gmail.com>
> >         > 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
> >         >         <linux@eikelenboom.it> 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=/dev/xvda1 ro
> >         >                 > console=hvc0 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
> >         >                 <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
> >         >                 >> 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
> >         >                 ‘xen_destroy_irq’
> >         >                 >>
> >         >
> >         > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29:
> error:
> >         >                 >> > previous definition of â
> >         €˜xen_destroy_irq’ was
> >         >                 here
> >         >                 >> > drivers/xen/events.c:637: error:
> >         redefinition of
> >         >                 ‘xen_create_msi_irq’
> >         >                 >>
> >         >
> >         > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25:
> error:
> >         >                 >> > previous definition of â
> >         €˜xen_create_msi_irq’
> >         >                 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 â
> >         >                 €˜pci_frontend_ops’
> >         >                 >> has
> >         >                 >> > initializut incomplete type
> >         >                 >> > drivers/pci/xen-pcifront.c:374: error:
> >         unknown
> >         >                 field ‘enable_msi’
> >         >                 >> > 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
> >         >                 >> > ‘pci_frontend_op)’
> >         >                 >> > drivers/pci/xen-pcifront.c:375: error:
> >         unknown
> >         >                 field ‘disable_msi’
> >         >                 >> > 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
> >         >                 >> > ‘pci_frontend_op)’
> >         >                 >> > drivers/pci/xen-pcifront.c:376: error:
> >         unknown
> >         >                 field ‘enable_msix’
> >         >                 >> > 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
> >         >                 >> > ‘pci_frontend_op)’
> >         >                 >> > drivers/pci/xen-pcifront.c:377: error:
> >         unknown
> >         >                 field ‘disable_msix’
> >         >                 >> > specified intializer
> >         >                 >> > drivers/pci/xen-pcifront.c:377:
> >         warning: excess
> >         >                 elements in struct
> >         >                 >> > initializer
> >         >                 >> > drivers/pci/xen-pcifront.c:377:
> >         warning: (near
> >         >                 initialization for
> >         >                 >> > ‘pci_frontend_op)’
> >         >                 >> > drivers/pci/xen-pcifront.c: In function
> >         â
> >         >                 €˜pci_frontend_registrar’:
> >         >                 >> > drivers/pci/xen-pcifront.c:383: error:
> >         â
> >         >                 €˜xen_pci_frontend’ 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
> >         >
> >         >
> >         >
> >         >
> >         >
> >
> >
> >
> >
>
>
>

[-- Attachment #1.2: Type: text/html, Size: 16673 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 14134 bytes --]

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=<uuid-of-vm> 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?

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 Campbell <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. 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
>> > <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
>> >         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
>> >         <ritu.kaur.us@gmail.com>
>> >         > 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
>> >         >         <linux@eikelenboom.it> 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=/dev/xvda1 ro
>> >         >                 > console=hvc0 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
>> >         >                 <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
>> >         >                 >> 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
>> >         >                 ‘xen_destroy_irq’
>> >         >                 >>
>> >         >
>> >         > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29:
>> error:
>> >         >                 >> > previous definition of â
>> >         €˜xen_destroy_irq’ was
>> >         >                 here
>> >         >                 >> > drivers/xen/events.c:637: error:
>> >         redefinition of
>> >         >                 ‘xen_create_msi_irq’
>> >         >                 >>
>> >         >
>> >         > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25:
>> error:
>> >         >                 >> > previous definition of â
>> >         €˜xen_create_msi_irq’
>> >         >                 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 â
>> >         >                 €˜pci_frontend_ops’
>> >         >                 >> has
>> >         >                 >> > initializut incomplete type
>> >         >                 >> > drivers/pci/xen-pcifront.c:374: error:
>> >         unknown
>> >         >                 field ‘enable_msi’
>> >         >                 >> > 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
>> >         >                 >> > ‘pci_frontend_op)’
>> >         >                 >> > drivers/pci/xen-pcifront.c:375: error:
>> >         unknown
>> >         >                 field ‘disable_msi’
>> >         >                 >> > 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
>> >         >                 >> > ‘pci_frontend_op)’
>> >         >                 >> > drivers/pci/xen-pcifront.c:376: error:
>> >         unknown
>> >         >                 field ‘enable_msix’
>> >         >                 >> > 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
>> >         >                 >> > ‘pci_frontend_op)’
>> >         >                 >> > drivers/pci/xen-pcifront.c:377: error:
>> >         unknown
>> >         >                 field ‘disable_msix’
>> >         >                 >> > specified intializer
>> >         >                 >> > drivers/pci/xen-pcifront.c:377:
>> >         warning: excess
>> >         >                 elements in struct
>> >         >                 >> > initializer
>> >         >                 >> > drivers/pci/xen-pcifront.c:377:
>> >         warning: (near
>> >         >                 initialization for
>> >         >                 >> > ‘pci_frontend_op)’
>> >         >                 >> > drivers/pci/xen-pcifront.c: In function
>> >         â
>> >         >                 €˜pci_frontend_registrar’:
>> >         >                 >> > drivers/pci/xen-pcifront.c:383: error:
>> >         â
>> >         >                 €˜xen_pci_frontend’ 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
>> >         >
>> >         >
>> >         >
>> >         >
>> >         >
>> >
>> >
>> >
>> >
>>
>>
>>
>

[-- Attachment #1.2: Type: text/html, Size: 17835 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Ian Campbell]

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=<uuid-of-vm> 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.

Re: domU guest for xcp 0.1.1

[Pasi Kärkkäinen]

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

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 3599 bytes --]

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

[-- Attachment #1.2: Type: text/html, Size: 3911 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 9978 bytes --]

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
 [<c01544f7>] __report_bad_irq+0x27/0x90
 [<c015485c>] note_interrupt+0x2fc/0x330
 [<f01df92d>] ? usb_hcd_irq+0x4d/0xe0 [usbcore]
 [<c0153931>] ? handle_IRQ_event+0x31/0x90
 [<c01551e4>] handle_level_irq+0xe4/0x110
 [<c0107733>] do_IRQ+0x43/0x90
 [<c01413b9>] ? ktime_get+0x19/0x40
 [<c026cfcf>] evtchn_do_upcall+0xdf/0x1f0
 [<c0105565>] hypervisor_callback+0x41/0x49
 [<c010797b>] ? xen_safe_halt+0x8b/0xc0
 [<c010afde>] xen_idle+0x1e/0x50
 [<c0103728>] cpu_idle+0x58/0xa0
 [<c0338f4e>] rest_init+0x4e/0x60
 =======================
handlers:
[<f01df8e0>] (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]  [<c11f2db1>] ? dev_watchdog+0xf8/0x188
[  287.816135]  [<c11f2db1>] ? dev_watchdog+0xf8/0x188
[  287.816143]  [<c1037a1b>] ? warn_slowpath_common+0x5e/0x8a
[  287.816151]  [<c1037a79>] ? warn_slowpath_fmt+0x26/0x2a
[  287.816159]  [<c11f2db1>] ? dev_watchdog+0xf8/0x188
[  287.816168]  [<c100665c>] ? check_events+0x8/0xc
[  287.816175]  [<c1005ff4>] ? xen_force_evtchn_callback+0xc/0x10
[  287.816183]  [<c100665c>] ? check_events+0x8/0xc
[  287.816191]  [<c1006653>] ? xen_restore_fl_direct_end+0x0/0x1
[  287.816200]  [<c124f4ea>] ? _spin_unlock_irqrestore+0xe/0x10
[  287.816209]  [<c1042a74>] ? mod_timer+0x15f/0x168
[  287.816217]  [<c11f2cb9>] ? dev_watchdog+0x0/0x188
[  287.816224]  [<c104263c>] ? run_timer_softirq+0x195/0x217
[  287.816232]  [<c103cb18>] ? __do_softirq+0xaa/0x151
[  287.816240]  [<c103cbf0>] ? do_softirq+0x31/0x3c
[  287.816247]  [<c103ccc6>] ? irq_exit+0x26/0x58
[  287.816256]  [<c118f14b>] ? xen_evtchn_do_upcall+0x13f/0x151
[  287.816264]  [<c1009087>] ? xen_do_upcall+0x7/0xc
[  287.816272]  [<c10023a7>] ? hypercall_page+0x3a7/0x1001
[  287.816280]  [<c1006075>] ? xen_safe_halt+0xf/0x1b
[  287.816287]  [<c1004083>] ? xen_idle+0x23/0x30
[  287.816295]  [<c100773c>] ? cpu_idle+0x46/0x62
[  287.816303]  [<c136e7e0>] ? start_kernel+0x2c7/0x2ca
[  287.816310]  [<c1370d33>] ? 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]  [<c1052d6d>] ? ktime_get_ts+0xd7/0xdf
[  480.052154]  [<c124e1eb>] ? io_schedule+0x5f/0x98
[  480.052162]  [<c10d49a2>] ? sync_buffer+0x30/0x33
[  480.052169]  [<c124e645>] ? __wait_on_bit+0x33/0x58
[  480.052176]  [<c10d4972>] ? sync_buffer+0x0/0x33
[  480.052183]  [<c124e720>] ? out_of_line_wait_on_bit+0xb6/0xbe
[  480.052190]  [<c10d4972>] ? sync_buffer+0x0/0x33
[  480.052198]  [<c104b97f>] ? wake_bit_function+0x0/0x3c
[  480.052205]  [<c10d493f>] ? __wait_on_buffer+0x16/0x18
[  480.052223]  [<d084622d>] ? journal_commit_transaction+0x85a/0xd6d [jbd]
[  480.052235]  [<c10323bf>] ? finish_task_switch+0x3d/0x9c
[  480.052243]  [<c100665c>] ? check_events+0x8/0xc
[  480.052250]  [<c1006653>] ? xen_restore_fl_direct_end+0x0/0x1
[  480.052258]  [<c124f4ea>] ? _spin_unlock_irqrestore+0xe/0x10
[  480.052267]  [<c1042c5a>] ? try_to_del_timer_sync+0x79/0x80
[  480.052276]  [<d0848b6f>] ? kjournald+0xbb/0x1e5 [jbd]
[  480.052283]  [<c104b952>] ? autoremove_wake_function+0x0/0x2d
[  480.052292]  [<d0848ab4>] ? kjournald+0x0/0x1e5 [jbd]
[  480.052299]  [<c104b71e>] ? kthread+0x61/0x66
[  480.052305]  [<c104b6bd>] ? kthread+0x0/0x66
[  480.052313]  [<c1009037>] ? 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]  [<d0877650>] ? __ext3_get_inode_loc+0xc7/0x275 [ext3]
[  480.052426]  [<c1005ff4>] ? xen_force_evtchn_callback+0xc/0x10
[  480.052434]  [<c100665c>] ? check_events+0x8/0xc
[  480.052442]  [<d0845072>] ? do_get_write_access+0x1f8/0x3b5 [jbd]
[  480.052450]  [<c104b97f>] ? wake_bit_function+0x0/0x3c
[  480.052459]  [<d0845247>] ? journal_get_write_access+0x18/0x26 [jbd]
[  480.052469]  [<d0882caf>] ? __ext3_journal_get_write_access+0x13/0x32
[ext3]
[  480.052479]  [<d0877baf>] ? ext3_reserve_inode_write+0x2d/0x5d [ext3]
[  480.052489]  [<d0877bf0>] ? ext3_mark_inode_dirty+0x11/0x27 [ext3]
[  480.052499]  [<d0877d05>] ? ext3_dirty_inode+0x50/0x63 [ext3]
[  480.052507]  [<c10cf541>] ? __mark_inode_dirty+0x20/0x10c
[  480.052515]  [<c10c7bc5>] ? file_update_time+0xbe/0xdf
[  480.052523]  [<c109107b>] ? __generic_file_aio_write+0x2f7/0x452
[  480.052531]  [<c1006653>] ? xen_restore_fl_direct_end+0x0/0x1
[  480.052539]  [<c124f4ea>] ? _spin_unlock_irqrestore+0xe/0x10
[  480.052546]  [<c104e617>] ? hrtimer_try_to_cancel+0x6e/0x83
[  480.052554]  [<c104e625>] ? hrtimer_try_to_cancel+0x7c/0x83
[  480.052561]  [<c1091227>] ? generic_file_aio_write+0x51/0x93
[  480.052571]  [<c10b8680>] ? do_sync_write+0xc0/0x107
[  480.052578]  [<c104b952>] ? autoremove_wake_function+0x0/0x2d
[  480.052586]  [<c102dd9e>] ? pick_next_task_fair+0x95/0x9c
[  480.052593]  [<c124e105>] ? schedule+0x5ea/0x671
[  480.052601]  [<c1107ae8>] ? security_file_permission+0xc/0xd
[  480.052609]  [<c10b85c0>] ? do_sync_write+0x0/0x107
[  480.052616]  [<c10b900b>] ? vfs_write+0x84/0x12f
[  480.052623]  [<c10b914e>] ? sys_write+0x3c/0x63
[  480.052630]  [<c10084b4>] ? sysenter_do_call+0x12/0x28

[-- Attachment #1.2: Type: text/html, Size: 11306 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Ian Campbell]

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
>  [<c01544f7>] __report_bad_irq+0x27/0x90
>  [<c015485c>] note_interrupt+0x2fc/0x330
>  [<f01df92d>] ? usb_hcd_irq+0x4d/0xe0 [usbcore]
>  [<c0153931>] ? handle_IRQ_event+0x31/0x90
>  [<c01551e4>] handle_level_irq+0xe4/0x110
>  [<c0107733>] do_IRQ+0x43/0x90
>  [<c01413b9>] ? ktime_get+0x19/0x40
>  [<c026cfcf>] evtchn_do_upcall+0xdf/0x1f0
>  [<c0105565>] hypervisor_callback+0x41/0x49
>  [<c010797b>] ? xen_safe_halt+0x8b/0xc0
>  [<c010afde>] xen_idle+0x1e/0x50
>  [<c0103728>] cpu_idle+0x58/0xa0
>  [<c0338f4e>] rest_init+0x4e/0x60
>  =======================
> handlers:
> [<f01df8e0>] (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]  [<c11f2db1>] ? dev_watchdog+0xf8/0x188
> [  287.816135]  [<c11f2db1>] ? dev_watchdog+0xf8/0x188
> [  287.816143]  [<c1037a1b>] ? warn_slowpath_common+0x5e/0x8a
> [  287.816151]  [<c1037a79>] ? warn_slowpath_fmt+0x26/0x2a
> [  287.816159]  [<c11f2db1>] ? dev_watchdog+0xf8/0x188
> [  287.816168]  [<c100665c>] ? check_events+0x8/0xc
> [  287.816175]  [<c1005ff4>] ? xen_force_evtchn_callback+0xc/0x10
> [  287.816183]  [<c100665c>] ? check_events+0x8/0xc
> [  287.816191]  [<c1006653>] ? xen_restore_fl_direct_end+0x0/0x1
> [  287.816200]  [<c124f4ea>] ? _spin_unlock_irqrestore+0xe/0x10
> [  287.816209]  [<c1042a74>] ? mod_timer+0x15f/0x168
> [  287.816217]  [<c11f2cb9>] ? dev_watchdog+0x0/0x188
> [  287.816224]  [<c104263c>] ? run_timer_softirq+0x195/0x217
> [  287.816232]  [<c103cb18>] ? __do_softirq+0xaa/0x151
> [  287.816240]  [<c103cbf0>] ? do_softirq+0x31/0x3c
> [  287.816247]  [<c103ccc6>] ? irq_exit+0x26/0x58
> [  287.816256]  [<c118f14b>] ? xen_evtchn_do_upcall+0x13f/0x151
> [  287.816264]  [<c1009087>] ? xen_do_upcall+0x7/0xc
> [  287.816272]  [<c10023a7>] ? hypercall_page+0x3a7/0x1001
> [  287.816280]  [<c1006075>] ? xen_safe_halt+0xf/0x1b
> [  287.816287]  [<c1004083>] ? xen_idle+0x23/0x30
> [  287.816295]  [<c100773c>] ? cpu_idle+0x46/0x62
> [  287.816303]  [<c136e7e0>] ? start_kernel+0x2c7/0x2ca
> [  287.816310]  [<c1370d33>] ? 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]  [<c1052d6d>] ? ktime_get_ts+0xd7/0xdf
> [  480.052154]  [<c124e1eb>] ? io_schedule+0x5f/0x98
> [  480.052162]  [<c10d49a2>] ? sync_buffer+0x30/0x33
> [  480.052169]  [<c124e645>] ? __wait_on_bit+0x33/0x58
> [  480.052176]  [<c10d4972>] ? sync_buffer+0x0/0x33
> [  480.052183]  [<c124e720>] ? out_of_line_wait_on_bit+0xb6/0xbe
> [  480.052190]  [<c10d4972>] ? sync_buffer+0x0/0x33
> [  480.052198]  [<c104b97f>] ? wake_bit_function+0x0/0x3c
> [  480.052205]  [<c10d493f>] ? __wait_on_buffer+0x16/0x18
> [  480.052223]  [<d084622d>] ? journal_commit_transaction+0x85a/0xd6d
> [jbd]
> [  480.052235]  [<c10323bf>] ? finish_task_switch+0x3d/0x9c
> [  480.052243]  [<c100665c>] ? check_events+0x8/0xc
> [  480.052250]  [<c1006653>] ? xen_restore_fl_direct_end+0x0/0x1
> [  480.052258]  [<c124f4ea>] ? _spin_unlock_irqrestore+0xe/0x10
> [  480.052267]  [<c1042c5a>] ? try_to_del_timer_sync+0x79/0x80
> [  480.052276]  [<d0848b6f>] ? kjournald+0xbb/0x1e5 [jbd]
> [  480.052283]  [<c104b952>] ? autoremove_wake_function+0x0/0x2d
> [  480.052292]  [<d0848ab4>] ? kjournald+0x0/0x1e5 [jbd]
> [  480.052299]  [<c104b71e>] ? kthread+0x61/0x66
> [  480.052305]  [<c104b6bd>] ? kthread+0x0/0x66
> [  480.052313]  [<c1009037>] ? 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]  [<d0877650>] ? __ext3_get_inode_loc+0xc7/0x275 [ext3]
> [  480.052426]  [<c1005ff4>] ? xen_force_evtchn_callback+0xc/0x10
> [  480.052434]  [<c100665c>] ? check_events+0x8/0xc
> [  480.052442]  [<d0845072>] ? do_get_write_access+0x1f8/0x3b5 [jbd]
> [  480.052450]  [<c104b97f>] ? wake_bit_function+0x0/0x3c
> [  480.052459]  [<d0845247>] ? journal_get_write_access+0x18/0x26
> [jbd]
> [  480.052469]  [<d0882caf>] ? __ext3_journal_get_write_access
> +0x13/0x32 [ext3]
> [  480.052479]  [<d0877baf>] ? ext3_reserve_inode_write+0x2d/0x5d
> [ext3]
> [  480.052489]  [<d0877bf0>] ? ext3_mark_inode_dirty+0x11/0x27 [ext3]
> [  480.052499]  [<d0877d05>] ? ext3_dirty_inode+0x50/0x63 [ext3]
> [  480.052507]  [<c10cf541>] ? __mark_inode_dirty+0x20/0x10c
> [  480.052515]  [<c10c7bc5>] ? file_update_time+0xbe/0xdf
> [  480.052523]  [<c109107b>] ? __generic_file_aio_write+0x2f7/0x452
> [  480.052531]  [<c1006653>] ? xen_restore_fl_direct_end+0x0/0x1
> [  480.052539]  [<c124f4ea>] ? _spin_unlock_irqrestore+0xe/0x10
> [  480.052546]  [<c104e617>] ? hrtimer_try_to_cancel+0x6e/0x83
> [  480.052554]  [<c104e625>] ? hrtimer_try_to_cancel+0x7c/0x83
> [  480.052561]  [<c1091227>] ? generic_file_aio_write+0x51/0x93
> [  480.052571]  [<c10b8680>] ? do_sync_write+0xc0/0x107
> [  480.052578]  [<c104b952>] ? autoremove_wake_function+0x0/0x2d
> [  480.052586]  [<c102dd9e>] ? pick_next_task_fair+0x95/0x9c
> [  480.052593]  [<c124e105>] ? schedule+0x5ea/0x671
> [  480.052601]  [<c1107ae8>] ? security_file_permission+0xc/0xd
> [  480.052609]  [<c10b85c0>] ? do_sync_write+0x0/0x107
> [  480.052616]  [<c10b900b>] ? vfs_write+0x84/0x12f
> [  480.052623]  [<c10b914e>] ? sys_write+0x3c/0x63
> [  480.052630]  [<c10084b4>] ? sysenter_do_call+0x12/0x28
> 
> 
> 
> 
> 
> 

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 12713 bytes --]

Hi Ian.

 pcifront_handler_aer is the callback function.

...
err = bind_evtchn_to_irqhandler(pdev->evtchn, pcifront_handler_aer,
                0, "pcifront", pdev);
        if (err < 0) {
                xenbus_free_evtchn(pdev->xdev, pdev->evtchn);
                xenbus_dev_fatal(pdev->xdev, err, "Failed to bind evtchn to
"
                                 "irqhandler.\n");
                return err;
        }
...

In pcifront_handler_aer, schedule_pcifront_aer_op is called.

irqreturn_t pcifront_handler_aer(int irq, void *dev)
{
        struct pcifront_device *pdev = dev;
        schedule_pcifront_aer_op(pdev);
        return IRQ_HANDLED;
}

So I am assuming it is called during normal path as well.

Yes my nic device is sharing interrupts(IRQ17) with usb and ide devices in
dom0.

cat /proc/interrupts in domU shows interrupts are never received by the
interface(probably confirmed that pcifront itself doesn't receive
interrupts). I am only passing 0000:08:01.0 nic device to a domU. It shares
IRQ 17 with usb/ide devices in dom0.

Thanks

On Thu, Mar 18, 2010 at 2:17 AM, Ian Campbell <Ian.Campbell@citrix.com>wrote:

> 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
> >  [<c01544f7>] __report_bad_irq+0x27/0x90
> >  [<c015485c>] note_interrupt+0x2fc/0x330
> >  [<f01df92d>] ? usb_hcd_irq+0x4d/0xe0 [usbcore]
> >  [<c0153931>] ? handle_IRQ_event+0x31/0x90
> >  [<c01551e4>] handle_level_irq+0xe4/0x110
> >  [<c0107733>] do_IRQ+0x43/0x90
> >  [<c01413b9>] ? ktime_get+0x19/0x40
> >  [<c026cfcf>] evtchn_do_upcall+0xdf/0x1f0
> >  [<c0105565>] hypervisor_callback+0x41/0x49
> >  [<c010797b>] ? xen_safe_halt+0x8b/0xc0
> >  [<c010afde>] xen_idle+0x1e/0x50
> >  [<c0103728>] cpu_idle+0x58/0xa0
> >  [<c0338f4e>] rest_init+0x4e/0x60
> >  =======================
> > handlers:
> > [<f01df8e0>] (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]  [<c11f2db1>] ? dev_watchdog+0xf8/0x188
> > [  287.816135]  [<c11f2db1>] ? dev_watchdog+0xf8/0x188
> > [  287.816143]  [<c1037a1b>] ? warn_slowpath_common+0x5e/0x8a
> > [  287.816151]  [<c1037a79>] ? warn_slowpath_fmt+0x26/0x2a
> > [  287.816159]  [<c11f2db1>] ? dev_watchdog+0xf8/0x188
> > [  287.816168]  [<c100665c>] ? check_events+0x8/0xc
> > [  287.816175]  [<c1005ff4>] ? xen_force_evtchn_callback+0xc/0x10
> > [  287.816183]  [<c100665c>] ? check_events+0x8/0xc
> > [  287.816191]  [<c1006653>] ? xen_restore_fl_direct_end+0x0/0x1
> > [  287.816200]  [<c124f4ea>] ? _spin_unlock_irqrestore+0xe/0x10
> > [  287.816209]  [<c1042a74>] ? mod_timer+0x15f/0x168
> > [  287.816217]  [<c11f2cb9>] ? dev_watchdog+0x0/0x188
> > [  287.816224]  [<c104263c>] ? run_timer_softirq+0x195/0x217
> > [  287.816232]  [<c103cb18>] ? __do_softirq+0xaa/0x151
> > [  287.816240]  [<c103cbf0>] ? do_softirq+0x31/0x3c
> > [  287.816247]  [<c103ccc6>] ? irq_exit+0x26/0x58
> > [  287.816256]  [<c118f14b>] ? xen_evtchn_do_upcall+0x13f/0x151
> > [  287.816264]  [<c1009087>] ? xen_do_upcall+0x7/0xc
> > [  287.816272]  [<c10023a7>] ? hypercall_page+0x3a7/0x1001
> > [  287.816280]  [<c1006075>] ? xen_safe_halt+0xf/0x1b
> > [  287.816287]  [<c1004083>] ? xen_idle+0x23/0x30
> > [  287.816295]  [<c100773c>] ? cpu_idle+0x46/0x62
> > [  287.816303]  [<c136e7e0>] ? start_kernel+0x2c7/0x2ca
> > [  287.816310]  [<c1370d33>] ? 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]  [<c1052d6d>] ? ktime_get_ts+0xd7/0xdf
> > [  480.052154]  [<c124e1eb>] ? io_schedule+0x5f/0x98
> > [  480.052162]  [<c10d49a2>] ? sync_buffer+0x30/0x33
> > [  480.052169]  [<c124e645>] ? __wait_on_bit+0x33/0x58
> > [  480.052176]  [<c10d4972>] ? sync_buffer+0x0/0x33
> > [  480.052183]  [<c124e720>] ? out_of_line_wait_on_bit+0xb6/0xbe
> > [  480.052190]  [<c10d4972>] ? sync_buffer+0x0/0x33
> > [  480.052198]  [<c104b97f>] ? wake_bit_function+0x0/0x3c
> > [  480.052205]  [<c10d493f>] ? __wait_on_buffer+0x16/0x18
> > [  480.052223]  [<d084622d>] ? journal_commit_transaction+0x85a/0xd6d
> > [jbd]
> > [  480.052235]  [<c10323bf>] ? finish_task_switch+0x3d/0x9c
> > [  480.052243]  [<c100665c>] ? check_events+0x8/0xc
> > [  480.052250]  [<c1006653>] ? xen_restore_fl_direct_end+0x0/0x1
> > [  480.052258]  [<c124f4ea>] ? _spin_unlock_irqrestore+0xe/0x10
> > [  480.052267]  [<c1042c5a>] ? try_to_del_timer_sync+0x79/0x80
> > [  480.052276]  [<d0848b6f>] ? kjournald+0xbb/0x1e5 [jbd]
> > [  480.052283]  [<c104b952>] ? autoremove_wake_function+0x0/0x2d
> > [  480.052292]  [<d0848ab4>] ? kjournald+0x0/0x1e5 [jbd]
> > [  480.052299]  [<c104b71e>] ? kthread+0x61/0x66
> > [  480.052305]  [<c104b6bd>] ? kthread+0x0/0x66
> > [  480.052313]  [<c1009037>] ? 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]  [<d0877650>] ? __ext3_get_inode_loc+0xc7/0x275 [ext3]
> > [  480.052426]  [<c1005ff4>] ? xen_force_evtchn_callback+0xc/0x10
> > [  480.052434]  [<c100665c>] ? check_events+0x8/0xc
> > [  480.052442]  [<d0845072>] ? do_get_write_access+0x1f8/0x3b5 [jbd]
> > [  480.052450]  [<c104b97f>] ? wake_bit_function+0x0/0x3c
> > [  480.052459]  [<d0845247>] ? journal_get_write_access+0x18/0x26
> > [jbd]
> > [  480.052469]  [<d0882caf>] ? __ext3_journal_get_write_access
> > +0x13/0x32 [ext3]
> > [  480.052479]  [<d0877baf>] ? ext3_reserve_inode_write+0x2d/0x5d
> > [ext3]
> > [  480.052489]  [<d0877bf0>] ? ext3_mark_inode_dirty+0x11/0x27 [ext3]
> > [  480.052499]  [<d0877d05>] ? ext3_dirty_inode+0x50/0x63 [ext3]
> > [  480.052507]  [<c10cf541>] ? __mark_inode_dirty+0x20/0x10c
> > [  480.052515]  [<c10c7bc5>] ? file_update_time+0xbe/0xdf
> > [  480.052523]  [<c109107b>] ? __generic_file_aio_write+0x2f7/0x452
> > [  480.052531]  [<c1006653>] ? xen_restore_fl_direct_end+0x0/0x1
> > [  480.052539]  [<c124f4ea>] ? _spin_unlock_irqrestore+0xe/0x10
> > [  480.052546]  [<c104e617>] ? hrtimer_try_to_cancel+0x6e/0x83
> > [  480.052554]  [<c104e625>] ? hrtimer_try_to_cancel+0x7c/0x83
> > [  480.052561]  [<c1091227>] ? generic_file_aio_write+0x51/0x93
> > [  480.052571]  [<c10b8680>] ? do_sync_write+0xc0/0x107
> > [  480.052578]  [<c104b952>] ? autoremove_wake_function+0x0/0x2d
> > [  480.052586]  [<c102dd9e>] ? pick_next_task_fair+0x95/0x9c
> > [  480.052593]  [<c124e105>] ? schedule+0x5ea/0x671
> > [  480.052601]  [<c1107ae8>] ? security_file_permission+0xc/0xd
> > [  480.052609]  [<c10b85c0>] ? do_sync_write+0x0/0x107
> > [  480.052616]  [<c10b900b>] ? vfs_write+0x84/0x12f
> > [  480.052623]  [<c10b914e>] ? sys_write+0x3c/0x63
> > [  480.052630]  [<c10084b4>] ? sysenter_do_call+0x12/0x28
> >
> >
> >
> >
> >
> >
>
>
>

[-- Attachment #1.2: Type: text/html, Size: 15265 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Ian Campbell]

On Thu, 2010-03-18 at 13:43 +0000, Ritu kaur wrote:
> Hi Ian.
> 
>  pcifront_handler_aer is the callback function.

This is not the same interrupt/evtchn as your device's interrupt though.
This is the PCI error handling notification interrupt (PCI AER is PCI
Advanced Error Reporting).

[...]

> Yes my nic device is sharing interrupts(IRQ17) with usb and ide
> devices in dom0. 

This may be your problem, I don't know if this is expected to work or
not.

You could experiment with another device which doesn't share an
interrupt, just to check that the basic mechanism is working.

Ian.

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 1155 bytes --]

Thanks Ian, could you please clarify me how are interrupts handled for pci
passthrough device. I thought it is delivered via evtchn from pciback to
pcifront i.e
InterruptDescTable->Hypervisor->pciback->pcifront->actual_device is this
correct?

IRQ is 11 in dom0 for nic device but after driver for nic is loaded in domU
IRQ is changed to 17. When you say try with another device should I try with
another nic device or someother device?

Thanks


On Thu, Mar 18, 2010 at 7:11 AM, Ian Campbell <Ian.Campbell@citrix.com>wrote:

> On Thu, 2010-03-18 at 13:43 +0000, Ritu kaur wrote:
> > Hi Ian.
> >
> >  pcifront_handler_aer is the callback function.
>
> This is not the same interrupt/evtchn as your device's interrupt though.
> This is the PCI error handling notification interrupt (PCI AER is PCI
> Advanced Error Reporting).
>
> [...]
>
> > Yes my nic device is sharing interrupts(IRQ17) with usb and ide
> > devices in dom0.
>
> This may be your problem, I don't know if this is expected to work or
> not.
>
> You could experiment with another device which doesn't share an
> interrupt, just to check that the basic mechanism is working.
>
> Ian.
>
>
>

[-- Attachment #1.2: Type: text/html, Size: 1625 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Ian Campbell]

On Thu, 2010-03-18 at 14:23 +0000, Ritu kaur wrote:
> Thanks Ian, could you please clarify me how are interrupts handled for
> pci passthrough device. I thought it is delivered via evtchn from
> pciback to pcifront i.e
> InterruptDescTable->Hypervisor->pciback->pcifront->actual_device is
> this correct?

Yes, but not on the event channel you found previously, there is a
separate one for each device IRQ.

> IRQ is 11 in dom0 for nic device but after driver for nic is loaded in
> domU IRQ is changed to 17.

That's expected, there isn't really any relationship between the IRQ
assignment in the guest and domain 0.

>  When you say try with another device should I try with another nic
> device or someother device?

Any device which doesn't share an IRQ with another, it doesn't really
matter what sort of device it is. NICs are often a convenient choice
since they are relatively easy to confirm they are working.

Ian.

> 
> Thanks
> 
> 
> On Thu, Mar 18, 2010 at 7:11 AM, Ian Campbell
> <Ian.Campbell@citrix.com> wrote:
>         On Thu, 2010-03-18 at 13:43 +0000, Ritu kaur wrote:
>         > Hi Ian.
>         >
>         >  pcifront_handler_aer is the callback function.
>         
>         
>         This is not the same interrupt/evtchn as your device's
>         interrupt though.
>         This is the PCI error handling notification interrupt (PCI AER
>         is PCI
>         Advanced Error Reporting).
>         
>         [...]
>         
>         > Yes my nic device is sharing interrupts(IRQ17) with usb and
>         ide
>         > devices in dom0.
>         
>         
>         This may be your problem, I don't know if this is expected to
>         work or
>         not.
>         
>         You could experiment with another device which doesn't share
>         an
>         interrupt, just to check that the basic mechanism is working.
>         
>         Ian.
>         
>         
> 

Re: domU guest for xcp 0.1.1

[Ian Campbell]

On Thu, 2010-03-18 at 14:27 +0000, Ian Campbell wrote:
> On Thu, 2010-03-18 at 14:23 +0000, Ritu kaur wrote:
> > Thanks Ian, could you please clarify me how are interrupts handled
> for
> > pci passthrough device. I thought it is delivered via evtchn from
> > pciback to pcifront i.e
> > InterruptDescTable->Hypervisor->pciback->pcifront->actual_device is
> > this correct?
> 
> Yes, but not on the event channel you found previously, there is a
> separate one for each device IRQ. 

Actually, not quite. pciback sets up an evtchn which pcifront binds to
but pciback then arranges for the hypervisor to directly inject the
interrupt on that event channel rather than bouncing through pciback for
every interrupt so the actual path is more like:

InterruptDescTable->Hypervisor->pcifront->actual_device

And really once the device is setup pcifront isn't really involved
either, the interrupt goes straight from the event channel to the device
driver's interrupt handlerm pciback doesn't do anything for this part.

Ian.

Re: domU guest for xcp 0.1.1

[Konrad Rzeszutek Wilk]

> > Yes my nic device is sharing interrupts(IRQ17) with usb and ide
> > devices in dom0. 
> 
> This may be your problem, I don't know if this is expected to work or
> not.

Oh yeah. That got fixed in the xen/next (or rather in the
pv/pcifront-2.6.32 branch and pv/pciback-2.6.32).

It should work with the newer kernel (xen/next from Jeremy's PV-OPS git
tree).

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 596 bytes --]

Thanks Ian for clarification on interrupt handling mechanism.

Thanks Konrad. Should I use xen/next in dom0 or domU?

Thanks

On Thu, Mar 18, 2010 at 7:39 AM, Konrad Rzeszutek Wilk <
konrad.wilk@oracle.com> wrote:

> > > Yes my nic device is sharing interrupts(IRQ17) with usb and ide
> > > devices in dom0.
> >
> > This may be your problem, I don't know if this is expected to work or
> > not.
>
> Oh yeah. That got fixed in the xen/next (or rather in the
> pv/pcifront-2.6.32 branch and pv/pciback-2.6.32).
>
> It should work with the newer kernel (xen/next from Jeremy's PV-OPS git
> tree).
>

[-- Attachment #1.2: Type: text/html, Size: 955 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Konrad Rzeszutek Wilk]

On Thu, Mar 18, 2010 at 08:28:18AM -0700, Ritu kaur wrote:
> Thanks Ian for clarification on interrupt handling mechanism.
> 
> Thanks Konrad. Should I use xen/next in dom0 or domU?

Both.

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 883 bytes --]

Thanks Konrad. I downloaded kernel code from  xen/next. I believe this
requires 3.4.3 or 4.0.0 xen hypervisor code, I downloaded xen hypervisor
from xenbits.xensource.com/xen-unstable.hg. For xcp dom0 all compilation
happens in DDK and no make utility is available and as I understand I need
to execute make install-* in dom0. For install-xen probably I can copy
xen.gz into /boot and modify files to reflect that but I am not sure what's
the needed to install tools and stubdom in xcp dom0?

make xen
make tools
make stubdom

make install-xen
make install-tools
make install-stubdom

Thanks

On Thu, Mar 18, 2010 at 9:26 AM, Konrad Rzeszutek Wilk <
konrad.wilk@oracle.com> wrote:

> On Thu, Mar 18, 2010 at 08:28:18AM -0700, Ritu kaur wrote:
> > Thanks Ian for clarification on interrupt handling mechanism.
> >
> > Thanks Konrad. Should I use xen/next in dom0 or domU?
>
> Both.
>

[-- Attachment #1.2: Type: text/html, Size: 1297 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 1545 bytes --]

with 3.4.3 xen and kernel code from Jeremy's xen/next puts dom0 into
continuous reboot mode.

1. downloaded xen/next code into DDK and generated tar-pkg, it generates
linux-2.6.32.tar. Copied this tar file into root directory of dom0 and
extracted the file.

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

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

Thanks

On Fri, Mar 19, 2010 at 8:27 AM, Ritu kaur <ritu.kaur.us@gmail.com> wrote:

> Thanks Konrad. I downloaded kernel code from  xen/next. I believe this
> requires 3.4.3 or 4.0.0 xen hypervisor code, I downloaded xen hypervisor
> from xenbits.xensource.com/xen-unstable.hg. For xcp dom0 all compilation
> happens in DDK and no make utility is available and as I understand I need
> to execute make install-* in dom0. For install-xen probably I can copy
> xen.gz into /boot and modify files to reflect that but I am not sure what's
> the needed to install tools and stubdom in xcp dom0?
>
> make xen
> make tools
> make stubdom
>
> make install-xen
> make install-tools
> make install-stubdom
>
> Thanks
>
>
> On Thu, Mar 18, 2010 at 9:26 AM, Konrad Rzeszutek Wilk <
> konrad.wilk@oracle.com> wrote:
>
>> On Thu, Mar 18, 2010 at 08:28:18AM -0700, Ritu kaur wrote:
>> > Thanks Ian for clarification on interrupt handling mechanism.
>> >
>> > Thanks Konrad. Should I use xen/next in dom0 or domU?
>>
>> Both.
>>
>
>

[-- Attachment #1.2: Type: text/html, Size: 2362 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 2436 bytes --]

Hi,

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

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

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

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

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

Thanks

On Sat, Mar 20, 2010 at 6:50 PM, Ritu kaur <ritu.kaur.us@gmail.com> wrote:

> with 3.4.3 xen and kernel code from Jeremy's xen/next puts dom0 into
> continuous reboot mode.
>
> 1. downloaded xen/next code into DDK and generated tar-pkg, it generates
> linux-2.6.32.tar. Copied this tar file into root directory of dom0 and
> extracted the file.
>
> 2. Copied xen code from http://xenbits.xensource.com/xen-3.4-testing.hginto DDK and did "make xen", copied xen.3.4.3.gz into /boot of dom0.
>
> modified extlinux.conf to point to new vmlinuz and xen. dom0 is in
> continuous reboot mode, let me know what am I doing wrong?
>
> Thanks
>
>
> On Fri, Mar 19, 2010 at 8:27 AM, Ritu kaur <ritu.kaur.us@gmail.com> wrote:
>
>> Thanks Konrad. I downloaded kernel code from  xen/next. I believe this
>> requires 3.4.3 or 4.0.0 xen hypervisor code, I downloaded xen hypervisor
>> from xenbits.xensource.com/xen-unstable.hg. For xcp dom0 all compilation
>> happens in DDK and no make utility is available and as I understand I need
>> to execute make install-* in dom0. For install-xen probably I can copy
>> xen.gz into /boot and modify files to reflect that but I am not sure what's
>> the needed to install tools and stubdom in xcp dom0?
>>
>> make xen
>> make tools
>> make stubdom
>>
>> make install-xen
>> make install-tools
>> make install-stubdom
>>
>> Thanks
>>
>>
>> On Thu, Mar 18, 2010 at 9:26 AM, Konrad Rzeszutek Wilk <
>> konrad.wilk@oracle.com> wrote:
>>
>>> On Thu, Mar 18, 2010 at 08:28:18AM -0700, Ritu kaur wrote:
>>> > Thanks Ian for clarification on interrupt handling mechanism.
>>> >
>>> > Thanks Konrad. Should I use xen/next in dom0 or domU?
>>>
>>> Both.
>>>
>>
>>
>

[-- Attachment #1.2: Type: text/html, Size: 3635 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Pasi Kärkkäinen]

On Sun, Mar 21, 2010 at 10:22:06AM -0700, Ritu kaur wrote:
>    Hi,
> 
>    I am running out of options to test pci passthrough with shared
>    interrupts, since xen/next kernel doesn't work with xcp0.1.1 dom0. I tried
>    couple of combinations
> 
>    1. xen 3.4.3 with xen/next kernel, dom0 continuous reboot, boot messages
>    goes off pretty fast so not sure what's going wrong here.
> 

You need to set up a serial console so you can capture the boot messages:
http://wiki.xensource.com/xenwiki/XenSerialConsole

>    2. xen 3.4.3 with 2.6.27.42-0.1.1.xs0.1.1.737.1065xen(i.e which comes with
>    xcp 0.1.1 default) system boots fine.
> 
>    3. Assuming "1" is related to wrong .config file, copied
>    kernel-2.6.27.42-0.1.1.xs0.1.1.737.1065-i686-xen.config which comes with
>    dom0 kernel code, compiled and still same result as "1".
> 

You can't really use the "xenlinux" kernel-2.6.27.42-0.1.1.xs0.1.1.737.1065-i686-xen.config
with a pvops dom0 kernel. They're different kernels with different .config options.

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

Set up the serial console and figure out why xen/next pvops dom0 kernel doesn't boot for you.

Make sure you have these options for the dom0 kernel:
console=hvc0 earlyprintk=xen nomodeset

More help here:
http://wiki.xensource.com/xenwiki/XenParavirtOps

-- Pasi

>    Thanks
> 
>    On Sat, Mar 20, 2010 at 6:50 PM, Ritu kaur <[1]ritu.kaur.us@[2]gmail.com>
>    wrote:
> 
>      with 3.4.3 xen and kernel code from Jeremy's xen/next puts dom0 into
>      continuous reboot mode.
> 
>      1. downloaded xen/next code into DDK and generated tar-pkg, it generates
>      linux-2.6.32.tar. Copied this tar file into root directory of dom0 and
>      extracted the file.
> 
>      2. Copied xen code from
>      [3]http://xenbits.xensource.com/xen-3.4-testing.hg into DDK and did
>      "make xen", copied xen.3.4.3.gz into /boot of dom0.
> 
>      modified extlinux.conf to point to new vmlinuz and xen. dom0 is in
>      continuous reboot mode, let me know what am I doing wrong?
> 
>      Thanks
> 
>      On Fri, Mar 19, 2010 at 8:27 AM, Ritu kaur
>      <[4]ritu.kaur.us@[5]gmail.com> wrote:
> 
>        Thanks Konrad. I downloaded kernel code from  xen/next. I believe this
>        requires 3.4.3 or 4.0.0 xen hypervisor code, I downloaded xen
>        hypervisor from [6]xenbits.xensource.com/xen-unstable.hg. For xcp dom0
>        all compilation happens in DDK and no make utility is available and as
>        I understand I need to execute make install-* in dom0. For install-xen
>        probably I can copy xen.gz into /boot and modify files to reflect that
>        but I am not sure what's the needed to install tools and stubdom in
>        xcp dom0?
> 
>        make xen
>        make tools
>        make stubdom
> 
>        make install-xen
>        make install-tools
>        make install-stubdom
> 
>        Thanks
> 
>        On Thu, Mar 18, 2010 at 9:26 AM, Konrad Rzeszutek Wilk
>        <[7]konrad.wilk@oracle.com> wrote:
> 
>          On Thu, Mar 18, 2010 at 08:28:18AM -0700, Ritu kaur wrote:
>          > Thanks Ian for clarification on interrupt handling mechanism.
>          >
>          > Thanks Konrad. Should I use xen/next in dom0 or domU?
> 
>          Both.
> 
> References
> 
>    Visible links
>    1. http://ritu.kaur.us/
>    2. http://gmail.com/
>    3. http://xenbits.xensource.com/xen-3.4-testing.hg
>    4. http://ritu.kaur.us/
>    5. http://gmail.com/
>    6. http://xenbits.xensource.com/xen-unstable.hg
>    7. mailto:konrad.wilk@oracle.com

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

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 434 bytes --]

Thanks Pasi, I did look into debugging via serial console yesterday, system
is rack mounted and currently not a viable option for me since it requires
admin approval, I am looking into this. Aside from that, I believe xen/next
should work with xcp 0.1.1 i.e

1. xen 3.4.3.gz, xen/next kernel. Take tar-pkg built from xen/next, untar it
in xcp0.1.1 dom0, modify extlinux.conf to boot from 3.4.3 and new kernel.
will this work?

Thanks

[-- Attachment #1.2: Type: text/html, Size: 457 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Pasi Kärkkäinen]

On Sun, Mar 21, 2010 at 02:21:31PM -0700, Ritu kaur wrote:
>    Thanks Pasi, I did look into debugging via serial console yesterday,
>    system is rack mounted and currently not a viable option for me since it
>    requires admin approval, I am looking into this. Aside from that, I
>    believe xen/next should work with xcp 0.1.1 i.e
> 
>    1. xen 3.4.3.gz, xen/next kernel. Take tar-pkg built from xen/next, untar
>    it in xcp0.1.1 dom0, modify extlinux.conf to boot from 3.4.3 and new
>    kernel. will this work?
> 

It should, assuming you don't have some incompatibility with xen/next and your hardware.
You might also want to try xen 4.0.0 instead of 3.4.3!

But anyway it's best to use the serial console, or SOL (Serial-Over-Lan) to capture
the boot messages, so we can actually SEE what's the problem.

-- Pasi

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 1198 bytes --]

While I wait for access to the system for serial debugging, I am suspecting
probably .config file used to build kernel might be wrong. Is there a
reference .config file for 32bit xen/next which I could compare with?

Thanks

On Mon, Mar 22, 2010 at 1:58 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote:

> On Sun, Mar 21, 2010 at 02:21:31PM -0700, Ritu kaur wrote:
> >    Thanks Pasi, I did look into debugging via serial console yesterday,
> >    system is rack mounted and currently not a viable option for me since
> it
> >    requires admin approval, I am looking into this. Aside from that, I
> >    believe xen/next should work with xcp 0.1.1 i.e
> >
> >    1. xen 3.4.3.gz, xen/next kernel. Take tar-pkg built from xen/next,
> untar
> >    it in xcp0.1.1 dom0, modify extlinux.conf to boot from 3.4.3 and new
> >    kernel. will this work?
> >
>
> It should, assuming you don't have some incompatibility with xen/next and
> your hardware.
> You might also want to try xen 4.0.0 instead of 3.4.3!
>
> But anyway it's best to use the serial console, or SOL (Serial-Over-Lan) to
> capture
> the boot messages, so we can actually SEE what's the problem.
>
> -- Pasi
>
>

[-- Attachment #1.2: Type: text/html, Size: 1589 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Pasi Kärkkäinen]

On Mon, Mar 22, 2010 at 02:02:33PM -0700, Ritu kaur wrote:
>    While I wait for access to the system for serial debugging, I am
>    suspecting probably .config file used to build kernel might be wrong. Is
>    there a reference .config file for 32bit xen/next which I could compare
>    with?
>

Yep, please check: http://wiki.xensource.com/xenwiki/XenParavirtOps
 
-- Pasi

>    Thanks
> 
>    On Mon, Mar 22, 2010 at 1:58 AM, Pasi Kärkkäinen <[1]pasik@iki.fi> wrote:
> 
>      On Sun, Mar 21, 2010 at 02:21:31PM -0700, Ritu kaur wrote:
>      >    Thanks Pasi, I did look into debugging via serial console
>      yesterday,
>      >    system is rack mounted and currently not a viable option for me
>      since it
>      >    requires admin approval, I am looking into this. Aside from that, I
>      >    believe xen/next should work with xcp 0.1.1 i.e
>      >
>      >    1. xen 3.4.3.gz, xen/next kernel. Take tar-pkg built from xen/next,
>      untar
>      >    it in xcp0.1.1 dom0, modify extlinux.conf to boot from 3.4.3 and
>      new
>      >    kernel. will this work?
>      >
> 
>      It should, assuming you don't have some incompatibility with xen/next
>      and your hardware.
>      You might also want to try xen 4.0.0 instead of 3.4.3!
> 
>      But anyway it's best to use the serial console, or SOL (Serial-Over-Lan)
>      to capture
>      the boot messages, so we can actually SEE what's the problem.
>      -- Pasi
> 
> References
> 
>    Visible links
>    1. mailto:pasik@iki.fi

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 759 bytes --]

Thanks Pasi. With .config file available at wiki I get following errors for
"make tar-pkg". I have tried both 2.6.32.9(which was available couple of
days earlier and with 2.6.32.10 and have compiled couple of times with the
same error)

...
 DEPMOD  2.6.32
/bin/sh: line 1:  2811 Killed                  /sbin/depmod -ae -F
System.map -b /root/kernel/linux-2.6.32/tar-install 2.6.32
make[3]: *** [_modinst_post] Error 137
make[2]: *** [sub-make] Error 2
make[1]: *** [tar-pkg] Error 2
make: *** [tar-pkg] Error 2
...

with the .config I have, tar-pkg is generated successfully. I double checked
.config I have  with " the xen config options of a working Dom0 given in
wiki", so not sure what could be wrong.  I have attached my .config for
reference.

Thanks

[-- Attachment #1.2: Type: text/html, Size: 835 bytes --]

[-- Attachment #2: .config.2.6.32 --]
[-- Type: application/octet-stream, Size: 97903 bytes --]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.32
# Thu Mar 18 15:02:01 2010
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
# CONFIG_X86_64 is not set
CONFIG_X86=y
CONFIG_OUTPUT_FORMAT="elf32-i386"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig"
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
# CONFIG_GENERIC_TIME_VSYSCALL is not set
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_DEFAULT_IDLE=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
# CONFIG_HAVE_CPUMASK_OF_CPU_MAP is not set
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
# CONFIG_ZONE_DMA32 is not set
CONFIG_ARCH_POPULATES_NODE_MAP=y
# CONFIG_AUDIT_ARCH is not set
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_USE_GENERIC_SMP_HELPERS=y
CONFIG_X86_32_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_X86_32_LAZY_GS=y
CONFIG_KTIME_SCALAR=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_CONSTRUCTORS=y

#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_BZIP2=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_TASK_XACCT=y
CONFIG_TASK_IO_ACCOUNTING=y
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
CONFIG_AUDIT_TREE=y

#
# RCU Subsystem
#
CONFIG_TREE_RCU=y
# CONFIG_TREE_PREEMPT_RCU is not set
# CONFIG_RCU_TRACE is not set
CONFIG_RCU_FANOUT=32
# CONFIG_RCU_FANOUT_EXACT is not set
# CONFIG_TREE_RCU_TRACE is not set
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=17
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
CONFIG_GROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
# CONFIG_RT_GROUP_SCHED is not set
# CONFIG_USER_SCHED is not set
CONFIG_CGROUP_SCHED=y
CONFIG_CGROUPS=y
# CONFIG_CGROUP_DEBUG is not set
CONFIG_CGROUP_NS=y
# CONFIG_CGROUP_FREEZER is not set
CONFIG_CGROUP_DEVICE=y
CONFIG_CPUSETS=y
CONFIG_PROC_PID_CPUSET=y
CONFIG_CGROUP_CPUACCT=y
# CONFIG_RESOURCE_COUNTERS is not set
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y
CONFIG_RELAY=y
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
CONFIG_USER_NS=y
CONFIG_PID_NS=y
# CONFIG_NET_NS is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_RD_GZIP=y
CONFIG_RD_BZIP2=y
CONFIG_RD_LZMA=y
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
CONFIG_ANON_INODES=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_PCSPKR_PLATFORM=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_HAVE_PERF_EVENTS=y

#
# Kernel Performance Events And Counters
#
CONFIG_PERF_EVENTS=y
CONFIG_EVENT_PROFILE=y
# CONFIG_PERF_COUNTERS is not set
# CONFIG_DEBUG_PERF_USE_VMALLOC is not set
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_PCI_QUIRKS=y
# CONFIG_COMPAT_BRK is not set
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_SLOB is not set
CONFIG_PROFILING=y
CONFIG_TRACEPOINTS=y
CONFIG_OPROFILE=m
# CONFIG_OPROFILE_IBS is not set
# CONFIG_OPROFILE_EVENT_MULTIPLEX is not set
CONFIG_HAVE_OPROFILE=y
# CONFIG_KPROBES is not set
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_HAVE_IOREMAP_PROT=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_HAVE_DMA_ATTRS=y
CONFIG_HAVE_DMA_API_DEBUG=y

#
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not set
CONFIG_SLOW_WORK=y
# CONFIG_SLOW_WORK_DEBUG is not set
CONFIG_HAVE_GENERIC_DMA_COHERENT=y
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
CONFIG_MODULE_FORCE_LOAD=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_MODVERSIONS=y
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
CONFIG_LBDAF=y
CONFIG_BLK_DEV_BSG=y
# CONFIG_BLK_DEV_INTEGRITY is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
CONFIG_PREEMPT_NOTIFIERS=y
CONFIG_FREEZER=y

#
# Processor type and features
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_SMP=y
# CONFIG_SPARSE_IRQ is not set
CONFIG_X86_MPPARSE=y
# CONFIG_X86_BIGSMP is not set
CONFIG_X86_EXTENDED_PLATFORM=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_MRST is not set
# CONFIG_X86_RDC321X is not set
# CONFIG_X86_32_NON_STANDARD is not set
CONFIG_X86_SUPPORTS_MEMORY_FAILURE=y
CONFIG_SCHED_OMIT_FRAME_POINTER=y
CONFIG_PARAVIRT_GUEST=y
CONFIG_XEN=y
CONFIG_XEN_MAX_DOMAIN_MEMORY=8
CONFIG_XEN_SAVE_RESTORE=y
# CONFIG_XEN_DEBUG_FS is not set
CONFIG_SWIOTLB_XEN=y
CONFIG_MICROCODE_XEN=y
CONFIG_XEN_DOM0=y
CONFIG_XEN_PRIVILEGED_GUEST=y
CONFIG_XEN_DOM0_PCI=y
# CONFIG_XEN_PCI_PASSTHROUGH is not set
CONFIG_VMI=y
CONFIG_KVM_CLOCK=y
CONFIG_KVM_GUEST=y
# CONFIG_LGUEST_GUEST is not set
CONFIG_PARAVIRT=y
# CONFIG_PARAVIRT_SPINLOCKS is not set
CONFIG_PARAVIRT_CLOCK=y
# CONFIG_PARAVIRT_DEBUG is not set
# CONFIG_MEMTEST is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
CONFIG_M686=y
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_MVIAC7 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
# CONFIG_MATOM is not set
# CONFIG_GENERIC_CPU is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CPU=y
CONFIG_X86_L1_CACHE_BYTES=64
CONFIG_X86_INTERNODE_CACHE_BYTES=64
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_X86_XADD=y
CONFIG_X86_PPRO_FENCE=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_TSC=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_FAMILY=5
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_CPU_SUP_INTEL=y
CONFIG_CPU_SUP_CYRIX_32=y
CONFIG_CPU_SUP_AMD=y
CONFIG_CPU_SUP_CENTAUR=y
CONFIG_CPU_SUP_TRANSMETA_32=y
CONFIG_CPU_SUP_UMC_32=y
# CONFIG_X86_DS is not set
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_DMI=y
CONFIG_SWIOTLB=y
CONFIG_IOMMU_HELPER=y
# CONFIG_IOMMU_API is not set
CONFIG_NR_CPUS=8
CONFIG_SCHED_SMT=y
CONFIG_SCHED_MC=y
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
# CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS is not set
CONFIG_X86_MCE=y
CONFIG_X86_MCE_INTEL=y
CONFIG_X86_MCE_AMD=y
# CONFIG_X86_ANCIENT_MCE is not set
CONFIG_X86_MCE_THRESHOLD=y
# CONFIG_X86_MCE_INJECT is not set
CONFIG_X86_THERMAL_VECTOR=y
CONFIG_VM86=y
CONFIG_TOSHIBA=m
CONFIG_I8K=m
# CONFIG_X86_REBOOTFIXUPS is not set
CONFIG_MICROCODE=m
CONFIG_MICROCODE_INTEL=y
# CONFIG_MICROCODE_AMD is not set
CONFIG_MICROCODE_OLD_INTERFACE=y
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m
# CONFIG_X86_CPU_DEBUG is not set
# CONFIG_NOHIGHMEM is not set
# CONFIG_HIGHMEM4G is not set
CONFIG_HIGHMEM64G=y
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_HIGHMEM=y
CONFIG_X86_PAE=y
CONFIG_ARCH_PHYS_ADDR_T_64BIT=y
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_SPARSEMEM_STATIC=y
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_PHYS_ADDR_T_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
CONFIG_HAVE_MLOCK=y
CONFIG_HAVE_MLOCKED_PAGE_BIT=y
CONFIG_MMU_NOTIFIER=y
# CONFIG_KSM is not set
CONFIG_DEFAULT_MMAP_MIN_ADDR=4096
CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y
# CONFIG_MEMORY_FAILURE is not set
# CONFIG_HIGHPTE is not set
# CONFIG_X86_CHECK_BIOS_CORRUPTION is not set
CONFIG_X86_RESERVE_LOW_64K=y
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
CONFIG_MTRR_SANITIZER=y
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=0
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1
# CONFIG_X86_PAT is not set
CONFIG_EFI=y
CONFIG_SECCOMP=y
# CONFIG_CC_STACKPROTECTOR is not set
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
CONFIG_SCHED_HRTICK=y
CONFIG_KEXEC=y
# CONFIG_CRASH_DUMP is not set
# CONFIG_KEXEC_JUMP is not set
CONFIG_PHYSICAL_START=0x1000000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x100000
CONFIG_HOTPLUG_CPU=y
# CONFIG_COMPAT_VDSO is not set
# CONFIG_CMDLINE_BOOL is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y

#
# Power management and ACPI options
#
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
CONFIG_PM_SLEEP_SMP=y
CONFIG_PM_SLEEP=y
CONFIG_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
CONFIG_HIBERNATION_NVS=y
CONFIG_HIBERNATION=y
CONFIG_PM_STD_PARTITION=""
# CONFIG_PM_RUNTIME is not set
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_PROCFS=y
CONFIG_ACPI_PROCFS_POWER=y
# CONFIG_ACPI_POWER_METER is not set
CONFIG_ACPI_SYSFS_POWER=y
CONFIG_ACPI_PROC_EVENT=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_VIDEO=m
CONFIG_ACPI_FAN=m
CONFIG_ACPI_DOCK=y
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_HOTPLUG_CPU=y
# CONFIG_ACPI_PROCESSOR_AGGREGATOR is not set
CONFIG_ACPI_THERMAL=m
# CONFIG_ACPI_CUSTOM_DSDT is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
# CONFIG_ACPI_PCI_SLOT is not set
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=m
CONFIG_ACPI_SBS=m
# CONFIG_SFI is not set
CONFIG_X86_APM_BOOT=y
CONFIG_APM=m
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
# CONFIG_APM_DO_ENABLE is not set
# CONFIG_APM_CPU_IDLE is not set
# CONFIG_APM_DISPLAY_BLANK is not set
# CONFIG_APM_ALLOW_INTS is not set

#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=m
# CONFIG_CPU_FREQ_DEBUG is not set
CONFIG_CPU_FREQ_STAT=m
# CONFIG_CPU_FREQ_STAT_DETAILS is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_CPU_FREQ_GOV_USERSPACE=m
CONFIG_CPU_FREQ_GOV_ONDEMAND=m
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m

#
# CPUFreq processor drivers
#
CONFIG_X86_ACPI_CPUFREQ=m
CONFIG_X86_POWERNOW_K6=m
CONFIG_X86_POWERNOW_K7=m
CONFIG_X86_POWERNOW_K7_ACPI=y
CONFIG_X86_POWERNOW_K8=m
CONFIG_X86_GX_SUSPMOD=m
CONFIG_X86_SPEEDSTEP_CENTRINO=m
CONFIG_X86_SPEEDSTEP_CENTRINO_TABLE=y
CONFIG_X86_SPEEDSTEP_ICH=m
CONFIG_X86_SPEEDSTEP_SMI=m
CONFIG_X86_P4_CLOCKMOD=m
CONFIG_X86_CPUFREQ_NFORCE2=m
CONFIG_X86_LONGRUN=m
CONFIG_X86_LONGHAUL=m
CONFIG_X86_E_POWERSAVER=m

#
# shared options
#
CONFIG_X86_SPEEDSTEP_LIB=m
CONFIG_X86_SPEEDSTEP_RELAXED_CAP_CHECK=y
CONFIG_CPU_IDLE=y
CONFIG_CPU_IDLE_GOV_LADDER=y
CONFIG_CPU_IDLE_GOV_MENU=y

#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
# CONFIG_PCI_GOOLPC is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_XEN=y
CONFIG_PCI_DOMAINS=y
# CONFIG_DMAR is not set
CONFIG_PCIEPORTBUS=y
CONFIG_HOTPLUG_PCI_PCIE=m
CONFIG_PCIEAER=y
# CONFIG_PCIE_ECRC is not set
# CONFIG_PCIEAER_INJECT is not set
# CONFIG_PCIEASPM is not set
CONFIG_ARCH_SUPPORTS_MSI=y
CONFIG_PCI_MSI=y
CONFIG_PCI_LEGACY=y
# CONFIG_PCI_DEBUG is not set
# CONFIG_PCI_STUB is not set
CONFIG_XEN_PCIDEV_FRONTEND=y
CONFIG_HT_IRQ=y
# CONFIG_PCI_IOV is not set
CONFIG_ISA_DMA_API=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
CONFIG_SCx200=m
CONFIG_SCx200HR_TIMER=m
# CONFIG_OLPC is not set
CONFIG_K8_NB=y
CONFIG_PCCARD=m
# CONFIG_PCMCIA_DEBUG is not set
CONFIG_PCMCIA=m
CONFIG_PCMCIA_LOAD_CIS=y
CONFIG_PCMCIA_IOCTL=y
CONFIG_CARDBUS=y

#
# PC-card bridges
#
CONFIG_YENTA=m
CONFIG_YENTA_O2=y
CONFIG_YENTA_RICOH=y
CONFIG_YENTA_TI=y
CONFIG_YENTA_ENE_TUNE=y
CONFIG_YENTA_TOSHIBA=y
CONFIG_PD6729=m
CONFIG_I82092=m
CONFIG_I82365=m
CONFIG_TCIC=m
CONFIG_PCMCIA_PROBE=y
CONFIG_PCCARD_NONSTATIC=m
CONFIG_HOTPLUG_PCI=m
CONFIG_HOTPLUG_PCI_FAKE=m
CONFIG_HOTPLUG_PCI_COMPAQ=m
# CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM is not set
CONFIG_HOTPLUG_PCI_IBM=m
CONFIG_HOTPLUG_PCI_ACPI=m
CONFIG_HOTPLUG_PCI_ACPI_IBM=m
CONFIG_HOTPLUG_PCI_CPCI=y
CONFIG_HOTPLUG_PCI_CPCI_ZT5550=m
CONFIG_HOTPLUG_PCI_CPCI_GENERIC=m
CONFIG_HOTPLUG_PCI_SHPC=m

#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
CONFIG_HAVE_AOUT=y
CONFIG_BINFMT_AOUT=m
CONFIG_BINFMT_MISC=m
CONFIG_HAVE_ATOMIC_IOMAP=y
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=m
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
# CONFIG_XFRM_STATISTICS is not set
CONFIG_XFRM_IPCOMP=m
CONFIG_NET_KEY=m
# CONFIG_NET_KEY_MIGRATE is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_ASK_IP_FIB_HASH=y
# CONFIG_IP_FIB_TRIE is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
CONFIG_NET_IPGRE_BROADCAST=y
CONFIG_IP_MROUTE=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
CONFIG_INET_AH=m
CONFIG_INET_ESP=m
CONFIG_INET_IPCOMP=m
CONFIG_INET_XFRM_TUNNEL=m
CONFIG_INET_TUNNEL=m
CONFIG_INET_XFRM_MODE_TRANSPORT=m
CONFIG_INET_XFRM_MODE_TUNNEL=m
CONFIG_INET_XFRM_MODE_BEET=m
CONFIG_INET_LRO=y
CONFIG_INET_DIAG=m
CONFIG_INET_TCP_DIAG=m
CONFIG_TCP_CONG_ADVANCED=y
CONFIG_TCP_CONG_BIC=m
CONFIG_TCP_CONG_CUBIC=y
CONFIG_TCP_CONG_WESTWOOD=m
CONFIG_TCP_CONG_HTCP=m
CONFIG_TCP_CONG_HSTCP=m
CONFIG_TCP_CONG_HYBLA=m
CONFIG_TCP_CONG_VEGAS=m
CONFIG_TCP_CONG_SCALABLE=m
CONFIG_TCP_CONG_LP=m
CONFIG_TCP_CONG_VENO=m
CONFIG_TCP_CONG_YEAH=m
CONFIG_TCP_CONG_ILLINOIS=m
# CONFIG_DEFAULT_BIC is not set
CONFIG_DEFAULT_CUBIC=y
# CONFIG_DEFAULT_HTCP is not set
# CONFIG_DEFAULT_VEGAS is not set
# CONFIG_DEFAULT_WESTWOOD is not set
# CONFIG_DEFAULT_RENO is not set
CONFIG_DEFAULT_TCP_CONG="cubic"
CONFIG_TCP_MD5SIG=y
CONFIG_IPV6=m
CONFIG_IPV6_PRIVACY=y
CONFIG_IPV6_ROUTER_PREF=y
CONFIG_IPV6_ROUTE_INFO=y
CONFIG_IPV6_OPTIMISTIC_DAD=y
CONFIG_INET6_AH=m
CONFIG_INET6_ESP=m
CONFIG_INET6_IPCOMP=m
CONFIG_IPV6_MIP6=m
CONFIG_INET6_XFRM_TUNNEL=m
CONFIG_INET6_TUNNEL=m
CONFIG_INET6_XFRM_MODE_TRANSPORT=m
CONFIG_INET6_XFRM_MODE_TUNNEL=m
CONFIG_INET6_XFRM_MODE_BEET=m
CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION=m
CONFIG_IPV6_SIT=m
CONFIG_IPV6_NDISC_NODETYPE=y
CONFIG_IPV6_TUNNEL=m
CONFIG_IPV6_MULTIPLE_TABLES=y
CONFIG_IPV6_SUBTREES=y
CONFIG_IPV6_MROUTE=y
CONFIG_IPV6_PIMSM_V2=y
# CONFIG_NETLABEL is not set
CONFIG_NETWORK_SECMARK=y
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_NETFILTER_ADVANCED=y
CONFIG_BRIDGE_NETFILTER=y

#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=m
CONFIG_NETFILTER_NETLINK_QUEUE=m
CONFIG_NETFILTER_NETLINK_LOG=m
CONFIG_NF_CONNTRACK=m
CONFIG_NF_CT_ACCT=y
CONFIG_NF_CONNTRACK_MARK=y
CONFIG_NF_CONNTRACK_SECMARK=y
CONFIG_NF_CONNTRACK_EVENTS=y
CONFIG_NF_CT_PROTO_DCCP=m
CONFIG_NF_CT_PROTO_GRE=m
CONFIG_NF_CT_PROTO_SCTP=m
CONFIG_NF_CT_PROTO_UDPLITE=m
CONFIG_NF_CONNTRACK_AMANDA=m
CONFIG_NF_CONNTRACK_FTP=m
CONFIG_NF_CONNTRACK_H323=m
CONFIG_NF_CONNTRACK_IRC=m
CONFIG_NF_CONNTRACK_NETBIOS_NS=m
CONFIG_NF_CONNTRACK_PPTP=m
CONFIG_NF_CONNTRACK_SANE=m
CONFIG_NF_CONNTRACK_SIP=m
CONFIG_NF_CONNTRACK_TFTP=m
CONFIG_NF_CT_NETLINK=m
# CONFIG_NETFILTER_TPROXY is not set
CONFIG_NETFILTER_XTABLES=m
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=m
CONFIG_NETFILTER_XT_TARGET_CONNMARK=m
CONFIG_NETFILTER_XT_TARGET_CONNSECMARK=m
CONFIG_NETFILTER_XT_TARGET_DSCP=m
CONFIG_NETFILTER_XT_TARGET_HL=m
# CONFIG_NETFILTER_XT_TARGET_LED is not set
CONFIG_NETFILTER_XT_TARGET_MARK=m
CONFIG_NETFILTER_XT_TARGET_NFLOG=m
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=m
CONFIG_NETFILTER_XT_TARGET_NOTRACK=m
CONFIG_NETFILTER_XT_TARGET_RATEEST=m
CONFIG_NETFILTER_XT_TARGET_TRACE=m
CONFIG_NETFILTER_XT_TARGET_SECMARK=m
CONFIG_NETFILTER_XT_TARGET_TCPMSS=m
CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP=m
# CONFIG_NETFILTER_XT_MATCH_CLUSTER is not set
CONFIG_NETFILTER_XT_MATCH_COMMENT=m
CONFIG_NETFILTER_XT_MATCH_CONNBYTES=m
CONFIG_NETFILTER_XT_MATCH_CONNLIMIT=m
CONFIG_NETFILTER_XT_MATCH_CONNMARK=m
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m
CONFIG_NETFILTER_XT_MATCH_DCCP=m
CONFIG_NETFILTER_XT_MATCH_DSCP=m
CONFIG_NETFILTER_XT_MATCH_ESP=m
CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=m
CONFIG_NETFILTER_XT_MATCH_HELPER=m
CONFIG_NETFILTER_XT_MATCH_HL=m
CONFIG_NETFILTER_XT_MATCH_IPRANGE=m
CONFIG_NETFILTER_XT_MATCH_LENGTH=m
CONFIG_NETFILTER_XT_MATCH_LIMIT=m
CONFIG_NETFILTER_XT_MATCH_MAC=m
CONFIG_NETFILTER_XT_MATCH_MARK=m
CONFIG_NETFILTER_XT_MATCH_MULTIPORT=m
CONFIG_NETFILTER_XT_MATCH_OWNER=m
CONFIG_NETFILTER_XT_MATCH_POLICY=m
CONFIG_NETFILTER_XT_MATCH_PHYSDEV=m
CONFIG_NETFILTER_XT_MATCH_PKTTYPE=m
CONFIG_NETFILTER_XT_MATCH_QUOTA=m
CONFIG_NETFILTER_XT_MATCH_RATEEST=m
CONFIG_NETFILTER_XT_MATCH_REALM=m
# CONFIG_NETFILTER_XT_MATCH_RECENT is not set
CONFIG_NETFILTER_XT_MATCH_SCTP=m
CONFIG_NETFILTER_XT_MATCH_STATE=m
CONFIG_NETFILTER_XT_MATCH_STATISTIC=m
CONFIG_NETFILTER_XT_MATCH_STRING=m
CONFIG_NETFILTER_XT_MATCH_TCPMSS=m
CONFIG_NETFILTER_XT_MATCH_TIME=m
CONFIG_NETFILTER_XT_MATCH_U32=m
# CONFIG_NETFILTER_XT_MATCH_OSF is not set
CONFIG_IP_VS=m
# CONFIG_IP_VS_IPV6 is not set
# CONFIG_IP_VS_DEBUG is not set
CONFIG_IP_VS_TAB_BITS=12

#
# IPVS transport protocol load balancing support
#
CONFIG_IP_VS_PROTO_TCP=y
CONFIG_IP_VS_PROTO_UDP=y
CONFIG_IP_VS_PROTO_AH_ESP=y
CONFIG_IP_VS_PROTO_ESP=y
CONFIG_IP_VS_PROTO_AH=y

#
# IPVS scheduler
#
CONFIG_IP_VS_RR=m
CONFIG_IP_VS_WRR=m
CONFIG_IP_VS_LC=m
CONFIG_IP_VS_WLC=m
CONFIG_IP_VS_LBLC=m
CONFIG_IP_VS_LBLCR=m
CONFIG_IP_VS_DH=m
CONFIG_IP_VS_SH=m
CONFIG_IP_VS_SED=m
CONFIG_IP_VS_NQ=m

#
# IPVS application helper
#
CONFIG_IP_VS_FTP=m

#
# IP: Netfilter Configuration
#
CONFIG_NF_DEFRAG_IPV4=m
CONFIG_NF_CONNTRACK_IPV4=m
CONFIG_NF_CONNTRACK_PROC_COMPAT=y
CONFIG_IP_NF_QUEUE=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_ADDRTYPE=m
CONFIG_IP_NF_MATCH_AH=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_NF_NAT=m
CONFIG_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_NETMAP=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_NF_NAT_SNMP_BASIC=m
CONFIG_NF_NAT_PROTO_DCCP=m
CONFIG_NF_NAT_PROTO_GRE=m
CONFIG_NF_NAT_PROTO_UDPLITE=m
CONFIG_NF_NAT_PROTO_SCTP=m
CONFIG_NF_NAT_FTP=m
CONFIG_NF_NAT_IRC=m
CONFIG_NF_NAT_TFTP=m
CONFIG_NF_NAT_AMANDA=m
CONFIG_NF_NAT_PPTP=m
CONFIG_NF_NAT_H323=m
CONFIG_NF_NAT_SIP=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_CLUSTERIP=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_TTL=m
CONFIG_IP_NF_RAW=m
# CONFIG_IP_NF_SECURITY is not set
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m

#
# IPv6: Netfilter Configuration
#
CONFIG_NF_CONNTRACK_IPV6=m
CONFIG_IP6_NF_QUEUE=m
CONFIG_IP6_NF_IPTABLES=m
CONFIG_IP6_NF_MATCH_AH=m
CONFIG_IP6_NF_MATCH_EUI64=m
CONFIG_IP6_NF_MATCH_FRAG=m
CONFIG_IP6_NF_MATCH_OPTS=m
CONFIG_IP6_NF_MATCH_HL=m
CONFIG_IP6_NF_MATCH_IPV6HEADER=m
CONFIG_IP6_NF_MATCH_MH=m
CONFIG_IP6_NF_MATCH_RT=m
CONFIG_IP6_NF_TARGET_HL=m
CONFIG_IP6_NF_TARGET_LOG=m
CONFIG_IP6_NF_FILTER=m
CONFIG_IP6_NF_TARGET_REJECT=m
CONFIG_IP6_NF_MANGLE=m
CONFIG_IP6_NF_RAW=m
# CONFIG_IP6_NF_SECURITY is not set

#
# DECnet: Netfilter Configuration
#
CONFIG_DECNET_NF_GRABULATOR=m
CONFIG_BRIDGE_NF_EBTABLES=m
CONFIG_BRIDGE_EBT_BROUTE=m
CONFIG_BRIDGE_EBT_T_FILTER=m
CONFIG_BRIDGE_EBT_T_NAT=m
CONFIG_BRIDGE_EBT_802_3=m
CONFIG_BRIDGE_EBT_AMONG=m
CONFIG_BRIDGE_EBT_ARP=m
CONFIG_BRIDGE_EBT_IP=m
# CONFIG_BRIDGE_EBT_IP6 is not set
CONFIG_BRIDGE_EBT_LIMIT=m
CONFIG_BRIDGE_EBT_MARK=m
CONFIG_BRIDGE_EBT_PKTTYPE=m
CONFIG_BRIDGE_EBT_STP=m
CONFIG_BRIDGE_EBT_VLAN=m
CONFIG_BRIDGE_EBT_ARPREPLY=m
CONFIG_BRIDGE_EBT_DNAT=m
CONFIG_BRIDGE_EBT_MARK_T=m
CONFIG_BRIDGE_EBT_REDIRECT=m
CONFIG_BRIDGE_EBT_SNAT=m
CONFIG_BRIDGE_EBT_LOG=m
CONFIG_BRIDGE_EBT_ULOG=m
CONFIG_BRIDGE_EBT_NFLOG=m
CONFIG_IP_DCCP=m
CONFIG_INET_DCCP_DIAG=m

#
# DCCP CCIDs Configuration (EXPERIMENTAL)
#
# CONFIG_IP_DCCP_CCID2_DEBUG is not set
CONFIG_IP_DCCP_CCID3=y
# CONFIG_IP_DCCP_CCID3_DEBUG is not set
CONFIG_IP_DCCP_CCID3_RTO=100
CONFIG_IP_DCCP_TFRC_LIB=y

#
# DCCP Kernel Hacking
#
# CONFIG_IP_DCCP_DEBUG is not set
CONFIG_IP_SCTP=m
# CONFIG_SCTP_DBG_MSG is not set
# CONFIG_SCTP_DBG_OBJCNT is not set
# CONFIG_SCTP_HMAC_NONE is not set
# CONFIG_SCTP_HMAC_SHA1 is not set
CONFIG_SCTP_HMAC_MD5=y
# CONFIG_RDS is not set
CONFIG_TIPC=m
CONFIG_TIPC_ADVANCED=y
CONFIG_TIPC_ZONES=3
CONFIG_TIPC_CLUSTERS=1
CONFIG_TIPC_NODES=255
CONFIG_TIPC_SLAVE_NODES=0
CONFIG_TIPC_PORTS=8191
CONFIG_TIPC_LOG=0
# CONFIG_TIPC_DEBUG is not set
CONFIG_ATM=m
CONFIG_ATM_CLIP=m
# CONFIG_ATM_CLIP_NO_ICMP is not set
CONFIG_ATM_LANE=m
CONFIG_ATM_MPOA=m
CONFIG_ATM_BR2684=m
# CONFIG_ATM_BR2684_IPFILTER is not set
CONFIG_STP=m
CONFIG_BRIDGE=m
# CONFIG_NET_DSA is not set
CONFIG_VLAN_8021Q=m
# CONFIG_VLAN_8021Q_GVRP is not set
CONFIG_DECNET=m
# CONFIG_DECNET_ROUTER is not set
CONFIG_LLC=y
CONFIG_LLC2=m
CONFIG_IPX=m
# CONFIG_IPX_INTERN is not set
CONFIG_ATALK=m
CONFIG_DEV_APPLETALK=m
CONFIG_LTPC=m
# CONFIG_COPS is not set
CONFIG_IPDDP=m
CONFIG_IPDDP_ENCAP=y
CONFIG_IPDDP_DECAP=y
CONFIG_X25=m
CONFIG_LAPB=m
CONFIG_ECONET=m
CONFIG_ECONET_AUNUDP=y
CONFIG_ECONET_NATIVE=y
CONFIG_WAN_ROUTER=m
# CONFIG_PHONET is not set
# CONFIG_IEEE802154 is not set
CONFIG_NET_SCHED=y

#
# Queueing/Scheduling
#
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
CONFIG_NET_SCH_HFSC=m
CONFIG_NET_SCH_ATM=m
CONFIG_NET_SCH_PRIO=m
# CONFIG_NET_SCH_MULTIQ is not set
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
CONFIG_NET_SCH_NETEM=m
# CONFIG_NET_SCH_DRR is not set
CONFIG_NET_SCH_INGRESS=m

#
# Classification
#
CONFIG_NET_CLS=y
CONFIG_NET_CLS_BASIC=m
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=m
CONFIG_NET_CLS_U32=m
CONFIG_CLS_U32_PERF=y
CONFIG_CLS_U32_MARK=y
CONFIG_NET_CLS_RSVP=m
CONFIG_NET_CLS_RSVP6=m
CONFIG_NET_CLS_FLOW=m
# CONFIG_NET_CLS_CGROUP is not set
CONFIG_NET_EMATCH=y
CONFIG_NET_EMATCH_STACK=32
CONFIG_NET_EMATCH_CMP=m
CONFIG_NET_EMATCH_NBYTE=m
CONFIG_NET_EMATCH_U32=m
CONFIG_NET_EMATCH_META=m
CONFIG_NET_EMATCH_TEXT=m
CONFIG_NET_CLS_ACT=y
CONFIG_NET_ACT_POLICE=m
CONFIG_NET_ACT_GACT=m
CONFIG_GACT_PROB=y
CONFIG_NET_ACT_MIRRED=m
CONFIG_NET_ACT_IPT=m
CONFIG_NET_ACT_NAT=m
CONFIG_NET_ACT_PEDIT=m
CONFIG_NET_ACT_SIMP=m
# CONFIG_NET_ACT_SKBEDIT is not set
CONFIG_NET_CLS_IND=y
CONFIG_NET_SCH_FIFO=y
# CONFIG_DCB is not set

#
# Network testing
#
CONFIG_NET_PKTGEN=m
# CONFIG_NET_DROP_MONITOR is not set
CONFIG_HAMRADIO=y

#
# Packet Radio protocols
#
CONFIG_AX25=m
# CONFIG_AX25_DAMA_SLAVE is not set
CONFIG_NETROM=m
CONFIG_ROSE=m

#
# AX.25 network device drivers
#
CONFIG_MKISS=m
CONFIG_6PACK=m
CONFIG_BPQETHER=m
CONFIG_SCC=m
# CONFIG_SCC_DELAY is not set
# CONFIG_SCC_TRXECHO is not set
CONFIG_BAYCOM_SER_FDX=m
CONFIG_BAYCOM_SER_HDX=m
CONFIG_BAYCOM_PAR=m
CONFIG_BAYCOM_EPP=m
# CONFIG_YAM is not set
CONFIG_CAN=m
CONFIG_CAN_RAW=m
CONFIG_CAN_BCM=m

#
# CAN Device Drivers
#
CONFIG_CAN_VCAN=m
# CONFIG_CAN_DEV is not set
# CONFIG_CAN_DEBUG_DEVICES is not set
CONFIG_IRDA=m

#
# IrDA protocols
#
CONFIG_IRLAN=m
CONFIG_IRNET=m
CONFIG_IRCOMM=m
# CONFIG_IRDA_ULTRA is not set

#
# IrDA options
#
CONFIG_IRDA_CACHE_LAST_LSAP=y
CONFIG_IRDA_FAST_RR=y
# CONFIG_IRDA_DEBUG is not set

#
# Infrared-port device drivers
#

#
# SIR device drivers
#
CONFIG_IRTTY_SIR=m

#
# Dongle support
#
CONFIG_DONGLE=y
CONFIG_ESI_DONGLE=m
CONFIG_ACTISYS_DONGLE=m
CONFIG_TEKRAM_DONGLE=m
CONFIG_TOIM3232_DONGLE=m
CONFIG_LITELINK_DONGLE=m
CONFIG_MA600_DONGLE=m
CONFIG_GIRBIL_DONGLE=m
CONFIG_MCP2120_DONGLE=m
CONFIG_OLD_BELKIN_DONGLE=m
CONFIG_ACT200L_DONGLE=m
CONFIG_KINGSUN_DONGLE=m
CONFIG_KSDAZZLE_DONGLE=m
CONFIG_KS959_DONGLE=m

#
# FIR device drivers
#
CONFIG_USB_IRDA=m
CONFIG_SIGMATEL_FIR=m
CONFIG_NSC_FIR=m
CONFIG_WINBOND_FIR=m
CONFIG_TOSHIBA_FIR=m
CONFIG_SMC_IRCC_FIR=m
CONFIG_ALI_FIR=m
CONFIG_VLSI_FIR=m
CONFIG_VIA_FIR=m
CONFIG_MCS_FIR=m
CONFIG_BT=m
CONFIG_BT_L2CAP=m
CONFIG_BT_SCO=m
CONFIG_BT_RFCOMM=m
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=m
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
CONFIG_BT_HIDP=m

#
# Bluetooth device drivers
#
# CONFIG_BT_HCIBTUSB is not set
CONFIG_BT_HCIBTSDIO=m
CONFIG_BT_HCIUART=m
CONFIG_BT_HCIUART_H4=y
CONFIG_BT_HCIUART_BCSP=y
CONFIG_BT_HCIUART_LL=y
CONFIG_BT_HCIBCM203X=m
CONFIG_BT_HCIBPA10X=m
CONFIG_BT_HCIBFUSB=m
CONFIG_BT_HCIDTL1=m
CONFIG_BT_HCIBT3C=m
CONFIG_BT_HCIBLUECARD=m
CONFIG_BT_HCIBTUART=m
CONFIG_BT_HCIVHCI=m
# CONFIG_BT_MRVL is not set
CONFIG_AF_RXRPC=m
# CONFIG_AF_RXRPC_DEBUG is not set
CONFIG_RXKAD=m
CONFIG_FIB_RULES=y
CONFIG_WIRELESS=y
CONFIG_CFG80211=m
# CONFIG_NL80211_TESTMODE is not set
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not set
# CONFIG_CFG80211_REG_DEBUG is not set
CONFIG_CFG80211_DEFAULT_PS=y
CONFIG_CFG80211_DEFAULT_PS_VALUE=1
# CONFIG_CFG80211_DEBUGFS is not set
# CONFIG_WIRELESS_OLD_REGULATORY is not set
CONFIG_WIRELESS_EXT=y
CONFIG_WIRELESS_EXT_SYSFS=y
CONFIG_LIB80211=m
CONFIG_LIB80211_CRYPT_WEP=m
CONFIG_LIB80211_CRYPT_CCMP=m
CONFIG_LIB80211_CRYPT_TKIP=m
# CONFIG_LIB80211_DEBUG is not set
CONFIG_MAC80211=m
CONFIG_MAC80211_RC_MINSTREL=y
# CONFIG_MAC80211_RC_DEFAULT_PID is not set
CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y
CONFIG_MAC80211_RC_DEFAULT="minstrel"
CONFIG_MAC80211_MESH=y
CONFIG_MAC80211_LEDS=y
# CONFIG_MAC80211_DEBUGFS is not set
# CONFIG_MAC80211_DEBUG_MENU is not set
# CONFIG_WIMAX is not set
CONFIG_RFKILL=m
CONFIG_RFKILL_LEDS=y
CONFIG_RFKILL_INPUT=y
CONFIG_NET_9P=m
CONFIG_NET_9P_VIRTIO=m
# CONFIG_NET_9P_RDMA is not set
# CONFIG_NET_9P_DEBUG is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
# CONFIG_DEVTMPFS is not set
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE=""
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
CONFIG_SYS_HYPERVISOR=y
CONFIG_CONNECTOR=m
CONFIG_MTD=m
# CONFIG_MTD_DEBUG is not set
# CONFIG_MTD_TESTS is not set
CONFIG_MTD_CONCAT=m
CONFIG_MTD_PARTITIONS=y
CONFIG_MTD_REDBOOT_PARTS=m
CONFIG_MTD_REDBOOT_DIRECTORY_BLOCK=-1
# CONFIG_MTD_REDBOOT_PARTS_UNALLOCATED is not set
# CONFIG_MTD_REDBOOT_PARTS_READONLY is not set
CONFIG_MTD_AR7_PARTS=m

#
# User Modules And Translation Layers
#
CONFIG_MTD_CHAR=m
CONFIG_MTD_BLKDEVS=m
CONFIG_MTD_BLOCK=m
CONFIG_MTD_BLOCK_RO=m
CONFIG_FTL=m
CONFIG_NFTL=m
CONFIG_NFTL_RW=y
CONFIG_INFTL=m
CONFIG_RFD_FTL=m
CONFIG_SSFDC=m
CONFIG_MTD_OOPS=m

#
# RAM/ROM/Flash chip drivers
#
CONFIG_MTD_CFI=m
CONFIG_MTD_JEDECPROBE=m
CONFIG_MTD_GEN_PROBE=m
# CONFIG_MTD_CFI_ADV_OPTIONS is not set
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
# CONFIG_MTD_MAP_BANK_WIDTH_8 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_16 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_32 is not set
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
# CONFIG_MTD_CFI_I4 is not set
# CONFIG_MTD_CFI_I8 is not set
CONFIG_MTD_CFI_INTELEXT=m
CONFIG_MTD_CFI_AMDSTD=m
CONFIG_MTD_CFI_STAA=m
CONFIG_MTD_CFI_UTIL=m
CONFIG_MTD_RAM=m
CONFIG_MTD_ROM=m
CONFIG_MTD_ABSENT=m

#
# Mapping drivers for chip access
#
CONFIG_MTD_COMPLEX_MAPPINGS=y
CONFIG_MTD_PHYSMAP=m
# CONFIG_MTD_PHYSMAP_COMPAT is not set
CONFIG_MTD_SC520CDP=m
CONFIG_MTD_NETSC520=m
CONFIG_MTD_TS5500=m
CONFIG_MTD_SBC_GXX=m
CONFIG_MTD_SCx200_DOCFLASH=m
# CONFIG_MTD_AMD76XROM is not set
# CONFIG_MTD_ICHXROM is not set
# CONFIG_MTD_ESB2ROM is not set
# CONFIG_MTD_CK804XROM is not set
# CONFIG_MTD_SCB2_FLASH is not set
CONFIG_MTD_NETtel=m
# CONFIG_MTD_L440GX is not set
CONFIG_MTD_PCI=m
CONFIG_MTD_INTEL_VR_NOR=m
CONFIG_MTD_PLATRAM=m

#
# Self-contained MTD device drivers
#
CONFIG_MTD_PMC551=m
# CONFIG_MTD_PMC551_BUGFIX is not set
# CONFIG_MTD_PMC551_DEBUG is not set
CONFIG_MTD_DATAFLASH=m
# CONFIG_MTD_DATAFLASH_WRITE_VERIFY is not set
# CONFIG_MTD_DATAFLASH_OTP is not set
CONFIG_MTD_M25P80=m
CONFIG_M25PXX_USE_FAST_READ=y
# CONFIG_MTD_SST25L is not set
CONFIG_MTD_SLRAM=m
CONFIG_MTD_PHRAM=m
CONFIG_MTD_MTDRAM=m
CONFIG_MTDRAM_TOTAL_SIZE=4096
CONFIG_MTDRAM_ERASE_SIZE=128
CONFIG_MTD_BLOCK2MTD=m

#
# Disk-On-Chip Device Drivers
#
CONFIG_MTD_DOC2000=m
CONFIG_MTD_DOC2001=m
CONFIG_MTD_DOC2001PLUS=m
CONFIG_MTD_DOCPROBE=m
CONFIG_MTD_DOCECC=m
# CONFIG_MTD_DOCPROBE_ADVANCED is not set
CONFIG_MTD_DOCPROBE_ADDRESS=0
CONFIG_MTD_NAND=m
# CONFIG_MTD_NAND_VERIFY_WRITE is not set
# CONFIG_MTD_NAND_ECC_SMC is not set
# CONFIG_MTD_NAND_MUSEUM_IDS is not set
CONFIG_MTD_NAND_IDS=m
CONFIG_MTD_NAND_DISKONCHIP=m
# CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADVANCED is not set
CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADDRESS=0
# CONFIG_MTD_NAND_DISKONCHIP_BBTWRITE is not set
CONFIG_MTD_NAND_CAFE=m
CONFIG_MTD_NAND_CS553X=m
# CONFIG_MTD_NAND_NANDSIM is not set
CONFIG_MTD_NAND_PLATFORM=m
CONFIG_MTD_ALAUDA=m
CONFIG_MTD_ONENAND=m
CONFIG_MTD_ONENAND_VERIFY_WRITE=y
# CONFIG_MTD_ONENAND_GENERIC is not set
# CONFIG_MTD_ONENAND_OTP is not set
CONFIG_MTD_ONENAND_2X_PROGRAM=y
CONFIG_MTD_ONENAND_SIM=m

#
# LPDDR flash memory drivers
#
# CONFIG_MTD_LPDDR is not set

#
# UBI - Unsorted block images
#
CONFIG_MTD_UBI=m
CONFIG_MTD_UBI_WL_THRESHOLD=4096
CONFIG_MTD_UBI_BEB_RESERVE=1
# CONFIG_MTD_UBI_GLUEBI is not set

#
# UBI debugging options
#
# CONFIG_MTD_UBI_DEBUG is not set
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_SERIAL=m
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
CONFIG_PARPORT_PC_PCMCIA=m
# CONFIG_PARPORT_GSC is not set
CONFIG_PARPORT_AX88796=m
CONFIG_PARPORT_1284=y
CONFIG_PARPORT_NOT_PC=y
CONFIG_PNP=y
CONFIG_PNP_DEBUG_MESSAGES=y

#
# Protocols
#
CONFIG_ISAPNP=y
CONFIG_PNPBIOS=y
CONFIG_PNPBIOS_PROC_FS=y
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
CONFIG_BLK_DEV_FD=m
CONFIG_BLK_DEV_XD=m
CONFIG_PARIDE=m

#
# Parallel IDE high-level drivers
#
CONFIG_PARIDE_PD=m
CONFIG_PARIDE_PCD=m
CONFIG_PARIDE_PF=m
CONFIG_PARIDE_PT=m
CONFIG_PARIDE_PG=m

#
# Parallel IDE protocol modules
#
CONFIG_PARIDE_ATEN=m
CONFIG_PARIDE_BPCK=m
CONFIG_PARIDE_BPCK6=m
CONFIG_PARIDE_COMM=m
CONFIG_PARIDE_DSTR=m
CONFIG_PARIDE_FIT2=m
CONFIG_PARIDE_FIT3=m
CONFIG_PARIDE_EPAT=m
# CONFIG_PARIDE_EPATC8 is not set
CONFIG_PARIDE_EPIA=m
CONFIG_PARIDE_FRIQ=m
CONFIG_PARIDE_FRPW=m
CONFIG_PARIDE_KBIC=m
CONFIG_PARIDE_KTTI=m
CONFIG_PARIDE_ON20=m
CONFIG_PARIDE_ON26=m
CONFIG_BLK_CPQ_DA=m
CONFIG_BLK_CPQ_CISS_DA=m
CONFIG_CISS_SCSI_TAPE=y
CONFIG_BLK_DEV_DAC960=m
CONFIG_BLK_DEV_UMEM=m
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_CRYPTOLOOP=m
CONFIG_BLK_DEV_NBD=m
CONFIG_BLK_DEV_SX8=m
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=8192
# CONFIG_BLK_DEV_XIP is not set
CONFIG_CDROM_PKTCDVD=m
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
CONFIG_ATA_OVER_ETH=m
CONFIG_XEN_BLKDEV_FRONTEND=m
CONFIG_VIRTIO_BLK=m
# CONFIG_BLK_DEV_HD is not set
CONFIG_MISC_DEVICES=y
CONFIG_IBM_ASM=m
CONFIG_PHANTOM=m
CONFIG_SGI_IOC4=m
CONFIG_TIFM_CORE=m
CONFIG_TIFM_7XX1=m
# CONFIG_ICS932S401 is not set
CONFIG_ENCLOSURE_SERVICES=m
CONFIG_HP_ILO=m
# CONFIG_DELL_LAPTOP is not set
# CONFIG_ISL29003 is not set
# CONFIG_C2PORT is not set

#
# EEPROM support
#
# CONFIG_EEPROM_AT24 is not set
# CONFIG_EEPROM_AT25 is not set
# CONFIG_EEPROM_LEGACY is not set
# CONFIG_EEPROM_MAX6875 is not set
CONFIG_EEPROM_93CX6=m
# CONFIG_CB710_CORE is not set
CONFIG_HAVE_IDE=y
CONFIG_IDE=y

#
# Please see Documentation/ide/ide.txt for help/info on IDE drives
#
CONFIG_IDE_XFER_MODE=y
CONFIG_IDE_TIMINGS=y
CONFIG_IDE_ATAPI=y
# CONFIG_BLK_DEV_IDE_SATA is not set
CONFIG_IDE_GD=m
CONFIG_IDE_GD_ATA=y
# CONFIG_IDE_GD_ATAPI is not set
CONFIG_BLK_DEV_IDECS=m
CONFIG_BLK_DEV_DELKIN=m
CONFIG_BLK_DEV_IDECD=m
CONFIG_BLK_DEV_IDECD_VERBOSE_ERRORS=y
CONFIG_BLK_DEV_IDETAPE=m
CONFIG_BLK_DEV_IDEACPI=y
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_PROC_FS=y

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=m
# CONFIG_BLK_DEV_PLATFORM is not set
CONFIG_BLK_DEV_CMD640=m
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
CONFIG_BLK_DEV_IDEPNP=m
CONFIG_BLK_DEV_IDEDMA_SFF=y

#
# PCI IDE chipsets support
#
CONFIG_BLK_DEV_IDEPCI=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=m
CONFIG_BLK_DEV_OPTI621=m
CONFIG_BLK_DEV_RZ1000=m
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_BLK_DEV_AEC62XX=m
CONFIG_BLK_DEV_ALI15X3=m
CONFIG_BLK_DEV_AMD74XX=m
CONFIG_BLK_DEV_ATIIXP=m
CONFIG_BLK_DEV_CMD64X=m
CONFIG_BLK_DEV_TRIFLEX=m
CONFIG_BLK_DEV_CS5520=m
CONFIG_BLK_DEV_CS5530=m
CONFIG_BLK_DEV_CS5535=m
# CONFIG_BLK_DEV_CS5536 is not set
CONFIG_BLK_DEV_HPT366=m
CONFIG_BLK_DEV_JMICRON=m
CONFIG_BLK_DEV_SC1200=m
CONFIG_BLK_DEV_PIIX=m
# CONFIG_BLK_DEV_IT8172 is not set
CONFIG_BLK_DEV_IT8213=m
CONFIG_BLK_DEV_IT821X=m
CONFIG_BLK_DEV_NS87415=m
CONFIG_BLK_DEV_PDC202XX_OLD=m
CONFIG_BLK_DEV_PDC202XX_NEW=m
CONFIG_BLK_DEV_SVWKS=m
CONFIG_BLK_DEV_SIIMAGE=m
CONFIG_BLK_DEV_SIS5513=m
CONFIG_BLK_DEV_SLC90E66=m
CONFIG_BLK_DEV_TRM290=m
CONFIG_BLK_DEV_VIA82CXXX=m
CONFIG_BLK_DEV_TC86C001=m

#
# Other IDE chipsets support
#

#
# Note: most of these also require special kernel boot parameters
#
# CONFIG_BLK_DEV_4DRIVES is not set
# CONFIG_BLK_DEV_ALI14XX is not set
# CONFIG_BLK_DEV_DTC2278 is not set
# CONFIG_BLK_DEV_HT6560B is not set
# CONFIG_BLK_DEV_QD65XX is not set
# CONFIG_BLK_DEV_UMC8672 is not set
CONFIG_BLK_DEV_IDEDMA=y

#
# SCSI device support
#
CONFIG_RAID_ATTRS=m
CONFIG_SCSI=m
CONFIG_SCSI_DMA=y
CONFIG_SCSI_TGT=m
CONFIG_SCSI_NETLINK=y
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
CONFIG_CHR_DEV_ST=m
CONFIG_CHR_DEV_OSST=m
CONFIG_BLK_DEV_SR=m
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=m
CONFIG_CHR_DEV_SCH=m
CONFIG_SCSI_ENCLOSURE=m
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
CONFIG_SCSI_SCAN_ASYNC=y
CONFIG_SCSI_WAIT_SCAN=m

#
# SCSI Transports
#
CONFIG_SCSI_SPI_ATTRS=m
CONFIG_SCSI_FC_ATTRS=m
CONFIG_SCSI_FC_TGT_ATTRS=y
CONFIG_SCSI_ISCSI_ATTRS=m
CONFIG_SCSI_SAS_ATTRS=m
CONFIG_SCSI_SAS_LIBSAS=m
CONFIG_SCSI_SAS_ATA=y
CONFIG_SCSI_SAS_HOST_SMP=y
# CONFIG_SCSI_SAS_LIBSAS_DEBUG is not set
CONFIG_SCSI_SRP_ATTRS=m
CONFIG_SCSI_SRP_TGT_ATTRS=y
CONFIG_SCSI_LOWLEVEL=y
CONFIG_ISCSI_TCP=m
# CONFIG_SCSI_CXGB3_ISCSI is not set
# CONFIG_SCSI_BNX2_ISCSI is not set
# CONFIG_BE2ISCSI is not set
CONFIG_BLK_DEV_3W_XXXX_RAID=m
CONFIG_SCSI_3W_9XXX=m
CONFIG_SCSI_7000FASST=m
CONFIG_SCSI_ACARD=m
CONFIG_SCSI_AHA152X=m
CONFIG_SCSI_AHA1542=m
CONFIG_SCSI_AACRAID=m
CONFIG_SCSI_AIC7XXX=m
CONFIG_AIC7XXX_CMDS_PER_DEVICE=8
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
CONFIG_AIC7XXX_DEBUG_ENABLE=y
CONFIG_AIC7XXX_DEBUG_MASK=0
CONFIG_AIC7XXX_REG_PRETTY_PRINT=y
CONFIG_SCSI_AIC7XXX_OLD=m
CONFIG_SCSI_AIC79XX=m
CONFIG_AIC79XX_CMDS_PER_DEVICE=32
CONFIG_AIC79XX_RESET_DELAY_MS=15000
CONFIG_AIC79XX_DEBUG_ENABLE=y
CONFIG_AIC79XX_DEBUG_MASK=0
CONFIG_AIC79XX_REG_PRETTY_PRINT=y
CONFIG_SCSI_AIC94XX=m
# CONFIG_AIC94XX_DEBUG is not set
CONFIG_SCSI_MVSAS=m
CONFIG_SCSI_MVSAS_DEBUG=y
CONFIG_SCSI_DPT_I2O=m
CONFIG_SCSI_ADVANSYS=m
CONFIG_SCSI_IN2000=m
CONFIG_SCSI_ARCMSR=m
# CONFIG_SCSI_ARCMSR_AER is not set
CONFIG_MEGARAID_NEWGEN=y
CONFIG_MEGARAID_MM=m
CONFIG_MEGARAID_MAILBOX=m
CONFIG_MEGARAID_LEGACY=m
CONFIG_MEGARAID_SAS=m
# CONFIG_SCSI_MPT2SAS is not set
CONFIG_SCSI_HPTIOP=m
CONFIG_SCSI_BUSLOGIC=m
# CONFIG_SCSI_FLASHPOINT is not set
# CONFIG_LIBFC is not set
# CONFIG_LIBFCOE is not set
# CONFIG_FCOE is not set
# CONFIG_FCOE_FNIC is not set
CONFIG_SCSI_DMX3191D=m
CONFIG_SCSI_DTC3280=m
CONFIG_SCSI_EATA=m
CONFIG_SCSI_EATA_TAGGED_QUEUE=y
CONFIG_SCSI_EATA_LINKED_COMMANDS=y
CONFIG_SCSI_EATA_MAX_TAGS=16
CONFIG_SCSI_FUTURE_DOMAIN=m
CONFIG_SCSI_GDTH=m
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set
CONFIG_SCSI_IPS=m
CONFIG_SCSI_INITIO=m
# CONFIG_SCSI_INIA100 is not set
CONFIG_SCSI_PPA=m
CONFIG_SCSI_IMM=m
# CONFIG_SCSI_IZIP_EPP16 is not set
# CONFIG_SCSI_IZIP_SLOW_CTR is not set
CONFIG_SCSI_NCR53C406A=m
CONFIG_SCSI_STEX=m
CONFIG_SCSI_SYM53C8XX_2=m
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1
CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16
CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
CONFIG_SCSI_SYM53C8XX_MMIO=y
CONFIG_SCSI_IPR=m
# CONFIG_SCSI_IPR_TRACE is not set
# CONFIG_SCSI_IPR_DUMP is not set
CONFIG_SCSI_PAS16=m
CONFIG_SCSI_QLOGIC_FAS=m
CONFIG_SCSI_QLOGIC_1280=m
CONFIG_SCSI_QLA_FC=m
CONFIG_SCSI_QLA_ISCSI=m
CONFIG_SCSI_LPFC=m
# CONFIG_SCSI_LPFC_DEBUG_FS is not set
CONFIG_SCSI_SYM53C416=m
CONFIG_SCSI_DC395x=m
CONFIG_SCSI_DC390T=m
CONFIG_SCSI_T128=m
CONFIG_SCSI_U14_34F=m
CONFIG_SCSI_U14_34F_TAGGED_QUEUE=y
CONFIG_SCSI_U14_34F_LINKED_COMMANDS=y
CONFIG_SCSI_U14_34F_MAX_TAGS=8
CONFIG_SCSI_ULTRASTOR=m
CONFIG_SCSI_NSP32=m
CONFIG_SCSI_DEBUG=m
# CONFIG_SCSI_PMCRAID is not set
CONFIG_SCSI_SRP=m
# CONFIG_SCSI_BFA_FC is not set
CONFIG_SCSI_LOWLEVEL_PCMCIA=y
CONFIG_PCMCIA_AHA152X=m
CONFIG_PCMCIA_FDOMAIN=m
CONFIG_PCMCIA_NINJA_SCSI=m
CONFIG_PCMCIA_QLOGIC=m
CONFIG_PCMCIA_SYM53C500=m
# CONFIG_SCSI_DH is not set
# CONFIG_SCSI_OSD_INITIATOR is not set
CONFIG_ATA=m
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_ATA_VERBOSE_ERROR=y
CONFIG_ATA_ACPI=y
CONFIG_SATA_PMP=y
CONFIG_SATA_AHCI=m
CONFIG_SATA_SIL24=m
CONFIG_ATA_SFF=y
CONFIG_SATA_SVW=m
CONFIG_ATA_PIIX=m
CONFIG_SATA_MV=m
CONFIG_SATA_NV=m
CONFIG_PDC_ADMA=m
CONFIG_SATA_QSTOR=m
CONFIG_SATA_PROMISE=m
CONFIG_SATA_SX4=m
CONFIG_SATA_SIL=m
CONFIG_SATA_SIS=m
CONFIG_SATA_ULI=m
CONFIG_SATA_VIA=m
CONFIG_SATA_VITESSE=m
CONFIG_SATA_INIC162X=m
# CONFIG_PATA_ACPI is not set
# CONFIG_PATA_ALI is not set
# CONFIG_PATA_AMD is not set
CONFIG_PATA_ARTOP=m
# CONFIG_PATA_ATP867X is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CS5520 is not set
# CONFIG_PATA_CS5530 is not set
# CONFIG_PATA_CS5535 is not set
# CONFIG_PATA_CS5536 is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
CONFIG_ATA_GENERIC=m
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_ISAPNP is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_JMICRON is not set
# CONFIG_PATA_LEGACY is not set
# CONFIG_PATA_TRIFLEX is not set
CONFIG_PATA_MARVELL=m
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_OLDPIIX is not set
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NINJA32 is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_NS87415 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PCMCIA is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_QDI is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RDC is not set
# CONFIG_PATA_RZ1000 is not set
# CONFIG_PATA_SC1200 is not set
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_SIL680 is not set
CONFIG_PATA_SIS=m
# CONFIG_PATA_VIA is not set
# CONFIG_PATA_WINBOND is not set
# CONFIG_PATA_WINBOND_VLB is not set
CONFIG_PATA_SCH=m
CONFIG_MD=y
CONFIG_BLK_DEV_MD=m
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
CONFIG_MD_RAID10=m
CONFIG_MD_RAID456=m
# CONFIG_MULTICORE_RAID456 is not set
CONFIG_MD_RAID6_PQ=m
# CONFIG_ASYNC_RAID6_TEST is not set
CONFIG_MD_MULTIPATH=m
CONFIG_MD_FAULTY=m
CONFIG_BLK_DEV_DM=m
# CONFIG_DM_DEBUG is not set
CONFIG_DM_CRYPT=m
CONFIG_DM_SNAPSHOT=m
CONFIG_DM_MIRROR=m
# CONFIG_DM_LOG_USERSPACE is not set
CONFIG_DM_ZERO=m
CONFIG_DM_MULTIPATH=m
# CONFIG_DM_MULTIPATH_QL is not set
# CONFIG_DM_MULTIPATH_ST is not set
CONFIG_DM_DELAY=m
CONFIG_DM_UEVENT=y
CONFIG_FUSION=y
CONFIG_FUSION_SPI=m
CONFIG_FUSION_FC=m
CONFIG_FUSION_SAS=m
CONFIG_FUSION_MAX_SGE=40
CONFIG_FUSION_CTL=m
CONFIG_FUSION_LAN=m
# CONFIG_FUSION_LOGGING is not set

#
# IEEE 1394 (FireWire) support
#

#
# You can enable one or both FireWire driver stacks.
#

#
# See the help texts for more information.
#
# CONFIG_FIREWIRE is not set
CONFIG_IEEE1394=m
CONFIG_IEEE1394_OHCI1394=m
CONFIG_IEEE1394_PCILYNX=m
CONFIG_IEEE1394_SBP2=m
# CONFIG_IEEE1394_SBP2_PHYS_DMA is not set
CONFIG_IEEE1394_ETH1394_ROM_ENTRY=y
CONFIG_IEEE1394_ETH1394=m
CONFIG_IEEE1394_RAWIO=m
CONFIG_IEEE1394_VIDEO1394=m
CONFIG_IEEE1394_DV1394=m
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
CONFIG_I2O=m
CONFIG_I2O_LCT_NOTIFY_ON_CHANGES=y
CONFIG_I2O_EXT_ADAPTEC=y
CONFIG_I2O_EXT_ADAPTEC_DMA64=y
CONFIG_I2O_CONFIG=m
CONFIG_I2O_CONFIG_OLD_IOCTL=y
CONFIG_I2O_BUS=m
CONFIG_I2O_BLOCK=m
CONFIG_I2O_SCSI=m
CONFIG_I2O_PROC=m
# CONFIG_MACINTOSH_DRIVERS is not set
CONFIG_NETDEVICES=y
CONFIG_IFB=m
CONFIG_DUMMY=m
CONFIG_BONDING=m
# CONFIG_MACVLAN is not set
CONFIG_EQUALIZER=m
CONFIG_TUN=m
CONFIG_VETH=m
CONFIG_NET_SB1000=m
CONFIG_ARCNET=m
CONFIG_ARCNET_1201=m
CONFIG_ARCNET_1051=m
CONFIG_ARCNET_RAW=m
CONFIG_ARCNET_CAP=m
CONFIG_ARCNET_COM90xx=m
CONFIG_ARCNET_COM90xxIO=m
CONFIG_ARCNET_RIM_I=m
CONFIG_ARCNET_COM20020=m
CONFIG_ARCNET_COM20020_ISA=m
CONFIG_ARCNET_COM20020_PCI=m
CONFIG_PHYLIB=m

#
# MII PHY device drivers
#
CONFIG_MARVELL_PHY=m
CONFIG_DAVICOM_PHY=m
CONFIG_QSEMI_PHY=m
CONFIG_LXT_PHY=m
CONFIG_CICADA_PHY=m
CONFIG_VITESSE_PHY=m
CONFIG_SMSC_PHY=m
CONFIG_BROADCOM_PHY=m
CONFIG_ICPLUS_PHY=m
CONFIG_REALTEK_PHY=m
# CONFIG_NATIONAL_PHY is not set
# CONFIG_STE10XP is not set
# CONFIG_LSI_ET1011C_PHY is not set
CONFIG_MDIO_BITBANG=m
CONFIG_NET_ETHERNET=y
CONFIG_MII=m
CONFIG_HAPPYMEAL=m
CONFIG_SUNGEM=m
CONFIG_CASSINI=m
CONFIG_NET_VENDOR_3COM=y
CONFIG_EL1=m
CONFIG_EL2=m
CONFIG_ELPLUS=m
CONFIG_EL16=m
CONFIG_EL3=m
CONFIG_3C515=m
CONFIG_VORTEX=m
CONFIG_TYPHOON=m
CONFIG_LANCE=m
CONFIG_NET_VENDOR_SMC=y
CONFIG_WD80x3=m
CONFIG_ULTRA=m
CONFIG_SMC9194=m
CONFIG_ENC28J60=m
# CONFIG_ENC28J60_WRITEVERIFY is not set
# CONFIG_ETHOC is not set
CONFIG_NET_VENDOR_RACAL=y
CONFIG_NI52=m
CONFIG_NI65=m
# CONFIG_DNET is not set
CONFIG_NET_TULIP=y
CONFIG_DE2104X=m
CONFIG_DE2104X_DSL=0
CONFIG_TULIP=m
# CONFIG_TULIP_MWI is not set
# CONFIG_TULIP_MMIO is not set
CONFIG_TULIP_NAPI=y
CONFIG_TULIP_NAPI_HW_MITIGATION=y
CONFIG_DE4X5=m
CONFIG_WINBOND_840=m
CONFIG_DM9102=m
CONFIG_ULI526X=m
CONFIG_PCMCIA_XIRCOM=m
CONFIG_AT1700=m
CONFIG_DEPCA=m
CONFIG_HP100=m
CONFIG_NET_ISA=y
CONFIG_E2100=m
CONFIG_EWRK3=m
CONFIG_EEXPRESS=m
CONFIG_EEXPRESS_PRO=m
CONFIG_HPLAN_PLUS=m
CONFIG_HPLAN=m
CONFIG_LP486E=m
CONFIG_ETH16I=m
CONFIG_NE2000=m
CONFIG_ZNET=m
CONFIG_SEEQ8005=m
# CONFIG_IBM_NEW_EMAC_ZMII is not set
# CONFIG_IBM_NEW_EMAC_RGMII is not set
# CONFIG_IBM_NEW_EMAC_TAH is not set
# CONFIG_IBM_NEW_EMAC_EMAC4 is not set
# CONFIG_IBM_NEW_EMAC_NO_FLOW_CTRL is not set
# CONFIG_IBM_NEW_EMAC_MAL_CLR_ICINTSTAT is not set
# CONFIG_IBM_NEW_EMAC_MAL_COMMON_ERR is not set
CONFIG_NET_PCI=y
CONFIG_PCNET32=m
CONFIG_AMD8111_ETH=m
CONFIG_ADAPTEC_STARFIRE=m
CONFIG_AC3200=m
CONFIG_APRICOT=m
CONFIG_B44=m
CONFIG_B44_PCI_AUTOSELECT=y
CONFIG_B44_PCICORE_AUTOSELECT=y
CONFIG_B44_PCI=y
CONFIG_FORCEDETH=m
# CONFIG_FORCEDETH_NAPI is not set
CONFIG_CS89x0=m
CONFIG_E100=m
CONFIG_FEALNX=m
CONFIG_NATSEMI=m
CONFIG_NE2K_PCI=m
CONFIG_8139CP=m
CONFIG_8139TOO=m
CONFIG_8139TOO_PIO=y
CONFIG_8139TOO_TUNE_TWISTER=y
CONFIG_8139TOO_8129=y
# CONFIG_8139_OLD_RX_RESET is not set
CONFIG_R6040=m
CONFIG_SIS900=m
CONFIG_EPIC100=m
# CONFIG_SMSC9420 is not set
CONFIG_SUNDANCE=m
# CONFIG_SUNDANCE_MMIO is not set
CONFIG_TLAN=m
# CONFIG_KS8842 is not set
# CONFIG_KS8851 is not set
# CONFIG_KS8851_MLL is not set
CONFIG_VIA_RHINE=m
# CONFIG_VIA_RHINE_MMIO is not set
CONFIG_SC92031=m
# CONFIG_NET_POCKET is not set
# CONFIG_ATL2 is not set
CONFIG_NETDEV_1000=y
CONFIG_ACENIC=m
# CONFIG_ACENIC_OMIT_TIGON_I is not set
CONFIG_DL2K=m
CONFIG_E1000=m
CONFIG_E1000E=m
CONFIG_IP1000=m
CONFIG_IGB=m
# CONFIG_IGBVF is not set
CONFIG_NS83820=m
CONFIG_HAMACHI=m
CONFIG_YELLOWFIN=m
CONFIG_R8169=m
CONFIG_R8169_VLAN=y
CONFIG_SIS190=m
CONFIG_SKGE=m
# CONFIG_SKGE_DEBUG is not set
CONFIG_SKY2=m
# CONFIG_SKY2_DEBUG is not set
CONFIG_VIA_VELOCITY=m
CONFIG_TIGON3=m
CONFIG_BNX2=m
# CONFIG_CNIC is not set
CONFIG_QLA3XXX=m
CONFIG_ATL1=m
CONFIG_ATL1E=m
# CONFIG_ATL1C is not set
# CONFIG_JME is not set
CONFIG_NETDEV_10000=y
CONFIG_MDIO=m
CONFIG_CHELSIO_T1=m
CONFIG_CHELSIO_T1_1G=y
CONFIG_CHELSIO_T3_DEPENDS=y
CONFIG_CHELSIO_T3=m
# CONFIG_ENIC is not set
CONFIG_IXGBE=m
CONFIG_IXGB=m
CONFIG_S2IO=m
# CONFIG_VXGE is not set
CONFIG_MYRI10GE=m
CONFIG_NETXEN_NIC=m
CONFIG_NIU=m
# CONFIG_MLX4_EN is not set
CONFIG_MLX4_CORE=m
CONFIG_MLX4_DEBUG=y
CONFIG_TEHUTI=m
CONFIG_BNX2X=m
# CONFIG_QLGE is not set
CONFIG_SFC=m
CONFIG_SFC_MTD=y
# CONFIG_BE2NET is not set
CONFIG_TR=y
CONFIG_IBMTR=m
CONFIG_IBMOL=m
CONFIG_IBMLS=m
# CONFIG_3C359 is not set
CONFIG_TMS380TR=m
CONFIG_TMSPCI=m
CONFIG_SKISA=m
CONFIG_PROTEON=m
CONFIG_ABYSS=m
# CONFIG_SMCTR is not set
CONFIG_WLAN=y
CONFIG_WLAN_PRE80211=y
CONFIG_STRIP=m
CONFIG_ARLAN=m
CONFIG_WAVELAN=m
CONFIG_PCMCIA_WAVELAN=m
CONFIG_PCMCIA_NETWAVE=m
CONFIG_WLAN_80211=y
CONFIG_PCMCIA_RAYCS=m
CONFIG_LIBERTAS=m
CONFIG_LIBERTAS_USB=m
CONFIG_LIBERTAS_CS=m
CONFIG_LIBERTAS_SDIO=m
# CONFIG_LIBERTAS_SPI is not set
# CONFIG_LIBERTAS_DEBUG is not set
# CONFIG_LIBERTAS_THINFIRM is not set
CONFIG_AIRO=m
CONFIG_ATMEL=m
CONFIG_PCI_ATMEL=m
CONFIG_PCMCIA_ATMEL=m
# CONFIG_AT76C50X_USB is not set
CONFIG_AIRO_CS=m
CONFIG_PCMCIA_WL3501=m
# CONFIG_PRISM54 is not set
CONFIG_USB_ZD1201=m
CONFIG_USB_NET_RNDIS_WLAN=m
CONFIG_RTL8180=m
CONFIG_RTL8187=m
CONFIG_RTL8187_LEDS=y
CONFIG_ADM8211=m
# CONFIG_MAC80211_HWSIM is not set
# CONFIG_MWL8K is not set
CONFIG_P54_COMMON=m
CONFIG_P54_USB=m
CONFIG_P54_PCI=m
# CONFIG_P54_SPI is not set
CONFIG_P54_LEDS=y
# CONFIG_ATH_COMMON is not set
CONFIG_IPW2100=m
CONFIG_IPW2100_MONITOR=y
# CONFIG_IPW2100_DEBUG is not set
CONFIG_IPW2200=m
CONFIG_IPW2200_MONITOR=y
CONFIG_IPW2200_RADIOTAP=y
CONFIG_IPW2200_PROMISCUOUS=y
CONFIG_IPW2200_QOS=y
# CONFIG_IPW2200_DEBUG is not set
CONFIG_LIBIPW=m
# CONFIG_LIBIPW_DEBUG is not set
CONFIG_IWLWIFI=m
CONFIG_IWLWIFI_LEDS=y
# CONFIG_IWLWIFI_SPECTRUM_MEASUREMENT is not set
# CONFIG_IWLWIFI_DEBUG is not set
# CONFIG_IWLAGN is not set
CONFIG_IWL3945=m
CONFIG_IWL3945_SPECTRUM_MEASUREMENT=y
CONFIG_HOSTAP=m
CONFIG_HOSTAP_FIRMWARE=y
# CONFIG_HOSTAP_FIRMWARE_NVRAM is not set
CONFIG_HOSTAP_PLX=m
CONFIG_HOSTAP_PCI=m
CONFIG_HOSTAP_CS=m
CONFIG_B43=m
CONFIG_B43_PCI_AUTOSELECT=y
CONFIG_B43_PCICORE_AUTOSELECT=y
CONFIG_B43_PCMCIA=y
# CONFIG_B43_SDIO is not set
CONFIG_B43_PIO=y
CONFIG_B43_PHY_LP=y
CONFIG_B43_LEDS=y
CONFIG_B43_HWRNG=y
# CONFIG_B43_DEBUG is not set
CONFIG_B43LEGACY=m
CONFIG_B43LEGACY_PCI_AUTOSELECT=y
CONFIG_B43LEGACY_PCICORE_AUTOSELECT=y
CONFIG_B43LEGACY_LEDS=y
CONFIG_B43LEGACY_HWRNG=y
CONFIG_B43LEGACY_DEBUG=y
CONFIG_B43LEGACY_DMA=y
CONFIG_B43LEGACY_PIO=y
CONFIG_B43LEGACY_DMA_AND_PIO_MODE=y
# CONFIG_B43LEGACY_DMA_MODE is not set
# CONFIG_B43LEGACY_PIO_MODE is not set
CONFIG_ZD1211RW=m
# CONFIG_ZD1211RW_DEBUG is not set
CONFIG_RT2X00=m
CONFIG_RT2400PCI=m
CONFIG_RT2500PCI=m
CONFIG_RT61PCI=m
CONFIG_RT2500USB=m
CONFIG_RT73USB=m
# CONFIG_RT2800USB is not set
CONFIG_RT2X00_LIB_PCI=m
CONFIG_RT2X00_LIB_USB=m
CONFIG_RT2X00_LIB=m
CONFIG_RT2X00_LIB_FIRMWARE=y
CONFIG_RT2X00_LIB_CRYPTO=y
CONFIG_RT2X00_LIB_LEDS=y
# CONFIG_RT2X00_DEBUG is not set
CONFIG_HERMES=m
CONFIG_HERMES_CACHE_FW_ON_INIT=y
CONFIG_PLX_HERMES=m
CONFIG_TMD_HERMES=m
CONFIG_NORTEL_HERMES=m
CONFIG_PCI_HERMES=m
CONFIG_PCMCIA_HERMES=m
CONFIG_PCMCIA_SPECTRUM=m
# CONFIG_WL12XX is not set
# CONFIG_IWM is not set

#
# Enable WiMAX (Networking options) to see the WiMAX drivers
#

#
# USB Network Adapters
#
CONFIG_USB_CATC=m
CONFIG_USB_KAWETH=m
CONFIG_USB_PEGASUS=m
CONFIG_USB_RTL8150=m
CONFIG_USB_USBNET=m
CONFIG_USB_NET_AX8817X=m
CONFIG_USB_NET_CDCETHER=m
# CONFIG_USB_NET_CDC_EEM is not set
CONFIG_USB_NET_DM9601=m
# CONFIG_USB_NET_SMSC95XX is not set
CONFIG_USB_NET_GL620A=m
CONFIG_USB_NET_NET1080=m
CONFIG_USB_NET_PLUSB=m
CONFIG_USB_NET_MCS7830=m
CONFIG_USB_NET_RNDIS_HOST=m
CONFIG_USB_NET_CDC_SUBSET=m
CONFIG_USB_ALI_M5632=y
CONFIG_USB_AN2720=y
CONFIG_USB_BELKIN=y
CONFIG_USB_ARMLINUX=y
CONFIG_USB_EPSON2888=y
CONFIG_USB_KC2190=y
CONFIG_USB_NET_ZAURUS=m
# CONFIG_USB_HSO is not set
# CONFIG_USB_NET_INT51X1 is not set
CONFIG_NET_PCMCIA=y
CONFIG_PCMCIA_3C589=m
CONFIG_PCMCIA_3C574=m
CONFIG_PCMCIA_FMVJ18X=m
CONFIG_PCMCIA_PCNET=m
CONFIG_PCMCIA_NMCLAN=m
CONFIG_PCMCIA_SMC91C92=m
CONFIG_PCMCIA_XIRC2PS=m
CONFIG_PCMCIA_AXNET=m
CONFIG_ARCNET_COM20020_CS=m
CONFIG_PCMCIA_IBMTR=m
CONFIG_WAN=y
CONFIG_HOSTESS_SV11=m
CONFIG_COSA=m
CONFIG_LANMEDIA=m
CONFIG_SEALEVEL_4021=m
CONFIG_HDLC=m
CONFIG_HDLC_RAW=m
CONFIG_HDLC_RAW_ETH=m
CONFIG_HDLC_CISCO=m
CONFIG_HDLC_FR=m
CONFIG_HDLC_PPP=m
CONFIG_HDLC_X25=m
CONFIG_PCI200SYN=m
CONFIG_WANXL=m
# CONFIG_PC300TOO is not set
CONFIG_N2=m
CONFIG_C101=m
CONFIG_FARSYNC=m
CONFIG_DSCC4=m
CONFIG_DSCC4_PCISYNC=y
CONFIG_DSCC4_PCI_RST=y
CONFIG_DLCI=m
CONFIG_DLCI_MAX=8
CONFIG_SDLA=m
CONFIG_WAN_ROUTER_DRIVERS=m
CONFIG_CYCLADES_SYNC=m
CONFIG_CYCLOMX_X25=y
CONFIG_LAPBETHER=m
CONFIG_X25_ASY=m
CONFIG_SBNI=m
# CONFIG_SBNI_MULTILINE is not set
CONFIG_ATM_DRIVERS=y
CONFIG_ATM_DUMMY=m
CONFIG_ATM_TCP=m
CONFIG_ATM_LANAI=m
CONFIG_ATM_ENI=m
# CONFIG_ATM_ENI_DEBUG is not set
# CONFIG_ATM_ENI_TUNE_BURST is not set
CONFIG_ATM_FIRESTREAM=m
CONFIG_ATM_ZATM=m
# CONFIG_ATM_ZATM_DEBUG is not set
CONFIG_ATM_NICSTAR=m
# CONFIG_ATM_NICSTAR_USE_SUNI is not set
# CONFIG_ATM_NICSTAR_USE_IDT77105 is not set
CONFIG_ATM_IDT77252=m
# CONFIG_ATM_IDT77252_DEBUG is not set
# CONFIG_ATM_IDT77252_RCV_ALL is not set
CONFIG_ATM_IDT77252_USE_SUNI=y
# CONFIG_ATM_AMBASSADOR is not set
CONFIG_ATM_HORIZON=m
# CONFIG_ATM_HORIZON_DEBUG is not set
CONFIG_ATM_IA=m
# CONFIG_ATM_IA_DEBUG is not set
# CONFIG_ATM_FORE200E is not set
CONFIG_ATM_HE=m
CONFIG_ATM_HE_USE_SUNI=y
# CONFIG_ATM_SOLOS is not set
CONFIG_XEN_NETDEV_FRONTEND=m
CONFIG_FDDI=y
CONFIG_DEFXX=m
# CONFIG_DEFXX_MMIO is not set
CONFIG_SKFP=m
CONFIG_HIPPI=y
CONFIG_ROADRUNNER=m
# CONFIG_ROADRUNNER_LARGE_RINGS is not set
CONFIG_PLIP=m
CONFIG_PPP=m
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
CONFIG_PPP_MPPE=m
CONFIG_PPPOE=m
CONFIG_PPPOATM=m
CONFIG_PPPOL2TP=m
CONFIG_SLIP=m
CONFIG_SLIP_COMPRESSED=y
CONFIG_SLHC=m
CONFIG_SLIP_SMART=y
CONFIG_SLIP_MODE_SLIP6=y
CONFIG_NET_FC=y
CONFIG_NETCONSOLE=m
CONFIG_NETCONSOLE_DYNAMIC=y
CONFIG_NETPOLL=y
# CONFIG_NETPOLL_TRAP is not set
CONFIG_NET_POLL_CONTROLLER=y
CONFIG_VIRTIO_NET=m
# CONFIG_VMXNET3 is not set
# CONFIG_ISDN is not set
CONFIG_PHONE=m
CONFIG_PHONE_IXJ=m
CONFIG_PHONE_IXJ_PCMCIA=m

#
# Input device support
#
CONFIG_INPUT=y
CONFIG_INPUT_FF_MEMLESS=m
CONFIG_INPUT_POLLDEV=m

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=m
CONFIG_INPUT_EVDEV=m
# CONFIG_INPUT_EVBUG is not set
CONFIG_XEN_KBDDEV_FRONTEND=y

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
# CONFIG_KEYBOARD_ADP5588 is not set
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_QT2160 is not set
CONFIG_KEYBOARD_LKKBD=m
# CONFIG_KEYBOARD_LM8323 is not set
# CONFIG_KEYBOARD_MAX7359 is not set
CONFIG_KEYBOARD_NEWTON=m
# CONFIG_KEYBOARD_OPENCORES is not set
CONFIG_KEYBOARD_STOWAWAY=m
CONFIG_KEYBOARD_SUNKBD=m
CONFIG_KEYBOARD_XTKBD=m
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=m
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
# CONFIG_MOUSE_PS2_ELANTECH is not set
# CONFIG_MOUSE_PS2_SENTELIC is not set
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
CONFIG_MOUSE_SERIAL=m
CONFIG_MOUSE_APPLETOUCH=m
# CONFIG_MOUSE_BCM5974 is not set
CONFIG_MOUSE_INPORT=m
# CONFIG_MOUSE_ATIXL is not set
CONFIG_MOUSE_LOGIBM=m
CONFIG_MOUSE_PC110PAD=m
CONFIG_MOUSE_VSXXXAA=m
# CONFIG_MOUSE_SYNAPTICS_I2C is not set
CONFIG_INPUT_JOYSTICK=y
CONFIG_JOYSTICK_ANALOG=m
CONFIG_JOYSTICK_A3D=m
CONFIG_JOYSTICK_ADI=m
CONFIG_JOYSTICK_COBRA=m
CONFIG_JOYSTICK_GF2K=m
CONFIG_JOYSTICK_GRIP=m
CONFIG_JOYSTICK_GRIP_MP=m
CONFIG_JOYSTICK_GUILLEMOT=m
CONFIG_JOYSTICK_INTERACT=m
CONFIG_JOYSTICK_SIDEWINDER=m
CONFIG_JOYSTICK_TMDC=m
CONFIG_JOYSTICK_IFORCE=m
CONFIG_JOYSTICK_IFORCE_USB=y
CONFIG_JOYSTICK_IFORCE_232=y
CONFIG_JOYSTICK_WARRIOR=m
CONFIG_JOYSTICK_MAGELLAN=m
CONFIG_JOYSTICK_SPACEORB=m
CONFIG_JOYSTICK_SPACEBALL=m
CONFIG_JOYSTICK_STINGER=m
CONFIG_JOYSTICK_TWIDJOY=m
CONFIG_JOYSTICK_ZHENHUA=m
CONFIG_JOYSTICK_DB9=m
CONFIG_JOYSTICK_GAMECON=m
CONFIG_JOYSTICK_TURBOGRAFX=m
CONFIG_JOYSTICK_JOYDUMP=m
CONFIG_JOYSTICK_XPAD=m
CONFIG_JOYSTICK_XPAD_FF=y
CONFIG_JOYSTICK_XPAD_LEDS=y
# CONFIG_JOYSTICK_WALKERA0701 is not set
CONFIG_INPUT_TABLET=y
CONFIG_TABLET_USB_ACECAD=m
CONFIG_TABLET_USB_AIPTEK=m
CONFIG_TABLET_USB_GTCO=m
CONFIG_TABLET_USB_KBTAB=m
CONFIG_TABLET_USB_WACOM=m
CONFIG_INPUT_TOUCHSCREEN=y
CONFIG_TOUCHSCREEN_ADS7846=m
# CONFIG_TOUCHSCREEN_AD7877 is not set
# CONFIG_TOUCHSCREEN_AD7879_I2C is not set
# CONFIG_TOUCHSCREEN_AD7879_SPI is not set
# CONFIG_TOUCHSCREEN_AD7879 is not set
# CONFIG_TOUCHSCREEN_EETI is not set
CONFIG_TOUCHSCREEN_FUJITSU=m
CONFIG_TOUCHSCREEN_GUNZE=m
CONFIG_TOUCHSCREEN_ELO=m
# CONFIG_TOUCHSCREEN_WACOM_W8001 is not set
# CONFIG_TOUCHSCREEN_MCS5000 is not set
CONFIG_TOUCHSCREEN_MTOUCH=m
# CONFIG_TOUCHSCREEN_INEXIO is not set
CONFIG_TOUCHSCREEN_MK712=m
# CONFIG_TOUCHSCREEN_HTCPEN is not set
CONFIG_TOUCHSCREEN_PENMOUNT=m
CONFIG_TOUCHSCREEN_TOUCHRIGHT=m
CONFIG_TOUCHSCREEN_TOUCHWIN=m
CONFIG_TOUCHSCREEN_WM97XX=m
CONFIG_TOUCHSCREEN_WM9705=y
CONFIG_TOUCHSCREEN_WM9712=y
CONFIG_TOUCHSCREEN_WM9713=y
CONFIG_TOUCHSCREEN_USB_COMPOSITE=m
CONFIG_TOUCHSCREEN_USB_EGALAX=y
CONFIG_TOUCHSCREEN_USB_PANJIT=y
CONFIG_TOUCHSCREEN_USB_3M=y
CONFIG_TOUCHSCREEN_USB_ITM=y
CONFIG_TOUCHSCREEN_USB_ETURBO=y
CONFIG_TOUCHSCREEN_USB_GUNZE=y
CONFIG_TOUCHSCREEN_USB_DMC_TSC10=y
CONFIG_TOUCHSCREEN_USB_IRTOUCH=y
CONFIG_TOUCHSCREEN_USB_IDEALTEK=y
CONFIG_TOUCHSCREEN_USB_GENERAL_TOUCH=y
CONFIG_TOUCHSCREEN_USB_GOTOP=y
CONFIG_TOUCHSCREEN_USB_JASTEC=y
CONFIG_TOUCHSCREEN_USB_E2I=y
# CONFIG_TOUCHSCREEN_TOUCHIT213 is not set
# CONFIG_TOUCHSCREEN_TSC2007 is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=m
CONFIG_INPUT_APANEL=m
CONFIG_INPUT_WISTRON_BTNS=m
CONFIG_INPUT_ATLAS_BTNS=m
CONFIG_INPUT_ATI_REMOTE=m
CONFIG_INPUT_ATI_REMOTE2=m
CONFIG_INPUT_KEYSPAN_REMOTE=m
CONFIG_INPUT_POWERMATE=m
CONFIG_INPUT_YEALINK=m
# CONFIG_INPUT_CM109 is not set
CONFIG_INPUT_UINPUT=m
# CONFIG_INPUT_WINBOND_CIR is not set

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=m
CONFIG_SERIO_CT82C710=m
CONFIG_SERIO_PARKBD=m
CONFIG_SERIO_PCIPS2=m
CONFIG_SERIO_LIBPS2=y
CONFIG_SERIO_RAW=m
CONFIG_GAMEPORT=m
CONFIG_GAMEPORT_NS558=m
CONFIG_GAMEPORT_L4=m
CONFIG_GAMEPORT_EMU10K1=m
CONFIG_GAMEPORT_FM801=m

#
# Character devices
#
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_VT_HW_CONSOLE_BINDING is not set
CONFIG_DEVKMEM=y
CONFIG_SERIAL_NONSTANDARD=y
CONFIG_COMPUTONE=m
CONFIG_ROCKETPORT=m
CONFIG_CYCLADES=m
# CONFIG_CYZ_INTR is not set
# CONFIG_DIGIEPCA is not set
# CONFIG_MOXA_INTELLIO is not set
CONFIG_MOXA_SMARTIO=m
# CONFIG_ISI is not set
CONFIG_SYNCLINK=m
CONFIG_SYNCLINKMP=m
CONFIG_SYNCLINK_GT=m
CONFIG_N_HDLC=m
# CONFIG_RISCOM8 is not set
# CONFIG_SPECIALIX is not set
CONFIG_STALDRV=y
# CONFIG_STALLION is not set
# CONFIG_ISTALLION is not set
CONFIG_NOZOMI=m

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
CONFIG_SERIAL_8250_CS=m
CONFIG_SERIAL_8250_NR_UARTS=32
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_FOURPORT=m
CONFIG_SERIAL_8250_ACCENT=m
CONFIG_SERIAL_8250_BOCA=m
CONFIG_SERIAL_8250_EXAR_ST16C554=m
CONFIG_SERIAL_8250_HUB6=m
CONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not set
CONFIG_SERIAL_8250_RSA=y

#
# Non-8250 serial port support
#
# CONFIG_SERIAL_MAX3100 is not set
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_SERIAL_JSM=m
CONFIG_UNIX98_PTYS=y
# CONFIG_DEVPTS_MULTIPLE_INSTANCES is not set
# CONFIG_LEGACY_PTYS is not set
CONFIG_PRINTER=m
# CONFIG_LP_CONSOLE is not set
CONFIG_PPDEV=m
CONFIG_HVC_DRIVER=y
CONFIG_HVC_IRQ=y
CONFIG_HVC_XEN=y
# CONFIG_VIRTIO_CONSOLE is not set
CONFIG_IPMI_HANDLER=m
# CONFIG_IPMI_PANIC_EVENT is not set
CONFIG_IPMI_DEVICE_INTERFACE=m
CONFIG_IPMI_SI=m
CONFIG_IPMI_WATCHDOG=m
CONFIG_IPMI_POWEROFF=m
CONFIG_HW_RANDOM=m
# CONFIG_HW_RANDOM_TIMERIOMEM is not set
CONFIG_HW_RANDOM_INTEL=m
CONFIG_HW_RANDOM_AMD=m
CONFIG_HW_RANDOM_GEODE=m
CONFIG_HW_RANDOM_VIA=m
CONFIG_HW_RANDOM_VIRTIO=m
CONFIG_NVRAM=m
CONFIG_DTLK=m
CONFIG_R3964=m
CONFIG_APPLICOM=m
CONFIG_SONYPI=m

#
# PCMCIA character devices
#
CONFIG_SYNCLINK_CS=m
CONFIG_CARDMAN_4000=m
CONFIG_CARDMAN_4040=m
CONFIG_IPWIRELESS=m
CONFIG_MWAVE=m
CONFIG_SCx200_GPIO=m
CONFIG_PC8736x_GPIO=m
CONFIG_NSC_GPIO=m
CONFIG_CS5535_GPIO=m
CONFIG_RAW_DRIVER=m
CONFIG_MAX_RAW_DEVS=256
CONFIG_HPET=y
CONFIG_HPET_MMAP=y
CONFIG_HANGCHECK_TIMER=m
CONFIG_TCG_TPM=m
CONFIG_TCG_TIS=m
CONFIG_TCG_NSC=m
CONFIG_TCG_ATMEL=m
CONFIG_TCG_INFINEON=m
CONFIG_TELCLOCK=m
CONFIG_DEVPORT=y
CONFIG_I2C=m
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_COMPAT=y
CONFIG_I2C_CHARDEV=m
CONFIG_I2C_HELPER_AUTO=y
CONFIG_I2C_ALGOBIT=m
CONFIG_I2C_ALGOPCA=m

#
# I2C Hardware Bus support
#

#
# PC SMBus host controller drivers
#
CONFIG_I2C_ALI1535=m
CONFIG_I2C_ALI1563=m
CONFIG_I2C_ALI15X3=m
CONFIG_I2C_AMD756=m
CONFIG_I2C_AMD756_S4882=m
CONFIG_I2C_AMD8111=m
CONFIG_I2C_I801=m
# CONFIG_I2C_ISCH is not set
CONFIG_I2C_PIIX4=m
CONFIG_I2C_NFORCE2=m
# CONFIG_I2C_NFORCE2_S4985 is not set
CONFIG_I2C_SIS5595=m
CONFIG_I2C_SIS630=m
CONFIG_I2C_SIS96X=m
CONFIG_I2C_VIA=m
CONFIG_I2C_VIAPRO=m

#
# ACPI drivers
#
# CONFIG_I2C_SCMI is not set

#
# I2C system bus drivers (mostly embedded / system-on-chip)
#
CONFIG_I2C_OCORES=m
CONFIG_I2C_SIMTEC=m

#
# External I2C/SMBus adapter drivers
#
CONFIG_I2C_PARPORT=m
CONFIG_I2C_PARPORT_LIGHT=m
CONFIG_I2C_TAOS_EVM=m
CONFIG_I2C_TINY_USB=m

#
# Graphics adapter I2C/DDC channel drivers
#
CONFIG_I2C_VOODOO3=m

#
# Other I2C/SMBus bus drivers
#
CONFIG_I2C_PCA_ISA=m
CONFIG_I2C_PCA_PLATFORM=m
CONFIG_I2C_STUB=m
CONFIG_SCx200_I2C=m
CONFIG_SCx200_I2C_SCL=12
CONFIG_SCx200_I2C_SDA=13
CONFIG_SCx200_ACB=m

#
# Miscellaneous I2C Chip support
#
CONFIG_DS1682=m
CONFIG_SENSORS_TSL2550=m
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set
CONFIG_SPI=y
# CONFIG_SPI_DEBUG is not set
CONFIG_SPI_MASTER=y

#
# SPI Master Controller Drivers
#
CONFIG_SPI_BITBANG=m
CONFIG_SPI_BUTTERFLY=m
CONFIG_SPI_LM70_LLP=m

#
# SPI Protocol Masters
#
# CONFIG_SPI_SPIDEV is not set
CONFIG_SPI_TLE62X0=m

#
# PPS support
#
# CONFIG_PPS is not set
CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
# CONFIG_GPIOLIB is not set
CONFIG_W1=m
CONFIG_W1_CON=y

#
# 1-wire Bus Masters
#
CONFIG_W1_MASTER_MATROX=m
CONFIG_W1_MASTER_DS2490=m
CONFIG_W1_MASTER_DS2482=m

#
# 1-wire Slaves
#
CONFIG_W1_SLAVE_THERM=m
CONFIG_W1_SLAVE_SMEM=m
# CONFIG_W1_SLAVE_DS2431 is not set
CONFIG_W1_SLAVE_DS2433=m
# CONFIG_W1_SLAVE_DS2433_CRC is not set
CONFIG_W1_SLAVE_DS2760=m
# CONFIG_W1_SLAVE_BQ27000 is not set
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
CONFIG_PDA_POWER=m
CONFIG_BATTERY_DS2760=m
# CONFIG_BATTERY_DS2782 is not set
# CONFIG_BATTERY_BQ27x00 is not set
# CONFIG_BATTERY_MAX17040 is not set
CONFIG_HWMON=y
CONFIG_HWMON_VID=m
# CONFIG_HWMON_DEBUG_CHIP is not set

#
# Native drivers
#
CONFIG_SENSORS_ABITUGURU=m
CONFIG_SENSORS_ABITUGURU3=m
# CONFIG_SENSORS_AD7414 is not set
CONFIG_SENSORS_AD7418=m
# CONFIG_SENSORS_ADCXX is not set
CONFIG_SENSORS_ADM1021=m
CONFIG_SENSORS_ADM1025=m
CONFIG_SENSORS_ADM1026=m
CONFIG_SENSORS_ADM1029=m
CONFIG_SENSORS_ADM1031=m
CONFIG_SENSORS_ADM9240=m
# CONFIG_SENSORS_ADT7462 is not set
CONFIG_SENSORS_ADT7470=m
CONFIG_SENSORS_ADT7473=m
# CONFIG_SENSORS_ADT7475 is not set
CONFIG_SENSORS_K8TEMP=m
CONFIG_SENSORS_ASB100=m
CONFIG_SENSORS_ATXP1=m
CONFIG_SENSORS_DS1621=m
CONFIG_SENSORS_I5K_AMB=m
CONFIG_SENSORS_F71805F=m
CONFIG_SENSORS_F71882FG=m
CONFIG_SENSORS_F75375S=m
CONFIG_SENSORS_FSCHMD=m
# CONFIG_SENSORS_G760A is not set
CONFIG_SENSORS_GL518SM=m
CONFIG_SENSORS_GL520SM=m
CONFIG_SENSORS_CORETEMP=m
CONFIG_SENSORS_IBMAEM=m
CONFIG_SENSORS_IBMPEX=m
CONFIG_SENSORS_IT87=m
CONFIG_SENSORS_LM63=m
CONFIG_SENSORS_LM70=m
CONFIG_SENSORS_LM75=m
CONFIG_SENSORS_LM77=m
CONFIG_SENSORS_LM78=m
CONFIG_SENSORS_LM80=m
CONFIG_SENSORS_LM83=m
CONFIG_SENSORS_LM85=m
CONFIG_SENSORS_LM87=m
CONFIG_SENSORS_LM90=m
CONFIG_SENSORS_LM92=m
CONFIG_SENSORS_LM93=m
# CONFIG_SENSORS_LTC4215 is not set
# CONFIG_SENSORS_LTC4245 is not set
# CONFIG_SENSORS_LM95241 is not set
# CONFIG_SENSORS_MAX1111 is not set
CONFIG_SENSORS_MAX1619=m
CONFIG_SENSORS_MAX6650=m
CONFIG_SENSORS_PC87360=m
CONFIG_SENSORS_PC87427=m
CONFIG_SENSORS_PCF8591=m
CONFIG_SENSORS_SIS5595=m
CONFIG_SENSORS_DME1737=m
CONFIG_SENSORS_SMSC47M1=m
CONFIG_SENSORS_SMSC47M192=m
CONFIG_SENSORS_SMSC47B397=m
CONFIG_SENSORS_ADS7828=m
CONFIG_SENSORS_THMC50=m
# CONFIG_SENSORS_TMP401 is not set
# CONFIG_SENSORS_TMP421 is not set
CONFIG_SENSORS_VIA686A=m
CONFIG_SENSORS_VT1211=m
CONFIG_SENSORS_VT8231=m
CONFIG_SENSORS_W83781D=m
CONFIG_SENSORS_W83791D=m
CONFIG_SENSORS_W83792D=m
CONFIG_SENSORS_W83793=m
CONFIG_SENSORS_W83L785TS=m
CONFIG_SENSORS_W83L786NG=m
CONFIG_SENSORS_W83627HF=m
CONFIG_SENSORS_W83627EHF=m
CONFIG_SENSORS_HDAPS=m
CONFIG_SENSORS_APPLESMC=m

#
# ACPI drivers
#
# CONFIG_SENSORS_ATK0110 is not set
# CONFIG_SENSORS_LIS3LV02D is not set
CONFIG_THERMAL=m
CONFIG_THERMAL_HWMON=y
CONFIG_WATCHDOG=y
# CONFIG_WATCHDOG_NOWAYOUT is not set

#
# Watchdog Device Drivers
#
CONFIG_SOFT_WATCHDOG=m
CONFIG_ACQUIRE_WDT=m
CONFIG_ADVANTECH_WDT=m
CONFIG_ALIM1535_WDT=m
CONFIG_ALIM7101_WDT=m
CONFIG_SC520_WDT=m
# CONFIG_SBC_FITPC2_WATCHDOG is not set
CONFIG_EUROTECH_WDT=m
CONFIG_IB700_WDT=m
CONFIG_IBMASR=m
CONFIG_WAFER_WDT=m
CONFIG_I6300ESB_WDT=m
CONFIG_ITCO_WDT=m
# CONFIG_ITCO_VENDOR_SUPPORT is not set
CONFIG_IT8712F_WDT=m
# CONFIG_IT87_WDT is not set
CONFIG_HP_WATCHDOG=m
CONFIG_SC1200_WDT=m
CONFIG_SCx200_WDT=m
CONFIG_PC87413_WDT=m
CONFIG_60XX_WDT=m
CONFIG_SBC8360_WDT=m
CONFIG_SBC7240_WDT=m
CONFIG_CPU5_WDT=m
# CONFIG_SMSC_SCH311X_WDT is not set
CONFIG_SMSC37B787_WDT=m
CONFIG_W83627HF_WDT=m
CONFIG_W83697HF_WDT=m
# CONFIG_W83697UG_WDT is not set
CONFIG_W83877F_WDT=m
CONFIG_W83977F_WDT=m
CONFIG_MACHZ_WDT=m
CONFIG_SBC_EPX_C3_WATCHDOG=m

#
# ISA-based Watchdog Cards
#
CONFIG_PCWATCHDOG=m
CONFIG_MIXCOMWD=m
CONFIG_WDT=m

#
# PCI-based Watchdog Cards
#
CONFIG_PCIPCWATCHDOG=m
CONFIG_WDTPCI=m

#
# USB-based Watchdog Cards
#
CONFIG_USBPCWATCHDOG=m
CONFIG_SSB_POSSIBLE=y

#
# Sonics Silicon Backplane
#
CONFIG_SSB=m
CONFIG_SSB_SPROM=y
CONFIG_SSB_BLOCKIO=y
CONFIG_SSB_PCIHOST_POSSIBLE=y
CONFIG_SSB_PCIHOST=y
CONFIG_SSB_B43_PCI_BRIDGE=y
CONFIG_SSB_PCMCIAHOST_POSSIBLE=y
CONFIG_SSB_PCMCIAHOST=y
CONFIG_SSB_SDIOHOST_POSSIBLE=y
# CONFIG_SSB_SDIOHOST is not set
# CONFIG_SSB_DEBUG is not set
CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y
CONFIG_SSB_DRIVER_PCICORE=y

#
# Multifunction device drivers
#
CONFIG_MFD_CORE=m
CONFIG_MFD_SM501=m
CONFIG_HTC_PASIC3=m
# CONFIG_MFD_TMIO is not set
# CONFIG_MFD_WM8400 is not set
# CONFIG_MFD_WM831X is not set
# CONFIG_MFD_WM8350_I2C is not set
# CONFIG_MFD_PCF50633 is not set
# CONFIG_MFD_MC13783 is not set
# CONFIG_AB3100_CORE is not set
# CONFIG_EZX_PCAP is not set
# CONFIG_REGULATOR is not set
# CONFIG_MEDIA_SUPPORT is not set

#
# Graphics support
#
CONFIG_AGP=m
CONFIG_AGP_ALI=m
CONFIG_AGP_ATI=m
CONFIG_AGP_AMD=m
CONFIG_AGP_AMD64=m
CONFIG_AGP_INTEL=m
CONFIG_AGP_NVIDIA=m
CONFIG_AGP_SIS=m
CONFIG_AGP_SWORKS=m
CONFIG_AGP_VIA=m
CONFIG_AGP_EFFICEON=m
CONFIG_VGA_ARB=y
CONFIG_DRM=m
CONFIG_DRM_KMS_HELPER=m
CONFIG_DRM_TTM=m
CONFIG_DRM_TDFX=m
CONFIG_DRM_R128=m
CONFIG_DRM_RADEON=m
CONFIG_DRM_I810=m
CONFIG_DRM_I830=m
CONFIG_DRM_I915=m
# CONFIG_DRM_I915_KMS is not set
CONFIG_DRM_MGA=m
CONFIG_DRM_SIS=m
CONFIG_DRM_VIA=m
CONFIG_DRM_SAVAGE=m
CONFIG_VGASTATE=m
CONFIG_VIDEO_OUTPUT_CONTROL=m
CONFIG_FB=y
CONFIG_FIRMWARE_EDID=y
CONFIG_FB_DDC=m
CONFIG_FB_BOOT_VESA_SUPPORT=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
CONFIG_FB_SYS_FILLRECT=y
CONFIG_FB_SYS_COPYAREA=y
CONFIG_FB_SYS_IMAGEBLIT=y
# CONFIG_FB_FOREIGN_ENDIAN is not set
CONFIG_FB_SYS_FOPS=y
CONFIG_FB_DEFERRED_IO=y
CONFIG_FB_HECUBA=m
CONFIG_FB_SVGALIB=m
# CONFIG_FB_MACMODES is not set
CONFIG_FB_BACKLIGHT=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y

#
# Frame buffer hardware drivers
#
CONFIG_FB_CIRRUS=m
CONFIG_FB_PM2=m
CONFIG_FB_PM2_FIFO_DISCONNECT=y
CONFIG_FB_CYBER2000=m
CONFIG_FB_ARC=m
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
CONFIG_FB_VGA16=m
CONFIG_FB_UVESA=m
CONFIG_FB_VESA=y
CONFIG_FB_EFI=y
CONFIG_FB_N411=m
CONFIG_FB_HGA=m
# CONFIG_FB_HGA_ACCEL is not set
CONFIG_FB_S1D13XXX=m
CONFIG_FB_NVIDIA=m
CONFIG_FB_NVIDIA_I2C=y
# CONFIG_FB_NVIDIA_DEBUG is not set
CONFIG_FB_NVIDIA_BACKLIGHT=y
# CONFIG_FB_RIVA is not set
CONFIG_FB_I810=m
# CONFIG_FB_I810_GTF is not set
CONFIG_FB_LE80578=m
CONFIG_FB_CARILLO_RANCH=m
CONFIG_FB_MATROX=m
CONFIG_FB_MATROX_MILLENIUM=y
CONFIG_FB_MATROX_MYSTIQUE=y
CONFIG_FB_MATROX_G=y
CONFIG_FB_MATROX_I2C=m
CONFIG_FB_MATROX_MAVEN=m
CONFIG_FB_RADEON=m
CONFIG_FB_RADEON_I2C=y
CONFIG_FB_RADEON_BACKLIGHT=y
# CONFIG_FB_RADEON_DEBUG is not set
CONFIG_FB_ATY128=m
CONFIG_FB_ATY128_BACKLIGHT=y
CONFIG_FB_ATY=m
CONFIG_FB_ATY_CT=y
CONFIG_FB_ATY_GENERIC_LCD=y
CONFIG_FB_ATY_GX=y
CONFIG_FB_ATY_BACKLIGHT=y
CONFIG_FB_S3=m
CONFIG_FB_SAVAGE=m
CONFIG_FB_SAVAGE_I2C=y
# CONFIG_FB_SAVAGE_ACCEL is not set
CONFIG_FB_SIS=m
CONFIG_FB_SIS_300=y
CONFIG_FB_SIS_315=y
# CONFIG_FB_VIA is not set
CONFIG_FB_NEOMAGIC=m
CONFIG_FB_KYRO=m
CONFIG_FB_3DFX=m
# CONFIG_FB_3DFX_ACCEL is not set
CONFIG_FB_3DFX_I2C=y
CONFIG_FB_VOODOO1=m
CONFIG_FB_VT8623=m
CONFIG_FB_TRIDENT=m
CONFIG_FB_ARK=m
CONFIG_FB_PM3=m
# CONFIG_FB_CARMINE is not set
CONFIG_FB_GEODE=y
CONFIG_FB_GEODE_LX=m
CONFIG_FB_GEODE_GX=m
CONFIG_FB_GEODE_GX1=m
# CONFIG_FB_TMIO is not set
CONFIG_FB_SM501=m
CONFIG_FB_VIRTUAL=m
CONFIG_XEN_FBDEV_FRONTEND=y
# CONFIG_FB_METRONOME is not set
# CONFIG_FB_MB862XX is not set
# CONFIG_FB_BROADSHEET is not set
CONFIG_BACKLIGHT_LCD_SUPPORT=y
# CONFIG_LCD_CLASS_DEVICE is not set
CONFIG_BACKLIGHT_CLASS_DEVICE=y
CONFIG_BACKLIGHT_GENERIC=y
CONFIG_BACKLIGHT_PROGEAR=m
# CONFIG_BACKLIGHT_MBP_NVIDIA is not set
# CONFIG_BACKLIGHT_SAHARA is not set

#
# Display device support
#
CONFIG_DISPLAY_SUPPORT=m

#
# Display hardware drivers
#

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
CONFIG_MDA_CONSOLE=m
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
# CONFIG_LOGO is not set
CONFIG_SOUND=m
CONFIG_SOUND_OSS_CORE=y
CONFIG_SOUND_OSS_CORE_PRECLAIM=y
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=m
CONFIG_SND_SEQ_DUMMY=m
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_PCM_OSS_PLUGINS=y
CONFIG_SND_SEQUENCER_OSS=y
# CONFIG_SND_HRTIMER is not set
# CONFIG_SND_DYNAMIC_MINORS is not set
CONFIG_SND_SUPPORT_OLD_API=y
CONFIG_SND_VERBOSE_PROCFS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
CONFIG_SND_VMASTER=y
CONFIG_SND_DMA_SGBUF=y
CONFIG_SND_RAWMIDI_SEQ=m
CONFIG_SND_OPL3_LIB_SEQ=m
CONFIG_SND_OPL4_LIB_SEQ=m
CONFIG_SND_SBAWE_SEQ=m
CONFIG_SND_EMU10K1_SEQ=m
CONFIG_SND_MPU401_UART=m
CONFIG_SND_OPL3_LIB=m
CONFIG_SND_OPL4_LIB=m
CONFIG_SND_VX_LIB=m
CONFIG_SND_AC97_CODEC=m
CONFIG_SND_DRIVERS=y
# CONFIG_SND_PCSP is not set
CONFIG_SND_DUMMY=m
CONFIG_SND_VIRMIDI=m
CONFIG_SND_MTPAV=m
CONFIG_SND_MTS64=m
CONFIG_SND_SERIAL_U16550=m
CONFIG_SND_MPU401=m
CONFIG_SND_PORTMAN2X4=m
CONFIG_SND_AC97_POWER_SAVE=y
CONFIG_SND_AC97_POWER_SAVE_DEFAULT=0
CONFIG_SND_WSS_LIB=m
CONFIG_SND_SB_COMMON=m
CONFIG_SND_SB8_DSP=m
CONFIG_SND_SB16_DSP=m
CONFIG_SND_ISA=y
CONFIG_SND_ADLIB=m
CONFIG_SND_AD1816A=m
CONFIG_SND_AD1848=m
CONFIG_SND_ALS100=m
CONFIG_SND_AZT2320=m
CONFIG_SND_CMI8330=m
CONFIG_SND_CS4231=m
CONFIG_SND_CS4236=m
CONFIG_SND_DT019X=m
CONFIG_SND_ES968=m
CONFIG_SND_ES1688=m
CONFIG_SND_ES18XX=m
CONFIG_SND_SC6000=m
CONFIG_SND_GUSCLASSIC=m
CONFIG_SND_GUSEXTREME=m
CONFIG_SND_GUSMAX=m
CONFIG_SND_INTERWAVE=m
CONFIG_SND_INTERWAVE_STB=m
CONFIG_SND_OPL3SA2=m
CONFIG_SND_OPTI92X_AD1848=m
CONFIG_SND_OPTI92X_CS4231=m
CONFIG_SND_OPTI93X=m
CONFIG_SND_MIRO=m
CONFIG_SND_SB8=m
CONFIG_SND_SB16=m
CONFIG_SND_SBAWE=m
CONFIG_SND_SB16_CSP=y
CONFIG_SND_SGALAXY=m
CONFIG_SND_SSCAPE=m
CONFIG_SND_WAVEFRONT=m
# CONFIG_SND_MSND_PINNACLE is not set
# CONFIG_SND_MSND_CLASSIC is not set
CONFIG_SND_PCI=y
CONFIG_SND_AD1889=m
CONFIG_SND_ALS300=m
CONFIG_SND_ALS4000=m
CONFIG_SND_ALI5451=m
CONFIG_SND_ATIIXP=m
CONFIG_SND_ATIIXP_MODEM=m
CONFIG_SND_AU8810=m
CONFIG_SND_AU8820=m
CONFIG_SND_AU8830=m
# CONFIG_SND_AW2 is not set
CONFIG_SND_AZT3328=m
CONFIG_SND_BT87X=m
# CONFIG_SND_BT87X_OVERCLOCK is not set
CONFIG_SND_CA0106=m
CONFIG_SND_CMIPCI=m
CONFIG_SND_OXYGEN_LIB=m
CONFIG_SND_OXYGEN=m
CONFIG_SND_CS4281=m
# CONFIG_SND_CS46XX is not set
CONFIG_SND_CS5530=m
CONFIG_SND_CS5535AUDIO=m
# CONFIG_SND_CTXFI is not set
CONFIG_SND_DARLA20=m
CONFIG_SND_GINA20=m
CONFIG_SND_LAYLA20=m
CONFIG_SND_DARLA24=m
CONFIG_SND_GINA24=m
CONFIG_SND_LAYLA24=m
CONFIG_SND_MONA=m
CONFIG_SND_MIA=m
CONFIG_SND_ECHO3G=m
CONFIG_SND_INDIGO=m
CONFIG_SND_INDIGOIO=m
CONFIG_SND_INDIGODJ=m
# CONFIG_SND_INDIGOIOX is not set
# CONFIG_SND_INDIGODJX is not set
CONFIG_SND_EMU10K1=m
CONFIG_SND_EMU10K1X=m
CONFIG_SND_ENS1370=m
CONFIG_SND_ENS1371=m
CONFIG_SND_ES1938=m
CONFIG_SND_ES1968=m
CONFIG_SND_FM801=m
CONFIG_SND_HDA_INTEL=m
# CONFIG_SND_HDA_HWDEP is not set
# CONFIG_SND_HDA_INPUT_BEEP is not set
# CONFIG_SND_HDA_INPUT_JACK is not set
# CONFIG_SND_HDA_PATCH_LOADER is not set
CONFIG_SND_HDA_CODEC_REALTEK=y
CONFIG_SND_HDA_CODEC_ANALOG=y
CONFIG_SND_HDA_CODEC_SIGMATEL=y
CONFIG_SND_HDA_CODEC_VIA=y
CONFIG_SND_HDA_CODEC_ATIHDMI=y
CONFIG_SND_HDA_CODEC_NVHDMI=y
CONFIG_SND_HDA_CODEC_INTELHDMI=y
CONFIG_SND_HDA_ELD=y
CONFIG_SND_HDA_CODEC_CIRRUS=y
CONFIG_SND_HDA_CODEC_CONEXANT=y
CONFIG_SND_HDA_CODEC_CA0110=y
CONFIG_SND_HDA_CODEC_CMEDIA=y
CONFIG_SND_HDA_CODEC_SI3054=y
CONFIG_SND_HDA_GENERIC=y
CONFIG_SND_HDA_POWER_SAVE=y
CONFIG_SND_HDA_POWER_SAVE_DEFAULT=0
CONFIG_SND_HDSP=m
CONFIG_SND_HDSPM=m
CONFIG_SND_HIFIER=m
CONFIG_SND_ICE1712=m
CONFIG_SND_ICE1724=m
CONFIG_SND_INTEL8X0=m
CONFIG_SND_INTEL8X0M=m
CONFIG_SND_KORG1212=m
# CONFIG_SND_LX6464ES is not set
CONFIG_SND_MAESTRO3=m
CONFIG_SND_MIXART=m
CONFIG_SND_NM256=m
CONFIG_SND_PCXHR=m
CONFIG_SND_RIPTIDE=m
CONFIG_SND_RME32=m
CONFIG_SND_RME96=m
CONFIG_SND_RME9652=m
CONFIG_SND_SIS7019=m
CONFIG_SND_SONICVIBES=m
CONFIG_SND_TRIDENT=m
CONFIG_SND_VIA82XX=m
CONFIG_SND_VIA82XX_MODEM=m
CONFIG_SND_VIRTUOSO=m
CONFIG_SND_VX222=m
CONFIG_SND_YMFPCI=m
CONFIG_SND_SPI=y
CONFIG_SND_USB=y
CONFIG_SND_USB_AUDIO=m
CONFIG_SND_USB_USX2Y=m
CONFIG_SND_USB_CAIAQ=m
CONFIG_SND_USB_CAIAQ_INPUT=y
# CONFIG_SND_USB_US122L is not set
CONFIG_SND_PCMCIA=y
CONFIG_SND_VXPOCKET=m
CONFIG_SND_PDAUDIOCF=m
# CONFIG_SND_SOC is not set
CONFIG_SOUND_PRIME=m
# CONFIG_SOUND_MSNDCLAS is not set
# CONFIG_SOUND_MSNDPIN is not set
CONFIG_SOUND_OSS=m
# CONFIG_SOUND_TRACEINIT is not set
# CONFIG_SOUND_DMAP is not set
CONFIG_SOUND_SSCAPE=m
CONFIG_SOUND_VMIDI=m
CONFIG_SOUND_TRIX=m
CONFIG_SOUND_MSS=m
CONFIG_SOUND_MPU401=m
CONFIG_SOUND_PAS=m
CONFIG_SOUND_PSS=m
CONFIG_PSS_MIXER=y
CONFIG_SOUND_SB=m
CONFIG_SOUND_YM3812=m
CONFIG_SOUND_UART6850=m
CONFIG_SOUND_AEDSP16=m
CONFIG_SC6600=y
CONFIG_SC6600_JOY=y
CONFIG_SC6600_CDROM=4
CONFIG_SC6600_CDROMBASE=0x0
CONFIG_SOUND_KAHLUA=m
CONFIG_AC97_BUS=m
CONFIG_HID_SUPPORT=y
CONFIG_HID=m
CONFIG_HIDRAW=y

#
# USB Input Devices
#
CONFIG_USB_HID=m
CONFIG_HID_PID=y
CONFIG_USB_HIDDEV=y

#
# Special HID drivers
#
CONFIG_HID_A4TECH=m
CONFIG_HID_APPLE=m
CONFIG_HID_BELKIN=m
CONFIG_HID_CHERRY=m
CONFIG_HID_CHICONY=m
CONFIG_HID_CYPRESS=m
CONFIG_HID_DRAGONRISE=m
# CONFIG_DRAGONRISE_FF is not set
CONFIG_HID_EZKEY=m
CONFIG_HID_KYE=m
CONFIG_HID_GYRATION=m
CONFIG_HID_TWINHAN=m
CONFIG_HID_KENSINGTON=m
CONFIG_HID_LOGITECH=m
CONFIG_LOGITECH_FF=y
CONFIG_LOGIRUMBLEPAD2_FF=y
CONFIG_HID_MICROSOFT=m
CONFIG_HID_MONTEREY=m
CONFIG_HID_NTRIG=m
CONFIG_HID_PANTHERLORD=m
CONFIG_PANTHERLORD_FF=y
CONFIG_HID_PETALYNX=m
CONFIG_HID_SAMSUNG=m
CONFIG_HID_SONY=m
CONFIG_HID_SUNPLUS=m
CONFIG_HID_GREENASIA=m
# CONFIG_GREENASIA_FF is not set
CONFIG_HID_SMARTJOYPLUS=m
# CONFIG_SMARTJOYPLUS_FF is not set
CONFIG_HID_TOPSEED=m
CONFIG_HID_THRUSTMASTER=m
CONFIG_THRUSTMASTER_FF=y
CONFIG_HID_WACOM=m
CONFIG_HID_ZEROPLUS=m
CONFIG_ZEROPLUS_FF=y
CONFIG_USB_SUPPORT=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set
CONFIG_USB_ANNOUNCE_NEW_DEVICES=y

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
CONFIG_USB_DEVICE_CLASS=y
# CONFIG_USB_DYNAMIC_MINORS is not set
CONFIG_USB_SUSPEND=y
# CONFIG_USB_OTG is not set
CONFIG_USB_MON=m
# CONFIG_USB_WUSB is not set
# CONFIG_USB_WUSB_CBAF is not set

#
# USB Host Controller Drivers
#
CONFIG_USB_C67X00_HCD=m
# CONFIG_USB_XHCI_HCD is not set
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
# CONFIG_USB_OXU210HP_HCD is not set
CONFIG_USB_ISP116X_HCD=m
# CONFIG_USB_ISP1760_HCD is not set
# CONFIG_USB_ISP1362_HCD is not set
CONFIG_USB_OHCI_HCD=m
# CONFIG_USB_OHCI_HCD_SSB is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=m
CONFIG_USB_U132_HCD=m
CONFIG_USB_SL811_HCD=m
CONFIG_USB_SL811_CS=m
CONFIG_USB_R8A66597_HCD=m
# CONFIG_USB_WHCI_HCD is not set
# CONFIG_USB_HWA_HCD is not set

#
# Enable Host or Gadget support to see Inventra options
#

#
# USB Device Class drivers
#
CONFIG_USB_ACM=m
CONFIG_USB_PRINTER=m
CONFIG_USB_WDM=m
# CONFIG_USB_TMC is not set

#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may
#

#
# also be needed; see USB_STORAGE Help for more info
#
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
CONFIG_USB_STORAGE_DATAFAB=m
CONFIG_USB_STORAGE_FREECOM=m
CONFIG_USB_STORAGE_ISD200=m
CONFIG_USB_STORAGE_USBAT=m
CONFIG_USB_STORAGE_SDDR09=m
CONFIG_USB_STORAGE_SDDR55=m
CONFIG_USB_STORAGE_JUMPSHOT=m
CONFIG_USB_STORAGE_ALAUDA=m
CONFIG_USB_STORAGE_ONETOUCH=m
CONFIG_USB_STORAGE_KARMA=m
CONFIG_USB_STORAGE_CYPRESS_ATACB=m
# CONFIG_USB_LIBUSUAL is not set

#
# USB Imaging devices
#
CONFIG_USB_MDC800=m
CONFIG_USB_MICROTEK=m

#
# USB port drivers
#
CONFIG_USB_USS720=m
CONFIG_USB_SERIAL=m
CONFIG_USB_EZUSB=y
CONFIG_USB_SERIAL_GENERIC=y
CONFIG_USB_SERIAL_AIRCABLE=m
CONFIG_USB_SERIAL_ARK3116=m
CONFIG_USB_SERIAL_BELKIN=m
CONFIG_USB_SERIAL_CH341=m
# CONFIG_USB_SERIAL_WHITEHEAT is not set
CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m
# CONFIG_USB_SERIAL_CP210X is not set
CONFIG_USB_SERIAL_CYPRESS_M8=m
CONFIG_USB_SERIAL_EMPEG=m
CONFIG_USB_SERIAL_FTDI_SIO=m
CONFIG_USB_SERIAL_FUNSOFT=m
CONFIG_USB_SERIAL_VISOR=m
CONFIG_USB_SERIAL_IPAQ=m
CONFIG_USB_SERIAL_IR=m
CONFIG_USB_SERIAL_EDGEPORT=m
CONFIG_USB_SERIAL_EDGEPORT_TI=m
CONFIG_USB_SERIAL_GARMIN=m
CONFIG_USB_SERIAL_IPW=m
CONFIG_USB_SERIAL_IUU=m
CONFIG_USB_SERIAL_KEYSPAN_PDA=m
CONFIG_USB_SERIAL_KEYSPAN=m
# CONFIG_USB_SERIAL_KEYSPAN_MPR is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28 is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28X is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28XA is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28XB is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA19 is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA18X is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA19W is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA19QW is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA19QI is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA49W is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA49WLC is not set
CONFIG_USB_SERIAL_KLSI=m
CONFIG_USB_SERIAL_KOBIL_SCT=m
CONFIG_USB_SERIAL_MCT_U232=m
CONFIG_USB_SERIAL_MOS7720=m
CONFIG_USB_SERIAL_MOS7840=m
CONFIG_USB_SERIAL_MOTOROLA=m
CONFIG_USB_SERIAL_NAVMAN=m
CONFIG_USB_SERIAL_PL2303=m
CONFIG_USB_SERIAL_OTI6858=m
# CONFIG_USB_SERIAL_QUALCOMM is not set
CONFIG_USB_SERIAL_SPCP8X5=m
CONFIG_USB_SERIAL_HP4X=m
CONFIG_USB_SERIAL_SAFE=m
# CONFIG_USB_SERIAL_SAFE_PADDED is not set
# CONFIG_USB_SERIAL_SIEMENS_MPI is not set
CONFIG_USB_SERIAL_SIERRAWIRELESS=m
# CONFIG_USB_SERIAL_SYMBOL is not set
# CONFIG_USB_SERIAL_TI is not set
CONFIG_USB_SERIAL_CYBERJACK=m
CONFIG_USB_SERIAL_XIRCOM=m
CONFIG_USB_SERIAL_OPTION=m
CONFIG_USB_SERIAL_OMNINET=m
# CONFIG_USB_SERIAL_OPTICON is not set
CONFIG_USB_SERIAL_DEBUG=m

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
CONFIG_USB_ADUTUX=m
# CONFIG_USB_SEVSEG is not set
CONFIG_USB_RIO500=m
CONFIG_USB_LEGOTOWER=m
CONFIG_USB_LCD=m
CONFIG_USB_BERRY_CHARGE=m
CONFIG_USB_LED=m
CONFIG_USB_CYPRESS_CY7C63=m
CONFIG_USB_CYTHERM=m
CONFIG_USB_IDMOUSE=m
CONFIG_USB_FTDI_ELAN=m
CONFIG_USB_APPLEDISPLAY=m
CONFIG_USB_SISUSBVGA=m
CONFIG_USB_SISUSBVGA_CON=y
CONFIG_USB_LD=m
CONFIG_USB_TRANCEVIBRATOR=m
CONFIG_USB_IOWARRIOR=m
CONFIG_USB_TEST=m
CONFIG_USB_ISIGHTFW=m
# CONFIG_USB_VST is not set
CONFIG_USB_ATM=m
CONFIG_USB_SPEEDTOUCH=m
CONFIG_USB_CXACRU=m
CONFIG_USB_UEAGLEATM=m
CONFIG_USB_XUSBATM=m
# CONFIG_USB_GADGET is not set

#
# OTG and related infrastructure
#
# CONFIG_NOP_USB_XCEIV is not set
# CONFIG_UWB is not set
CONFIG_MMC=m
# CONFIG_MMC_DEBUG is not set
# CONFIG_MMC_UNSAFE_RESUME is not set

#
# MMC/SD/SDIO Card Drivers
#
CONFIG_MMC_BLOCK=m
CONFIG_MMC_BLOCK_BOUNCE=y
CONFIG_SDIO_UART=m
# CONFIG_MMC_TEST is not set

#
# MMC/SD/SDIO Host Controller Drivers
#
CONFIG_MMC_SDHCI=m
# CONFIG_MMC_SDHCI_PCI is not set
# CONFIG_MMC_SDHCI_PLTFM is not set
CONFIG_MMC_WBSD=m
# CONFIG_MMC_AT91 is not set
# CONFIG_MMC_ATMELMCI is not set
CONFIG_MMC_TIFM_SD=m
# CONFIG_MMC_SDRICOH_CS is not set
# CONFIG_MMC_CB710 is not set
# CONFIG_MMC_VIA_SDMMC is not set
CONFIG_MEMSTICK=m
# CONFIG_MEMSTICK_DEBUG is not set

#
# MemoryStick drivers
#
# CONFIG_MEMSTICK_UNSAFE_RESUME is not set
CONFIG_MSPRO_BLOCK=m

#
# MemoryStick Host Controller Drivers
#
CONFIG_MEMSTICK_TIFM_MS=m
CONFIG_MEMSTICK_JMICRON_38X=m
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=m

#
# LED drivers
#
CONFIG_LEDS_NET48XX=m
CONFIG_LEDS_WRAP=m
# CONFIG_LEDS_ALIX2 is not set
# CONFIG_LEDS_PCA9532 is not set
# CONFIG_LEDS_LP3944 is not set
CONFIG_LEDS_CLEVO_MAIL=m
# CONFIG_LEDS_PCA955X is not set
# CONFIG_LEDS_DAC124S085 is not set
# CONFIG_LEDS_BD2802 is not set

#
# LED Triggers
#
CONFIG_LEDS_TRIGGERS=y
CONFIG_LEDS_TRIGGER_TIMER=m
CONFIG_LEDS_TRIGGER_IDE_DISK=y
CONFIG_LEDS_TRIGGER_HEARTBEAT=m
# CONFIG_LEDS_TRIGGER_BACKLIGHT is not set
CONFIG_LEDS_TRIGGER_DEFAULT_ON=m

#
# iptables trigger is under Netfilter config (LED target)
#
CONFIG_ACCESSIBILITY=y
CONFIG_A11Y_BRAILLE_CONSOLE=y
CONFIG_INFINIBAND=m
CONFIG_INFINIBAND_USER_MAD=m
CONFIG_INFINIBAND_USER_ACCESS=m
CONFIG_INFINIBAND_USER_MEM=y
CONFIG_INFINIBAND_ADDR_TRANS=y
CONFIG_INFINIBAND_MTHCA=m
CONFIG_INFINIBAND_MTHCA_DEBUG=y
CONFIG_INFINIBAND_AMSO1100=m
# CONFIG_INFINIBAND_AMSO1100_DEBUG is not set
CONFIG_INFINIBAND_CXGB3=m
# CONFIG_INFINIBAND_CXGB3_DEBUG is not set
CONFIG_MLX4_INFINIBAND=m
CONFIG_INFINIBAND_NES=m
# CONFIG_INFINIBAND_NES_DEBUG is not set
CONFIG_INFINIBAND_IPOIB=m
# CONFIG_INFINIBAND_IPOIB_CM is not set
CONFIG_INFINIBAND_IPOIB_DEBUG=y
# CONFIG_INFINIBAND_IPOIB_DEBUG_DATA is not set
CONFIG_INFINIBAND_SRP=m
CONFIG_INFINIBAND_ISER=m
CONFIG_EDAC=y

#
# Reporting subsystems
#
# CONFIG_EDAC_DEBUG is not set
CONFIG_EDAC_DECODE_MCE=y
CONFIG_EDAC_MM_EDAC=m
CONFIG_EDAC_AMD76X=m
CONFIG_EDAC_E7XXX=m
CONFIG_EDAC_E752X=m
CONFIG_EDAC_I82875P=m
CONFIG_EDAC_I82975X=m
CONFIG_EDAC_I3000=m
# CONFIG_EDAC_I3200 is not set
# CONFIG_EDAC_X38 is not set
# CONFIG_EDAC_I5400 is not set
CONFIG_EDAC_I82860=m
CONFIG_EDAC_R82600=m
CONFIG_EDAC_I5000=m
# CONFIG_EDAC_I5100 is not set
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
# CONFIG_RTC_DEBUG is not set

#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# CONFIG_RTC_DRV_TEST is not set

#
# I2C RTC drivers
#
CONFIG_RTC_DRV_DS1307=m
CONFIG_RTC_DRV_DS1374=m
CONFIG_RTC_DRV_DS1672=m
CONFIG_RTC_DRV_MAX6900=m
CONFIG_RTC_DRV_RS5C372=m
CONFIG_RTC_DRV_ISL1208=m
CONFIG_RTC_DRV_X1205=m
CONFIG_RTC_DRV_PCF8563=m
CONFIG_RTC_DRV_PCF8583=m
CONFIG_RTC_DRV_M41T80=m
# CONFIG_RTC_DRV_M41T80_WDT is not set
CONFIG_RTC_DRV_S35390A=m
CONFIG_RTC_DRV_FM3130=m
# CONFIG_RTC_DRV_RX8581 is not set
# CONFIG_RTC_DRV_RX8025 is not set

#
# SPI RTC drivers
#
# CONFIG_RTC_DRV_M41T94 is not set
# CONFIG_RTC_DRV_DS1305 is not set
# CONFIG_RTC_DRV_DS1390 is not set
CONFIG_RTC_DRV_MAX6902=m
CONFIG_RTC_DRV_R9701=m
CONFIG_RTC_DRV_RS5C348=m
# CONFIG_RTC_DRV_DS3234 is not set
# CONFIG_RTC_DRV_PCF2123 is not set

#
# Platform RTC drivers
#
CONFIG_RTC_DRV_CMOS=y
# CONFIG_RTC_DRV_DS1286 is not set
CONFIG_RTC_DRV_DS1511=m
CONFIG_RTC_DRV_DS1553=m
CONFIG_RTC_DRV_DS1742=m
CONFIG_RTC_DRV_STK17TA8=m
CONFIG_RTC_DRV_M48T86=m
# CONFIG_RTC_DRV_M48T35 is not set
CONFIG_RTC_DRV_M48T59=m
# CONFIG_RTC_DRV_BQ4802 is not set
CONFIG_RTC_DRV_V3020=m

#
# on-CPU RTC drivers
#
# CONFIG_DMADEVICES is not set
# CONFIG_AUXDISPLAY is not set
CONFIG_UIO=m
CONFIG_UIO_CIF=m
# CONFIG_UIO_PDRV is not set
# CONFIG_UIO_PDRV_GENIRQ is not set
CONFIG_UIO_SMX=m
# CONFIG_UIO_AEC is not set
# CONFIG_UIO_SERCOS3 is not set
# CONFIG_UIO_PCI_GENERIC is not set

#
# TI VLYNQ
#
CONFIG_XEN_BALLOON=y
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_DEV_EVTCHN=y
CONFIG_XEN_BACKEND=y
CONFIG_XEN_NETDEV_BACKEND=y
CONFIG_XEN_BLKDEV_BACKEND=y
CONFIG_XEN_BLKDEV_TAP=y
CONFIG_XEN_BLKBACK_PAGEMAP=y
CONFIG_XEN_PCIDEV_BACKEND=y
# CONFIG_XEN_PCIDEV_BACKEND_VPCI is not set
CONFIG_XEN_PCIDEV_BACKEND_PASS=y
# CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set
# CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set
CONFIG_XEN_PCIDEV_BE_DEBUG=y
CONFIG_XENFS=y
CONFIG_XEN_COMPAT_XENFS=y
CONFIG_XEN_SYS_HYPERVISOR=y
CONFIG_XEN_XENBUS_FRONTEND=y
# CONFIG_XEN_GNTDEV is not set
# CONFIG_STAGING is not set
CONFIG_X86_PLATFORM_DEVICES=y
CONFIG_ACER_WMI=m
# CONFIG_ACERHDF is not set
CONFIG_ASUS_LAPTOP=m
# CONFIG_DELL_WMI is not set
CONFIG_FUJITSU_LAPTOP=m
# CONFIG_FUJITSU_LAPTOP_DEBUG is not set
CONFIG_TC1100_WMI=m
# CONFIG_HP_WMI is not set
CONFIG_MSI_LAPTOP=m
# CONFIG_PANASONIC_LAPTOP is not set
# CONFIG_COMPAL_LAPTOP is not set
CONFIG_SONY_LAPTOP=m
CONFIG_SONYPI_COMPAT=y
CONFIG_THINKPAD_ACPI=m
# CONFIG_THINKPAD_ACPI_DEBUGFACILITIES is not set
# CONFIG_THINKPAD_ACPI_DEBUG is not set
# CONFIG_THINKPAD_ACPI_UNSAFE_LEDS is not set
CONFIG_THINKPAD_ACPI_VIDEO=y
CONFIG_THINKPAD_ACPI_HOTKEY_POLL=y
# CONFIG_INTEL_MENLOW is not set
CONFIG_EEEPC_LAPTOP=m
CONFIG_ACPI_WMI=m
CONFIG_ACPI_ASUS=m
# CONFIG_TOPSTAR_LAPTOP is not set
CONFIG_ACPI_TOSHIBA=m

#
# Firmware Drivers
#
CONFIG_EDD=m
# CONFIG_EDD_OFF is not set
CONFIG_FIRMWARE_MEMMAP=y
CONFIG_EFI_VARS=m
CONFIG_DELL_RBU=m
CONFIG_DCDBAS=m
CONFIG_DMIID=y
CONFIG_ISCSI_IBFT_FIND=y
CONFIG_ISCSI_IBFT=y

#
# File systems
#
CONFIG_EXT2_FS=m
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=m
# CONFIG_EXT3_DEFAULTS_TO_ORDERED is not set
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
# CONFIG_EXT4_FS is not set
CONFIG_JBD=m
# CONFIG_JBD_DEBUG is not set
CONFIG_JBD2=m
# CONFIG_JBD2_DEBUG is not set
CONFIG_FS_MBCACHE=m
CONFIG_REISERFS_FS=m
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
CONFIG_REISERFS_FS_SECURITY=y
CONFIG_JFS_FS=m
CONFIG_JFS_POSIX_ACL=y
CONFIG_JFS_SECURITY=y
# CONFIG_JFS_DEBUG is not set
# CONFIG_JFS_STATISTICS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_XFS_FS=m
CONFIG_XFS_QUOTA=y
CONFIG_XFS_POSIX_ACL=y
CONFIG_XFS_RT=y
# CONFIG_XFS_DEBUG is not set
CONFIG_GFS2_FS=m
# CONFIG_GFS2_FS_LOCKING_DLM is not set
CONFIG_OCFS2_FS=m
CONFIG_OCFS2_FS_O2CB=m
CONFIG_OCFS2_FS_USERSPACE_CLUSTER=m
CONFIG_OCFS2_FS_STATS=y
CONFIG_OCFS2_DEBUG_MASKLOG=y
# CONFIG_OCFS2_DEBUG_FS is not set
# CONFIG_OCFS2_FS_POSIX_ACL is not set
# CONFIG_BTRFS_FS is not set
# CONFIG_NILFS2_FS is not set
CONFIG_FILE_LOCKING=y
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_QUOTA=y
CONFIG_QUOTA_NETLINK_INTERFACE=y
CONFIG_PRINT_QUOTA_WARNING=y
CONFIG_QUOTA_TREE=m
CONFIG_QFMT_V1=m
CONFIG_QFMT_V2=m
CONFIG_QUOTACTL=y
CONFIG_AUTOFS_FS=m
CONFIG_AUTOFS4_FS=m
CONFIG_FUSE_FS=m
# CONFIG_CUSE is not set
CONFIG_GENERIC_ACL=y

#
# Caches
#
# CONFIG_FSCACHE is not set

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="utf8"
CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
CONFIG_NTFS_RW=y

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_CONFIGFS_FS=m
CONFIG_MISC_FILESYSTEMS=y
CONFIG_ADFS_FS=m
# CONFIG_ADFS_FS_RW is not set
CONFIG_AFFS_FS=m
CONFIG_ECRYPT_FS=m
CONFIG_HFS_FS=m
CONFIG_HFSPLUS_FS=m
CONFIG_BEFS_FS=m
# CONFIG_BEFS_DEBUG is not set
CONFIG_BFS_FS=m
CONFIG_EFS_FS=m
CONFIG_JFFS2_FS=m
CONFIG_JFFS2_FS_DEBUG=0
CONFIG_JFFS2_FS_WRITEBUFFER=y
# CONFIG_JFFS2_FS_WBUF_VERIFY is not set
CONFIG_JFFS2_SUMMARY=y
CONFIG_JFFS2_FS_XATTR=y
CONFIG_JFFS2_FS_POSIX_ACL=y
CONFIG_JFFS2_FS_SECURITY=y
CONFIG_JFFS2_COMPRESSION_OPTIONS=y
CONFIG_JFFS2_ZLIB=y
CONFIG_JFFS2_LZO=y
CONFIG_JFFS2_RTIME=y
# CONFIG_JFFS2_RUBIN is not set
# CONFIG_JFFS2_CMODE_NONE is not set
CONFIG_JFFS2_CMODE_PRIORITY=y
# CONFIG_JFFS2_CMODE_SIZE is not set
# CONFIG_JFFS2_CMODE_FAVOURLZO is not set
# CONFIG_UBIFS_FS is not set
CONFIG_CRAMFS=m
# CONFIG_SQUASHFS is not set
CONFIG_VXFS_FS=m
CONFIG_MINIX_FS=m
# CONFIG_OMFS_FS is not set
CONFIG_HPFS_FS=m
CONFIG_QNX4FS_FS=m
CONFIG_ROMFS_FS=m
CONFIG_ROMFS_BACKED_BY_BLOCK=y
# CONFIG_ROMFS_BACKED_BY_MTD is not set
# CONFIG_ROMFS_BACKED_BY_BOTH is not set
CONFIG_ROMFS_ON_BLOCK=y
CONFIG_SYSV_FS=m
CONFIG_UFS_FS=m
# CONFIG_UFS_FS_WRITE is not set
# CONFIG_UFS_DEBUG is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
# CONFIG_NFS_V4_1 is not set
CONFIG_NFSD=m
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_NFS_ACL_SUPPORT=m
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=m
CONFIG_SUNRPC_GSS=m
CONFIG_SUNRPC_XPRT_RDMA=m
CONFIG_RPCSEC_GSS_KRB5=m
CONFIG_RPCSEC_GSS_SPKM3=m
# CONFIG_SMB_FS is not set
CONFIG_CIFS=m
# CONFIG_CIFS_STATS is not set
CONFIG_CIFS_WEAK_PW_HASH=y
CONFIG_CIFS_UPCALL=y
CONFIG_CIFS_XATTR=y
CONFIG_CIFS_POSIX=y
# CONFIG_CIFS_DEBUG2 is not set
CONFIG_CIFS_DFS_UPCALL=y
CONFIG_CIFS_EXPERIMENTAL=y
CONFIG_NCP_FS=m
# CONFIG_NCPFS_PACKET_SIGNING is not set
# CONFIG_NCPFS_IOCTL_LOCKING is not set
# CONFIG_NCPFS_STRONG is not set
CONFIG_NCPFS_NFS_NS=y
CONFIG_NCPFS_OS2_NS=y
# CONFIG_NCPFS_SMALLDOS is not set
CONFIG_NCPFS_NLS=y
CONFIG_NCPFS_EXTRAS=y
CONFIG_CODA_FS=m
CONFIG_AFS_FS=m
# CONFIG_AFS_DEBUG is not set
CONFIG_9P_FS=m

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
CONFIG_ACORN_PARTITION=y
# CONFIG_ACORN_PARTITION_CUMANA is not set
# CONFIG_ACORN_PARTITION_EESOX is not set
CONFIG_ACORN_PARTITION_ICS=y
# CONFIG_ACORN_PARTITION_ADFS is not set
# CONFIG_ACORN_PARTITION_POWERTEC is not set
CONFIG_ACORN_PARTITION_RISCIX=y
CONFIG_OSF_PARTITION=y
CONFIG_AMIGA_PARTITION=y
CONFIG_ATARI_PARTITION=y
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
CONFIG_MINIX_SUBPARTITION=y
CONFIG_SOLARIS_X86_PARTITION=y
CONFIG_UNIXWARE_DISKLABEL=y
CONFIG_LDM_PARTITION=y
# CONFIG_LDM_DEBUG is not set
CONFIG_SGI_PARTITION=y
CONFIG_ULTRIX_PARTITION=y
CONFIG_SUN_PARTITION=y
CONFIG_KARMA_PARTITION=y
CONFIG_EFI_PARTITION=y
# CONFIG_SYSV68_PARTITION is not set
CONFIG_NLS=m
CONFIG_NLS_DEFAULT="utf8"
CONFIG_NLS_CODEPAGE_437=m
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
CONFIG_NLS_CODEPAGE_857=m
CONFIG_NLS_CODEPAGE_860=m
CONFIG_NLS_CODEPAGE_861=m
CONFIG_NLS_CODEPAGE_862=m
CONFIG_NLS_CODEPAGE_863=m
CONFIG_NLS_CODEPAGE_864=m
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
CONFIG_NLS_CODEPAGE_936=m
CONFIG_NLS_CODEPAGE_950=m
CONFIG_NLS_CODEPAGE_932=m
CONFIG_NLS_CODEPAGE_949=m
CONFIG_NLS_CODEPAGE_874=m
CONFIG_NLS_ISO8859_8=m
CONFIG_NLS_CODEPAGE_1250=m
CONFIG_NLS_CODEPAGE_1251=m
CONFIG_NLS_ASCII=m
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_ISO8859_13=m
CONFIG_NLS_ISO8859_14=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
CONFIG_NLS_KOI8_U=m
CONFIG_NLS_UTF8=m
CONFIG_DLM=m
CONFIG_DLM_DEBUG=y

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_PRINTK_TIME=y
CONFIG_ENABLE_WARN_DEPRECATED=y
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_FRAME_WARN=1024
CONFIG_MAGIC_SYSRQ=y
# CONFIG_STRIP_ASM_SYMS is not set
CONFIG_UNUSED_SYMBOLS=y
CONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
CONFIG_DETECT_SOFTLOCKUP=y
# CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set
CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0
CONFIG_DETECT_HUNG_TASK=y
# CONFIG_BOOTPARAM_HUNG_TASK_PANIC is not set
CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=0
CONFIG_SCHED_DEBUG=y
# CONFIG_SCHEDSTATS is not set
CONFIG_TIMER_STATS=y
# CONFIG_DEBUG_OBJECTS is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_KMEMLEAK is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
CONFIG_STACKTRACE=y
# CONFIG_DEBUG_KOBJECT is not set
# CONFIG_DEBUG_HIGHMEM is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_VIRTUAL is not set
# CONFIG_DEBUG_WRITECOUNT is not set
CONFIG_DEBUG_MEMORY_INIT=y
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_DEBUG_NOTIFIERS is not set
# CONFIG_DEBUG_CREDENTIALS is not set
CONFIG_ARCH_WANT_FRAME_POINTERS=y
# CONFIG_FRAME_POINTER is not set
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_RCU_CPU_STALL_DETECTOR is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
# CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_LATENCYTOP is not set
CONFIG_SYSCTL_SYSCALL_CHECK=y
# CONFIG_DEBUG_PAGEALLOC is not set
CONFIG_USER_STACKTRACE_SUPPORT=y
CONFIG_NOP_TRACER=y
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_FP_TEST=y
CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
CONFIG_HAVE_SYSCALL_TRACEPOINTS=y
CONFIG_RING_BUFFER=y
CONFIG_EVENT_TRACING=y
CONFIG_CONTEXT_SWITCH_TRACER=y
CONFIG_RING_BUFFER_ALLOW_SWAP=y
CONFIG_TRACING=y
CONFIG_GENERIC_TRACER=y
CONFIG_TRACING_SUPPORT=y
CONFIG_FTRACE=y
# CONFIG_FUNCTION_TRACER is not set
# CONFIG_IRQSOFF_TRACER is not set
# CONFIG_SYSPROF_TRACER is not set
# CONFIG_SCHED_TRACER is not set
# CONFIG_FTRACE_SYSCALLS is not set
# CONFIG_BOOT_TRACER is not set
CONFIG_BRANCH_PROFILE_NONE=y
# CONFIG_PROFILE_ANNOTATED_BRANCHES is not set
# CONFIG_PROFILE_ALL_BRANCHES is not set
# CONFIG_POWER_TRACER is not set
# CONFIG_STACK_TRACER is not set
# CONFIG_KMEMTRACE is not set
# CONFIG_WORKQUEUE_TRACER is not set
CONFIG_BLK_DEV_IO_TRACE=y
# CONFIG_FTRACE_STARTUP_TEST is not set
# CONFIG_MMIOTRACE is not set
# CONFIG_RING_BUFFER_BENCHMARK is not set
# CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set
# CONFIG_DYNAMIC_DEBUG is not set
# CONFIG_DMA_API_DEBUG is not set
# CONFIG_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
# CONFIG_KGDB is not set
CONFIG_HAVE_ARCH_KMEMCHECK=y
# CONFIG_STRICT_DEVMEM is not set
CONFIG_X86_VERBOSE_BOOTUP=y
CONFIG_EARLY_PRINTK=y
# CONFIG_EARLY_PRINTK_DBGP is not set
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PER_CPU_MAPS is not set
# CONFIG_X86_PTDUMP is not set
# CONFIG_DEBUG_RODATA is not set
# CONFIG_DEBUG_NX_TEST is not set
# CONFIG_4KSTACKS is not set
CONFIG_DOUBLEFAULT=y
# CONFIG_IOMMU_STRESS is not set
CONFIG_HAVE_MMIOTRACE_SUPPORT=y
CONFIG_IO_DELAY_TYPE_0X80=0
CONFIG_IO_DELAY_TYPE_0XED=1
CONFIG_IO_DELAY_TYPE_UDELAY=2
CONFIG_IO_DELAY_TYPE_NONE=3
CONFIG_IO_DELAY_0X80=y
# CONFIG_IO_DELAY_0XED is not set
# CONFIG_IO_DELAY_UDELAY is not set
# CONFIG_IO_DELAY_NONE is not set
CONFIG_DEFAULT_IO_DELAY_TYPE=0
# CONFIG_DEBUG_BOOT_PARAMS is not set
# CONFIG_CPA_DEBUG is not set
# CONFIG_OPTIMIZE_INLINING is not set

#
# Security options
#
CONFIG_KEYS=y
# CONFIG_KEYS_DEBUG_PROC_KEYS is not set
CONFIG_SECURITY=y
CONFIG_SECURITYFS=y
CONFIG_SECURITY_NETWORK=y
CONFIG_SECURITY_NETWORK_XFRM=y
# CONFIG_SECURITY_PATH is not set
CONFIG_SECURITY_FILE_CAPABILITIES=y
CONFIG_LSM_MMAP_MIN_ADDR=65535
CONFIG_SECURITY_SELINUX=y
CONFIG_SECURITY_SELINUX_BOOTPARAM=y
CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=0
CONFIG_SECURITY_SELINUX_DISABLE=y
CONFIG_SECURITY_SELINUX_DEVELOP=y
CONFIG_SECURITY_SELINUX_AVC_STATS=y
CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1
# CONFIG_SECURITY_SELINUX_POLICYDB_VERSION_MAX is not set
# CONFIG_SECURITY_TOMOYO is not set
# CONFIG_IMA is not set
CONFIG_XOR_BLOCKS=m
CONFIG_ASYNC_CORE=m
CONFIG_ASYNC_MEMCPY=m
CONFIG_ASYNC_XOR=m
CONFIG_ASYNC_PQ=m
CONFIG_ASYNC_RAID6_RECOV=m
CONFIG_CRYPTO=y

#
# Crypto core or helper
#
# CONFIG_CRYPTO_FIPS is not set
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD=m
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_BLKCIPHER=m
CONFIG_CRYPTO_BLKCIPHER2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
CONFIG_CRYPTO_RNG=m
CONFIG_CRYPTO_RNG2=y
CONFIG_CRYPTO_PCOMP=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_MANAGER2=y
CONFIG_CRYPTO_GF128MUL=m
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_WORKQUEUE=y
# CONFIG_CRYPTO_CRYPTD is not set
CONFIG_CRYPTO_AUTHENC=m
CONFIG_CRYPTO_TEST=m

#
# Authenticated Encryption with Associated Data
#
CONFIG_CRYPTO_CCM=m
CONFIG_CRYPTO_GCM=m
CONFIG_CRYPTO_SEQIV=m

#
# Block modes
#
CONFIG_CRYPTO_CBC=m
CONFIG_CRYPTO_CTR=m
CONFIG_CRYPTO_CTS=m
CONFIG_CRYPTO_ECB=m
CONFIG_CRYPTO_LRW=m
CONFIG_CRYPTO_PCBC=m
CONFIG_CRYPTO_XTS=m

#
# Hash modes
#
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_XCBC=m
# CONFIG_CRYPTO_VMAC is not set

#
# Digest
#
CONFIG_CRYPTO_CRC32C=m
# CONFIG_CRYPTO_CRC32C_INTEL is not set
CONFIG_CRYPTO_GHASH=m
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_MICHAEL_MIC=m
# CONFIG_CRYPTO_RMD128 is not set
# CONFIG_CRYPTO_RMD160 is not set
# CONFIG_CRYPTO_RMD256 is not set
# CONFIG_CRYPTO_RMD320 is not set
CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_TGR192=m
CONFIG_CRYPTO_WP512=m

#
# Ciphers
#
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_AES_586=m
CONFIG_CRYPTO_ANUBIS=m
CONFIG_CRYPTO_ARC4=m
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_CAMELLIA=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_FCRYPT=m
CONFIG_CRYPTO_KHAZAD=m
CONFIG_CRYPTO_SALSA20=m
CONFIG_CRYPTO_SALSA20_586=m
CONFIG_CRYPTO_SEED=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_TEA=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_TWOFISH_COMMON=m
CONFIG_CRYPTO_TWOFISH_586=m

#
# Compression
#
CONFIG_CRYPTO_DEFLATE=m
# CONFIG_CRYPTO_ZLIB is not set
CONFIG_CRYPTO_LZO=m

#
# Random Number Generation
#
CONFIG_CRYPTO_ANSI_CPRNG=m
CONFIG_CRYPTO_HW=y
CONFIG_CRYPTO_DEV_PADLOCK=m
CONFIG_CRYPTO_DEV_PADLOCK_AES=m
CONFIG_CRYPTO_DEV_PADLOCK_SHA=m
CONFIG_CRYPTO_DEV_GEODE=m
CONFIG_CRYPTO_DEV_HIFN_795X=m
CONFIG_CRYPTO_DEV_HIFN_795X_RNG=y
CONFIG_HAVE_KVM=y
CONFIG_HAVE_KVM_IRQCHIP=y
CONFIG_HAVE_KVM_EVENTFD=y
CONFIG_KVM_APIC_ARCHITECTURE=y
CONFIG_VIRTUALIZATION=y
CONFIG_KVM=m
CONFIG_KVM_INTEL=m
CONFIG_KVM_AMD=m
# CONFIG_LGUEST is not set
CONFIG_VIRTIO=m
CONFIG_VIRTIO_RING=m
CONFIG_VIRTIO_PCI=m
CONFIG_VIRTIO_BALLOON=m
CONFIG_BINARY_PRINTF=y

#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_GENERIC_FIND_FIRST_BIT=y
CONFIG_GENERIC_FIND_NEXT_BIT=y
CONFIG_GENERIC_FIND_LAST_BIT=y
CONFIG_CRC_CCITT=m
CONFIG_CRC16=m
CONFIG_CRC_T10DIF=m
CONFIG_CRC_ITU_T=m
CONFIG_CRC32=y
CONFIG_CRC7=m
CONFIG_LIBCRC32C=m
CONFIG_AUDIT_GENERIC=y
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=m
CONFIG_LZO_COMPRESS=m
CONFIG_LZO_DECOMPRESS=m
CONFIG_DECOMPRESS_GZIP=y
CONFIG_DECOMPRESS_BZIP2=y
CONFIG_DECOMPRESS_LZMA=y
CONFIG_GENERIC_ALLOCATOR=y
CONFIG_REED_SOLOMON=m
CONFIG_REED_SOLOMON_DEC16=y
CONFIG_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=m
CONFIG_TEXTSEARCH_BM=m
CONFIG_TEXTSEARCH_FSM=m
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
CONFIG_CHECK_SIGNATURE=y
CONFIG_NLATTR=y

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 1911 bytes --]

Hi Pasi,

Messages seen with not-working case

/***********************************************************************************
kernel:/boot/xen.3.4.3.gz dom0-mem=752M lowmem-emergency-pool=1M
crashkernel=64M@32M console=comX vga=mode-0x0311
loading /boot/xen.3.4.3.gz..........
Module:/boot/vmlinuz-2.6.32 root=LABEL=root-mhycetek ro Xencons=hvc
console=hvc0 console=tty0 quiet vga=785 splash
Loading /boot/vmlinuz-2.6.32.........
Module:/boot/initrd-2.6-xen.img
Loading
/boot/initrd-2.6-xen.img...............................................................................................
Booting:MBI=0x00010120, entry=0x00100000
***************************************************************************************/

Screen is blank after these messages and system returns to BIOS setup.

Messages seen with working case
/***********************************************************************************
kernel:/boot/xen.gz dom0-mem=752M lowmem-emergency-pool=1M
crashkernel=64M@32M comsole=comX vga=mode-0x0311
loading /boot/xen.gz..........
Module:/boot/vmlinuz-2.6.xen root=LABEL=root-mhycetek ro Xencons=hvc
console=hvc0 console=tty0 quiet vga=785 splash
Loading /boot/vmlinuz-2.6.xen.........
Module:/boot/initrd-2.6-xen.img
Loading
/boot/initrd-2.6-xen.img...............................................................................................
Booting:MBI=0x00010120, entry=0x00100000
***************************************************************************************/

Versions used in Non-working case

xen - 3.4.3/4.0.0
kernel - xen/next
initrd - default one which came with xcp0.1.1 download.(Ps note, in xcp ddk
cannot build initrd image)

in Working case

xen - 3.4.2
kernel - xcp 0.1.1
initrd - one that came with xcp 0.1.1

Checked in my .config and changed CONFIG_PHYSICAL_START to 0x00100000 and
CONFIG_PHYSICAL_ALIGN=0x100000, didn't help.

Inputs appreciated.

Thanks

[-- Attachment #1.2: Type: text/html, Size: 2093 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 2317 bytes --]

Any inputs on this? I compiled xen/next kernel in Debian Lenny and booted
successfully as a domU(I am using same .config file which I used to build
under xcp-ddk). Looks to me xen/next doesn't work with xcp0.1.1.

Thanks

On Fri, Mar 26, 2010 at 12:11 PM, Ritu kaur <ritu.kaur.us@gmail.com> wrote:

> Hi Pasi,
>
> Messages seen with not-working case
>
>
> /***********************************************************************************
> kernel:/boot/xen.3.4.3.gz dom0-mem=752M lowmem-emergency-pool=1M
> crashkernel=64M@32M console=comX vga=mode-0x0311
> loading /boot/xen.3.4.3.gz..........
> Module:/boot/vmlinuz-2.6.32 root=LABEL=root-mhycetek ro Xencons=hvc
> console=hvc0 console=tty0 quiet vga=785 splash
> Loading /boot/vmlinuz-2.6.32.........
> Module:/boot/initrd-2.6-xen.img
> Loading
> /boot/initrd-2.6-xen.img...............................................................................................
> Booting:MBI=0x00010120, entry=0x00100000
>
> ***************************************************************************************/
>
> Screen is blank after these messages and system returns to BIOS setup.
>
> Messages seen with working case
>
> /***********************************************************************************
> kernel:/boot/xen.gz dom0-mem=752M lowmem-emergency-pool=1M
> crashkernel=64M@32M comsole=comX vga=mode-0x0311
> loading /boot/xen.gz..........
> Module:/boot/vmlinuz-2.6.xen root=LABEL=root-mhycetek ro Xencons=hvc
> console=hvc0 console=tty0 quiet vga=785 splash
> Loading /boot/vmlinuz-2.6.xen.........
> Module:/boot/initrd-2.6-xen.img
> Loading
> /boot/initrd-2.6-xen.img...............................................................................................
> Booting:MBI=0x00010120, entry=0x00100000
>
> ***************************************************************************************/
>
> Versions used in Non-working case
>
> xen - 3.4.3/4.0.0
> kernel - xen/next
> initrd - default one which came with xcp0.1.1 download.(Ps note, in xcp ddk
> cannot build initrd image)
>
> in Working case
>
> xen - 3.4.2
> kernel - xcp 0.1.1
> initrd - one that came with xcp 0.1.1
>
> Checked in my .config and changed CONFIG_PHYSICAL_START to 0x00100000 and
> CONFIG_PHYSICAL_ALIGN=0x100000, didn't help.
>
> Inputs appreciated.
>
> Thanks
>
>
>

[-- Attachment #1.2: Type: text/html, Size: 2697 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Pasi Kärkkäinen]

On Sat, Mar 27, 2010 at 11:28:12AM -0700, Ritu kaur wrote:
>    Any inputs on this? I compiled xen/next kernel in Debian Lenny and booted
>    successfully as a domU(I am using same .config file which I used to build
>    under xcp-ddk). Looks to me xen/next doesn't work with xcp0.1.1.
> 

You need to re-generate the dom0 kernel initrd to match your kernel.
You cannot use the default xcp initrd image.

Please provide the full serial console boot log so we can troubleshoot it:
http://wiki.xensource.com/xenwiki/XenSerialConsole

-- Pasi

>    Thanks
> 
>    On Fri, Mar 26, 2010 at 12:11 PM, Ritu kaur <[1]ritu.kaur.us@[2]gmail.com>
>    wrote:
> 
>      Hi Pasi,
> 
>      Messages seen with not-working case
> 
>      /***********************************************************************************
>      kernel:/boot/xen.3.4.3.gz dom0-mem=752M lowmem-emergency-pool=1M
>      crashkernel=64M@32M console=comX vga=mode-0x0311
>      loading /boot/xen.3.4.3.gz..........
>      Module:/boot/vmlinuz-2.6.32 root=LABEL=root-mhycetek ro Xencons=hvc
>      console=hvc0 console=tty0 quiet vga=785 splash
>      Loading /boot/vmlinuz-2.6.32.........
>      Module:/boot/initrd-2.6-xen.img
>      Loading
>      /boot/initrd-2.6-xen.img...............................................................................................
>      Booting:MBI=0x00010120, entry=0x00100000
>      ***************************************************************************************/
> 
>      Screen is blank after these messages and system returns to BIOS setup.
> 
>      Messages seen with working case
>      /***********************************************************************************
>      kernel:/boot/xen.gz dom0-mem=752M lowmem-emergency-pool=1M
>      crashkernel=64M@32M comsole=comX vga=mode-0x0311
>      loading /boot/xen.gz..........
>      Module:/boot/vmlinuz-2.6.xen root=LABEL=root-mhycetek ro Xencons=hvc
>      console=hvc0 console=tty0 quiet vga=785 splash
>      Loading /boot/vmlinuz-2.6.xen.........
>      Module:/boot/initrd-2.6-xen.img
>      Loading
>      /boot/initrd-2.6-xen.img...............................................................................................
>      Booting:MBI=0x00010120, entry=0x00100000
>      ***************************************************************************************/
> 
>      Versions used in Non-working case
> 
>      xen - 3.4.3/4.0.0
>      kernel - xen/next
>      initrd - default one which came with xcp0.1.1 download.(Ps note, in xcp
>      ddk cannot build initrd image)
> 
>      in Working case
> 
>      xen - 3.4.2
>      kernel - xcp 0.1.1
>      initrd - one that came with xcp 0.1.1
> 
>      Checked in my .config and changed CONFIG_PHYSICAL_START to 0x00100000
>      and CONFIG_PHYSICAL_ALIGN=0x100000, didn't help.
> 
>      Inputs appreciated.
> 
>      Thanks
> 
> References
> 
>    Visible links
>    1. http://ritu.kaur.us/
>    2. http://gmail.com/

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

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 3854 bytes --]

Thanks Pasi. I had used following command to regenerate initrd image in xcp
ddk

mkinitrd -f ./initrd-2.6.32.img  2.6.27.42-0.1.1.xs0.1.1.737.1065xen

it doesn't work either. While booting screen goes blank immediately after I
see

...
 Booting:MBI=0x00010120, entry=0x00100000

and next thing I see is BIOS setup, so not sure connecting serial cable will
reveal anything more. Inputs appreciated.

Thanks

On Sat, Mar 27, 2010 at 11:43 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote:

> On Sat, Mar 27, 2010 at 11:28:12AM -0700, Ritu kaur wrote:
> >    Any inputs on this? I compiled xen/next kernel in Debian Lenny and
> booted
> >    successfully as a domU(I am using same .config file which I used to
> build
> >    under xcp-ddk). Looks to me xen/next doesn't work with xcp0.1.1.
> >
>
> You need to re-generate the dom0 kernel initrd to match your kernel.
> You cannot use the default xcp initrd image.
>
> Please provide the full serial console boot log so we can troubleshoot it:
> http://wiki.xensource.com/xenwiki/XenSerialConsole
>
> -- Pasi
>
> >    Thanks
> >
> >    On Fri, Mar 26, 2010 at 12:11 PM, Ritu kaur <[1]ritu.kaur.us@[2]
> gmail.com>
> >    wrote:
> >
> >      Hi Pasi,
> >
> >      Messages seen with not-working case
> >
> >
>  /***********************************************************************************
> >      kernel:/boot/xen.3.4.3.gz dom0-mem=752M lowmem-emergency-pool=1M
> >      crashkernel=64M@32M console=comX vga=mode-0x0311
> >      loading /boot/xen.3.4.3.gz..........
> >      Module:/boot/vmlinuz-2.6.32 root=LABEL=root-mhycetek ro Xencons=hvc
> >      console=hvc0 console=tty0 quiet vga=785 splash
> >      Loading /boot/vmlinuz-2.6.32.........
> >      Module:/boot/initrd-2.6-xen.img
> >      Loading
> >
>  /boot/initrd-2.6-xen.img...............................................................................................
> >      Booting:MBI=0x00010120, entry=0x00100000
> >
>  ***************************************************************************************/
> >
> >      Screen is blank after these messages and system returns to BIOS
> setup.
> >
> >      Messages seen with working case
> >
>  /***********************************************************************************
> >      kernel:/boot/xen.gz dom0-mem=752M lowmem-emergency-pool=1M
> >      crashkernel=64M@32M comsole=comX vga=mode-0x0311
> >      loading /boot/xen.gz..........
> >      Module:/boot/vmlinuz-2.6.xen root=LABEL=root-mhycetek ro Xencons=hvc
> >      console=hvc0 console=tty0 quiet vga=785 splash
> >      Loading /boot/vmlinuz-2.6.xen.........
> >      Module:/boot/initrd-2.6-xen.img
> >      Loading
> >
>  /boot/initrd-2.6-xen.img...............................................................................................
> >      Booting:MBI=0x00010120, entry=0x00100000
> >
>  ***************************************************************************************/
> >
> >      Versions used in Non-working case
> >
> >      xen - 3.4.3/4.0.0
> >      kernel - xen/next
> >      initrd - default one which came with xcp0.1.1 download.(Ps note, in
> xcp
> >      ddk cannot build initrd image)
> >
> >      in Working case
> >
> >      xen - 3.4.2
> >      kernel - xcp 0.1.1
> >      initrd - one that came with xcp 0.1.1
> >
> >      Checked in my .config and changed CONFIG_PHYSICAL_START to
> 0x00100000
> >      and CONFIG_PHYSICAL_ALIGN=0x100000, didn't help.
> >
> >      Inputs appreciated.
> >
> >      Thanks
> >
> > References
> >
> >    Visible links
> >    1. http://ritu.kaur.us/
> >    2. http://gmail.com/
>
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
>
>

[-- Attachment #1.2: Type: text/html, Size: 5041 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 4470 bytes --]

I tried another thing. After compilation,  I did "make modules_install" in
xcp ddk in order to use following command

mkinitrd -f ./initrd-2.6.32.img 2.6.32

I get following errors...

modinfo: could not find module ide-disk
No module ide-disk found for kernel 2.6.32, aborting

My boot disk is ide and looking into .config didn't give me any ideas as to
what has to be enabled.

Thanks

On Sat, Mar 27, 2010 at 6:32 PM, Ritu kaur <ritu.kaur.us@gmail.com> wrote:

> Thanks Pasi. I had used following command to regenerate initrd image in xcp
> ddk
>
> mkinitrd -f ./initrd-2.6.32.img  2.6.27.42-0.1.1.xs0.1.1.737.1065xen
>
> it doesn't work either. While booting screen goes blank immediately after I
> see
>
> ...
>  Booting:MBI=0x00010120, entry=0x00100000
>
> and next thing I see is BIOS setup, so not sure connecting serial cable
> will reveal anything more. Inputs appreciated.
>
> Thanks
>
>
> On Sat, Mar 27, 2010 at 11:43 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote:
>
>> On Sat, Mar 27, 2010 at 11:28:12AM -0700, Ritu kaur wrote:
>> >    Any inputs on this? I compiled xen/next kernel in Debian Lenny and
>> booted
>> >    successfully as a domU(I am using same .config file which I used to
>> build
>> >    under xcp-ddk). Looks to me xen/next doesn't work with xcp0.1.1.
>> >
>>
>> You need to re-generate the dom0 kernel initrd to match your kernel.
>> You cannot use the default xcp initrd image.
>>
>> Please provide the full serial console boot log so we can troubleshoot it:
>> http://wiki.xensource.com/xenwiki/XenSerialConsole
>>
>> -- Pasi
>>
>> >    Thanks
>> >
>> >    On Fri, Mar 26, 2010 at 12:11 PM, Ritu kaur <[1]ritu.kaur.us@[2]
>> gmail.com>
>> >    wrote:
>> >
>> >      Hi Pasi,
>> >
>> >      Messages seen with not-working case
>> >
>> >
>>  /***********************************************************************************
>> >      kernel:/boot/xen.3.4.3.gz dom0-mem=752M lowmem-emergency-pool=1M
>> >      crashkernel=64M@32M console=comX vga=mode-0x0311
>> >      loading /boot/xen.3.4.3.gz..........
>> >      Module:/boot/vmlinuz-2.6.32 root=LABEL=root-mhycetek ro Xencons=hvc
>> >      console=hvc0 console=tty0 quiet vga=785 splash
>> >      Loading /boot/vmlinuz-2.6.32.........
>> >      Module:/boot/initrd-2.6-xen.img
>> >      Loading
>> >
>>  /boot/initrd-2.6-xen.img...............................................................................................
>> >      Booting:MBI=0x00010120, entry=0x00100000
>> >
>>  ***************************************************************************************/
>> >
>> >      Screen is blank after these messages and system returns to BIOS
>> setup.
>> >
>> >      Messages seen with working case
>> >
>>  /***********************************************************************************
>> >      kernel:/boot/xen.gz dom0-mem=752M lowmem-emergency-pool=1M
>> >      crashkernel=64M@32M comsole=comX vga=mode-0x0311
>> >      loading /boot/xen.gz..........
>> >      Module:/boot/vmlinuz-2.6.xen root=LABEL=root-mhycetek ro
>> Xencons=hvc
>> >      console=hvc0 console=tty0 quiet vga=785 splash
>> >      Loading /boot/vmlinuz-2.6.xen.........
>> >      Module:/boot/initrd-2.6-xen.img
>> >      Loading
>> >
>>  /boot/initrd-2.6-xen.img...............................................................................................
>> >      Booting:MBI=0x00010120, entry=0x00100000
>> >
>>  ***************************************************************************************/
>> >
>> >      Versions used in Non-working case
>> >
>> >      xen - 3.4.3/4.0.0
>> >      kernel - xen/next
>> >      initrd - default one which came with xcp0.1.1 download.(Ps note, in
>> xcp
>> >      ddk cannot build initrd image)
>> >
>> >      in Working case
>> >
>> >      xen - 3.4.2
>> >      kernel - xcp 0.1.1
>> >      initrd - one that came with xcp 0.1.1
>> >
>> >      Checked in my .config and changed CONFIG_PHYSICAL_START to
>> 0x00100000
>> >      and CONFIG_PHYSICAL_ALIGN=0x100000, didn't help.
>> >
>> >      Inputs appreciated.
>> >
>> >      Thanks
>> >
>> > References
>> >
>> >    Visible links
>> >    1. http://ritu.kaur.us/
>> >    2. http://gmail.com/
>>
>> > _______________________________________________
>> > Xen-devel mailing list
>> > Xen-devel@lists.xensource.com
>> > http://lists.xensource.com/xen-devel
>>
>>
>

[-- Attachment #1.2: Type: text/html, Size: 5898 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Pasi Kärkkäinen]

On Sat, Mar 27, 2010 at 08:21:49PM -0700, Ritu kaur wrote:
>    I tried another thing. After compilation,  I did "make modules_install" in
>    xcp ddk in order to use following command
> 
>    mkinitrd -f ./initrd-2.6.32.img 2.6.32
> 
>    I get following errors...
> 
>    modinfo: could not find module ide-disk
>    No module ide-disk found for kernel 2.6.32, aborting
> 

mkinitrd reads /etc/modprobe.conf to figure out what modules should be included into the initrd image.

>    My boot disk is ide and looking into .config didn't give me any ideas as
>    to what has to be enabled.
> 

If you need some other module then fix it in /etc/modprobe.conf
You need to figure out what's the correct driver for your root/boot disk. 

-- Pasi

>    Thanks
> 
>    On Sat, Mar 27, 2010 at 6:32 PM, Ritu kaur <[1]ritu.kaur.us@[2]gmail.com>
>    wrote:
> 
>      Thanks Pasi. I had used following command to regenerate initrd image in
>      xcp ddk
> 
>      mkinitrd -f ./initrd-2.6.32.img  2.6.27.42-0.1.1.xs0.1.1.737.1065xen
> 
>      it doesn't work either. While booting screen goes blank immediately
>      after I see
>      ...
>       Booting:MBI=0x00010120, entry=0x00100000
> 
>      and next thing I see is BIOS setup, so not sure connecting serial cable
>      will reveal anything more. Inputs appreciated.
> 
>      Thanks
> 
>      On Sat, Mar 27, 2010 at 11:43 AM, Pasi Kärkkäinen <[3]pasik@iki.fi>
>      wrote:
> 
>        On Sat, Mar 27, 2010 at 11:28:12AM -0700, Ritu kaur wrote:
>        >    Any inputs on this? I compiled xen/next kernel in Debian Lenny
>        and booted
>        >    successfully as a domU(I am using same .config file which I used
>        to build
>        >    under xcp-ddk). Looks to me xen/next doesn't work with xcp0.1.1.
>        >
> 
>        You need to re-generate the dom0 kernel initrd to match your kernel.
>        You cannot use the default xcp initrd image.
> 
>        Please provide the full serial console boot log so we can troubleshoot
>        it:
>        [4]http://wiki.xensource.com/xenwiki/XenSerialConsole
> 
>        -- Pasi
> 
>        >    Thanks
>        >
>        >    On Fri, Mar 26, 2010 at 12:11 PM, Ritu kaur
>        <[1][5]ritu.kaur.us@[2][6]gmail.com>
>        >    wrote:
>        >
>        >      Hi Pasi,
>        >
>        >      Messages seen with not-working case
>        >
>        >
>         /***********************************************************************************
>        >      kernel:/boot/xen.3.4.3.gz dom0-mem=752M
>        lowmem-emergency-pool=1M
>        >      crashkernel=64M@32M console=comX vga=mode-0x0311
>        >      loading /boot/xen.3.4.3.gz..........
>        >      Module:/boot/vmlinuz-2.6.32 root=LABEL=root-mhycetek ro
>        Xencons=hvc
>        >      console=hvc0 console=tty0 quiet vga=785 splash
>        >      Loading /boot/vmlinuz-2.6.32.........
>        >      Module:/boot/initrd-2.6-xen.img
>        >      Loading
>        >
>         /boot/initrd-2.6-xen.img...............................................................................................
>        >      Booting:MBI=0x00010120, entry=0x00100000
>        >
>         ***************************************************************************************/
>        >
>        >      Screen is blank after these messages and system returns to BIOS
>        setup.
>        >
>        >      Messages seen with working case
>        >
>         /***********************************************************************************
>        >      kernel:/boot/xen.gz dom0-mem=752M lowmem-emergency-pool=1M
>        >      crashkernel=64M@32M comsole=comX vga=mode-0x0311
>        >      loading /boot/xen.gz..........
>        >      Module:/boot/vmlinuz-2.6.xen root=LABEL=root-mhycetek ro
>        Xencons=hvc
>        >      console=hvc0 console=tty0 quiet vga=785 splash
>        >      Loading /boot/vmlinuz-2.6.xen.........
>        >      Module:/boot/initrd-2.6-xen.img
>        >      Loading
>        >
>         /boot/initrd-2.6-xen.img...............................................................................................
>        >      Booting:MBI=0x00010120, entry=0x00100000
>        >
>         ***************************************************************************************/
>        >
>        >      Versions used in Non-working case
>        >
>        >      xen - 3.4.3/4.0.0
>        >      kernel - xen/next
>        >      initrd - default one which came with xcp0.1.1 download.(Ps
>        note, in xcp
>        >      ddk cannot build initrd image)
>        >
>        >      in Working case
>        >
>        >      xen - 3.4.2
>        >      kernel - xcp 0.1.1
>        >      initrd - one that came with xcp 0.1.1
>        >
>        >      Checked in my .config and changed CONFIG_PHYSICAL_START to
>        0x00100000
>        >      and CONFIG_PHYSICAL_ALIGN=0x100000, didn't help.
>        >
>        >      Inputs appreciated.
>        >
>        >      Thanks
>        >
>        > References
>        >
>        >    Visible links
>        >    1. [7]http://ritu.kaur.us/
>        >    2. [8]http://gmail.com/
> 
>        > _______________________________________________
>        > Xen-devel mailing list
>        > [9]Xen-devel@lists.xensource.com
>        > [10]http://lists.xensource.com/xen-devel
> 
> References
> 
>    Visible links
>    1. http://ritu.kaur.us/
>    2. http://gmail.com/
>    3. mailto:pasik@iki.fi
>    4. http://wiki.xensource.com/xenwiki/XenSerialConsole
>    5. http://ritu.kaur.us/
>    6. http://gmail.com/
>    7. http://ritu.kaur.us/
>    8. http://gmail.com/
>    9. mailto:Xen-devel@lists.xensource.com
>   10. http://lists.xensource.com/xen-devel

Re: domU guest for xcp 0.1.1

[Pasi Kärkkäinen]

On Sun, Mar 28, 2010 at 02:34:39PM +0300, Pasi Kärkkäinen wrote:
> On Sat, Mar 27, 2010 at 08:21:49PM -0700, Ritu kaur wrote:
> >    I tried another thing. After compilation,  I did "make modules_install" in
> >    xcp ddk in order to use following command
> > 
> >    mkinitrd -f ./initrd-2.6.32.img 2.6.32
> > 
> >    I get following errors...
> > 
> >    modinfo: could not find module ide-disk
> >    No module ide-disk found for kernel 2.6.32, aborting
> > 
> 
> mkinitrd reads /etc/modprobe.conf to figure out what modules should be included into the initrd image.
> 

also I'm not sure if ide-disk is a required module for 2.6.32? 

-- Pasi

> >    My boot disk is ide and looking into .config didn't give me any ideas as
> >    to what has to be enabled.
> > 
> 
> If you need some other module then fix it in /etc/modprobe.conf
> You need to figure out what's the correct driver for your root/boot disk. 
> 
> -- Pasi
> 
> >    Thanks
> > 
> >    On Sat, Mar 27, 2010 at 6:32 PM, Ritu kaur <[1]ritu.kaur.us@[2]gmail.com>
> >    wrote:
> > 
> >      Thanks Pasi. I had used following command to regenerate initrd image in
> >      xcp ddk
> > 
> >      mkinitrd -f ./initrd-2.6.32.img  2.6.27.42-0.1.1.xs0.1.1.737.1065xen
> > 
> >      it doesn't work either. While booting screen goes blank immediately
> >      after I see
> >      ...
> >       Booting:MBI=0x00010120, entry=0x00100000
> > 
> >      and next thing I see is BIOS setup, so not sure connecting serial cable
> >      will reveal anything more. Inputs appreciated.
> > 
> >      Thanks
> > 
> >      On Sat, Mar 27, 2010 at 11:43 AM, Pasi Kärkkäinen <[3]pasik@iki.fi>
> >      wrote:
> > 
> >        On Sat, Mar 27, 2010 at 11:28:12AM -0700, Ritu kaur wrote:
> >        >    Any inputs on this? I compiled xen/next kernel in Debian Lenny
> >        and booted
> >        >    successfully as a domU(I am using same .config file which I used
> >        to build
> >        >    under xcp-ddk). Looks to me xen/next doesn't work with xcp0.1.1.
> >        >
> > 
> >        You need to re-generate the dom0 kernel initrd to match your kernel.
> >        You cannot use the default xcp initrd image.
> > 
> >        Please provide the full serial console boot log so we can troubleshoot
> >        it:
> >        [4]http://wiki.xensource.com/xenwiki/XenSerialConsole
> > 
> >        -- Pasi
> > 
> >        >    Thanks
> >        >
> >        >    On Fri, Mar 26, 2010 at 12:11 PM, Ritu kaur
> >        <[1][5]ritu.kaur.us@[2][6]gmail.com>
> >        >    wrote:
> >        >
> >        >      Hi Pasi,
> >        >
> >        >      Messages seen with not-working case
> >        >
> >        >
> >         /***********************************************************************************
> >        >      kernel:/boot/xen.3.4.3.gz dom0-mem=752M
> >        lowmem-emergency-pool=1M
> >        >      crashkernel=64M@32M console=comX vga=mode-0x0311
> >        >      loading /boot/xen.3.4.3.gz..........
> >        >      Module:/boot/vmlinuz-2.6.32 root=LABEL=root-mhycetek ro
> >        Xencons=hvc
> >        >      console=hvc0 console=tty0 quiet vga=785 splash
> >        >      Loading /boot/vmlinuz-2.6.32.........
> >        >      Module:/boot/initrd-2.6-xen.img
> >        >      Loading
> >        >
> >         /boot/initrd-2.6-xen.img...............................................................................................
> >        >      Booting:MBI=0x00010120, entry=0x00100000
> >        >
> >         ***************************************************************************************/
> >        >
> >        >      Screen is blank after these messages and system returns to BIOS
> >        setup.
> >        >
> >        >      Messages seen with working case
> >        >
> >         /***********************************************************************************
> >        >      kernel:/boot/xen.gz dom0-mem=752M lowmem-emergency-pool=1M
> >        >      crashkernel=64M@32M comsole=comX vga=mode-0x0311
> >        >      loading /boot/xen.gz..........
> >        >      Module:/boot/vmlinuz-2.6.xen root=LABEL=root-mhycetek ro
> >        Xencons=hvc
> >        >      console=hvc0 console=tty0 quiet vga=785 splash
> >        >      Loading /boot/vmlinuz-2.6.xen.........
> >        >      Module:/boot/initrd-2.6-xen.img
> >        >      Loading
> >        >
> >         /boot/initrd-2.6-xen.img...............................................................................................
> >        >      Booting:MBI=0x00010120, entry=0x00100000
> >        >
> >         ***************************************************************************************/
> >        >
> >        >      Versions used in Non-working case
> >        >
> >        >      xen - 3.4.3/4.0.0
> >        >      kernel - xen/next
> >        >      initrd - default one which came with xcp0.1.1 download.(Ps
> >        note, in xcp
> >        >      ddk cannot build initrd image)
> >        >
> >        >      in Working case
> >        >
> >        >      xen - 3.4.2
> >        >      kernel - xcp 0.1.1
> >        >      initrd - one that came with xcp 0.1.1
> >        >
> >        >      Checked in my .config and changed CONFIG_PHYSICAL_START to
> >        0x00100000
> >        >      and CONFIG_PHYSICAL_ALIGN=0x100000, didn't help.
> >        >
> >        >      Inputs appreciated.
> >        >
> >        >      Thanks
> >        >
> >        > References
> >        >
> >        >    Visible links
> >        >    1. [7]http://ritu.kaur.us/
> >        >    2. [8]http://gmail.com/
> > 
> >        > _______________________________________________
> >        > Xen-devel mailing list
> >        > [9]Xen-devel@lists.xensource.com
> >        > [10]http://lists.xensource.com/xen-devel
> > 
> > References
> > 
> >    Visible links
> >    1. http://ritu.kaur.us/
> >    2. http://gmail.com/
> >    3. mailto:pasik@iki.fi
> >    4. http://wiki.xensource.com/xenwiki/XenSerialConsole
> >    5. http://ritu.kaur.us/
> >    6. http://gmail.com/
> >    7. http://ritu.kaur.us/
> >    8. http://gmail.com/
> >    9. mailto:Xen-devel@lists.xensource.com
> >   10. http://lists.xensource.com/xen-devel
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 7823 bytes --]

Hi Pasi,

Serial console just doesn't seem to work. In extlinux.conf file I have

# location mbr
serial 0 115200
default xe-serial
prompt 1
timeout 50
...

label xe-serial
  # XenCloudPlatform (Serial)
  kernel mboot.c32
  append /boot/xen.3.4.3.gz com1=115200,8n1 console=com1,vga dom0_mem=752M
lowmem_emergency_pool=1M crashkernel=64M@32M --- /boot/vmlinuz-2.6.32
root=LABEL=root-mhycetek ro console=tty0 earlyprintk=xen nomodeset
xencons=hvc console=hvc0 --- /boot/initrd-2.6.32.img

>From another linux m/c, I run minicom -s /dev/ttyS0, configure serial port
to match above config. minicom always reports serial port as offline.
Googled and tried another option "minicom -c on /dev/ttyS0" still no luck. I
have made sure from BIOS on both m/c's serial com ports are enabled. Not
quite sure what is wrong here. Does extlinux.conf entry looks fine?

Thanks

On Sun, Mar 28, 2010 at 4:55 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote:

> On Sun, Mar 28, 2010 at 02:34:39PM +0300, Pasi Kärkkäinen wrote:
> > On Sat, Mar 27, 2010 at 08:21:49PM -0700, Ritu kaur wrote:
> > >    I tried another thing. After compilation,  I did "make
> modules_install" in
> > >    xcp ddk in order to use following command
> > >
> > >    mkinitrd -f ./initrd-2.6.32.img 2.6.32
> > >
> > >    I get following errors...
> > >
> > >    modinfo: could not find module ide-disk
> > >    No module ide-disk found for kernel 2.6.32, aborting
> > >
> >
> > mkinitrd reads /etc/modprobe.conf to figure out what modules should be
> included into the initrd image.
> >
>
> also I'm not sure if ide-disk is a required module for 2.6.32?
>
> -- Pasi
>
> > >    My boot disk is ide and looking into .config didn't give me any
> ideas as
> > >    to what has to be enabled.
> > >
> >
> > If you need some other module then fix it in /etc/modprobe.conf
> > You need to figure out what's the correct driver for your root/boot disk.
> >
> > -- Pasi
> >
> > >    Thanks
> > >
> > >    On Sat, Mar 27, 2010 at 6:32 PM, Ritu kaur <[1]ritu.kaur.us@[2]
> gmail.com>
> > >    wrote:
> > >
> > >      Thanks Pasi. I had used following command to regenerate initrd
> image in
> > >      xcp ddk
> > >
> > >      mkinitrd -f ./initrd-2.6.32.img
>  2.6.27.42-0.1.1.xs0.1.1.737.1065xen
> > >
> > >      it doesn't work either. While booting screen goes blank
> immediately
> > >      after I see
> > >      ...
> > >       Booting:MBI=0x00010120, entry=0x00100000
> > >
> > >      and next thing I see is BIOS setup, so not sure connecting serial
> cable
> > >      will reveal anything more. Inputs appreciated.
> > >
> > >      Thanks
> > >
> > >      On Sat, Mar 27, 2010 at 11:43 AM, Pasi Kärkkäinen <[3]
> pasik@iki.fi>
> > >      wrote:
> > >
> > >        On Sat, Mar 27, 2010 at 11:28:12AM -0700, Ritu kaur wrote:
> > >        >    Any inputs on this? I compiled xen/next kernel in Debian
> Lenny
> > >        and booted
> > >        >    successfully as a domU(I am using same .config file which I
> used
> > >        to build
> > >        >    under xcp-ddk). Looks to me xen/next doesn't work with
> xcp0.1.1.
> > >        >
> > >
> > >        You need to re-generate the dom0 kernel initrd to match your
> kernel.
> > >        You cannot use the default xcp initrd image.
> > >
> > >        Please provide the full serial console boot log so we can
> troubleshoot
> > >        it:
> > >        [4]http://wiki.xensource.com/xenwiki/XenSerialConsole
> > >
> > >        -- Pasi
> > >
> > >        >    Thanks
> > >        >
> > >        >    On Fri, Mar 26, 2010 at 12:11 PM, Ritu kaur
> > >        <[1][5]ritu.kaur.us@[2][6]gmail.com>
> > >        >    wrote:
> > >        >
> > >        >      Hi Pasi,
> > >        >
> > >        >      Messages seen with not-working case
> > >        >
> > >        >
> > >
> /***********************************************************************************
> > >        >      kernel:/boot/xen.3.4.3.gz dom0-mem=752M
> > >        lowmem-emergency-pool=1M
> > >        >      crashkernel=64M@32M console=comX vga=mode-0x0311
> > >        >      loading /boot/xen.3.4.3.gz..........
> > >        >      Module:/boot/vmlinuz-2.6.32 root=LABEL=root-mhycetek ro
> > >        Xencons=hvc
> > >        >      console=hvc0 console=tty0 quiet vga=785 splash
> > >        >      Loading /boot/vmlinuz-2.6.32.........
> > >        >      Module:/boot/initrd-2.6-xen.img
> > >        >      Loading
> > >        >
> > >
> /boot/initrd-2.6-xen.img...............................................................................................
> > >        >      Booting:MBI=0x00010120, entry=0x00100000
> > >        >
> > >
> ***************************************************************************************/
> > >        >
> > >        >      Screen is blank after these messages and system returns
> to BIOS
> > >        setup.
> > >        >
> > >        >      Messages seen with working case
> > >        >
> > >
> /***********************************************************************************
> > >        >      kernel:/boot/xen.gz dom0-mem=752M
> lowmem-emergency-pool=1M
> > >        >      crashkernel=64M@32M comsole=comX vga=mode-0x0311
> > >        >      loading /boot/xen.gz..........
> > >        >      Module:/boot/vmlinuz-2.6.xen root=LABEL=root-mhycetek ro
> > >        Xencons=hvc
> > >        >      console=hvc0 console=tty0 quiet vga=785 splash
> > >        >      Loading /boot/vmlinuz-2.6.xen.........
> > >        >      Module:/boot/initrd-2.6-xen.img
> > >        >      Loading
> > >        >
> > >
> /boot/initrd-2.6-xen.img...............................................................................................
> > >        >      Booting:MBI=0x00010120, entry=0x00100000
> > >        >
> > >
> ***************************************************************************************/
> > >        >
> > >        >      Versions used in Non-working case
> > >        >
> > >        >      xen - 3.4.3/4.0.0
> > >        >      kernel - xen/next
> > >        >      initrd - default one which came with xcp0.1.1
> download.(Ps
> > >        note, in xcp
> > >        >      ddk cannot build initrd image)
> > >        >
> > >        >      in Working case
> > >        >
> > >        >      xen - 3.4.2
> > >        >      kernel - xcp 0.1.1
> > >        >      initrd - one that came with xcp 0.1.1
> > >        >
> > >        >      Checked in my .config and changed CONFIG_PHYSICAL_START
> to
> > >        0x00100000
> > >        >      and CONFIG_PHYSICAL_ALIGN=0x100000, didn't help.
> > >        >
> > >        >      Inputs appreciated.
> > >        >
> > >        >      Thanks
> > >        >
> > >        > References
> > >        >
> > >        >    Visible links
> > >        >    1. [7]http://ritu.kaur.us/
> > >        >    2. [8]http://gmail.com/
> > >
> > >        > _______________________________________________
> > >        > Xen-devel mailing list
> > >        > [9]Xen-devel@lists.xensource.com
> > >        > [10]http://lists.xensource.com/xen-devel
> > >
> > > References
> > >
> > >    Visible links
> > >    1. http://ritu.kaur.us/
> > >    2. http://gmail.com/
> > >    3. mailto:pasik@iki.fi
> > >    4. http://wiki.xensource.com/xenwiki/XenSerialConsole
> > >    5. http://ritu.kaur.us/
> > >    6. http://gmail.com/
> > >    7. http://ritu.kaur.us/
> > >    8. http://gmail.com/
> > >    9. mailto:Xen-devel@lists.xensource.com
> > >   10. http://lists.xensource.com/xen-devel
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
>

[-- Attachment #1.2: Type: text/html, Size: 10940 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 8282 bytes --]

Just to add, I have tried both com1 and com2 from baud rate 38400 to 115200
no luck. Inputs much appreciated.

Thanks

On Tue, Mar 30, 2010 at 5:28 PM, Ritu kaur <ritu.kaur.us@gmail.com> wrote:

> Hi Pasi,
>
> Serial console just doesn't seem to work. In extlinux.conf file I have
>
> # location mbr
> serial 0 115200
> default xe-serial
> prompt 1
> timeout 50
> ...
>
> label xe-serial
>   # XenCloudPlatform (Serial)
>   kernel mboot.c32
>   append /boot/xen.3.4.3.gz com1=115200,8n1 console=com1,vga dom0_mem=752M
> lowmem_emergency_pool=1M crashkernel=64M@32M --- /boot/vmlinuz-2.6.32
> root=LABEL=root-mhycetek ro console=tty0 earlyprintk=xen nomodeset
> xencons=hvc console=hvc0 --- /boot/initrd-2.6.32.img
>
> From another linux m/c, I run minicom -s /dev/ttyS0, configure serial port
> to match above config. minicom always reports serial port as offline.
> Googled and tried another option "minicom -c on /dev/ttyS0" still no luck. I
> have made sure from BIOS on both m/c's serial com ports are enabled. Not
> quite sure what is wrong here. Does extlinux.conf entry looks fine?
>
> Thanks
>
>
> On Sun, Mar 28, 2010 at 4:55 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote:
>
>> On Sun, Mar 28, 2010 at 02:34:39PM +0300, Pasi Kärkkäinen wrote:
>> > On Sat, Mar 27, 2010 at 08:21:49PM -0700, Ritu kaur wrote:
>> > >    I tried another thing. After compilation,  I did "make
>> modules_install" in
>> > >    xcp ddk in order to use following command
>> > >
>> > >    mkinitrd -f ./initrd-2.6.32.img 2.6.32
>> > >
>> > >    I get following errors...
>> > >
>> > >    modinfo: could not find module ide-disk
>> > >    No module ide-disk found for kernel 2.6.32, aborting
>> > >
>> >
>> > mkinitrd reads /etc/modprobe.conf to figure out what modules should be
>> included into the initrd image.
>> >
>>
>> also I'm not sure if ide-disk is a required module for 2.6.32?
>>
>> -- Pasi
>>
>> > >    My boot disk is ide and looking into .config didn't give me any
>> ideas as
>> > >    to what has to be enabled.
>> > >
>> >
>> > If you need some other module then fix it in /etc/modprobe.conf
>> > You need to figure out what's the correct driver for your root/boot
>> disk.
>> >
>> > -- Pasi
>> >
>> > >    Thanks
>> > >
>> > >    On Sat, Mar 27, 2010 at 6:32 PM, Ritu kaur <[1]ritu.kaur.us@[2]
>> gmail.com>
>> > >    wrote:
>> > >
>> > >      Thanks Pasi. I had used following command to regenerate initrd
>> image in
>> > >      xcp ddk
>> > >
>> > >      mkinitrd -f ./initrd-2.6.32.img
>>  2.6.27.42-0.1.1.xs0.1.1.737.1065xen
>> > >
>> > >      it doesn't work either. While booting screen goes blank
>> immediately
>> > >      after I see
>> > >      ...
>> > >       Booting:MBI=0x00010120, entry=0x00100000
>> > >
>> > >      and next thing I see is BIOS setup, so not sure connecting serial
>> cable
>> > >      will reveal anything more. Inputs appreciated.
>> > >
>> > >      Thanks
>> > >
>> > >      On Sat, Mar 27, 2010 at 11:43 AM, Pasi Kärkkäinen <[3]
>> pasik@iki.fi>
>> > >      wrote:
>> > >
>> > >        On Sat, Mar 27, 2010 at 11:28:12AM -0700, Ritu kaur wrote:
>> > >        >    Any inputs on this? I compiled xen/next kernel in Debian
>> Lenny
>> > >        and booted
>> > >        >    successfully as a domU(I am using same .config file which
>> I used
>> > >        to build
>> > >        >    under xcp-ddk). Looks to me xen/next doesn't work with
>> xcp0.1.1.
>> > >        >
>> > >
>> > >        You need to re-generate the dom0 kernel initrd to match your
>> kernel.
>> > >        You cannot use the default xcp initrd image.
>> > >
>> > >        Please provide the full serial console boot log so we can
>> troubleshoot
>> > >        it:
>> > >        [4]http://wiki.xensource.com/xenwiki/XenSerialConsole
>> > >
>> > >        -- Pasi
>> > >
>> > >        >    Thanks
>> > >        >
>> > >        >    On Fri, Mar 26, 2010 at 12:11 PM, Ritu kaur
>> > >        <[1][5]ritu.kaur.us@[2][6]gmail.com>
>> > >        >    wrote:
>> > >        >
>> > >        >      Hi Pasi,
>> > >        >
>> > >        >      Messages seen with not-working case
>> > >        >
>> > >        >
>> > >
>> /***********************************************************************************
>> > >        >      kernel:/boot/xen.3.4.3.gz dom0-mem=752M
>> > >        lowmem-emergency-pool=1M
>> > >        >      crashkernel=64M@32M console=comX vga=mode-0x0311
>> > >        >      loading /boot/xen.3.4.3.gz..........
>> > >        >      Module:/boot/vmlinuz-2.6.32 root=LABEL=root-mhycetek ro
>> > >        Xencons=hvc
>> > >        >      console=hvc0 console=tty0 quiet vga=785 splash
>> > >        >      Loading /boot/vmlinuz-2.6.32.........
>> > >        >      Module:/boot/initrd-2.6-xen.img
>> > >        >      Loading
>> > >        >
>> > >
>> /boot/initrd-2.6-xen.img...............................................................................................
>> > >        >      Booting:MBI=0x00010120, entry=0x00100000
>> > >        >
>> > >
>> ***************************************************************************************/
>> > >        >
>> > >        >      Screen is blank after these messages and system returns
>> to BIOS
>> > >        setup.
>> > >        >
>> > >        >      Messages seen with working case
>> > >        >
>> > >
>> /***********************************************************************************
>> > >        >      kernel:/boot/xen.gz dom0-mem=752M
>> lowmem-emergency-pool=1M
>> > >        >      crashkernel=64M@32M comsole=comX vga=mode-0x0311
>> > >        >      loading /boot/xen.gz..........
>> > >        >      Module:/boot/vmlinuz-2.6.xen root=LABEL=root-mhycetek ro
>> > >        Xencons=hvc
>> > >        >      console=hvc0 console=tty0 quiet vga=785 splash
>> > >        >      Loading /boot/vmlinuz-2.6.xen.........
>> > >        >      Module:/boot/initrd-2.6-xen.img
>> > >        >      Loading
>> > >        >
>> > >
>> /boot/initrd-2.6-xen.img...............................................................................................
>> > >        >      Booting:MBI=0x00010120, entry=0x00100000
>> > >        >
>> > >
>> ***************************************************************************************/
>> > >        >
>> > >        >      Versions used in Non-working case
>> > >        >
>> > >        >      xen - 3.4.3/4.0.0
>> > >        >      kernel - xen/next
>> > >        >      initrd - default one which came with xcp0.1.1
>> download.(Ps
>> > >        note, in xcp
>> > >        >      ddk cannot build initrd image)
>> > >        >
>> > >        >      in Working case
>> > >        >
>> > >        >      xen - 3.4.2
>> > >        >      kernel - xcp 0.1.1
>> > >        >      initrd - one that came with xcp 0.1.1
>> > >        >
>> > >        >      Checked in my .config and changed CONFIG_PHYSICAL_START
>> to
>> > >        0x00100000
>> > >        >      and CONFIG_PHYSICAL_ALIGN=0x100000, didn't help.
>> > >        >
>> > >        >      Inputs appreciated.
>> > >        >
>> > >        >      Thanks
>> > >        >
>> > >        > References
>> > >        >
>> > >        >    Visible links
>> > >        >    1. [7]http://ritu.kaur.us/
>> > >        >    2. [8]http://gmail.com/
>> > >
>> > >        > _______________________________________________
>> > >        > Xen-devel mailing list
>> > >        > [9]Xen-devel@lists.xensource.com
>> > >        > [10]http://lists.xensource.com/xen-devel
>> > >
>> > > References
>> > >
>> > >    Visible links
>> > >    1. http://ritu.kaur.us/
>> > >    2. http://gmail.com/
>> > >    3. mailto:pasik@iki.fi
>> > >    4. http://wiki.xensource.com/xenwiki/XenSerialConsole
>> > >    5. http://ritu.kaur.us/
>> > >    6. http://gmail.com/
>> > >    7. http://ritu.kaur.us/
>> > >    8. http://gmail.com/
>> > >    9. mailto:Xen-devel@lists.xensource.com
>> > >   10. http://lists.xensource.com/xen-devel
>> >
>> > _______________________________________________
>> > Xen-devel mailing list
>> > Xen-devel@lists.xensource.com
>> > http://lists.xensource.com/xen-devel
>>
>
>

[-- Attachment #1.2: Type: text/html, Size: 11550 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Pasi Kärkkäinen]

On Tue, Mar 30, 2010 at 06:07:44PM -0700, Ritu kaur wrote:
>    Just to add, I have tried both com1 and com2 from baud rate 38400 to
>    115200 no luck. Inputs much appreciated.
>

Do you have an onboard serial port, or is at some kind of SOL?

-- Pasi
 
>    Thanks
> 
>    On Tue, Mar 30, 2010 at 5:28 PM, Ritu kaur <[1]ritu.kaur.us@[2]gmail.com>
>    wrote:
> 
>      Hi Pasi,
> 
>      Serial console just doesn't seem to work. In extlinux.conf file I have
> 
>      # location mbr
>      serial 0 115200
>      default xe-serial
>      prompt 1
>      timeout 50
>      ...
> 
>      label xe-serial
>        # XenCloudPlatform (Serial)
>        kernel mboot.c32
>        append /boot/xen.3.4.3.gz com1=115200,8n1 console=com1,vga
>      dom0_mem=752M lowmem_emergency_pool=1M crashkernel=64M@32M ---
>      /boot/vmlinuz-2.6.32 root=LABEL=root-mhycetek ro console=tty0
>      earlyprintk=xen nomodeset xencons=hvc console=hvc0 ---
>      /boot/initrd-2.6.32.img
> 
>      From another linux m/c, I run minicom -s /dev/ttyS0, configure serial
>      port to match above config. minicom always reports serial port as
>      offline. Googled and tried another option "minicom -c on /dev/ttyS0"
>      still no luck. I have made sure from BIOS on both m/c's serial com ports
>      are enabled. Not quite sure what is wrong here. Does extlinux.conf entry
>      looks fine?
> 
>      Thanks
> 
>      On Sun, Mar 28, 2010 at 4:55 AM, Pasi Kärkkäinen <[3]pasik@iki.fi>
>      wrote:
> 
>        On Sun, Mar 28, 2010 at 02:34:39PM +0300, Pasi Kärkkäinen wrote:
>        > On Sat, Mar 27, 2010 at 08:21:49PM -0700, Ritu kaur wrote:
>        > >    I tried another thing. After compilation,  I did "make
>        modules_install" in
>        > >    xcp ddk in order to use following command
>        > >
>        > >    mkinitrd -f ./initrd-2.6.32.img 2.6.32
>        > >
>        > >    I get following errors...
>        > >
>        > >    modinfo: could not find module ide-disk
>        > >    No module ide-disk found for kernel 2.6.32, aborting
>        > >
>        >
>        > mkinitrd reads /etc/modprobe.conf to figure out what modules should
>        be included into the initrd image.
>        >
> 
>        also I'm not sure if ide-disk is a required module for 2.6.32?
> 
>        -- Pasi
>        > >    My boot disk is ide and looking into .config didn't give me any
>        ideas as
>        > >    to what has to be enabled.
>        > >
>        >
>        > If you need some other module then fix it in /etc/modprobe.conf
>        > You need to figure out what's the correct driver for your root/boot
>        disk.
>        >
>        > -- Pasi
>        >
>        > >    Thanks
>        > >
>        > >    On Sat, Mar 27, 2010 at 6:32 PM, Ritu kaur
>        <[1][4]ritu.kaur.us@[2][5]gmail.com>
>        > >    wrote:
>        > >
>        > >      Thanks Pasi. I had used following command to regenerate
>        initrd image in
>        > >      xcp ddk
>        > >
>        > >      mkinitrd -f ./initrd-2.6.32.img
>         2.6.27.42-0.1.1.xs0.1.1.737.1065xen
>        > >
>        > >      it doesn't work either. While booting screen goes blank
>        immediately
>        > >      after I see
>        > >      ...
>        > >       Booting:MBI=0x00010120, entry=0x00100000
>        > >
>        > >      and next thing I see is BIOS setup, so not sure connecting
>        serial cable
>        > >      will reveal anything more. Inputs appreciated.
>        > >
>        > >      Thanks
>        > >
>        > >      On Sat, Mar 27, 2010 at 11:43 AM, Pasi Kärkkäinen
>        <[3][6]pasik@iki.fi>
>        > >      wrote:
>        > >
>        > >        On Sat, Mar 27, 2010 at 11:28:12AM -0700, Ritu kaur wrote:
>        > >        >    Any inputs on this? I compiled xen/next kernel in
>        Debian Lenny
>        > >        and booted
>        > >        >    successfully as a domU(I am using same .config file
>        which I used
>        > >        to build
>        > >        >    under xcp-ddk). Looks to me xen/next doesn't work with
>        xcp0.1.1.
>        > >        >
>        > >
>        > >        You need to re-generate the dom0 kernel initrd to match
>        your kernel.
>        > >        You cannot use the default xcp initrd image.
>        > >
>        > >        Please provide the full serial console boot log so we can
>        troubleshoot
>        > >        it:
>        > >        [4][7]http://wiki.xensource.com/xenwiki/XenSerialConsole
>        > >
>        > >        -- Pasi
>        > >
>        > >        >    Thanks
>        > >        >
>        > >        >    On Fri, Mar 26, 2010 at 12:11 PM, Ritu kaur
>        > >        <[1][5][8]ritu.kaur.us@[2][6][9]gmail.com>
>        > >        >    wrote:
>        > >        >
>        > >        >      Hi Pasi,
>        > >        >
>        > >        >      Messages seen with not-working case
>        > >        >
>        > >        >
>        > >
>        /***********************************************************************************
>        > >        >      kernel:/boot/xen.3.4.3.gz dom0-mem=752M
>        > >        lowmem-emergency-pool=1M
>        > >        >      crashkernel=64M@32M console=comX vga=mode-0x0311
>        > >        >      loading /boot/xen.3.4.3.gz..........
>        > >        >      Module:/boot/vmlinuz-2.6.32 root=LABEL=root-mhycetek
>        ro
>        > >        Xencons=hvc
>        > >        >      console=hvc0 console=tty0 quiet vga=785 splash
>        > >        >      Loading /boot/vmlinuz-2.6.32.........
>        > >        >      Module:/boot/initrd-2.6-xen.img
>        > >        >      Loading
>        > >        >
>        > >
>        /boot/initrd-2.6-xen.img...............................................................................................
>        > >        >      Booting:MBI=0x00010120, entry=0x00100000
>        > >        >
>        > >
>        ***************************************************************************************/
>        > >        >
>        > >        >      Screen is blank after these messages and system
>        returns to BIOS
>        > >        setup.
>        > >        >
>        > >        >      Messages seen with working case
>        > >        >
>        > >
>        /***********************************************************************************
>        > >        >      kernel:/boot/xen.gz dom0-mem=752M
>        lowmem-emergency-pool=1M
>        > >        >      crashkernel=64M@32M comsole=comX vga=mode-0x0311
>        > >        >      loading /boot/xen.gz..........
>        > >        >      Module:/boot/vmlinuz-2.6.xen
>        root=LABEL=root-mhycetek ro
>        > >        Xencons=hvc
>        > >        >      console=hvc0 console=tty0 quiet vga=785 splash
>        > >        >      Loading /boot/vmlinuz-2.6.xen.........
>        > >        >      Module:/boot/initrd-2.6-xen.img
>        > >        >      Loading
>        > >        >
>        > >
>        /boot/initrd-2.6-xen.img...............................................................................................
>        > >        >      Booting:MBI=0x00010120, entry=0x00100000
>        > >        >
>        > >
>        ***************************************************************************************/
>        > >        >
>        > >        >      Versions used in Non-working case
>        > >        >
>        > >        >      xen - 3.4.3/4.0.0
>        > >        >      kernel - xen/next
>        > >        >      initrd - default one which came with xcp0.1.1
>        download.(Ps
>        > >        note, in xcp
>        > >        >      ddk cannot build initrd image)
>        > >        >
>        > >        >      in Working case
>        > >        >
>        > >        >      xen - 3.4.2
>        > >        >      kernel - xcp 0.1.1
>        > >        >      initrd - one that came with xcp 0.1.1
>        > >        >
>        > >        >      Checked in my .config and changed
>        CONFIG_PHYSICAL_START to
>        > >        0x00100000
>        > >        >      and CONFIG_PHYSICAL_ALIGN=0x100000, didn't help.
>        > >        >
>        > >        >      Inputs appreciated.
>        > >        >
>        > >        >      Thanks
>        > >        >
>        > >        > References
>        > >        >
>        > >        >    Visible links
>        > >        >    1. [7][10]http://ritu.kaur.us/
>        > >        >    2. [8][11]http://gmail.com/
>        > >
>        > >        > _______________________________________________
>        > >        > Xen-devel mailing list
>        > >        > [9][12]Xen-devel@lists.xensource.com
>        > >        > [10][13]http://lists.xensource.com/xen-devel
>        > >
>        > > References
>        > >
>        > >    Visible links
>        > >    1. [14]http://ritu.kaur.us/
>        > >    2. [15]http://gmail.com/
>        > >    3. mailto:[16]pasik@iki.fi
>        > >    4. [17]http://wiki.xensource.com/xenwiki/XenSerialConsole
>        > >    5. [18]http://ritu.kaur.us/
>        > >    6. [19]http://gmail.com/
>        > >    7. [20]http://ritu.kaur.us/
>        > >    8. [21]http://gmail.com/
>        > >    9. mailto:[22]Xen-devel@lists.xensource.com
>        > >   10. [23]http://lists.xensource.com/xen-devel
>        >
>        > _______________________________________________
>        > Xen-devel mailing list
>        > [24]Xen-devel@lists.xensource.com
>        > [25]http://lists.xensource.com/xen-devel
> 
> References
> 
>    Visible links
>    1. http://ritu.kaur.us/
>    2. http://gmail.com/
>    3. mailto:pasik@iki.fi
>    4. http://ritu.kaur.us/
>    5. http://gmail.com/
>    6. mailto:pasik@iki.fi
>    7. http://wiki.xensource.com/xenwiki/XenSerialConsole
>    8. http://ritu.kaur.us/
>    9. http://gmail.com/
>   10. http://ritu.kaur.us/
>   11. http://gmail.com/
>   12. mailto:Xen-devel@lists.xensource.com
>   13. http://lists.xensource.com/xen-devel
>   14. http://ritu.kaur.us/
>   15. http://gmail.com/
>   16. mailto:pasik@iki.fi
>   17. http://wiki.xensource.com/xenwiki/XenSerialConsole
>   18. http://ritu.kaur.us/
>   19. http://gmail.com/
>   20. http://ritu.kaur.us/
>   21. http://gmail.com/
>   22. mailto:Xen-devel@lists.xensource.com
>   23. http://lists.xensource.com/xen-devel
>   24. mailto:Xen-devel@lists.xensource.com
>   25. http://lists.xensource.com/xen-devel

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 11518 bytes --]

It's a onboard serial port. From dmesg there are ttyS0 and ttyS1 ports are
shown and I have tried both of them.

Thanks

On Tue, Mar 30, 2010 at 11:30 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote:

> On Tue, Mar 30, 2010 at 06:07:44PM -0700, Ritu kaur wrote:
> >    Just to add, I have tried both com1 and com2 from baud rate 38400 to
> >    115200 no luck. Inputs much appreciated.
> >
>
> Do you have an onboard serial port, or is at some kind of SOL?
>
> -- Pasi
>
> >    Thanks
> >
> >    On Tue, Mar 30, 2010 at 5:28 PM, Ritu kaur <[1]ritu.kaur.us@[2]
> gmail.com>
> >    wrote:
> >
> >      Hi Pasi,
> >
> >      Serial console just doesn't seem to work. In extlinux.conf file I
> have
> >
> >      # location mbr
> >      serial 0 115200
> >      default xe-serial
> >      prompt 1
> >      timeout 50
> >      ...
> >
> >      label xe-serial
> >        # XenCloudPlatform (Serial)
> >        kernel mboot.c32
> >        append /boot/xen.3.4.3.gz com1=115200,8n1 console=com1,vga
> >      dom0_mem=752M lowmem_emergency_pool=1M crashkernel=64M@32M ---
> >      /boot/vmlinuz-2.6.32 root=LABEL=root-mhycetek ro console=tty0
> >      earlyprintk=xen nomodeset xencons=hvc console=hvc0 ---
> >      /boot/initrd-2.6.32.img
> >
> >      From another linux m/c, I run minicom -s /dev/ttyS0, configure
> serial
> >      port to match above config. minicom always reports serial port as
> >      offline. Googled and tried another option "minicom -c on /dev/ttyS0"
> >      still no luck. I have made sure from BIOS on both m/c's serial com
> ports
> >      are enabled. Not quite sure what is wrong here. Does extlinux.conf
> entry
> >      looks fine?
> >
> >      Thanks
> >
> >      On Sun, Mar 28, 2010 at 4:55 AM, Pasi Kärkkäinen <[3]pasik@iki.fi>
> >      wrote:
> >
> >        On Sun, Mar 28, 2010 at 02:34:39PM +0300, Pasi Kärkkäinen wrote:
> >        > On Sat, Mar 27, 2010 at 08:21:49PM -0700, Ritu kaur wrote:
> >        > >    I tried another thing. After compilation,  I did "make
> >        modules_install" in
> >        > >    xcp ddk in order to use following command
> >        > >
> >        > >    mkinitrd -f ./initrd-2.6.32.img 2.6.32
> >        > >
> >        > >    I get following errors...
> >        > >
> >        > >    modinfo: could not find module ide-disk
> >        > >    No module ide-disk found for kernel 2.6.32, aborting
> >        > >
> >        >
> >        > mkinitrd reads /etc/modprobe.conf to figure out what modules
> should
> >        be included into the initrd image.
> >        >
> >
> >        also I'm not sure if ide-disk is a required module for 2.6.32?
> >
> >        -- Pasi
> >        > >    My boot disk is ide and looking into .config didn't give me
> any
> >        ideas as
> >        > >    to what has to be enabled.
> >        > >
> >        >
> >        > If you need some other module then fix it in /etc/modprobe.conf
> >        > You need to figure out what's the correct driver for your
> root/boot
> >        disk.
> >        >
> >        > -- Pasi
> >        >
> >        > >    Thanks
> >        > >
> >        > >    On Sat, Mar 27, 2010 at 6:32 PM, Ritu kaur
> >        <[1][4]ritu.kaur.us@[2][5]gmail.com>
> >        > >    wrote:
> >        > >
> >        > >      Thanks Pasi. I had used following command to regenerate
> >        initrd image in
> >        > >      xcp ddk
> >        > >
> >        > >      mkinitrd -f ./initrd-2.6.32.img
> >         2.6.27.42-0.1.1.xs0.1.1.737.1065xen
> >        > >
> >        > >      it doesn't work either. While booting screen goes blank
> >        immediately
> >        > >      after I see
> >        > >      ...
> >        > >       Booting:MBI=0x00010120, entry=0x00100000
> >        > >
> >        > >      and next thing I see is BIOS setup, so not sure
> connecting
> >        serial cable
> >        > >      will reveal anything more. Inputs appreciated.
> >        > >
> >        > >      Thanks
> >        > >
> >        > >      On Sat, Mar 27, 2010 at 11:43 AM, Pasi Kärkkäinen
> >        <[3][6]pasik@iki.fi>
> >        > >      wrote:
> >        > >
> >        > >        On Sat, Mar 27, 2010 at 11:28:12AM -0700, Ritu kaur
> wrote:
> >        > >        >    Any inputs on this? I compiled xen/next kernel in
> >        Debian Lenny
> >        > >        and booted
> >        > >        >    successfully as a domU(I am using same .config
> file
> >        which I used
> >        > >        to build
> >        > >        >    under xcp-ddk). Looks to me xen/next doesn't work
> with
> >        xcp0.1.1.
> >        > >        >
> >        > >
> >        > >        You need to re-generate the dom0 kernel initrd to match
> >        your kernel.
> >        > >        You cannot use the default xcp initrd image.
> >        > >
> >        > >        Please provide the full serial console boot log so we
> can
> >        troubleshoot
> >        > >        it:
> >        > >        [4][7]
> http://wiki.xensource.com/xenwiki/XenSerialConsole
> >        > >
> >        > >        -- Pasi
> >        > >
> >        > >        >    Thanks
> >        > >        >
> >        > >        >    On Fri, Mar 26, 2010 at 12:11 PM, Ritu kaur
> >        > >        <[1][5][8]ritu.kaur.us@[2][6][9]gmail.com>
> >        > >        >    wrote:
> >        > >        >
> >        > >        >      Hi Pasi,
> >        > >        >
> >        > >        >      Messages seen with not-working case
> >        > >        >
> >        > >        >
> >        > >
> >
>  /***********************************************************************************
> >        > >        >      kernel:/boot/xen.3.4.3.gz dom0-mem=752M
> >        > >        lowmem-emergency-pool=1M
> >        > >        >      crashkernel=64M@32M console=comX
> vga=mode-0x0311
> >        > >        >      loading /boot/xen.3.4.3.gz..........
> >        > >        >      Module:/boot/vmlinuz-2.6.32
> root=LABEL=root-mhycetek
> >        ro
> >        > >        Xencons=hvc
> >        > >        >      console=hvc0 console=tty0 quiet vga=785 splash
> >        > >        >      Loading /boot/vmlinuz-2.6.32.........
> >        > >        >      Module:/boot/initrd-2.6-xen.img
> >        > >        >      Loading
> >        > >        >
> >        > >
> >
>  /boot/initrd-2.6-xen.img...............................................................................................
> >        > >        >      Booting:MBI=0x00010120, entry=0x00100000
> >        > >        >
> >        > >
> >
>  ***************************************************************************************/
> >        > >        >
> >        > >        >      Screen is blank after these messages and system
> >        returns to BIOS
> >        > >        setup.
> >        > >        >
> >        > >        >      Messages seen with working case
> >        > >        >
> >        > >
> >
>  /***********************************************************************************
> >        > >        >      kernel:/boot/xen.gz dom0-mem=752M
> >        lowmem-emergency-pool=1M
> >        > >        >      crashkernel=64M@32M comsole=comX
> vga=mode-0x0311
> >        > >        >      loading /boot/xen.gz..........
> >        > >        >      Module:/boot/vmlinuz-2.6.xen
> >        root=LABEL=root-mhycetek ro
> >        > >        Xencons=hvc
> >        > >        >      console=hvc0 console=tty0 quiet vga=785 splash
> >        > >        >      Loading /boot/vmlinuz-2.6.xen.........
> >        > >        >      Module:/boot/initrd-2.6-xen.img
> >        > >        >      Loading
> >        > >        >
> >        > >
> >
>  /boot/initrd-2.6-xen.img...............................................................................................
> >        > >        >      Booting:MBI=0x00010120, entry=0x00100000
> >        > >        >
> >        > >
> >
>  ***************************************************************************************/
> >        > >        >
> >        > >        >      Versions used in Non-working case
> >        > >        >
> >        > >        >      xen - 3.4.3/4.0.0
> >        > >        >      kernel - xen/next
> >        > >        >      initrd - default one which came with xcp0.1.1
> >        download.(Ps
> >        > >        note, in xcp
> >        > >        >      ddk cannot build initrd image)
> >        > >        >
> >        > >        >      in Working case
> >        > >        >
> >        > >        >      xen - 3.4.2
> >        > >        >      kernel - xcp 0.1.1
> >        > >        >      initrd - one that came with xcp 0.1.1
> >        > >        >
> >        > >        >      Checked in my .config and changed
> >        CONFIG_PHYSICAL_START to
> >        > >        0x00100000
> >        > >        >      and CONFIG_PHYSICAL_ALIGN=0x100000, didn't help.
> >        > >        >
> >        > >        >      Inputs appreciated.
> >        > >        >
> >        > >        >      Thanks
> >        > >        >
> >        > >        > References
> >        > >        >
> >        > >        >    Visible links
> >        > >        >    1. [7][10]http://ritu.kaur.us/
> >        > >        >    2. [8][11]http://gmail.com/
> >        > >
> >        > >        > _______________________________________________
> >        > >        > Xen-devel mailing list
> >        > >        > [9][12]Xen-devel@lists.xensource.com
> >        > >        > [10][13]http://lists.xensource.com/xen-devel
> >        > >
> >        > > References
> >        > >
> >        > >    Visible links
> >        > >    1. [14]http://ritu.kaur.us/
> >        > >    2. [15]http://gmail.com/
> >        > >    3. mailto:[16]pasik@iki.fi
> >        > >    4. [17]http://wiki.xensource.com/xenwiki/XenSerialConsole
> >        > >    5. [18]http://ritu.kaur.us/
> >        > >    6. [19]http://gmail.com/
> >        > >    7. [20]http://ritu.kaur.us/
> >        > >    8. [21]http://gmail.com/
> >        > >    9. mailto:[22]Xen-devel@lists.xensource.com
> >        > >   10. [23]http://lists.xensource.com/xen-devel
> >        >
> >        > _______________________________________________
> >        > Xen-devel mailing list
> >        > [24]Xen-devel@lists.xensource.com
> >        > [25]http://lists.xensource.com/xen-devel
> >
> > References
> >
> >    Visible links
> >    1. http://ritu.kaur.us/
> >    2. http://gmail.com/
> >    3. mailto:pasik@iki.fi
> >    4. http://ritu.kaur.us/
> >    5. http://gmail.com/
> >    6. mailto:pasik@iki.fi
> >    7. http://wiki.xensource.com/xenwiki/XenSerialConsole
> >    8. http://ritu.kaur.us/
> >    9. http://gmail.com/
> >   10. http://ritu.kaur.us/
> >   11. http://gmail.com/
> >   12. mailto:Xen-devel@lists.xensource.com
> >   13. http://lists.xensource.com/xen-devel
> >   14. http://ritu.kaur.us/
> >   15. http://gmail.com/
> >   16. mailto:pasik@iki.fi
> >   17. http://wiki.xensource.com/xenwiki/XenSerialConsole
> >   18. http://ritu.kaur.us/
> >   19. http://gmail.com/
> >   20. http://ritu.kaur.us/
> >   21. http://gmail.com/
> >   22. mailto:Xen-devel@lists.xensource.com
> >   23. http://lists.xensource.com/xen-devel
> >   24. mailto:Xen-devel@lists.xensource.com
> >   25. http://lists.xensource.com/xen-devel
>

[-- Attachment #1.2: Type: text/html, Size: 17245 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Konrad Rzeszutek Wilk]

On Wed, Mar 31, 2010 at 06:15:59AM -0700, Ritu kaur wrote:
> It's a onboard serial port. From dmesg there are ttyS0 and ttyS1 ports are
> shown and I have tried both of them.

And the cable you have, it is a null modem serial cable? Have you ever
had serial cable working (say with baremetal Linux?)

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 486 bytes --]

Konrad, yes it is a null-modem cable. Cable was bought for this testing.

Thanks

On Wed, Mar 31, 2010 at 6:42 AM, Konrad Rzeszutek Wilk <
konrad.wilk@oracle.com> wrote:

> On Wed, Mar 31, 2010 at 06:15:59AM -0700, Ritu kaur wrote:
> > It's a onboard serial port. From dmesg there are ttyS0 and ttyS1 ports
> are
> > shown and I have tried both of them.
>
> And the cable you have, it is a null modem serial cable? Have you ever
> had serial cable working (say with baremetal Linux?)
>

[-- Attachment #1.2: Type: text/html, Size: 801 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Pasi Kärkkäinen]

On Wed, Mar 31, 2010 at 06:55:54AM -0700, Ritu kaur wrote:
>    Konrad, yes it is a null-modem cable. Cable was bought for this testing.
> 

First get it working on baremetal Linux (non-Xen), then continue with Xen.

-- Pasi

>    Thanks
> 
>    On Wed, Mar 31, 2010 at 6:42 AM, Konrad Rzeszutek Wilk
>    <[1]konrad.wilk@oracle.com> wrote:
> 
>      On Wed, Mar 31, 2010 at 06:15:59AM -0700, Ritu kaur wrote:
>      > It's a onboard serial port. From dmesg there are ttyS0 and ttyS1 ports
>      are
>      > shown and I have tried both of them.
> 
>      And the cable you have, it is a null modem serial cable? Have you ever
>      had serial cable working (say with baremetal Linux?)
> 
> References
> 
>    Visible links
>    1. mailto:konrad.wilk@oracle.com

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 1036 bytes --]

Attached xen debug logs. Just to update this is with xen/next and xcp0.1.1
as dom0. Inputs appreciated.

Thanks


On Wed, Mar 31, 2010 at 7:39 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote:

> On Wed, Mar 31, 2010 at 06:55:54AM -0700, Ritu kaur wrote:
> >    Konrad, yes it is a null-modem cable. Cable was bought for this
> testing.
> >
>
> First get it working on baremetal Linux (non-Xen), then continue with Xen.
>
> -- Pasi
>
> >    Thanks
> >
> >    On Wed, Mar 31, 2010 at 6:42 AM, Konrad Rzeszutek Wilk
> >    <[1]konrad.wilk@oracle.com> wrote:
> >
> >      On Wed, Mar 31, 2010 at 06:15:59AM -0700, Ritu kaur wrote:
> >      > It's a onboard serial port. From dmesg there are ttyS0 and ttyS1
> ports
> >      are
> >      > shown and I have tried both of them.
> >
> >      And the cable you have, it is a null modem serial cable? Have you
> ever
> >      had serial cable working (say with baremetal Linux?)
> >
> > References
> >
> >    Visible links
> >    1. mailto:konrad.wilk@oracle.com
>

[-- Attachment #1.2: Type: text/html, Size: 1601 bytes --]

[-- Attachment #2: xen-debugs.xcp --]
[-- Type: application/octet-stream, Size: 11659 bytes --]

 \ \/ /___ _ __   |___ /| || |  |___ /    _ __ ___| || |     _ __  _ __ ___ 
  \  // _ \ '_ \    |_ \| || |_   |_ \ __| '__/ __| || |_ __| '_ \| '__/ _ \
  /  \  __/ | | |  ___) |__   _| ___) |__| | | (__|__   _|__| |_) | | |  __/
 /_/\_\___|_| |_| |____(_) |_|(_)____/   |_|  \___|  |_|    | .__/|_|  \___|
                                                            |_|             
(XEN) Xen version 3.4.3-rc4-pre (root@) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-46)) Sat Mar 20 21:13:47 EDT 2010
(XEN) Latest ChangeSet: Tue Mar 09 18:15:52 2010 +0000 19924:6e72f8c3c017
(XEN) Command line: com1=115200,8n1 console=com1,vga dom0_mem=752M lowmem_emergency_pool=1M crashkernel=64M@32M 
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds
(XEN)  EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information:
(XEN)  Found 1 MBR signatures
(XEN)  Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009cc00 (usable)
(XEN)  000000000009cc00 - 00000000000a0000 (reserved)
(XEN)  00000000000e4000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 000000007f680000 (usable)
(XEN)  000000007f680000 - 000000007f68b000 (ACPI data)
(XEN)  000000007f68b000 - 000000007f700000 (ACPI NVS)
(XEN)  000000007f700000 - 0000000080000000 (reserved)
(XEN)  00000000e0000000 - 00000000e4000000 (reserved)
(XEN)  00000000fec00000 - 00000000fec10000 (reserved)
(XEN)  00000000fee00000 - 00000000fee01000 (reserved)
(XEN)  00000000ff000000 - 0000000100000000 (reserved)
(XEN) Kdump: 64MB (65536kB) at 0x2000000
(XEN) System RAM: 2038MB (2087024kB)
(XEN) ACPI: RSDP 000F6EE0, 0014 (r0 INTELB)
(XEN) ACPI: RSDT 7F683D75, 003C (r1 PTLTD    RSDT    6040000  LTP        0)
(XEN) ACPI: FACP 7F68AE7E, 0084 (r1 SUPRMC           6040000 PTL         3)
(XEN) ACPI: DSDT 7F6855E3, 589B (r1  INTEL BR_WATER  6040000 MSFT  3000001)
(XEN) ACPI: FACS 7F68BFC0, 0040
(XEN) ACPI: TCPA 7F68AF02, 0032 (r1 SMC              6040000 PTL         0)
(XEN) ACPI: MCFG 7F68AF34, 003C (r1 INTELB R_WATERP  6040000  LTP        0)
(XEN) ACPI: APIC 7F68AF70, 0068 (r1 INTELB R_WATERP  6040000  LTP        0)
(XEN) ACPI: BOOT 7F68AFD8, 0028 (r1 INTELB R_WATERP  6040000  LTP        1)
(XEN) ACPI: SSDT 7F683DB1, 13EC (r1 INTELB R_WATERW     3000 INTL 20061109)
(XEN) Xen heap: 9MB (9800kB)
(XEN) Domain heap initialised
(XEN) Processor #0 6:15 APIC version 20
(XEN) Processor #1 6:15 APIC version 20
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 1862.041 MHz processor.
(XEN) VMX: Supported advanced features:
(XEN)  - MSR direct-access bitmap
(XEN) HVM: VMX enabled
(XEN) CPU0: Intel(R) Core(TM)2 CPU          6320  @ 1.86GHz stepping 06
(XEN) Booting processor 1/1 eip 88000
(XEN) CPU1: Intel(R) Core(TM)2 CPU          6320  @ 1.86GHz stepping 06
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) checking TSC synchronization across 2 CPUs: passed.
(XEN) Platform timer is 3.579MHz ACPI PM Timer
ÿ(XEN) Brought up 2 CPUs
(XEN) I/O virtualisation disabled
(XEN) CPUIDLE: disabled due to no HPET. Force enable with 'cpuidle'.
(XEN) *** LOADING DOMAIN 0 ***
(XEN)  Xen  kernel: 32-bit, PAE, lsb
(XEN)  Dom0 kernel: 32-bit, PAE, lsb, paddr 0x400000 -> 0x9ad000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   000000003c000000->000000003e000000 (184320 pages to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: c0400000->c09ad000
(XEN)  Init. ramdisk: c09ad000->c0ee6a00
(XEN)  Phys-Mach map: c0ee7000->c0fa3000
(XEN)  Start info:    c0fa3000->c0fa347c
(XEN)  Page tables:   c0fa4000->c0fb3000
(XEN)  Boot stack:    c0fb3000->c0fb4000
(XEN)  TOTAL:         c0000000->c1400000
(XEN)  ENTRY ADDRESS: c0780000
(XEN) Dom0 has maximum 2 VCPUs
(XEN) Scrubbing Free RAM: .............done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 116kB init memory.
mapping kernel into physical memory
Xen: setup ISA identity maps
about to get started...
[    0.000000] Reserving virtual address space above 0xf5800000
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.32 (root@localhost.localdomain) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-46)) #7 SMP Sun Mar 28 12:16:38 EDT 2010
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   NSC Geode by NSC
[    0.000000]   Cyrix CyrixInstead
[    0.000000]   Centaur CentaurHauls
[    0.000000]   Transmeta GenuineTMx86
[    0.000000]   Transmeta TransmetaCPU
[    0.000000]   UMC UMC UMC UMC
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  Xen: 0000000000000000 - 000000000009cc00 (usable)
[    0.000000]  Xen: 000000000009cc00 - 0000000000100000 (reserved)
[    0.000000]  Xen: 0000000000100000 - 000000002f000000 (usable)
[    0.000000]  Xen: 000000007f680000 - 000000007f68b000 (ACPI data)
[    0.000000]  Xen: 000000007f68b000 - 000000007f700000 (ACPI NVS)
[    0.000000]  Xen: 000000007f700000 - 0000000080000000 (reserved)
[    0.000000]  Xen: 00000000e0000000 - 00000000e4000000 (reserved)
[    0.000000]  Xen: 00000000fec00000 - 00000000fec10000 (reserved)
[    0.000000]  Xen: 00000000fee00000 - 00000000fee01000 (reserved)
[    0.000000]  Xen: 00000000ff000000 - 0000000100000000 (reserved)
[    0.000000] bootconsole [xenboot0] enabled
[    0.000000] DMI present.
[    0.000000] Phoenix BIOS detected: BIOS may corrupt low RAM, working around it.
[    0.000000] last_pfn = 0x2f000 max_arch_pfn = 0x1000000
[    0.000000] init_memory_mapping: 0000000000000000-000000002d1fe000
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] RAMDISK: 009ad000 - 00ee6a00
[    0.000000] ACPI: RSDP 000f6ee0 00014 (v00 INTELB)
[    0.000000] ACPI: RSDT 7f683d75 0003C (v01 PTLTD    RSDT   06040000  LTP 00000000)
[    0.000000] ACPI: FACP 7f68ae7e 00084 (v01 SUPRMC          06040000 PTL  00000003)
[    0.000000] ACPI: DSDT 7f6855e3 0589B (v01  INTEL BR_WATER 06040000 MSFT 03000001)
[    0.000000] ACPI: FACS 7f68bfc0 00040
[    0.000000] ACPI: TCPA 7f68af02 00032 (v01 SMC             06040000 PTL  00000000)
[    0.000000] ACPI: MCFG 7f68af34 0003C (v01 INTELB R_WATERP 06040000  LTP 00000000)
[    0.000000] ACPI: APIC 7f68af70 00068 (v01 INTELB R_WATERP 06040000  LTP 00000000)
[    0.000000] ACPI: BOOT 7f68afd8 00028 (v01 INTELB R_WATERP 06040000  LTP 00000001)
[    0.000000] ACPI: SSDT 7f683db1 013EC (v01 INTELB R_WATERW 00003000 INTL 20061109)
[    0.000000] 30MB HIGHMEM available.
[    0.000000] 721MB LOWMEM available.
[    0.000000]   mapped low ram: 0 - 2d1fe000
[    0.000000]   low ram: 0 - 2d1fe000
[    0.000000]   node 0 low ram: 00000000 - 2d1fe000
[    0.000000]   node 0 bootmap 00010000 - 00015a40
[    0.000000] (10 early reservations) ==> bootmem [0000000000 - 002d1fe000]
[    0.000000]   #0 [0000000000 - 0000001000]   BIOS data page ==> [0000000000 - 0000001000]
[    0.000000]   #1 [0000fa4000 - 0000fb3000]   XEN PAGETABLES ==> [0000fa4000 - 0000fb3000]
[    0.000000]   #2 [0000001000 - 0000002000]    EX TRAMPOLINE ==> [0000001000 - 0000002000]
[    0.000000]   #3 [0000006000 - 0000007000]       TRAMPOLINE ==> [0000006000 - 0000007000]
[    0.000000]   #4 [0000400000 - 0000887fa4]    TEXT DATA BSS ==> [0000400000 - 0000887fa4]
[    0.000000]   #5 [00009ad000 - 0000ee6a00]          RAMDISK ==> [00009ad000 - 0000ee6a00]
[    0.000000]   #6 [0000ee7000 - 0000fa4000]   XEN START INFO ==> [0000ee7000 - 0000fa4000]
[    0.000000]   #7 [0000888000 - 000088813c]              BRK ==> [0000888000 - 000088813c]
[    0.000000]   #8 [0000100000 - 000025c000]          PGTABLE ==> [0000100000 - 000025c000]
[    0.000000]   #9 [0000010000 - 0000016000]          BOOTMAP ==> [0000010000 - 0000016000]
[    0.000000] found SMP MP-table at [c00f6f10] f6f10
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA      0x00000010 -> 0x00001000
[    0.000000]   Normal   0x00001000 -> 0x0002d1fe
[    0.000000]   HighMem  0x0002d1fe -> 0x0002f000
[    0.000000] Movable zone start PFN for each node
[    0.000000] early_node_map[2] active PFN ranges
[    0.000000]     0: 0x00000010 -> 0x0000009c
[    0.000000]     0: 0x00000100 -> 0x0002f000
[    0.000000] Using APIC driver default
[    0.000000] ACPI: PM-Timer IO Port: 0x1008
[    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[    0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
(XEN) mm.c:1699:d0 Bad L1 flags 100
(XEN) mm.c:720:d0 Bad L1 flags 100
(XEN) mm.c:4221:d0 ptwr_emulate: could not get_page_from_l1e()
(XEN) d0:v0: unhandled page fault (ec=0003)
(XEN) Pagetable walk from c07f8fd0:
(XEN)  L3[0x003] = 000000003c7f6001 000007f6
(XEN)  L2[0x003] = 000000003cfac067 00000fac 
(XEN)  L1[0x1f8] = 800000003c7f8061 000007f8
(XEN) domain_crash_sync called from entry.S (ff1b47ee)
(XEN) Domain 0 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-3.4.3-rc4-pre  x86_32p  debug=n  Not tainted ]----
(XEN) CPU:    0
(XEN) EIP:    e019:[<c04058df>]
(XEN) EFLAGS: 00000246   EM: 1   CONTEXT: pv guest
(XEN) eax: 00000000   ebx: 3c7f7163   ecx: 00000000   edx: 00000000
(XEN) esi: 80000000   edi: c07f8fd0   ebp: 80000000   esp: c0731e78
(XEN) cr0: 8005003b   cr4: 000026f0   cr3: 3c733000   cr2: c07f8fd0
(XEN) ds: e021   es: e021   fs: 00d8   gs: 0000   ss: e021   cs: e019
(XEN) Guest stack trace from esp=c0731e78:
(XEN)    00000003 c04058df 0001e019 00010046 3c7f8067 c07f8fd0 007f7163 c0426a62
(XEN)    3c7f7163 80000000 00000000 c040438a 007f7163 3c7f7163 80000000 f57fa000
(XEN)    f57fa000 00000002 00000000 f5600fd8 c042592f 00000000 c078e60c 0000017b
(XEN)    80000000 f5600fac 00000001 c06c5bf6 c078a7be f5600fac c07a11ac 00000001
(XEN)    00000068 f5600f70 00000000 00000000 2f000000 00000000 c07a1224 c078a794
(XEN)    00000040 c078ac8a 2d1fe000 00000000 c0784b1d 0000000f 00ee6a00 00000000
(XEN)    009ad000 00000000 00000000 00000005 00000000 00000000 00000000 00000000
(XEN)    205b6a00 30202020 3030302e 5d303030 009a0020 00000000 009ad000 009ad000
(XEN)    c0755dc0 00000002 00000000 00000000 c0438472 00000000 00000000 00000000
(XEN)    00000000 00000000 c0731fdc 00000000 00000000 c07805c2 c06be459 c0652020
(XEN)    c07b0d40 c0fa3458 c0782cea 00000000 c0731fec 00000000 00000000 00000000
(XEN)    00000000 1fc89375 80000281 00020800 000006f6 00000001 00000000 c0fa3000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN) Domain 0 crashed: rebooting machine in 5 seconds.

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 1237 bytes --]

Hi Pasi,

Sorry to bother. Any inputs on debugs provided?

Thanks

On Wed, Mar 31, 2010 at 2:10 PM, Ritu kaur <ritu.kaur.us@gmail.com> wrote:

> Attached xen debug logs. Just to update this is with xen/next and xcp0.1.1
> as dom0. Inputs appreciated.
>
> Thanks
>
>
>
> On Wed, Mar 31, 2010 at 7:39 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote:
>
>> On Wed, Mar 31, 2010 at 06:55:54AM -0700, Ritu kaur wrote:
>> >    Konrad, yes it is a null-modem cable. Cable was bought for this
>> testing.
>> >
>>
>> First get it working on baremetal Linux (non-Xen), then continue with Xen.
>>
>> -- Pasi
>>
>> >    Thanks
>> >
>> >    On Wed, Mar 31, 2010 at 6:42 AM, Konrad Rzeszutek Wilk
>> >    <[1]konrad.wilk@oracle.com> wrote:
>> >
>> >      On Wed, Mar 31, 2010 at 06:15:59AM -0700, Ritu kaur wrote:
>> >      > It's a onboard serial port. From dmesg there are ttyS0 and ttyS1
>> ports
>> >      are
>> >      > shown and I have tried both of them.
>> >
>> >      And the cable you have, it is a null modem serial cable? Have you
>> ever
>> >      had serial cable working (say with baremetal Linux?)
>> >
>> > References
>> >
>> >    Visible links
>> >    1. mailto:konrad.wilk@oracle.com
>>
>
>

[-- Attachment #1.2: Type: text/html, Size: 2080 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 1961 bytes --]

Hello,

Any inputs folks on xen debugs provided? dom0 crashes when  xen/next kernel
is used in xcp 0.1.1.

Snippets of debugs...

(XEN) d0:v0: unhandled page fault (ec=0003)
(XEN) Pagetable walk from c07f8fd0:
(XEN)  L3[0x003] = 000000003c7f6001 000007f6
(XEN)  L2[0x003] = 000000003cfac067 00000fac
(XEN)  L1[0x1f8] = 800000003c7f8061 000007f8
(XEN) domain_crash_sync called from entry.S (ff1b47ee)
(XEN) Domain 0 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-3.4.3-rc4-pre  x86_32p  debug=n  Not tainted ]----
...

Complete debugs attached one more time.

Thanks

On Thu, Apr 1, 2010 at 5:48 AM, Ritu kaur <ritu.kaur.us@gmail.com> wrote:

> Hi Pasi,
>
> Sorry to bother. Any inputs on debugs provided?
>
> Thanks
>
>
> On Wed, Mar 31, 2010 at 2:10 PM, Ritu kaur <ritu.kaur.us@gmail.com> wrote:
>
>> Attached xen debug logs. Just to update this is with xen/next and xcp0.1.1
>> as dom0. Inputs appreciated.
>>
>> Thanks
>>
>>
>>
>> On Wed, Mar 31, 2010 at 7:39 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote:
>>
>>> On Wed, Mar 31, 2010 at 06:55:54AM -0700, Ritu kaur wrote:
>>> >    Konrad, yes it is a null-modem cable. Cable was bought for this
>>> testing.
>>> >
>>>
>>> First get it working on baremetal Linux (non-Xen), then continue with
>>> Xen.
>>>
>>> -- Pasi
>>>
>>> >    Thanks
>>> >
>>> >    On Wed, Mar 31, 2010 at 6:42 AM, Konrad Rzeszutek Wilk
>>> >    <[1]konrad.wilk@oracle.com> wrote:
>>> >
>>> >      On Wed, Mar 31, 2010 at 06:15:59AM -0700, Ritu kaur wrote:
>>> >      > It's a onboard serial port. From dmesg there are ttyS0 and ttyS1
>>> ports
>>> >      are
>>> >      > shown and I have tried both of them.
>>> >
>>> >      And the cable you have, it is a null modem serial cable? Have you
>>> ever
>>> >      had serial cable working (say with baremetal Linux?)
>>> >
>>> > References
>>> >
>>> >    Visible links
>>> >    1. mailto:konrad.wilk@oracle.com
>>>
>>
>>
>

[-- Attachment #1.2: Type: text/html, Size: 3135 bytes --]

[-- Attachment #2: xen-xcp-debugs.txt --]
[-- Type: text/plain, Size: 11659 bytes --]

 \ \/ /___ _ __   |___ /| || |  |___ /    _ __ ___| || |     _ __  _ __ ___ 
  \  // _ \ '_ \    |_ \| || |_   |_ \ __| '__/ __| || |_ __| '_ \| '__/ _ \
  /  \  __/ | | |  ___) |__   _| ___) |__| | | (__|__   _|__| |_) | | |  __/
 /_/\_\___|_| |_| |____(_) |_|(_)____/   |_|  \___|  |_|    | .__/|_|  \___|
                                                            |_|             
(XEN) Xen version 3.4.3-rc4-pre (root@) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-46)) Sat Mar 20 21:13:47 EDT 2010
(XEN) Latest ChangeSet: Tue Mar 09 18:15:52 2010 +0000 19924:6e72f8c3c017
(XEN) Command line: com1=115200,8n1 console=com1,vga dom0_mem=752M lowmem_emergency_pool=1M crashkernel=64M@32M 
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds
(XEN)  EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information:
(XEN)  Found 1 MBR signatures
(XEN)  Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009cc00 (usable)
(XEN)  000000000009cc00 - 00000000000a0000 (reserved)
(XEN)  00000000000e4000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 000000007f680000 (usable)
(XEN)  000000007f680000 - 000000007f68b000 (ACPI data)
(XEN)  000000007f68b000 - 000000007f700000 (ACPI NVS)
(XEN)  000000007f700000 - 0000000080000000 (reserved)
(XEN)  00000000e0000000 - 00000000e4000000 (reserved)
(XEN)  00000000fec00000 - 00000000fec10000 (reserved)
(XEN)  00000000fee00000 - 00000000fee01000 (reserved)
(XEN)  00000000ff000000 - 0000000100000000 (reserved)
(XEN) Kdump: 64MB (65536kB) at 0x2000000
(XEN) System RAM: 2038MB (2087024kB)
(XEN) ACPI: RSDP 000F6EE0, 0014 (r0 INTELB)
(XEN) ACPI: RSDT 7F683D75, 003C (r1 PTLTD    RSDT    6040000  LTP        0)
(XEN) ACPI: FACP 7F68AE7E, 0084 (r1 SUPRMC           6040000 PTL         3)
(XEN) ACPI: DSDT 7F6855E3, 589B (r1  INTEL BR_WATER  6040000 MSFT  3000001)
(XEN) ACPI: FACS 7F68BFC0, 0040
(XEN) ACPI: TCPA 7F68AF02, 0032 (r1 SMC              6040000 PTL         0)
(XEN) ACPI: MCFG 7F68AF34, 003C (r1 INTELB R_WATERP  6040000  LTP        0)
(XEN) ACPI: APIC 7F68AF70, 0068 (r1 INTELB R_WATERP  6040000  LTP        0)
(XEN) ACPI: BOOT 7F68AFD8, 0028 (r1 INTELB R_WATERP  6040000  LTP        1)
(XEN) ACPI: SSDT 7F683DB1, 13EC (r1 INTELB R_WATERW     3000 INTL 20061109)
(XEN) Xen heap: 9MB (9800kB)
(XEN) Domain heap initialised
(XEN) Processor #0 6:15 APIC version 20
(XEN) Processor #1 6:15 APIC version 20
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 1862.041 MHz processor.
(XEN) VMX: Supported advanced features:
(XEN)  - MSR direct-access bitmap
(XEN) HVM: VMX enabled
(XEN) CPU0: Intel(R) Core(TM)2 CPU          6320  @ 1.86GHz stepping 06
(XEN) Booting processor 1/1 eip 88000
(XEN) CPU1: Intel(R) Core(TM)2 CPU          6320  @ 1.86GHz stepping 06
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) checking TSC synchronization across 2 CPUs: passed.
(XEN) Platform timer is 3.579MHz ACPI PM Timer
ÿ(XEN) Brought up 2 CPUs
(XEN) I/O virtualisation disabled
(XEN) CPUIDLE: disabled due to no HPET. Force enable with 'cpuidle'.
(XEN) *** LOADING DOMAIN 0 ***
(XEN)  Xen  kernel: 32-bit, PAE, lsb
(XEN)  Dom0 kernel: 32-bit, PAE, lsb, paddr 0x400000 -> 0x9ad000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   000000003c000000->000000003e000000 (184320 pages to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: c0400000->c09ad000
(XEN)  Init. ramdisk: c09ad000->c0ee6a00
(XEN)  Phys-Mach map: c0ee7000->c0fa3000
(XEN)  Start info:    c0fa3000->c0fa347c
(XEN)  Page tables:   c0fa4000->c0fb3000
(XEN)  Boot stack:    c0fb3000->c0fb4000
(XEN)  TOTAL:         c0000000->c1400000
(XEN)  ENTRY ADDRESS: c0780000
(XEN) Dom0 has maximum 2 VCPUs
(XEN) Scrubbing Free RAM: .............done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 116kB init memory.
mapping kernel into physical memory
Xen: setup ISA identity maps
about to get started...
[    0.000000] Reserving virtual address space above 0xf5800000
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.32 (root@localhost.localdomain) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-46)) #7 SMP Sun Mar 28 12:16:38 EDT 2010
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   NSC Geode by NSC
[    0.000000]   Cyrix CyrixInstead
[    0.000000]   Centaur CentaurHauls
[    0.000000]   Transmeta GenuineTMx86
[    0.000000]   Transmeta TransmetaCPU
[    0.000000]   UMC UMC UMC UMC
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  Xen: 0000000000000000 - 000000000009cc00 (usable)
[    0.000000]  Xen: 000000000009cc00 - 0000000000100000 (reserved)
[    0.000000]  Xen: 0000000000100000 - 000000002f000000 (usable)
[    0.000000]  Xen: 000000007f680000 - 000000007f68b000 (ACPI data)
[    0.000000]  Xen: 000000007f68b000 - 000000007f700000 (ACPI NVS)
[    0.000000]  Xen: 000000007f700000 - 0000000080000000 (reserved)
[    0.000000]  Xen: 00000000e0000000 - 00000000e4000000 (reserved)
[    0.000000]  Xen: 00000000fec00000 - 00000000fec10000 (reserved)
[    0.000000]  Xen: 00000000fee00000 - 00000000fee01000 (reserved)
[    0.000000]  Xen: 00000000ff000000 - 0000000100000000 (reserved)
[    0.000000] bootconsole [xenboot0] enabled
[    0.000000] DMI present.
[    0.000000] Phoenix BIOS detected: BIOS may corrupt low RAM, working around it.
[    0.000000] last_pfn = 0x2f000 max_arch_pfn = 0x1000000
[    0.000000] init_memory_mapping: 0000000000000000-000000002d1fe000
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] RAMDISK: 009ad000 - 00ee6a00
[    0.000000] ACPI: RSDP 000f6ee0 00014 (v00 INTELB)
[    0.000000] ACPI: RSDT 7f683d75 0003C (v01 PTLTD    RSDT   06040000  LTP 00000000)
[    0.000000] ACPI: FACP 7f68ae7e 00084 (v01 SUPRMC          06040000 PTL  00000003)
[    0.000000] ACPI: DSDT 7f6855e3 0589B (v01  INTEL BR_WATER 06040000 MSFT 03000001)
[    0.000000] ACPI: FACS 7f68bfc0 00040
[    0.000000] ACPI: TCPA 7f68af02 00032 (v01 SMC             06040000 PTL  00000000)
[    0.000000] ACPI: MCFG 7f68af34 0003C (v01 INTELB R_WATERP 06040000  LTP 00000000)
[    0.000000] ACPI: APIC 7f68af70 00068 (v01 INTELB R_WATERP 06040000  LTP 00000000)
[    0.000000] ACPI: BOOT 7f68afd8 00028 (v01 INTELB R_WATERP 06040000  LTP 00000001)
[    0.000000] ACPI: SSDT 7f683db1 013EC (v01 INTELB R_WATERW 00003000 INTL 20061109)
[    0.000000] 30MB HIGHMEM available.
[    0.000000] 721MB LOWMEM available.
[    0.000000]   mapped low ram: 0 - 2d1fe000
[    0.000000]   low ram: 0 - 2d1fe000
[    0.000000]   node 0 low ram: 00000000 - 2d1fe000
[    0.000000]   node 0 bootmap 00010000 - 00015a40
[    0.000000] (10 early reservations) ==> bootmem [0000000000 - 002d1fe000]
[    0.000000]   #0 [0000000000 - 0000001000]   BIOS data page ==> [0000000000 - 0000001000]
[    0.000000]   #1 [0000fa4000 - 0000fb3000]   XEN PAGETABLES ==> [0000fa4000 - 0000fb3000]
[    0.000000]   #2 [0000001000 - 0000002000]    EX TRAMPOLINE ==> [0000001000 - 0000002000]
[    0.000000]   #3 [0000006000 - 0000007000]       TRAMPOLINE ==> [0000006000 - 0000007000]
[    0.000000]   #4 [0000400000 - 0000887fa4]    TEXT DATA BSS ==> [0000400000 - 0000887fa4]
[    0.000000]   #5 [00009ad000 - 0000ee6a00]          RAMDISK ==> [00009ad000 - 0000ee6a00]
[    0.000000]   #6 [0000ee7000 - 0000fa4000]   XEN START INFO ==> [0000ee7000 - 0000fa4000]
[    0.000000]   #7 [0000888000 - 000088813c]              BRK ==> [0000888000 - 000088813c]
[    0.000000]   #8 [0000100000 - 000025c000]          PGTABLE ==> [0000100000 - 000025c000]
[    0.000000]   #9 [0000010000 - 0000016000]          BOOTMAP ==> [0000010000 - 0000016000]
[    0.000000] found SMP MP-table at [c00f6f10] f6f10
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA      0x00000010 -> 0x00001000
[    0.000000]   Normal   0x00001000 -> 0x0002d1fe
[    0.000000]   HighMem  0x0002d1fe -> 0x0002f000
[    0.000000] Movable zone start PFN for each node
[    0.000000] early_node_map[2] active PFN ranges
[    0.000000]     0: 0x00000010 -> 0x0000009c
[    0.000000]     0: 0x00000100 -> 0x0002f000
[    0.000000] Using APIC driver default
[    0.000000] ACPI: PM-Timer IO Port: 0x1008
[    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[    0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
(XEN) mm.c:1699:d0 Bad L1 flags 100
(XEN) mm.c:720:d0 Bad L1 flags 100
(XEN) mm.c:4221:d0 ptwr_emulate: could not get_page_from_l1e()
(XEN) d0:v0: unhandled page fault (ec=0003)
(XEN) Pagetable walk from c07f8fd0:
(XEN)  L3[0x003] = 000000003c7f6001 000007f6
(XEN)  L2[0x003] = 000000003cfac067 00000fac 
(XEN)  L1[0x1f8] = 800000003c7f8061 000007f8
(XEN) domain_crash_sync called from entry.S (ff1b47ee)
(XEN) Domain 0 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-3.4.3-rc4-pre  x86_32p  debug=n  Not tainted ]----
(XEN) CPU:    0
(XEN) EIP:    e019:[<c04058df>]
(XEN) EFLAGS: 00000246   EM: 1   CONTEXT: pv guest
(XEN) eax: 00000000   ebx: 3c7f7163   ecx: 00000000   edx: 00000000
(XEN) esi: 80000000   edi: c07f8fd0   ebp: 80000000   esp: c0731e78
(XEN) cr0: 8005003b   cr4: 000026f0   cr3: 3c733000   cr2: c07f8fd0
(XEN) ds: e021   es: e021   fs: 00d8   gs: 0000   ss: e021   cs: e019
(XEN) Guest stack trace from esp=c0731e78:
(XEN)    00000003 c04058df 0001e019 00010046 3c7f8067 c07f8fd0 007f7163 c0426a62
(XEN)    3c7f7163 80000000 00000000 c040438a 007f7163 3c7f7163 80000000 f57fa000
(XEN)    f57fa000 00000002 00000000 f5600fd8 c042592f 00000000 c078e60c 0000017b
(XEN)    80000000 f5600fac 00000001 c06c5bf6 c078a7be f5600fac c07a11ac 00000001
(XEN)    00000068 f5600f70 00000000 00000000 2f000000 00000000 c07a1224 c078a794
(XEN)    00000040 c078ac8a 2d1fe000 00000000 c0784b1d 0000000f 00ee6a00 00000000
(XEN)    009ad000 00000000 00000000 00000005 00000000 00000000 00000000 00000000
(XEN)    205b6a00 30202020 3030302e 5d303030 009a0020 00000000 009ad000 009ad000
(XEN)    c0755dc0 00000002 00000000 00000000 c0438472 00000000 00000000 00000000
(XEN)    00000000 00000000 c0731fdc 00000000 00000000 c07805c2 c06be459 c0652020
(XEN)    c07b0d40 c0fa3458 c0782cea 00000000 c0731fec 00000000 00000000 00000000
(XEN)    00000000 1fc89375 80000281 00020800 000006f6 00000001 00000000 c0fa3000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN) Domain 0 crashed: rebooting machine in 5 seconds.

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Konrad Rzeszutek Wilk]

On Mon, Apr 05, 2010 at 07:10:22AM -0700, Ritu kaur wrote:
> Hello,
> 
> Any inputs folks on xen debugs provided? dom0 crashes when  xen/next kernel


What you are hitting should have been fixed a week ago. Are you up to
the latest in xen/next? Did you do 'git pull' ? Do you see this as the
latest when you do 'git log | head':



 git log | head -5
commit 900f6d725874ca97c21cdc5a2c4e05bd62db4e86
Merge: f2530fa 89689b1
Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Date:   Thu Apr 1 14:24:30 2010 -0700

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 3490 bytes --]

Thanks Konrad.

I downloaded new code and still doesn't work(albeit different problem). I
will enumerate them below

(Please note 1, 2 and 3 are seen with old xen/next as well). What seemed
simple testing of pci passthrough via config changes doesn't seem to be the
case.

1. mkinitrd doesn't work in xcp ddk. I get below errors

mkinitrd -f ./initrd-2.6.32.ing 2.6.32
modinfo: could not find module ide-disk
No module ide-disk found for kernel 2.6.32, aborting.

I copied ide-disk.ko from
/lib/modules/2.6.27.42-0.1.1.xs0.1.1.737.1065xen/kernel/drivers/ide/ide-disk.ko(just
to check what other errors arise from mkinitrd in xcp ddk), I get

mkinitrd -f ./initrd-2.6.32.ing 2.6.32
modinfo: could not find module ide-disk
modinfo: could not find module dm-mem-cache
modinfo: could not find module dm-message
modinfo: could not find module dm-raid45

2. Looked into .config I have(generated via make menuconfig) and there isn't
anything on IDEDISK. I cross checked config file that comes with xcp source
code it has
...
CONFIG_BLK_DEV_IDEDISK=m
CONFIG_IDEDISK_MULTI_MODE=y
...

I copied above configs into my .config and when I run make(it asks some IDE
config related questions ) and these configs are deleted after that. I have
tried all options "y/n/m" to the questions and same result.

3. I downloaded .config file from
http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_32

there isn't IDEDISK config in it either and in addition "make tar-pkg"
doesn't work with this .config file. I get following errors

DEPMOD  2.6.32


/bin/sh: line 1:  3341 Killed                  /sbin/depmod -ae -F
System.map -b /root/kernel/linux-2.6.32/tar-install 2.6.32
make[3]: *** [_modinst_post] Error 137
make[2]: *** [sub-make] Error 2
make[1]: *** [tar-pkg] Error 2
make: *** [tar-pkg] Error 2

4. I tried with the vmlinuz and initrd image built from "2" above(I know
initrd image is not correct, I just wanted to try) and I get

[0.000000] ERROR: Unable to locate IOAPIC for GSI 2
[0.000000] ERROR: Unable to locate IOAPIC for GSI 9
[0.000000] ERROR: Unable to locate IOAPIC for GSI 2
[0.000000] ERROR: Unable to locate IOAPIC for GSI 9
[0.493572] registering netback
Red Hat nash version 5.1.19.6 starting
einsmod: error inserting 'lib/ide-disk.ko': -1 Invalid module format
indmos: error inserting '/lib/dm-region-hash.ko': -1 File Exists
mount: could not fine filesystem '/dev/root'
setuproot: moving /dev failed: No such file or directory
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
switchroot: mount failed: No such file or directory
[0.905987] Kernel panic - not syncing: Attempted to kill init!

Let me know how to proceed on this.

Thanks


<http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_32>
On Mon, Apr 5, 2010 at 10:00 AM, Konrad Rzeszutek Wilk <
konrad.wilk@oracle.com> wrote:

> On Mon, Apr 05, 2010 at 07:10:22AM -0700, Ritu kaur wrote:
> > Hello,
> >
> > Any inputs folks on xen debugs provided? dom0 crashes when  xen/next
> kernel
>
>
> What you are hitting should have been fixed a week ago. Are you up to
> the latest in xen/next? Did you do 'git pull' ? Do you see this as the
> latest when you do 'git log | head':
>
>
>
>  git log | head -5
> commit 900f6d725874ca97c21cdc5a2c4e05bd62db4e86
> Merge: f2530fa 89689b1
> Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
> Date:   Thu Apr 1 14:24:30 2010 -0700
>
>

[-- Attachment #1.2: Type: text/html, Size: 4411 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Pasi Kärkkäinen]

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

Did you install the modules after you compiled the kernel? 
Did you run "depmod -a <kernelversion>" ? 
 
>    I copied ide-disk.ko from
>    /lib/modules/2.6.27.42-0.1.1.xs0.1.1.737.1065xen/kernel/drivers/ide/ide-disk.ko(just
>    to check what other errors arise from mkinitrd in xcp ddk), I get
> 

You can't modules from a different kernel version!!!

>    mkinitrd -f ./initrd-2.6.32.ing 2.6.32
>    modinfo: could not find module ide-disk
>    modinfo: could not find module dm-mem-cache
>    modinfo: could not find module dm-message
>    modinfo: could not find module dm-raid45
> 

Looks like you didn't install the modules from the new kernel.

>    2. Looked into .config I have(generated via make menuconfig) and there
>    isn't anything on IDEDISK. I cross checked config file that comes with xcp
>    source code it has
>    ...
>    CONFIG_BLK_DEV_IDEDISK=m
>    CONFIG_IDEDISK_MULTI_MODE=y
>    ...
>

XCP default kernel is 2.6.27. You're trying to use 2.6.32. 
There might have been changes between the kernel versions.
 
>    I copied above configs into my .config and when I run make(it asks some
>    IDE config related questions ) and these configs are deleted after that. I
>    have tried all options "y/n/m" to the questions and same result.
> 
>    3. I downloaded .config file from
>    [1]http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_32
> 
>    there isn't IDEDISK config in it either and in addition "make tar-pkg"
>    doesn't work with this .config file. I get following errors
> 

If ide-disk module is not used/required anymore in 2.6.32, then you should
remove it from /etc/modprobe.conf so that mkinitrd doesn't try to include it!

(replace it with the proper new module name).

>    DEPMOD  2.6.32
> 
>    /bin/sh: line 1:  3341 Killed                  /sbin/depmod -ae -F
>    System.map -b /root/kernel/linux-2.6.32/tar-install 2.6.32
>    make[3]: *** [_modinst_post] Error 137
>    make[2]: *** [sub-make] Error 2
>    make[1]: *** [tar-pkg] Error 2
>    make: *** [tar-pkg] Error 2
> 
>    4. I tried with the vmlinuz and initrd image built from "2" above(I know
>    initrd image is not correct, I just wanted to try) and I get
> 
>    [0.000000] ERROR: Unable to locate IOAPIC for GSI 2
>    [0.000000] ERROR: Unable to locate IOAPIC for GSI 9
>    [0.000000] ERROR: Unable to locate IOAPIC for GSI 2
>    [0.000000] ERROR: Unable to locate IOAPIC for GSI 9
>    [0.493572] registering netback
>    Red Hat nash version 5.1.19.6 starting
>    einsmod: error inserting 'lib/ide-disk.ko': -1 Invalid module format
>

"Invalid module format" means it's from a different kernel and cannot be
used with this kernel.

>    indmos: error inserting '/lib/dm-region-hash.ko': -1 File Exists
>    mount: could not fine filesystem '/dev/root'
>    setuproot: moving /dev failed: No such file or directory
>    setuproot: error mounting /proc: No such file or directory
>    setuproot: error mounting /sys: No such file or directory
>    switchroot: mount failed: No such file or directory
>    [0.905987] Kernel panic - not syncing: Attempted to kill init!
> 
>    Let me know how to proceed on this.
>

Install for example Fedora 12, or any other distro that has 2.6.32 kernel
as a default, and check which modules are used for your hardware,
then replace "ide-disk" in modprobe.conf with the actual module.

-- Pasi

 
>    Thanks
> 
>    On Mon, Apr 5, 2010 at 10:00 AM, Konrad Rzeszutek Wilk
>    <[2]konrad.wilk@oracle.com> wrote:
> 
>      On Mon, Apr 05, 2010 at 07:10:22AM -0700, Ritu kaur wrote:
>      > Hello,
>      >
>      > Any inputs folks on xen debugs provided? dom0 crashes when  xen/next
>      kernel
> 
>      What you are hitting should have been fixed a week ago. Are you up to
>      the latest in xen/next? Did you do 'git pull' ? Do you see this as the
>      latest when you do 'git log | head':
> 
>       git log | head -5
>      commit 900f6d725874ca97c21cdc5a2c4e05bd62db4e86
>      Merge: f2530fa 89689b1
>      Author: Jeremy Fitzhardinge <[3]jeremy.fitzhardinge@citrix.com>
>      Date:   Thu Apr 1 14:24:30 2010 -0700
> 
> References
> 
>    Visible links
>    1. http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_32
>    2. mailto:konrad.wilk@oracle.com
>    3. mailto:jeremy.fitzhardinge@citrix.com

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

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 5914 bytes --]

Thanks Pasi. When will new xcp with 2.6.32 kernel be released?

Replies inline...

On Mon, Apr 5, 2010 at 11:03 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote:

> On Mon, Apr 05, 2010 at 09:00:59PM -0700, Ritu kaur wrote:
> >    Thanks Konrad.
> >
> >    I downloaded new code and still doesn't work(albeit different
> problem). I
> >    will enumerate them below
> >
> >    (Please note 1, 2 and 3 are seen with old xen/next as well). What
> seemed
> >    simple testing of pci passthrough via config changes doesn't seem to
> be
> >    the case.
> >
> >    1. mkinitrd doesn't work in xcp ddk. I get below errors
> >
> >    mkinitrd -f ./initrd-2.6.32.ing 2.6.32
> >    modinfo: could not find module ide-disk
> >    No module ide-disk found for kernel 2.6.32, aborting.
> >
>
> Did you install the modules after you compiled the kernel?
> Did you run "depmod -a <kernelversion>" ?
>
>
yes I have done it and still the same problem.


> >    I copied ide-disk.ko from
> >
>  /lib/modules/2.6.27.42-0.1.1.xs0.1.1.737.1065xen/kernel/drivers/ide/ide-disk.ko(just
> >    to check what other errors arise from mkinitrd in xcp ddk), I get
> >
>
> You can't modules from a different kernel version!!!
>
>
I understand that. Just want to check what additional problems arise.


> >    mkinitrd -f ./initrd-2.6.32.ing 2.6.32
> >    modinfo: could not find module ide-disk
> >    modinfo: could not find module dm-mem-cache
> >    modinfo: could not find module dm-message
> >    modinfo: could not find module dm-raid45
> >
>
> Looks like you didn't install the modules from the new kernel.
>

I have installed modules via "make modules_install" and depmod as well.


>
> >    2. Looked into .config I have(generated via make menuconfig) and there
> >    isn't anything on IDEDISK. I cross checked config file that comes with
> xcp
> >    source code it has
> >    ...
> >    CONFIG_BLK_DEV_IDEDISK=m
> >    CONFIG_IDEDISK_MULTI_MODE=y
> >    ...
> >
>
> XCP default kernel is 2.6.27. You're trying to use 2.6.32.
> There might have been changes between the kernel versions.
>
> >    I copied above configs into my .config and when I run make(it asks
> some
> >    IDE config related questions ) and these configs are deleted after
> that. I
> >    have tried all options "y/n/m" to the questions and same result.
> >
> >    3. I downloaded .config file from
> >    [1]
> http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_32
> >
> >    there isn't IDEDISK config in it either and in addition "make tar-pkg"
> >    doesn't work with this .config file. I get following errors
> >
>
> If ide-disk module is not used/required anymore in 2.6.32, then you should
> remove it from /etc/modprobe.conf so that mkinitrd doesn't try to include
> it!
>
> (replace it with the proper new module name).
>
> >    DEPMOD  2.6.32
> >
> >    /bin/sh: line 1:  3341 Killed                  /sbin/depmod -ae -F
> >    System.map -b /root/kernel/linux-2.6.32/tar-install 2.6.32
> >    make[3]: *** [_modinst_post] Error 137
> >    make[2]: *** [sub-make] Error 2
> >    make[1]: *** [tar-pkg] Error 2
> >    make: *** [tar-pkg] Error 2
> >
> >    4. I tried with the vmlinuz and initrd image built from "2" above(I
> know
> >    initrd image is not correct, I just wanted to try) and I get
> >
> >    [0.000000] ERROR: Unable to locate IOAPIC for GSI 2
> >    [0.000000] ERROR: Unable to locate IOAPIC for GSI 9
> >    [0.000000] ERROR: Unable to locate IOAPIC for GSI 2
> >    [0.000000] ERROR: Unable to locate IOAPIC for GSI 9
> >    [0.493572] registering netback
> >    Red Hat nash version 5.1.19.6 starting
> >    einsmod: error inserting 'lib/ide-disk.ko': -1 Invalid module format
> >
>
> "Invalid module format" means it's from a different kernel and cannot be
> used with this kernel.
>
> >    indmos: error inserting '/lib/dm-region-hash.ko': -1 File Exists
> >    mount: could not fine filesystem '/dev/root'
> >    setuproot: moving /dev failed: No such file or directory
> >    setuproot: error mounting /proc: No such file or directory
> >    setuproot: error mounting /sys: No such file or directory
> >    switchroot: mount failed: No such file or directory
> >    [0.905987] Kernel panic - not syncing: Attempted to kill init!
> >
> >    Let me know how to proceed on this.
> >
>
> Install for example Fedora 12, or any other distro that has 2.6.32 kernel
> as a default, and check which modules are used for your hardware,
> then replace "ide-disk" in modprobe.conf with the actual module.
>

Will look into it.

Thanks

>
> -- Pasi
>
>
> >    Thanks
> >
> >    On Mon, Apr 5, 2010 at 10:00 AM, Konrad Rzeszutek Wilk
> >    <[2]konrad.wilk@oracle.com> wrote:
> >
> >      On Mon, Apr 05, 2010 at 07:10:22AM -0700, Ritu kaur wrote:
> >      > Hello,
> >      >
> >      > Any inputs folks on xen debugs provided? dom0 crashes when
>  xen/next
> >      kernel
> >
> >      What you are hitting should have been fixed a week ago. Are you up
> to
> >      the latest in xen/next? Did you do 'git pull' ? Do you see this as
> the
> >      latest when you do 'git log | head':
> >
> >       git log | head -5
> >      commit 900f6d725874ca97c21cdc5a2c4e05bd62db4e86
> >      Merge: f2530fa 89689b1
> >      Author: Jeremy Fitzhardinge <[3]jeremy.fitzhardinge@citrix.com>
> >      Date:   Thu Apr 1 14:24:30 2010 -0700
> >
> > References
> >
> >    Visible links
> >    1.
> http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_32
> >    2. mailto:konrad.wilk@oracle.com
> >    3. mailto:jeremy.fitzhardinge@citrix.com
>
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
>
>

[-- Attachment #1.2: Type: text/html, Size: 8700 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 6526 bytes --]

Our technical guru/consultant suggested to check if backporting
fixes(changes for shared interrupts) into 2.6.27 XCP source is feasible? i.e


XCP 2.6.27 source + fix(es) for shared interrupts = pci-passthrough work
seamlessly

If it is possible do let me know and pointer to the changes would be helpful
as well.

Thanks

On Tue, Apr 6, 2010 at 6:31 AM, Ritu kaur <ritu.kaur.us@gmail.com> wrote:

> Thanks Pasi. When will new xcp with 2.6.32 kernel be released?
>
> Replies inline...
>
> On Mon, Apr 5, 2010 at 11:03 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote:
>
>> On Mon, Apr 05, 2010 at 09:00:59PM -0700, Ritu kaur wrote:
>> >    Thanks Konrad.
>> >
>> >    I downloaded new code and still doesn't work(albeit different
>> problem). I
>> >    will enumerate them below
>> >
>> >    (Please note 1, 2 and 3 are seen with old xen/next as well). What
>> seemed
>> >    simple testing of pci passthrough via config changes doesn't seem to
>> be
>> >    the case.
>> >
>> >    1. mkinitrd doesn't work in xcp ddk. I get below errors
>> >
>> >    mkinitrd -f ./initrd-2.6.32.ing 2.6.32
>> >    modinfo: could not find module ide-disk
>> >    No module ide-disk found for kernel 2.6.32, aborting.
>> >
>>
>> Did you install the modules after you compiled the kernel?
>> Did you run "depmod -a <kernelversion>" ?
>>
>>
> yes I have done it and still the same problem.
>
>
>>  >    I copied ide-disk.ko from
>> >
>>  /lib/modules/2.6.27.42-0.1.1.xs0.1.1.737.1065xen/kernel/drivers/ide/ide-disk.ko(just
>> >    to check what other errors arise from mkinitrd in xcp ddk), I get
>> >
>>
>> You can't modules from a different kernel version!!!
>>
>>
> I understand that. Just want to check what additional problems arise.
>
>
>>  >    mkinitrd -f ./initrd-2.6.32.ing 2.6.32
>> >    modinfo: could not find module ide-disk
>> >    modinfo: could not find module dm-mem-cache
>> >    modinfo: could not find module dm-message
>> >    modinfo: could not find module dm-raid45
>> >
>>
>> Looks like you didn't install the modules from the new kernel.
>>
>
> I have installed modules via "make modules_install" and depmod as well.
>
>
>>
>> >    2. Looked into .config I have(generated via make menuconfig) and
>> there
>> >    isn't anything on IDEDISK. I cross checked config file that comes
>> with xcp
>> >    source code it has
>> >    ...
>> >    CONFIG_BLK_DEV_IDEDISK=m
>> >    CONFIG_IDEDISK_MULTI_MODE=y
>> >    ...
>> >
>>
>> XCP default kernel is 2.6.27. You're trying to use 2.6.32.
>> There might have been changes between the kernel versions.
>>
>> >    I copied above configs into my .config and when I run make(it asks
>> some
>> >    IDE config related questions ) and these configs are deleted after
>> that. I
>> >    have tried all options "y/n/m" to the questions and same result.
>> >
>> >    3. I downloaded .config file from
>> >    [1]
>> http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_32
>> >
>> >    there isn't IDEDISK config in it either and in addition "make
>> tar-pkg"
>> >    doesn't work with this .config file. I get following errors
>> >
>>
>> If ide-disk module is not used/required anymore in 2.6.32, then you should
>> remove it from /etc/modprobe.conf so that mkinitrd doesn't try to include
>> it!
>>
>> (replace it with the proper new module name).
>>
>> >    DEPMOD  2.6.32
>> >
>> >    /bin/sh: line 1:  3341 Killed                  /sbin/depmod -ae -F
>> >    System.map -b /root/kernel/linux-2.6.32/tar-install 2.6.32
>> >    make[3]: *** [_modinst_post] Error 137
>> >    make[2]: *** [sub-make] Error 2
>> >    make[1]: *** [tar-pkg] Error 2
>> >    make: *** [tar-pkg] Error 2
>> >
>> >    4. I tried with the vmlinuz and initrd image built from "2" above(I
>> know
>> >    initrd image is not correct, I just wanted to try) and I get
>> >
>> >    [0.000000] ERROR: Unable to locate IOAPIC for GSI 2
>> >    [0.000000] ERROR: Unable to locate IOAPIC for GSI 9
>> >    [0.000000] ERROR: Unable to locate IOAPIC for GSI 2
>> >    [0.000000] ERROR: Unable to locate IOAPIC for GSI 9
>> >    [0.493572] registering netback
>> >    Red Hat nash version 5.1.19.6 starting
>> >    einsmod: error inserting 'lib/ide-disk.ko': -1 Invalid module format
>> >
>>
>> "Invalid module format" means it's from a different kernel and cannot be
>> used with this kernel.
>>
>> >    indmos: error inserting '/lib/dm-region-hash.ko': -1 File Exists
>> >    mount: could not fine filesystem '/dev/root'
>> >    setuproot: moving /dev failed: No such file or directory
>> >    setuproot: error mounting /proc: No such file or directory
>> >    setuproot: error mounting /sys: No such file or directory
>> >    switchroot: mount failed: No such file or directory
>> >    [0.905987] Kernel panic - not syncing: Attempted to kill init!
>> >
>> >    Let me know how to proceed on this.
>> >
>>
>> Install for example Fedora 12, or any other distro that has 2.6.32 kernel
>> as a default, and check which modules are used for your hardware,
>> then replace "ide-disk" in modprobe.conf with the actual module.
>>
>
> Will look into it.
>
> Thanks
>
>>
>> -- Pasi
>>
>>
>> >    Thanks
>> >
>> >    On Mon, Apr 5, 2010 at 10:00 AM, Konrad Rzeszutek Wilk
>> >    <[2]konrad.wilk@oracle.com> wrote:
>> >
>> >      On Mon, Apr 05, 2010 at 07:10:22AM -0700, Ritu kaur wrote:
>> >      > Hello,
>> >      >
>> >      > Any inputs folks on xen debugs provided? dom0 crashes when
>>  xen/next
>> >      kernel
>> >
>> >      What you are hitting should have been fixed a week ago. Are you up
>> to
>> >      the latest in xen/next? Did you do 'git pull' ? Do you see this as
>> the
>> >      latest when you do 'git log | head':
>> >
>> >       git log | head -5
>> >      commit 900f6d725874ca97c21cdc5a2c4e05bd62db4e86
>> >      Merge: f2530fa 89689b1
>> >      Author: Jeremy Fitzhardinge <[3]jeremy.fitzhardinge@citrix.com>
>> >      Date:   Thu Apr 1 14:24:30 2010 -0700
>> >
>> > References
>> >
>> >    Visible links
>> >    1.
>> http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_32
>> >    2. mailto:konrad.wilk@oracle.com
>> >    3. mailto:jeremy.fitzhardinge@citrix.com
>>
>> > _______________________________________________
>> > Xen-devel mailing list
>> > Xen-devel@lists.xensource.com
>> > http://lists.xensource.com/xen-devel
>>
>>
>

[-- Attachment #1.2: Type: text/html, Size: 9358 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 7098 bytes --]

Hello

Any inputs on backporting changes to xcp 2.6.27 source?

In addition, I had another question. I believe pci-passthrough works for
pci-e slots as well. I have not tested it just wanted to check if any
additional config changes are needed to make it work?

Thanks

On Fri, Apr 9, 2010 at 8:53 AM, Ritu kaur <ritu.kaur.us@gmail.com> wrote:

> Our technical guru/consultant suggested to check if backporting
> fixes(changes for shared interrupts) into 2.6.27 XCP source is feasible? i.e
>
>
> XCP 2.6.27 source + fix(es) for shared interrupts = pci-passthrough work
> seamlessly
>
> If it is possible do let me know and pointer to the changes would be
> helpful as well.
>
> Thanks
>
>
> On Tue, Apr 6, 2010 at 6:31 AM, Ritu kaur <ritu.kaur.us@gmail.com> wrote:
>
>> Thanks Pasi. When will new xcp with 2.6.32 kernel be released?
>>
>> Replies inline...
>>
>> On Mon, Apr 5, 2010 at 11:03 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote:
>>
>>> On Mon, Apr 05, 2010 at 09:00:59PM -0700, Ritu kaur wrote:
>>> >    Thanks Konrad.
>>> >
>>> >    I downloaded new code and still doesn't work(albeit different
>>> problem). I
>>> >    will enumerate them below
>>> >
>>> >    (Please note 1, 2 and 3 are seen with old xen/next as well). What
>>> seemed
>>> >    simple testing of pci passthrough via config changes doesn't seem to
>>> be
>>> >    the case.
>>> >
>>> >    1. mkinitrd doesn't work in xcp ddk. I get below errors
>>> >
>>> >    mkinitrd -f ./initrd-2.6.32.ing 2.6.32
>>> >    modinfo: could not find module ide-disk
>>> >    No module ide-disk found for kernel 2.6.32, aborting.
>>> >
>>>
>>> Did you install the modules after you compiled the kernel?
>>> Did you run "depmod -a <kernelversion>" ?
>>>
>>>
>> yes I have done it and still the same problem.
>>
>>
>>>  >    I copied ide-disk.ko from
>>> >
>>>  /lib/modules/2.6.27.42-0.1.1.xs0.1.1.737.1065xen/kernel/drivers/ide/ide-disk.ko(just
>>> >    to check what other errors arise from mkinitrd in xcp ddk), I get
>>> >
>>>
>>> You can't modules from a different kernel version!!!
>>>
>>>
>> I understand that. Just want to check what additional problems arise.
>>
>>
>>>  >    mkinitrd -f ./initrd-2.6.32.ing 2.6.32
>>> >    modinfo: could not find module ide-disk
>>> >    modinfo: could not find module dm-mem-cache
>>> >    modinfo: could not find module dm-message
>>> >    modinfo: could not find module dm-raid45
>>> >
>>>
>>> Looks like you didn't install the modules from the new kernel.
>>>
>>
>> I have installed modules via "make modules_install" and depmod as well.
>>
>>
>>>
>>> >    2. Looked into .config I have(generated via make menuconfig) and
>>> there
>>> >    isn't anything on IDEDISK. I cross checked config file that comes
>>> with xcp
>>> >    source code it has
>>> >    ...
>>> >    CONFIG_BLK_DEV_IDEDISK=m
>>> >    CONFIG_IDEDISK_MULTI_MODE=y
>>> >    ...
>>> >
>>>
>>> XCP default kernel is 2.6.27. You're trying to use 2.6.32.
>>> There might have been changes between the kernel versions.
>>>
>>> >    I copied above configs into my .config and when I run make(it asks
>>> some
>>> >    IDE config related questions ) and these configs are deleted after
>>> that. I
>>> >    have tried all options "y/n/m" to the questions and same result.
>>> >
>>> >    3. I downloaded .config file from
>>> >    [1]
>>> http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_32
>>> >
>>> >    there isn't IDEDISK config in it either and in addition "make
>>> tar-pkg"
>>> >    doesn't work with this .config file. I get following errors
>>> >
>>>
>>> If ide-disk module is not used/required anymore in 2.6.32, then you
>>> should
>>> remove it from /etc/modprobe.conf so that mkinitrd doesn't try to include
>>> it!
>>>
>>> (replace it with the proper new module name).
>>>
>>> >    DEPMOD  2.6.32
>>> >
>>> >    /bin/sh: line 1:  3341 Killed                  /sbin/depmod -ae -F
>>> >    System.map -b /root/kernel/linux-2.6.32/tar-install 2.6.32
>>> >    make[3]: *** [_modinst_post] Error 137
>>> >    make[2]: *** [sub-make] Error 2
>>> >    make[1]: *** [tar-pkg] Error 2
>>> >    make: *** [tar-pkg] Error 2
>>> >
>>> >    4. I tried with the vmlinuz and initrd image built from "2" above(I
>>> know
>>> >    initrd image is not correct, I just wanted to try) and I get
>>> >
>>> >    [0.000000] ERROR: Unable to locate IOAPIC for GSI 2
>>> >    [0.000000] ERROR: Unable to locate IOAPIC for GSI 9
>>> >    [0.000000] ERROR: Unable to locate IOAPIC for GSI 2
>>> >    [0.000000] ERROR: Unable to locate IOAPIC for GSI 9
>>> >    [0.493572] registering netback
>>> >    Red Hat nash version 5.1.19.6 starting
>>> >    einsmod: error inserting 'lib/ide-disk.ko': -1 Invalid module format
>>> >
>>>
>>> "Invalid module format" means it's from a different kernel and cannot be
>>> used with this kernel.
>>>
>>> >    indmos: error inserting '/lib/dm-region-hash.ko': -1 File Exists
>>> >    mount: could not fine filesystem '/dev/root'
>>> >    setuproot: moving /dev failed: No such file or directory
>>> >    setuproot: error mounting /proc: No such file or directory
>>> >    setuproot: error mounting /sys: No such file or directory
>>> >    switchroot: mount failed: No such file or directory
>>> >    [0.905987] Kernel panic - not syncing: Attempted to kill init!
>>> >
>>> >    Let me know how to proceed on this.
>>> >
>>>
>>> Install for example Fedora 12, or any other distro that has 2.6.32 kernel
>>> as a default, and check which modules are used for your hardware,
>>> then replace "ide-disk" in modprobe.conf with the actual module.
>>>
>>
>> Will look into it.
>>
>> Thanks
>>
>>>
>>> -- Pasi
>>>
>>>
>>> >    Thanks
>>> >
>>> >    On Mon, Apr 5, 2010 at 10:00 AM, Konrad Rzeszutek Wilk
>>> >    <[2]konrad.wilk@oracle.com> wrote:
>>> >
>>> >      On Mon, Apr 05, 2010 at 07:10:22AM -0700, Ritu kaur wrote:
>>> >      > Hello,
>>> >      >
>>> >      > Any inputs folks on xen debugs provided? dom0 crashes when
>>>  xen/next
>>> >      kernel
>>> >
>>> >      What you are hitting should have been fixed a week ago. Are you up
>>> to
>>> >      the latest in xen/next? Did you do 'git pull' ? Do you see this as
>>> the
>>> >      latest when you do 'git log | head':
>>> >
>>> >       git log | head -5
>>> >      commit 900f6d725874ca97c21cdc5a2c4e05bd62db4e86
>>> >      Merge: f2530fa 89689b1
>>> >      Author: Jeremy Fitzhardinge <[3]jeremy.fitzhardinge@citrix.com>
>>> >      Date:   Thu Apr 1 14:24:30 2010 -0700
>>> >
>>> > References
>>> >
>>> >    Visible links
>>> >    1.
>>> http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.10-pvops-dom0-xen-stable-x86_32
>>> >    2. mailto:konrad.wilk@oracle.com
>>> >    3. mailto:jeremy.fitzhardinge@citrix.com
>>>
>>> > _______________________________________________
>>> > Xen-devel mailing list
>>> > Xen-devel@lists.xensource.com
>>> > http://lists.xensource.com/xen-devel
>>>
>>>
>>
>

[-- Attachment #1.2: Type: text/html, Size: 10045 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Konrad Rzeszutek Wilk]

On Sun, Apr 11, 2010 at 10:11:40AM -0700, Ritu kaur wrote:
> Hello
> 
> Any inputs on backporting changes to xcp 2.6.27 source?

I've haven't looked at the 2.6.27 source (don't have the time).
The back-port might be as easy as just plucking in two or three
lines of code that pass in the
BIND_PIRQ__WILL_SHARE flag to the EVTCHNOP_bind_pirq hypercall.

But .. it might be much more complex where you will need to backport the
drivers/xen/events.c framework.

> 
> In addition, I had another question. I believe pci-passthrough works for
> pci-e slots as well. I have not tested it just wanted to check if any
> additional config changes are needed to make it work?

Yes. It should work.

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 1104 bytes --]

Thanks Konrad. The reason I am asking is if it is feasible and doable in a
reasonable amount of time(2 ~ 3 weeks of development/testing) I can check
with my boss if I could volunteer to do this work. I am not familiar with
2.6.27 code either but thought I could learn along with this.

Thanks

On Mon, Apr 12, 2010 at 7:04 AM, Konrad Rzeszutek Wilk <
konrad.wilk@oracle.com> wrote:

> On Sun, Apr 11, 2010 at 10:11:40AM -0700, Ritu kaur wrote:
> > Hello
> >
> > Any inputs on backporting changes to xcp 2.6.27 source?
>
> I've haven't looked at the 2.6.27 source (don't have the time).
> The back-port might be as easy as just plucking in two or three
> lines of code that pass in the
> BIND_PIRQ__WILL_SHARE flag to the EVTCHNOP_bind_pirq hypercall.
>
> But .. it might be much more complex where you will need to backport the
> drivers/xen/events.c framework.
>
> >
> > In addition, I had another question. I believe pci-passthrough works for
> > pci-e slots as well. I have not tested it just wanted to check if any
> > additional config changes are needed to make it work?
>
> Yes. It should work.
>

[-- Attachment #1.2: Type: text/html, Size: 1531 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Ian Campbell]

Backporting is usually pretty easy but it does somewhat depend on the
scope of the changesets you are backporting, do you have a list?

Please try and pickup complete upstream commits and include them in the
relevant place within the 2.6.27 patch queue (either the "Patches from
Linux Torvalds linux-2.6.git tree" or "Patches from xen.git" section I
guess) and sort plus name the patches as described in the section
headers.

Ian.

On Mon, 2010-04-12 at 23:14 +0100, Ritu kaur wrote:
> Thanks Konrad. The reason I am asking is if it is feasible and doable
> in a reasonable amount of time(2 ~ 3 weeks of development/testing) I
> can check with my boss if I could volunteer to do this work. I am not
> familiar with 2.6.27 code either but thought I could learn along with
> this.
> 
> Thanks
> 
> On Mon, Apr 12, 2010 at 7:04 AM, Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com> wrote:
>         On Sun, Apr 11, 2010 at 10:11:40AM -0700, Ritu kaur wrote:
>         > Hello
>         >
>         
>         > Any inputs on backporting changes to xcp 2.6.27 source?
>         
>         
>         I've haven't looked at the 2.6.27 source (don't have the
>         time).
>         The back-port might be as easy as just plucking in two or
>         three
>         lines of code that pass in the
>         BIND_PIRQ__WILL_SHARE flag to the EVTCHNOP_bind_pirq
>         hypercall.
>         
>         But .. it might be much more complex where you will need to
>         backport the
>         drivers/xen/events.c framework.
>         
>         >
>         > In addition, I had another question. I believe
>         pci-passthrough works for
>         > pci-e slots as well. I have not tested it just wanted to
>         check if any
>         > additional config changes are needed to make it work?
>         
>         
>         Yes. It should work.
> 

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 2394 bytes --]

Thanks Ian, I don't have the list. I looked into

http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Fjeremy%2Fxen.git&a=search&h=xen%2Fstable-2.6.32.x&st=commit&s=shared

I see couple of fixes that were committed for shared interrupts +
passthrough. I am not sure however it is confined to those commits. If I can
get a list of commits to fix shared interrupts I can take a look at patching
those into xcp source.

Thanks

On Tue, Apr 13, 2010 at 1:34 AM, Ian Campbell <Ian.Campbell@citrix.com>wrote:

> Backporting is usually pretty easy but it does somewhat depend on the
> scope of the changesets you are backporting, do you have a list?
>
> Please try and pickup complete upstream commits and include them in the
> relevant place within the 2.6.27 patch queue (either the "Patches from
> Linux Torvalds linux-2.6.git tree" or "Patches from xen.git" section I
> guess) and sort plus name the patches as described in the section
> headers.
>
> Ian.
>
> On Mon, 2010-04-12 at 23:14 +0100, Ritu kaur wrote:
> > Thanks Konrad. The reason I am asking is if it is feasible and doable
> > in a reasonable amount of time(2 ~ 3 weeks of development/testing) I
> > can check with my boss if I could volunteer to do this work. I am not
> > familiar with 2.6.27 code either but thought I could learn along with
> > this.
> >
> > Thanks
> >
> > On Mon, Apr 12, 2010 at 7:04 AM, Konrad Rzeszutek Wilk
> > <konrad.wilk@oracle.com> wrote:
> >         On Sun, Apr 11, 2010 at 10:11:40AM -0700, Ritu kaur wrote:
> >         > Hello
> >         >
> >
> >         > Any inputs on backporting changes to xcp 2.6.27 source?
> >
> >
> >         I've haven't looked at the 2.6.27 source (don't have the
> >         time).
> >         The back-port might be as easy as just plucking in two or
> >         three
> >         lines of code that pass in the
> >         BIND_PIRQ__WILL_SHARE flag to the EVTCHNOP_bind_pirq
> >         hypercall.
> >
> >         But .. it might be much more complex where you will need to
> >         backport the
> >         drivers/xen/events.c framework.
> >
> >         >
> >         > In addition, I had another question. I believe
> >         pci-passthrough works for
> >         > pci-e slots as well. I have not tested it just wanted to
> >         check if any
> >         > additional config changes are needed to make it work?
> >
> >
> >         Yes. It should work.
> >
>
>
>

[-- Attachment #1.2: Type: text/html, Size: 3302 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: domU guest for xcp 0.1.1

[Ian Campbell]

On Tue, 2010-04-13 at 23:06 +0100, Ritu kaur wrote:
> Thanks Ian, I don't have the list. I looked into
> 
> http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Fjeremy%
> 2Fxen.git&a=search&h=xen%2Fstable-2.6.32.x&st=commit&s=shared
> 
> I see couple of fixes that were committed for shared interrupts +
> passthrough. I am not sure however it is confined to those commits. If
> I can get a list of commits to fix shared interrupts I can take a look
> at patching those into xcp source.

Hmm, those patches seem to be largely to the event channel subsystem
which somewhat invalidates my suggestion that it is usually "pretty
easy" since the event channel stuff is a bit different in 2.6.27 and
pvops. Still it shouldn't be _that_ hard.

Ian.

> 
> Thanks
> 
> On Tue, Apr 13, 2010 at 1:34 AM, Ian Campbell
> <Ian.Campbell@citrix.com> wrote:
>         Backporting is usually pretty easy but it does somewhat depend
>         on the
>         scope of the changesets you are backporting, do you have a
>         list?
>         
>         Please try and pickup complete upstream commits and include
>         them in the
>         relevant place within the 2.6.27 patch queue (either the
>         "Patches from
>         Linux Torvalds linux-2.6.git tree" or "Patches from xen.git"
>         section I
>         guess) and sort plus name the patches as described in the
>         section
>         headers.
>         
>         Ian.
>         
>         
>         On Mon, 2010-04-12 at 23:14 +0100, Ritu kaur wrote:
>         > Thanks Konrad. The reason I am asking is if it is feasible
>         and doable
>         > in a reasonable amount of time(2 ~ 3 weeks of
>         development/testing) I
>         > can check with my boss if I could volunteer to do this work.
>         I am not
>         > familiar with 2.6.27 code either but thought I could learn
>         along with
>         > this.
>         >
>         > Thanks
>         >
>         > On Mon, Apr 12, 2010 at 7:04 AM, Konrad Rzeszutek Wilk
>         > <konrad.wilk@oracle.com> wrote:
>         >         On Sun, Apr 11, 2010 at 10:11:40AM -0700, Ritu kaur
>         wrote:
>         >         > Hello
>         >         >
>         >
>         >         > Any inputs on backporting changes to xcp 2.6.27
>         source?
>         >
>         >
>         >         I've haven't looked at the 2.6.27 source (don't have
>         the
>         >         time).
>         >         The back-port might be as easy as just plucking in
>         two or
>         >         three
>         >         lines of code that pass in the
>         >         BIND_PIRQ__WILL_SHARE flag to the EVTCHNOP_bind_pirq
>         >         hypercall.
>         >
>         >         But .. it might be much more complex where you will
>         need to
>         >         backport the
>         >         drivers/xen/events.c framework.
>         >
>         >         >
>         >         > In addition, I had another question. I believe
>         >         pci-passthrough works for
>         >         > pci-e slots as well. I have not tested it just
>         wanted to
>         >         check if any
>         >         > additional config changes are needed to make it
>         work?
>         >
>         >
>         >         Yes. It should work.
>         >
>         
>         
>         
> 

Re: domU guest for xcp 0.1.1

[Pasi Kärkkäinen]

On Sat, Mar 27, 2010 at 06:32:00PM -0700, Ritu kaur wrote:
>    Thanks Pasi. I had used following command to regenerate initrd image in
>    xcp ddk
> 
>    mkinitrd -f ./initrd-2.6.32.img  2.6.27.42-0.1.1.xs0.1.1.737.1065xen
> 

Uhm.. this is wrong.

If you want to generate initrd image for 2.6.32 kernel, then you need to do it like this:
mkinitrd initrd-2.6.32.img 2.6.32

>    it doesn't work either. While booting screen goes blank immediately after
>    I see
> 

Do you have "console=hvc0 earlyprintk=xen nomodeset" parameters for the pvops dom0 kernel? 

-- Pasi

>    ...
>     Booting:MBI=0x00010120, entry=0x00100000
> 
>    and next thing I see is BIOS setup, so not sure connecting serial cable
>    will reveal anything more. Inputs appreciated.
> 
>    Thanks
> 
>    On Sat, Mar 27, 2010 at 11:43 AM, Pasi Kärkkäinen <[1]pasik@iki.fi> wrote:
> 
>      On Sat, Mar 27, 2010 at 11:28:12AM -0700, Ritu kaur wrote:
>      >    Any inputs on this? I compiled xen/next kernel in Debian Lenny and
>      booted
>      >    successfully as a domU(I am using same .config file which I used to
>      build
>      >    under xcp-ddk). Looks to me xen/next doesn't work with xcp0.1.1.
>      >
> 
>      You need to re-generate the dom0 kernel initrd to match your kernel.
>      You cannot use the default xcp initrd image.
> 
>      Please provide the full serial console boot log so we can troubleshoot
>      it:
>      [2]http://wiki.xensource.com/xenwiki/XenSerialConsole
> 
>      -- Pasi
> 
>      >    Thanks
>      >
>      >    On Fri, Mar 26, 2010 at 12:11 PM, Ritu kaur
>      <[1][3]ritu.kaur.us@[2][4]gmail.com>
>      >    wrote:
>      >
>      >      Hi Pasi,
>      >
>      >      Messages seen with not-working case
>      >
>      >
>       /***********************************************************************************
>      >      kernel:/boot/xen.3.4.3.gz dom0-mem=752M lowmem-emergency-pool=1M
>      >      crashkernel=64M@32M console=comX vga=mode-0x0311
>      >      loading /boot/xen.3.4.3.gz..........
>      >      Module:/boot/vmlinuz-2.6.32 root=LABEL=root-mhycetek ro
>      Xencons=hvc
>      >      console=hvc0 console=tty0 quiet vga=785 splash
>      >      Loading /boot/vmlinuz-2.6.32.........
>      >      Module:/boot/initrd-2.6-xen.img
>      >      Loading
>      >
>       /boot/initrd-2.6-xen.img...............................................................................................
>      >      Booting:MBI=0x00010120, entry=0x00100000
>      >
>       ***************************************************************************************/
>      >
>      >      Screen is blank after these messages and system returns to BIOS
>      setup.
>      >
>      >      Messages seen with working case
>      >
>       /***********************************************************************************
>      >      kernel:/boot/xen.gz dom0-mem=752M lowmem-emergency-pool=1M
>      >      crashkernel=64M@32M comsole=comX vga=mode-0x0311
>      >      loading /boot/xen.gz..........
>      >      Module:/boot/vmlinuz-2.6.xen root=LABEL=root-mhycetek ro
>      Xencons=hvc
>      >      console=hvc0 console=tty0 quiet vga=785 splash
>      >      Loading /boot/vmlinuz-2.6.xen.........
>      >      Module:/boot/initrd-2.6-xen.img
>      >      Loading
>      >
>       /boot/initrd-2.6-xen.img...............................................................................................
>      >      Booting:MBI=0x00010120, entry=0x00100000
>      >
>       ***************************************************************************************/
>      >
>      >      Versions used in Non-working case
>      >
>      >      xen - 3.4.3/4.0.0
>      >      kernel - xen/next
>      >      initrd - default one which came with xcp0.1.1 download.(Ps note,
>      in xcp
>      >      ddk cannot build initrd image)
>      >
>      >      in Working case
>      >
>      >      xen - 3.4.2
>      >      kernel - xcp 0.1.1
>      >      initrd - one that came with xcp 0.1.1
>      >
>      >      Checked in my .config and changed CONFIG_PHYSICAL_START to
>      0x00100000
>      >      and CONFIG_PHYSICAL_ALIGN=0x100000, didn't help.
>      >
>      >      Inputs appreciated.
>      >
>      >      Thanks
>      >
>      > References
>      >
>      >    Visible links
>      >    1. [5]http://ritu.kaur.us/
>      >    2. [6]http://gmail.com/
> 
>      > _______________________________________________
>      > Xen-devel mailing list
>      > [7]Xen-devel@lists.xensource.com
>      > [8]http://lists.xensource.com/xen-devel
> 
> References
> 
>    Visible links
>    1. mailto:pasik@iki.fi
>    2. http://wiki.xensource.com/xenwiki/XenSerialConsole
>    3. http://ritu.kaur.us/
>    4. http://gmail.com/
>    5. http://ritu.kaur.us/
>    6. http://gmail.com/
>    7. mailto:Xen-devel@lists.xensource.com
>    8. http://lists.xensource.com/xen-devel

Re: domU guest for xcp 0.1.1

[Ritu kaur]

[-- Attachment #1.1: Type: text/plain, Size: 1104 bytes --]

> 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
>
>
Hi Ian,

Currently, I have to reboot dom0 when I use

xe vm-param-set uuid=<vm-uuid> other-config:pci=<pci-bfd>  for pci
passthrough.

I looked at above bind/unbind files and they are present in
/sys/bus/pci/drivers/<driver_name>/. Currently my driver is not loaded in
dom0(not intended to load in dom0 due to passthrough) so I don't think I
need to unbind. I did echo -n $pcidev > /sys/bus/pci/drivers/pciback/bind
and I get

-bash: echo: write error: No such device

Currently, only way passthrough is enabled in domU is reboot of dom0 and
domU after xe vm-param-set...

Kindly let me know if there is a way to avoid reboot.

Thanks

[-- Attachment #1.2: Type: text/html, Size: 1507 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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