All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: "Rustedt, Florian" <Florian.Rustedt@smartnet.de>
Cc: xen-devel@lists.xensource.com
Subject: Re: AW: The right way to get an	actualxen-enabledkernel-source tree?
Date: Fri, 06 Mar 2009 15:01:48 +0100	[thread overview]
Message-ID: <49B12CCC.4010307@redhat.com> (raw)
In-Reply-To: <152CD2A019ABF542B87AFDC5010DFBEE3C4954@smart-dc-01.smartnet.local>

Rustedt, Florian wrote:
> 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.

I can't recommmend the 2.6.27 tree at xenbits.  That was a one-time
dump, nobody does any maintainance (fix bugs, plug security holes, ...)
there.  You also have to flip certain config options into the correct
state to get the thing even build.

> 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..

The place to look for suse kernels is here:
http://download.opensuse.org/repositories/Kernel:/

Xen stuff for SLES is here:
http://forge.novell.com/modules/xfmod/project/?xenpreview

Note that SLES-10 is 2.6.16-based and SLES-11 (which might come with the
2.6.28 kernel you heared off, I don't known what inside the tarballs is)
isn't released yet.

> What is your advice concerning the stability of jeremys pv_ops
> enabled git-sources concerning stability?

x86_64 works mostly stable for me since a month, with bugs showing up
now and then though.  i386 has more problems and isn't really usable.
No production quality (yet) IMHO.

/me hopes that the majority of the dom0 bits gets merged during the
2.6.30 merge window.  Then this stuff should stabilize while rc's are
released, giving is a good 2.6.30 kernel with dom0 support.

>> I'd recommend you to use a distribution that already includes dom0
>> capable kernel out-of-the-box.

That is certainly the best option.

cheers,
  Gerd

  parent reply	other threads:[~2009-03-06 14:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-06 11:22 The right way to get an actual xen-enabled kernel-source tree? Rustedt, Florian
2009-03-06 11:47 ` Pasi Kärkkäinen
2009-03-06 12:05   ` AW: The right way to get an actual xen-enabledkernel-source tree? Rustedt, Florian
2009-03-06 12:56     ` Carsten Schiers
2009-03-06 13:03     ` Pasi Kärkkäinen
2009-03-06 13:14       ` AW: The right way to get an actualxen-enabledkernel-source tree? Rustedt, Florian
2009-03-06 13:33         ` Pasi Kärkkäinen
2009-03-06 14:01         ` Gerd Hoffmann [this message]
2009-03-06 14:18           ` AW: " Keir Fraser
2009-03-06 14:37             ` Boris Derzhavets

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=49B12CCC.4010307@redhat.com \
    --to=kraxel@redhat.com \
    --cc=Florian.Rustedt@smartnet.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.