Thanks again ;)
Reason for 2.6.28 is, that i was told by xen-users that 2.6.27 from SLES is
buggy and after tests, i could approve that.
Additionally, i was told that 2.6.28 with xen support is stable. Unfortunately,
nobody could tell me until now, where i could get that mysterious
2.6.28-xen-kernel, so that's why i am asking now here..
As i am using gentoo, i would need a source-tree to compile the kernel for me,
prebuild binaries wont be from help.
I didn't find any not sles-xen-kernel-source (src-rpm) in higher versions, p.e.
by redhat to "steel" this ;)
I tried the "lenny"-way, but debian makes some strange things in the
kernel-source packages that i don't understand in result as non-debianist, so i
went back again to the roots and wanted to take the good old vanilla-source and
patch it ;)
What is your advice concerning the stability of jeremys pv_ops enabled
git-sources concerning stability?
An absolute no-go, or is it near stable, just waiting for some last checks?
Cheers, Florian
> -----Ursprüngliche Nachricht-----
> Von: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] Im Auftrag von
> Pasi Kärkkäinen
> Gesendet: Freitag, 6. März 2009 14:03
> An: Rustedt, Florian
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Betreff: Re: [Xen-devel] The right way to get an
> actualxen-enabledkernel-source tree?
>
> On Fri, Mar 06, 2009 at 01:05:04PM +0100, Rustedt, Florian wrote:
> > Thanks a lot for the fast answer and yes, i need it for dom0!
> >
> > Does this "pv_ops"-way mean, that i would have to use an
> not productional usable kernel?
> > So perhaps it would be better for me, to patch a kernel
> with the 2.6.18 patchset?
> >
>
> Current pv_ops dom0 development is tracking 2.6.29 (and
> 2.6.30 later), so that's what's available atm.
>
> There are no recommended dom0 patches for 2.6.28 that I'm aware of.
>
> Other option is to use Xensource xenlinux patches for 2.6.18,
> or then forward-port of those to 2.6.27 by novell/sles/suse people.
>
> http://xenbits.xen.org/linux-2.6.18-xen.hg
> http://xenbits.xen.org/ext/linux-2.6.27-xen.hg
>
> I'd recommend you to use a distribution that already includes
> dom0 capable kernel out-of-the-box.
>
> -- Pasi
>
> > If it is usable:
> > As i never used git before, could you please provide me the
> commandline to use it for a 2.6.28 kernel?
> >
> > Is it like patching in that way:
> > 1. download 2.6.28(.rcxx) vanilla-sources 2. untar and go to that
> > directory 3. do "git something" now?
> >
> > Cheers, Florian
> >
> > > -----Ursprüngliche Nachricht-----
> > > Von: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> > > [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] Im Auftrag
> von Pasi
> > > Kärkkäinen
> > > Gesendet: Freitag, 6. März 2009 12:47
> > > An: Rustedt, Florian
> > > Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> > > Betreff: Re: [Xen-devel] The right way to get an actual
> > > xen-enabledkernel-source tree?
> > >
> > > On Fri, Mar 06, 2009 at 12:22:12PM +0100, Rustedt, Florian wrote:
> > > > Hello list,
> > > >
> > > > I need a xen-kernel in version 2.6.28, but can't find any
> > > hint, how i can come to this point?
> > > > AFAIK the xensources stopped with 2.6.18?
> > > >
> > > > So what'S actual the way to get a vanilla-kernel and patch
> > > it with xen?
> > > >
> > >
> > > Xen domU support has been in vanilla Linux kernels since
> > > 2.6.23 (pv_ops domU).
> > >
> > > pv_ops based dom0 support is currently under development and it's
> > > planned to get merged to 2.6.30 vanilla kernel.
> > >
> > > See: http://wiki.xensource.com/xenwiki/XenParavirtOps
> > >
> > > latest development/unstable pv_ops Linux tree with dom0 patches:
> > > http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=sho
> > > rtlog;h=xen/dom0/hackery
> > >
> > > -- Pasi
> > >
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>
>
**********************************************************************************************
IMPORTANT: The contents of this email and any attachments are confidential.
They are intended for the
named recipient(s) only.
If you have received this email in error, please notify the system manager or
the sender immediately and do
not disclose the contents to anyone or make copies thereof.
*** eSafe scanned this email for viruses, vandals, and malicious content. ***
**********************************************************************************************
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home