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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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
>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
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_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2010-Mar-14 09:04 UTC
Re: [Xen-devel] pvops xen/master and xen/stable domU kernel compilation errors
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. >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 >> >> >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 > > > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 > > > > > > > > > > > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 > > > > > > > > > > > > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 > > > > > > > > > > > > > > > > > > > > > > > > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 >> > > >> > > >> > > >> > > >> > > >> > >> > >> > >> > >> >> >> >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
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
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
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 > > > > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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
> >
> >
> >
> >
> >
> >
>
>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
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. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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. > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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. > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> > 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). _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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). >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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. >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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. >> > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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. >>> >> >> >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 >> >> >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 portto 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 >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 >> > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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?) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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?) >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> 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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 >> > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 >>> >> >> >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 kernelWhat 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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 >> >> >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 >>> >>> >> >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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. >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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. >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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. > > > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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. > > > > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel