Xen devel - Sep 2009 - newer dom0 kernel

Some weeks (months?) back I think I remember discussion about starting
to focus on a newer Linux kernel for dom0, and about a hg tree for it,
but now I can''t find the discussion. Is there a hg tree for this yet or
did I imagine the whole thing?

Thanks

James

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

On Tue, Sep 22, 2009 at 08:05:55PM +1000, James Harper
wrote:
> Some weeks (months?) back I think I remember discussion about starting
> to focus on a newer Linux kernel for dom0, and about a hg tree for it,
> but now I can''t find the discussion. Is there a hg tree for this
yet or
> did I imagine the whole thing?
> 
xen-unstable switched to using pv_ops dom0 kernel (git tree).

Or did you mean the talks about community supported xenlinux
forward-port tree, based on the novell/opensuse patches?

-- Pasi


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

On Tuesday 22 September 2009 14:10:09 Pasi Kärkkäinen
wrote:
> On Tue, Sep 22, 2009 at 08:05:55PM +1000, James Harper wrote:
> > Some weeks (months?) back I think I remember discussion about starting
> > to focus on a newer Linux kernel for dom0, and about a hg tree for it,
> > but now I can''t find the discussion. Is there a hg tree for
this yet or
> > did I imagine the whole thing?
>
> xen-unstable switched to using pv_ops dom0 kernel (git tree).
From which version will the mainstream kernel have dom0 support?
Every time I check it only has domU support.

Thanks,

Joost

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

On Tue, Sep 22, 2009 at 02:44:19PM +0200, J. Roeleveld
wrote:
> On Tuesday 22 September 2009 14:10:09 Pasi Kärkkäinen wrote:
> > On Tue, Sep 22, 2009 at 08:05:55PM +1000, James Harper wrote:
> > > Some weeks (months?) back I think I remember discussion about
starting
> > > to focus on a newer Linux kernel for dom0, and about a hg tree
for it,
> > > but now I can''t find the discussion. Is there a hg tree
for this yet or
> > > did I imagine the whole thing?
> >
> > xen-unstable switched to using pv_ops dom0 kernel (git tree).
> 
> From which version will the mainstream kernel have dom0 support?
> Every time I check it only has domU support.
> 
Well, pv_ops based dom0 patches are still under development to get them
less intrusive and acceptable to upstream Linux kernel.

If you want to help feel free to contribute. Just a couple of days ago 
Jeremy announced the new xen/master tree, which people should test,
and hopefully send patches against.

This is the work that will be sent for upstream inclusion later.

-- Pasi


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

If I run: hg clone http://xenbits.xensource.com/xen-unstable.hg  I''ll
get
the most recent work? with the latest pvops dom0? Linux 2.6.31?
2009/9/22 Pasi Kärkkäinen <pasik@iki.fi>
> On Tue, Sep 22, 2009 at 02:44:19PM +0200, J. Roeleveld wrote:
> > On Tuesday 22 September 2009 14:10:09 Pasi Kärkkäinen wrote:
> > > On Tue, Sep 22, 2009 at 08:05:55PM +1000, James Harper wrote:
> > > > Some weeks (months?) back I think I remember discussion
about
> starting
> > > > to focus on a newer Linux kernel for dom0, and about a hg
tree for
> it,
> > > > but now I can''t find the discussion. Is there a hg
tree for this yet
> or
> > > > did I imagine the whole thing?
> > >
> > > xen-unstable switched to using pv_ops dom0 kernel (git tree).
> >
> > From which version will the mainstream kernel have dom0 support?
> > Every time I check it only has domU support.
> >
>
> Well, pv_ops based dom0 patches are still under development to get them
> less intrusive and acceptable to upstream Linux kernel.
>
> If you want to help feel free to contribute. Just a couple of days ago
> Jeremy announced the new xen/master tree, which people should test,
> and hopefully send patches against.
>
> This is the work that will be sent for upstream inclusion later.
>
> -- Pasi
>
>
> _______________________________________________
> 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, Sep 22, 2009 at 10:49:01AM -0300, Thiago Camargo Martins Cordeiro
wrote:
> If I run: hg clone http://xenbits.xensource.com/xen-unstable.hg 
I''ll get
> the most recent work? with the latest pvops dom0? Linux 2.6.31?
I''m not sure if xen-unstable.hg points to the latest git tree yet?
Keir?

You can always get the latest git dom0 kernel tree based on the
instruction here:
http://wiki.xensource.com/xenwiki/XenParavirtOps

-- Pasi


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

Gotcha!

 To make use of the latest pv_ops dom0 need I the xen-unstable tree?
 Or can I use the Xen 3.4.1 / 3.3.2 from xen.org?

Thanks!
Thiago

2009/9/22 Pasi Kärkkäinen <pasik@iki.fi>
> On Tue, Sep 22, 2009 at 10:49:01AM -0300, Thiago Camargo Martins Cordeiro
> wrote:
> > If I run: hg clone http://xenbits.xensource.com/xen-unstable.hg 
I''ll
> get
> > the most recent work? with the latest pvops dom0? Linux 2.6.31?
>
> I''m not sure if xen-unstable.hg points to the latest git tree yet?
Keir?
>
> You can always get the latest git dom0 kernel tree based on the
> instruction here:
> http://wiki.xensource.com/xenwiki/XenParavirtOps
>
> -- Pasi
>
>

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

On 09/22/09 16:26, Thiago Camargo Martins Cordeiro
wrote:
> Gotcha!
>
>  To make use of the latest pv_ops dom0 need I the xen-unstable tree?
>  Or can I use the Xen 3.4.1 / 3.3.2 from xen.org <http://xen.org>?
There''s no close tie between dom0 and Xen itself; it should work with
any fairly recent version of Xen (and if it doesn''t that''s
interesting
information).

    J

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

On Tue, Sep 22, 2009 at 04:28:56PM -0700, Jeremy Fitzhardinge
wrote:
> On 09/22/09 16:26, Thiago Camargo Martins Cordeiro wrote:
> > Gotcha!
> >
> >  To make use of the latest pv_ops dom0 need I the xen-unstable tree?
> >  Or can I use the Xen 3.4.1 / 3.3.2 from xen.org
<http://xen.org>?
> 
> There''s no close tie between dom0 and Xen itself; it should work
with
> any fairly recent version of Xen (and if it doesn''t
that''s interesting
> information).
> 
Works for me with Xen 3.4.1 hypervisor.

Earlier I used it with Xen 3.3.1.

-- Pasi


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

On Wed, Sep 23, 2009 at 09:52:37AM +0300, Pasi Kärkkäinen
wrote:
> On Tue, Sep 22, 2009 at 04:28:56PM -0700, Jeremy Fitzhardinge wrote:
> > On 09/22/09 16:26, Thiago Camargo Martins Cordeiro wrote:
> > > Gotcha!
> > >
> > >  To make use of the latest pv_ops dom0 need I the xen-unstable
tree?
> > >  Or can I use the Xen 3.4.1 / 3.3.2 from xen.org
<http://xen.org>?
> > 
> > There''s no close tie between dom0 and Xen itself; it should
work with
> > any fairly recent version of Xen (and if it doesn''t
that''s interesting
> > information).
> > 
> 
> Works for me with Xen 3.4.1 hypervisor.
> 
> Earlier I used it with Xen 3.3.1.
> 
.. but I forgot to mention that 3.3.1 needs some extra (backported) patches.

So Xen 3.4.x or newer is a safe choise.

See: http://wiki.xensource.com/xenwiki/XenParavirtOps

-- Pasi


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

> 
> So Xen 3.4.x or newer is a safe choise.
> 
> See: http://wiki.xensource.com/xenwiki/XenParavirtOps
> 
Following instructions there:

To check out a working tree, use:

$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
linux-2.6-xen
$ cd linux-2.6-xen
$ git checkout origin/xen/master -b xen/master

The last line says "fatal: A branch named ''xen/master''
already exists."

Is this a problem? I think the wiki should at least mention it...

Thanks

James

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

On Wed, Sep 23, 2009 at 06:46:32PM +1000, James Harper
wrote:
> > 
> > So Xen 3.4.x or newer is a safe choise.
> > 
> > See: http://wiki.xensource.com/xenwiki/XenParavirtOps
> > 
> 
> Following instructions there:
> 
> To check out a working tree, use:
> 
> $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
linux-2.6-xen
> $ cd linux-2.6-xen
> $ git checkout origin/xen/master -b xen/master
> 
> The last line says "fatal: A branch named
''xen/master'' already exists."
> 
> Is this a problem? I think the wiki should at least mention it...
>
Actually I removed that ''git checkout origin/xen/master -b
xen/master''
from the Wiki page yesterday.. 

It seems it''s not needed anymore.

-- Pasi


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

> > > See: http://wiki.xensource.com/xenwiki/XenParavirtOps
> > >
> >
> > Following instructions there:
> >
> > To check out a working tree, use:
> >
> > $ git clone
git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> linux-2.6-xen
> > $ cd linux-2.6-xen
> > $ git checkout origin/xen/master -b xen/master
> >
> > The last line says "fatal: A branch named
''xen/master'' already exists."
> >
> > Is this a problem? I think the wiki should at least mention it...
> >
> 
> Actually I removed that ''git checkout origin/xen/master -b
xen/master''
> from the Wiki page yesterday..
> 
> It seems it''s not needed anymore.
> 
Hehe. I had the page open in my browser since yesterday and have only just had
time now to go through and do the checkout. Guess I should have hit refresh :)

James

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

> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
> bounces@lists.xensource.com] On Behalf Of Pasi Kärkkäinen
> Sent: Wednesday, 23 September 2009 16:58
> To: Jeremy Fitzhardinge
> Cc: J. Roeleveld; xen-devel@lists.xensource.com; Thiago Camargo Martins
> Cordeiro; keir.fraser@eu.citrix.com
> Subject: Re: [Xen-devel] newer dom0 kernel / xen-unstable git kernel tree
> 
> On Wed, Sep 23, 2009 at 09:52:37AM +0300, Pasi Kärkkäinen wrote:
> > On Tue, Sep 22, 2009 at 04:28:56PM -0700, Jeremy Fitzhardinge wrote:
> > > On 09/22/09 16:26, Thiago Camargo Martins Cordeiro wrote:
> > > > Gotcha!
> > > >
> > > >  To make use of the latest pv_ops dom0 need I the
xen-unstable tree?
> > > >  Or can I use the Xen 3.4.1 / 3.3.2 from xen.org
<http://xen.org>?
> > >
> > > There''s no close tie between dom0 and Xen itself; it
should work with
> > > any fairly recent version of Xen (and if it doesn''t
that''s interesting
> > > information).
> > >
> >
> > Works for me with Xen 3.4.1 hypervisor.
> >
> > Earlier I used it with Xen 3.3.1.
> >
> 
> .. but I forgot to mention that 3.3.1 needs some extra (backported)
patches.
> 
> So Xen 3.4.x or newer is a safe choise.
> 
> See: http://wiki.xensource.com/xenwiki/XenParavirtOps
> 
drivers/built-in.o: In function `processor_cntl_xen_prepare'':
(.text+0x50aba): undefined reference to
`acpi_processor_get_performance_info''
drivers/built-in.o: In function `processor_cntl_xen_prepare'':
(.text+0x50ad9): undefined reference to `acpi_processor_get_psd''
drivers/built-in.o: In function `xenfb_init'':
xen-fbfront.c:(.init.text+0xd62): undefined reference to
`__xenbus_register_frontend''
drivers/built-in.o: In function `xenkbd_init'':
xen-kbdfront.c:(.init.text+0x7b48): undefined reference to
`__xenbus_register_frontend''
make: *** [.tmp_vmlinux1] Error 1

Is there a .config file that is known to work?

James

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

On Wed, Sep 23, 2009 at 07:31:30PM +1000, James Harper
wrote:
> 
> 
> > -----Original Message-----
> > From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
> > bounces@lists.xensource.com] On Behalf Of Pasi Kärkkäinen
> > Sent: Wednesday, 23 September 2009 16:58
> > To: Jeremy Fitzhardinge
> > Cc: J. Roeleveld; xen-devel@lists.xensource.com; Thiago Camargo
Martins
> > Cordeiro; keir.fraser@eu.citrix.com
> > Subject: Re: [Xen-devel] newer dom0 kernel / xen-unstable git kernel
tree
> > 
> > On Wed, Sep 23, 2009 at 09:52:37AM +0300, Pasi Kärkkäinen wrote:
> > > On Tue, Sep 22, 2009 at 04:28:56PM -0700, Jeremy Fitzhardinge
wrote:
> > > > On 09/22/09 16:26, Thiago Camargo Martins Cordeiro wrote:
> > > > > Gotcha!
> > > > >
> > > > >  To make use of the latest pv_ops dom0 need I the
xen-unstable tree?
> > > > >  Or can I use the Xen 3.4.1 / 3.3.2 from xen.org
<http://xen.org>?
> > > >
> > > > There''s no close tie between dom0 and Xen itself;
it should work with
> > > > any fairly recent version of Xen (and if it doesn''t
that''s interesting
> > > > information).
> > > >
> > >
> > > Works for me with Xen 3.4.1 hypervisor.
> > >
> > > Earlier I used it with Xen 3.3.1.
> > >
> > 
> > .. but I forgot to mention that 3.3.1 needs some extra (backported)
patches.
> > 
> > So Xen 3.4.x or newer is a safe choise.
> > 
> > See: http://wiki.xensource.com/xenwiki/XenParavirtOps
> > 
> 
> drivers/built-in.o: In function `processor_cntl_xen_prepare'':
> (.text+0x50aba): undefined reference to
`acpi_processor_get_performance_info''
> drivers/built-in.o: In function `processor_cntl_xen_prepare'':
> (.text+0x50ad9): undefined reference to `acpi_processor_get_psd''
> drivers/built-in.o: In function `xenfb_init'':
> xen-fbfront.c:(.init.text+0xd62): undefined reference to
`__xenbus_register_frontend''
> drivers/built-in.o: In function `xenkbd_init'':
> xen-kbdfront.c:(.init.text+0x7b48): undefined reference to
`__xenbus_register_frontend''
> make: *** [.tmp_vmlinux1] Error 1
> 
> Is there a .config file that is known to work?
> 
Here''s my (working) .config for 2.6.31-rc8:
http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.31-rc8-rebase-master-no-highpte

Sorry I don''t have the 2.6.31-final .config online atm.

That''s for 32bit PAE. It''s originally based on some 2.6.29
fedora kernel
.config, and changed many times pretty randomly after that.. good luck :)

You could also grab http://fedorapeople.org/~myoung/dom0/ kernel and
extract the .config from them..

-- Pasi


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

> >
> > drivers/built-in.o: In function `processor_cntl_xen_prepare'':
> > (.text+0x50aba): undefined reference to
> `acpi_processor_get_performance_info''
> > drivers/built-in.o: In function `processor_cntl_xen_prepare'':
> > (.text+0x50ad9): undefined reference to
`acpi_processor_get_psd''
This was caused by CONFIG_ACPI_PROCESSOR=m instead of CONFIG_ACPI_PROCESSOR=y

I started my .config from the Debian 2.6.26 kernel, which likes pretty much
everything as modules.

Are you interested in hearing about these sorts of problems?

James

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

> > drivers/built-in.o: In function `xenfb_init'':
> > xen-fbfront.c:(.init.text+0xd62): undefined reference to
> `__xenbus_register_frontend''
> > drivers/built-in.o: In function `xenkbd_init'':
> > xen-kbdfront.c:(.init.text+0x7b48): undefined reference to
> `__xenbus_register_frontend''
> > make: *** [.tmp_vmlinux1] Error 1
> >
if CONFIG_XEN_BLKDEV_FRONTEND=m and CONFIG_XEN_NETDEV_FRONTEND=m then it seems
to force CONFIG_XEN_XENBUS_FRONTEND=m, which is incompatible with xenfb and
xenkbd being built into the kernel...

James

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

> # git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
># cd  linux-2.6-xen
#git branch.

Boris.




      

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

On 09/23/09 02:31, James Harper wrote:
> drivers/built-in.o: In function `processor_cntl_xen_prepare'':
> (.text+0x50aba): undefined reference to
`acpi_processor_get_performance_info''
> drivers/built-in.o: In function `processor_cntl_xen_prepare'':
> (.text+0x50ad9): undefined reference to `acpi_processor_get_psd''
> drivers/built-in.o: In function `xenfb_init'':
> xen-fbfront.c:(.init.text+0xd62): undefined reference to
`__xenbus_register_frontend''
> drivers/built-in.o: In function `xenkbd_init'':
> xen-kbdfront.c:(.init.text+0x7b48): undefined reference to
`__xenbus_register_frontend''
> make: *** [.tmp_vmlinux1] Error 1
>
> Is there a .config file that is known to work?
>   
There''s a known problem with making ACPI modular.  Compiling them
builting (=y) should work.

    J

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

On 09/23/09 03:57, James Harper wrote:
> if CONFIG_XEN_BLKDEV_FRONTEND=m and CONFIG_XEN_NETDEV_FRONTEND=m then it
seems to force CONFIG_XEN_XENBUS_FRONTEND=m, which is incompatible with xenfb
and xenkbd being built into the kernel...
>   
Yeah, that config stuff is a mess ATM, and needs a bit of love and close
attention.  Again, non-modular is the quick fix.

    J

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

On 09/22/09 23:57, Pasi Kärkkäinen wrote:
> .. but I forgot to mention that 3.3.1 needs some extra (backported)
patches.
>   
They''re for the toolstack rather than Xen itself, right?

    J

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

On Wed, Sep 23, 2009 at 12:52:10PM -0700, Jeremy Fitzhardinge
wrote:
> On 09/22/09 23:57, Pasi Kärkkäinen wrote:
> > .. but I forgot to mention that 3.3.1 needs some extra (backported)
patches.
> >   
> 
> They''re for the toolstack rather than Xen itself, right?
> 
I think stock Xen 3.3.1 is missing Xen hypervisor dom0 kernel bzImage loader,
and
the tools are missing sysfs memory ballooning stuff..

-- Pasi


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

On 09/23/09 12:59, Pasi Kärkkäinen wrote:
> I think stock Xen 3.3.1 is missing Xen hypervisor dom0 kernel bzImage
loader,
OK.  That can be worked around, but it is a bit awkward.
>  and
> the tools are missing sysfs memory ballooning stuff..
>   
Right.  Also the xentop change.

    J

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

> > drivers/built-in.o: In function `processor_cntl_xen_prepare'':
> > (.text+0x50aba): undefined reference to
> `acpi_processor_get_performance_info''
> > drivers/built-in.o: In function `processor_cntl_xen_prepare'':
> > (.text+0x50ad9): undefined reference to
`acpi_processor_get_psd''
> > drivers/built-in.o: In function `xenfb_init'':
> > xen-fbfront.c:(.init.text+0xd62): undefined reference to
> `__xenbus_register_frontend''
> > drivers/built-in.o: In function `xenkbd_init'':
> > xen-kbdfront.c:(.init.text+0x7b48): undefined reference to
> `__xenbus_register_frontend''
> > make: *** [.tmp_vmlinux1] Error 1
> >
> > Is there a .config file that is known to work?
> >
As per previous emails I fixed up those problems with config changes (mostly
incompatibilities between things compiled into the kernel depending on things
compiled as modules) and tested it in a DomU, which worked, and then in Dom0,
which also worked. I needed to mount xenfs on /proc/xen but other than that
everything "just worked".

Thanks

James

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