WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] domU guest for xcp 0.1.1

To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Subject: Re: [Xen-devel] domU guest for xcp 0.1.1
From: Ritu kaur <ritu.kaur.us@xxxxxxxxx>
Date: Mon, 15 Mar 2010 06:42:30 -0700
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 15 Mar 2010 06:43:26 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=12SHa/uzUsMhGf2dIIiqE3InmoiNcqsT/QRk255Il+c=; b=A9nQw4sPCx18fPm0FDZb4ux4+jLjrQbgVUwJuGH/l8bpoeHKbFJeYzmN6iKw0G8FST nc6T08drrRPH261+isIjYWdDmB4UADzhQAYvDtf6bICIUl0jV6vCiSXA/ovBcr9AOjhQ ySFeDoEgrrlddo5ZMlAfvWOW1suA5OuyeKn7Q=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=hNK/ddubOd3XQXM3ycFtzR6lLQEVJB0lheBEsA1+3v0QlYyys+rVo81fVgIm7UltSO yvtnJhiFdo/Pmi9WM59epJm+kI+IYuvClomNMthp8BnvSM3nNt9LhN0du34V+uQu+xv2 IkmDUsoLM261Rq3JDhZAHdz0VJTa7W0Iy6Ry0=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1268642688.8652.2792.camel@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <29b32d341003120910l5340bc01tcada3ca2adbaf763@xxxxxxxxxxxxxx> <29b32d341003130809u49d1edcas234fdca4c3d70ed@xxxxxxxxxxxxxx> <20100313164102.GZ1878@xxxxxxxxxxx> <29b32d341003131743j6ae271d6of486a3c1a4858513@xxxxxxxxxxxxxx> <112460240.20100314121540@xxxxxxxxxxxxxx> <29b32d341003141329v3c6a73c0y8030cf3c6736634c@xxxxxxxxxxxxxx> <1056770753.20100314215224@xxxxxxxxxxxxxx> <29b32d341003141840x5a55e74sfb2eda56005e4f84@xxxxxxxxxxxxxx> <29b32d341003142030p1fe511d2ke30b8483ff8cc368@xxxxxxxxxxxxxx> <1268642688.8652.2792.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxx> 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@xxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxx>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@xxxxxxxxxxxxxx
>                 >>
>                 >>
>
>
>
>
>                 --
>
>                 Best regards,
>                  Sander
>                  mailto:linux@xxxxxxxxxxxxxx
>
>
>
>
>



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