Bastian Blank
2010-Jun-10 15:58 UTC
[Pkg-xen-devel] [RESENT] Re: Xen for Squeeze, 3.4 or 4.0
Whoops, wrong recipient. On Thu, Jun 10, 2010 at 05:54:28PM +0200, Bastian Blank wrote:> I'm currently thinking about which version of Xen supporting in Squeeze. > There are two possibilities: 3.4 and 4.0. 3.4 is currently in testing > and unstable, 4.0 is in experimental. > > Xen 3.4 > ======> Pros > - Proofed to be stable > Cons > - NUMA-mode only opt-in, no infos about stability > - Fails on several modern machines because of IO-APIC problems > > Xen 4.0 > ======> Pros > - NUMA > - More tested with the Kernel in Squeeze > Cons > - Quite new > > My personal preference would be to go with 4.0. > > Bastian > > Cc debian-devel, as there was quite a few discussions about this matter > in the last months.-- Vulcans worship peace above all. -- McCoy, "Return to Tomorrow", stardate 4768.3
Łukasz Oleś
2010-Jun-10 17:29 UTC
[Pkg-xen-devel] [RESENT] Re: Xen for Squeeze, 3.4 or 4.0
2010/6/10 Bastian Blank <waldi at debian.org>:>> My personal preference would be to go with 4.0.I completely agree. Probably more people will use pvops kernel with 4.0 instead 3.4, so hopefully it will be better tested. -- ?ukasz Ole?
Russell Coker
2010-Jun-11 02:23 UTC
[Pkg-xen-devel] [RESENT] Re: Xen for Squeeze, 3.4 or 4.0
On Fri, 11 Jun 2010, Bastian Blank <waldi at debian.org> wrote:> On Thu, Jun 10, 2010 at 05:54:28PM +0200, Bastian Blank wrote: > > I'm currently thinking about which version of Xen supporting in Squeeze. > > There are two possibilities: 3.4 and 4.0. 3.4 is currently in testing > > and unstable, 4.0 is in experimental. > > > > Xen 3.4 > > ======> > Pros > > - Proofed to be stableNot on my machines it hasn't. One i386 server which ran Lenny/Xen for ages without problems (since before Lenny was released) is now running Xen 3.4 from Unstable and it's not going particularly well. The other day it was in a cycle of booting and crashing when loading 2.6.32, I booted 2.6.26 and then before the init scripts finished I rebooted with 2.6.32 and it worked. Different machines require different amounts of memory reserved for Dom0 for unknown reasons. A couple of other machines which according to the Xen web site have suitable CPUs won't boot the Xen kernels that are currently in Unstable. It just seems flakey to me.> > Cons > > - NUMA-mode only opt-in, no infos about stability > > - Fails on several modern machines because of IO-APIC problemsIt fails on plenty of i386 machines (P3 class) for me.> > Xen 4.0 > > ======> > Pros > > - NUMA > > - More tested with the Kernel in Squeeze > > Cons > > - Quite new > > > > My personal preference would be to go with 4.0.Based on my experience with Xen I think that we should have both. Then if one doesn't work we can try the other. My impression of Xen stability is that trying two different versions and hoping that one will work is a good strategy for any given server. Bastian, thanks a lot for all your great work on this, it's very important to me and to lots of other people! But through no fault of anyone in the Debian project I expect that an ideal result of one version that works well for almost everyone can't be achieved. PS It would be nice if we could get Grub2 updated to boot Xen kernels. My SE Linux Play Machine is offline right now because I messed up the Grub2 configuration so badly that it won't even give me a boot menu. -- russell at coker.com.au http://etbe.coker.com.au/ My Main Blog http://doc.coker.com.au/ My Documents Blog
Maybe Matching Threads
- multiple btrfsck runs
- Bug#586666: xen-utils-4.0: xen-utils depends on python << 2.6 which isn't available in Unstable.
- Bug#574675: xen-utils-common: stop fails when some of the daemons are not running
- Bug#597403: xen-utils-common: need to run restorecon in /etc/init.d/xend on SE Linux systems
- Bug#433780: xen-utils-common: /etc/init.d/xend restart should restart xenstored and xenconsole