From: Ritu kaur <ritu.kaur.us@gmail.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: domU guest for xcp 0.1.1
Date: Mon, 15 Mar 2010 19:04:54 -0700 [thread overview]
Message-ID: <29b32d341003151904m2a992be5s74697d6047b864c6@mail.gmail.com> (raw)
In-Reply-To: <29b32d341003150646o4d215dfel1c2a2bc6d287edc@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 14134 bytes --]
Thanks Ian and Pasi, it took me much less time than I had thought to fix
drivers and I am able to see nic interfaces via ifconfig. I am yet to test
ping and other stuff. Had couple of questions
1. I used xe vm-param-clear uuid=<uuid-of-vm> param-name=other-config on
dom0 and rebooted domU assuming dom0 will get back pci device. It didn't. I
had to reboot dom0 in order to unhook pci device from domU. Is this the way
it is supposed to work?
2. Unrelated to pci passthrough, xen/stable code I downloaded doesn't seem
to have netfront drivers or any front drivers, doesn't it come by default
when you download from xen/stable?
Thanks
On Mon, Mar 15, 2010 at 6:46 AM, Ritu kaur <ritu.kaur.us@gmail.com> wrote:
> Thanks Ian, I will take a look at it.
>
>
> On Mon, Mar 15, 2010 at 6:44 AM, Ian Campbell <Ian.Campbell@citrix.com>wrote:
>
>> On Mon, 2010-03-15 at 13:42 +0000, Ritu kaur wrote:
>> > Hi Ian,
>> >
>> > Thanks. Should I use DDK to compile my drivers? I have pci device
>> > listed in domU and drivers are not compilable there hence wondering
>> > how do I use the it?
>>
>> You must compile your driver against the kernel used in the domU. This
>> is not a Xen specific requirement -- you must always compile your driver
>> against the kernel you want to use it with. Note that this may involve
>> porting your driver to work with the kernel you are using in your domU.
>>
>> Ian.
>>
>> >
>> > Thanks
>> >
>> > On Mon, Mar 15, 2010 at 1:44 AM, Ian Campbell
>> > <Ian.Campbell@citrix.com> wrote:
>> > On Mon, 2010-03-15 at 03:30 +0000, Ritu kaur wrote:
>> > > Just to add, this driver compiles fine in other linux
>> > flavors(Debian
>> > > Lenny 5.0, Citrix Xenserver...) so it has to do with
>> > Xen/stable.
>> > > Didn't see anything related to this in xen-devel, inputs
>> > appreciated.
>> >
>> >
>> > This is because the pvops kernel is based on a much newer
>> > upstream
>> > kernel (2.6.31 or 32) than that found in Lenny (2.6.26) or
>> > Citrix
>> > XenServer (2.6.18/27) and some of the kernel's internal
>> > interfaces must
>> > have changed.
>> >
>> > This has nothing to do with Xen per-se but rather
>> > compatibility with
>> > different Linux kernels.
>> >
>> > Ian.
>> >
>> >
>> > >
>> > > Thanks
>> > >
>> > > On Sun, Mar 14, 2010 at 6:40 PM, Ritu kaur
>> > <ritu.kaur.us@gmail.com>
>> > > wrote:
>> > > Hi Pasi,
>> > >
>> > > I am able to use xen/stable kernel in domU(debian
>> > lenny) and
>> > > lspci lists the device(i am testing pci
>> > passthrough). however,
>> > > when I compile my driver in domU I get
>> > >
>> > > struct net_device has no member named open
>> > > struct net_device has no member named stop
>> > > struct net_device has no member named
>> > hard_start_xmit
>> > > ...
>> > >
>> > > I need to compile my driver in domU and load it in
>> > order to
>> > > use the nic from domU. Inputs appreciated.
>> > >
>> > > Thanks
>> > >
>> > >
>> > >
>> > > On Sun, Mar 14, 2010 at 1:52 PM, Sander Eikelenboom
>> > > <linux@eikelenboom.it> wrote:
>> > > Hello Ritu,
>> > >
>> > > I don't have experience with XCP
>> > specifically, but
>> > > normal compiled pvops-kernels work fine for
>> > me with
>> > > Debian lenny domU's.
>> > >
>> > > --
>> > > Sander
>> > >
>> > >
>> > > Sunday, March 14, 2010, 9:29:29 PM, you
>> > wrote:
>> > >
>> > > > Hi Sander,
>> > >
>> > > > Thanks, I enabled DOM0 and other backend
>> > drivers
>> > > along with pci frontend in
>> > > > .config file. I am able to get it build.
>> > However, I
>> > > having additional
>> > > > questions, inputs appreciated.
>> > >
>> > > > 1. can this kernel be used in any linux
>> > > distribution? I have Debian Lenny as
>> > > > DomU?
>> > >
>> > > > 2. In Debian Lenny /boot/grub/menu.lst, I
>> > have
>> > > > title Debian GNU/Linux, kernel
>> > > 2.6.26-2-686-bigmem
>> > > > root (hd0,0)
>> > > > kernel
>> > /boot/vmlinuz-2.6.26-2-686-bigmem
>> > > root=/dev/xvda1 ro
>> > > > console=hvc0 quiet
>> > > > initrd
>> > /boot/initrd.img-2.6.26-2-686-bigmem
>> > >
>> > > > but the kernel image built in
>> > arch/i386/boot is
>> > > bzImage. Does "make
>> > > > modules_install" and "make install" take
>> > care of it,
>> > > since I am not sure I
>> > > > haven't tried it.
>> > >
>> > > > Basically, my question boils down to
>> > >
>> > > > 1. Can I use bzImage in debian lenny,
>> > > > 2. does make install take care of
>> > configuring it
>> > >
>> > >
>> > > > Thanks
>> > >
>> > > > On Sun, Mar 14, 2010 at 4:15 AM, Sander
>> > Eikelenboom
>> > > <linux@eikelenboom.it>wrote:
>> > >
>> > > >> Hello Ritu,
>> > > >>
>> > > >> There are some problems with pci.h, i
>> > have also
>> > > reported this to Konrad.
>> > > >> As a workaround you can enable dom0
>> > support in
>> > > these kernels, then they
>> > > >> compile fine in my case.
>> > > >>
>> > > >> --
>> > > >>
>> > > >> Sander
>> > > >>
>> > > >>
>> > > >> Sunday, March 14, 2010, 2:43:23 AM, you
>> > wrote:
>> > > >>
>> > > >> > I followed the steps mentioned in wiki
>> > to pull
>> > > xen code to compile domU
>> > > >> > kernel from
>> > > >>
>> > > >> > 1. xen/master, I get following
>> > compilation
>> > > errors. I do see in xen-devel
>> > > >> > forum someone else has reported similar
>> > issue but
>> > > no solution yet(patch
>> > > >> > provided by Konrad has followup errors)
>> > > >>
>> > > >> > CC [M] drivers/watchdog/machzwd.o
>> > > >> > CC [M] drivers/watchdog/sbc_epx_c3.o
>> > > >> > CC [M] drivers/watchdog/softdog.o
>> > > >> > CC drivers/xen/grant-table.o
>> > > >> > CC drivers/xen/features.o
>> > > >> > CC drivers/xen/events.o
>> > > >> > drivers/xen/events.c:605: error:
>> > redefinition of
>> > > ‘xen_destroy_irq’
>> > > >>
>> > >
>> > > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29:
>> error:
>> > > >> > previous definition of â
>> > €˜xen_destroy_irq’ was
>> > > here
>> > > >> > drivers/xen/events.c:637: error:
>> > redefinition of
>> > > ‘xen_create_msi_irq’
>> > > >>
>> > >
>> > > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25:
>> error:
>> > > >> > previous definition of â
>> > €˜xen_create_msi_irq’
>> > > was here
>> > > >> > make[2]: *** [drivers/xen/events.o]
>> > Error 1
>> > > >> > make[1]: *** [drivers/xen] Error 2
>> > > >> > make: *** [drivers] Error 2
>> > > >>
>> > > >> > 2. xen/stable, I get following errors
>> > > >>
>> > > >> > CC drivers/pci/xen-pcifront.o
>> > > >> > drivers/pci/xen-pcifront.c:373: error:
>> > variable â
>> > > €˜pci_frontend_ops’
>> > > >> has
>> > > >> > initializut incomplete type
>> > > >> > drivers/pci/xen-pcifront.c:374: error:
>> > unknown
>> > > field ‘enable_msi’
>> > > >> > specified in ializer
>> > > >> > drivers/pci/xen-pcifront.c:374:
>> > warning: excess
>> > > elements in struct
>> > > >> > initializer
>> > > >> > drivers/pci/xen-pcifront.c:374:
>> > warning: (near
>> > > initialization for
>> > > >> > ‘pci_frontend_op)’
>> > > >> > drivers/pci/xen-pcifront.c:375: error:
>> > unknown
>> > > field ‘disable_msi’
>> > > >> > specified in ializer
>> > > >> > drivers/pci/xen-pcifront.c:375:
>> > warning: excess
>> > > elements in struct
>> > > >> > initializer
>> > > >> > drivers/pci/xen-pcifront.c:375:
>> > warning: (near
>> > > initialization for
>> > > >> > ‘pci_frontend_op)’
>> > > >> > drivers/pci/xen-pcifront.c:376: error:
>> > unknown
>> > > field ‘enable_msix’
>> > > >> > specified in ializer
>> > > >> > drivers/pci/xen-pcifront.c:376:
>> > warning: excess
>> > > elements in struct
>> > > >> > initializer
>> > > >> > drivers/pci/xen-pcifront.c:376:
>> > warning: (near
>> > > initialization for
>> > > >> > ‘pci_frontend_op)’
>> > > >> > drivers/pci/xen-pcifront.c:377: error:
>> > unknown
>> > > field ‘disable_msix’
>> > > >> > specified intializer
>> > > >> > drivers/pci/xen-pcifront.c:377:
>> > warning: excess
>> > > elements in struct
>> > > >> > initializer
>> > > >> > drivers/pci/xen-pcifront.c:377:
>> > warning: (near
>> > > initialization for
>> > > >> > ‘pci_frontend_op)’
>> > > >> > drivers/pci/xen-pcifront.c: In function
>> > â
>> > > €˜pci_frontend_registrar’:
>> > > >> > drivers/pci/xen-pcifront.c:383: error:
>> > â
>> > > €˜xen_pci_frontend’ undeclared
>> > > >> > (first use his function)
>> > > >> > drivers/pci/xen-pcifront.c:383: error:
>> > (Each
>> > > undeclared identifier is
>> > > >> > reported only once
>> > > >> > drivers/pci/xen-pcifront.c:383: error:
>> > for each
>> > > function it appears in.)
>> > > >> > make[2]: ***
>> > [drivers/pci/xen-pcifront.o] Error 1
>> > > >> > make[1]: *** [drivers/pci] Error 2
>> > > >> > make: *** [drivers] Error 2
>> > > >>
>> > > >> > Kindly let me know how to proceed on
>> > this.
>> > > >>
>> > > >> > Thanks
>> > > >>
>> > > >>
>> > > >>
>> > > >> --
>> > > >> Best regards,
>> > > >> Sander
>> > > mailto:linux@eikelenboom.it
>> > > >>
>> > > >>
>> > >
>> > >
>> > >
>> > >
>> > > --
>> > >
>> > > Best regards,
>> > > Sander
>> > > mailto:linux@eikelenboom.it
>> > >
>> > >
>> > >
>> > >
>> > >
>> >
>> >
>> >
>> >
>>
>>
>>
>
[-- Attachment #1.2: Type: text/html, Size: 17835 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-03-16 2:04 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 17:10 domU guest for xcp 0.1.1 Ritu kaur
2010-03-12 17:51 ` Pasi Kärkkäinen
2010-03-13 1:51 ` Ritu kaur
2010-03-13 11:18 ` Pasi Kärkkäinen
2010-03-13 16:09 ` Ritu kaur
2010-03-13 16:41 ` Pasi Kärkkäinen
2010-03-14 1:43 ` Ritu kaur
2010-03-14 9:04 ` pvops xen/master and xen/stable domU kernel compilation errors Pasi Kärkkäinen
2010-03-14 11:15 ` domU guest for xcp 0.1.1 Sander Eikelenboom
2010-03-14 20:29 ` Ritu kaur
2010-03-14 20:52 ` Sander Eikelenboom
2010-03-15 1:40 ` Ritu kaur
2010-03-15 3:30 ` Ritu kaur
2010-03-15 8:44 ` Ian Campbell
2010-03-15 13:42 ` Ritu kaur
2010-03-15 13:44 ` Ian Campbell
2010-03-15 13:46 ` Ritu kaur
2010-03-16 2:04 ` Ritu kaur [this message]
2010-03-16 7:37 ` Ian Campbell
2010-03-16 15:23 ` Pasi Kärkkäinen
2010-03-16 23:25 ` Ritu kaur
2010-03-17 18:44 ` Ritu kaur
2010-03-18 9:17 ` Ian Campbell
2010-03-18 13:43 ` Ritu kaur
2010-03-18 14:11 ` Ian Campbell
2010-03-18 14:23 ` Ritu kaur
2010-03-18 14:27 ` Ian Campbell
2010-03-18 14:32 ` Ian Campbell
2010-03-18 14:39 ` Konrad Rzeszutek Wilk
2010-03-18 15:28 ` Ritu kaur
2010-03-18 16:26 ` Konrad Rzeszutek Wilk
2010-03-19 15:27 ` Ritu kaur
2010-03-21 1:50 ` Ritu kaur
2010-03-21 17:22 ` Ritu kaur
2010-03-21 18:41 ` Pasi Kärkkäinen
2010-03-21 21:21 ` Ritu kaur
2010-03-22 8:58 ` Pasi Kärkkäinen
2010-03-22 21:02 ` Ritu kaur
2010-03-22 21:09 ` Pasi Kärkkäinen
2010-03-23 20:21 ` Ritu kaur
2010-03-26 19:11 ` Ritu kaur
2010-03-27 18:28 ` Ritu kaur
2010-03-27 18:43 ` Pasi Kärkkäinen
2010-03-28 1:32 ` Ritu kaur
2010-03-28 3:21 ` Ritu kaur
2010-03-28 11:34 ` Pasi Kärkkäinen
2010-03-28 11:55 ` Pasi Kärkkäinen
2010-03-31 0:28 ` Ritu kaur
2010-03-31 1:07 ` Ritu kaur
2010-03-31 6:30 ` Pasi Kärkkäinen
2010-03-31 13:15 ` Ritu kaur
2010-03-31 13:42 ` Konrad Rzeszutek Wilk
2010-03-31 13:55 ` Ritu kaur
2010-03-31 14:39 ` Pasi Kärkkäinen
2010-03-31 21:10 ` Ritu kaur
2010-04-01 12:48 ` Ritu kaur
2010-04-05 14:10 ` Ritu kaur
2010-04-05 17:00 ` Konrad Rzeszutek Wilk
2010-04-06 4:00 ` Ritu kaur
2010-04-06 6:03 ` Pasi Kärkkäinen
2010-04-06 13:31 ` Ritu kaur
2010-04-09 15:53 ` Ritu kaur
2010-04-11 17:11 ` Ritu kaur
2010-04-12 14:04 ` Konrad Rzeszutek Wilk
2010-04-12 22:14 ` Ritu kaur
2010-04-13 8:34 ` Ian Campbell
2010-04-13 22:06 ` Ritu kaur
2010-04-14 8:48 ` Ian Campbell
2010-03-28 11:33 ` Pasi Kärkkäinen
2010-03-31 23:23 ` Ritu kaur
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=29b32d341003151904m2a992be5s74697d6047b864c6@mail.gmail.com \
--to=ritu.kaur.us@gmail.com \
--cc=Ian.Campbell@citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).