Just to add, this driver compiles fine in other linux flavors(Debian Lenny 5.0, Citrix Xenserver...) so it has to do with Xen/stable. Didn't see anything related to this in xen-devel, inputs appreciated. Thanks On Sun, Mar 14, 2010 at 6:40 PM, Ritu kaur wrote: > Hi Pasi, > > I am able to use xen/stable kernel in domU(debian lenny) and lspci lists > the device(i am testing pci passthrough). however, when I compile my driver > in domU I get > > struct net_device has no member named open > struct net_device has no member named stop > struct net_device has no member named hard_start_xmit > ... > > I need to compile my driver in domU and load it in order to use the nic > from domU. Inputs appreciated. > > Thanks > > > On Sun, Mar 14, 2010 at 1:52 PM, Sander Eikelenboom wrote: > >> Hello Ritu, >> >> I don't have experience with XCP specifically, but normal compiled >> pvops-kernels work fine for me with Debian lenny domU's. >> >> -- >> Sander >> >> Sunday, March 14, 2010, 9:29:29 PM, you wrote: >> >> > Hi Sander, >> >> > Thanks, I enabled DOM0 and other backend drivers along with pci frontend >> in >> > .config file. I am able to get it build. However, I having additional >> > questions, inputs appreciated. >> >> > 1. can this kernel be used in any linux distribution? I have Debian >> Lenny as >> > DomU? >> >> > 2. In Debian Lenny /boot/grub/menu.lst, I have >> > title Debian GNU/Linux, kernel 2.6.26-2-686-bigmem >> > root (hd0,0) >> > kernel /boot/vmlinuz-2.6.26-2-686-bigmem root=/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 >> >> >