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

Thanks

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

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

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

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

Thanks


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

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

--
Sander

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

> Hi Sander,

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

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

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

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

> Basically, my question boils down to

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


> Thanks

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

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



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



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