The linux-image-2.6.26-1-xen-686 only works as a domu, not a dom0. For a dom0 you still need a 2.6.18 kernel.
Or are you running a 2.6.26 kernel as a dom0 ? - in which case I'm very interested ! All my non-xen machines are dist-upgraded. I suspect the 2.6.18 kernel to remain in the repository until a newer dom0 kernel becomes available. Kindest regards, Peter. On Tuesday 30 September 2008 14:39:32 Mariusz Sielicki wrote: > 2008/9/30 Peter Van Biesen <[EMAIL PROTECTED]>: > > Because you can't use a newer kernel as a xen dom0 kernel. The only working > > dom0 kernel ( at the moment ) is a 2.6.18 afaik. > > > On Lenny I've got linux-image-2.6.26-1-xen-686. > Lenny will be stable just a moment, may by its time to dist-upgrade ? :) > > > > > > > Kindest regards, > > > > Peter. > > > > On Tuesday 30 September 2008 13:48:10 Rich Healey wrote: > >> Peter Van Biesen wrote: > >> > Hi, > >> > > >> > I'm trying to setup a dom0 starting from a debian testing installation. > >> > I installed testing, then installed the 2.6.18 kernel from stable and > >> > the hypervisor from testing. After a reboot xen is now up and running. I > >> > now want to use clvm. So I install redhat-cluster-suite and clvm. This > >> > installs the kernel modules for the 2.6.26 and the 2.6.18 kernel. > >> > However, the modules for the 2.6.18 kernel are version 1.3x, while for > >> > the 2.6.26 kernel are 2.x . Needless to say, cman will not start. > >> > > >> > I then tried to compile de kernel module for my 2.6.18 kernel from > >> > source using the module-assistant. This fails on lm_interface.h, which > >> > is not in the 2.6.18 source tree. > >> > > >> > Is it really impossible to run clvm 2.x on a dom0 ? Or am i missing > >> > something ? Has anybody used clvm with xen ? > >> > > >> > Kindest regards, > >> > > >> > Peter. > >> > >> Why exactly do you want to use the Etch kernel? > >> > >> -- > >> Rich Healey - iTReign \ .''`. / [EMAIL PROTECTED] > >> Developer / Systems Admin \ : :' : / [EMAIL PROTECTED] > >> AIM: richohealey33 \ `. `' / [EMAIL PROTECTED] > >> MSN: [EMAIL PROTECTED] \ `- / [EMAIL PROTECTED] > >> ?: blackhole.pca.dfn.de: Connection refused > >> gpgkeys: HTTP fetch error 7: couldn't connect: Connection refused > >> > >> > > > > > > > > -- > > Peter Van Biesen > > Sysadmin VAPH > > > > tel: +32 (0) 2 225 85 70 > > fax: +32 (0) 2 225 85 88 > > e-mail: [EMAIL PROTECTED] > > PGP: http://www.vaph.be/pgpkeys > > > > Opgelet ! De domeinnaam van het Vlaams Agentschap is vanaf heden > > vaph.be. Dit betekent dat u uw correspondent kan bereiken via > > [EMAIL PROTECTED] Gelieve aub dit aan te passen in uw adresboek. > > > > DISCLAIMER > > ------------------------------------------------------------------------------- > > De personeelsleden van het agentschap doen hun best om in e-mails > > betrouwbare informatie te geven. > > Toch kan niemand rechten doen gelden op basis van deze inhoud. > > Als in de e-mail een stellingname voorkomt, is dat niet noodzakelijk het > > standpunt van het agentschap. > > Rechtsgeldige beslissingen of officiele standpunten worden alleen per > > brief toegestuurd. > > > > > > -- > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > > > > Best regards. > Mariusz Sielicki > > -- Peter Van Biesen Sysadmin VAPH tel: +32 (0) 2 225 85 70 fax: +32 (0) 2 225 85 88 e-mail: [EMAIL PROTECTED] PGP: http://www.vaph.be/pgpkeys Opgelet ! De domeinnaam van het Vlaams Agentschap is vanaf heden vaph.be. Dit betekent dat u uw correspondent kan bereiken via [EMAIL PROTECTED] Gelieve aub dit aan te passen in uw adresboek. DISCLAIMER ------------------------------------------------------------------------------- De personeelsleden van het agentschap doen hun best om in e-mails betrouwbare informatie te geven. Toch kan niemand rechten doen gelden op basis van deze inhoud. Als in de e-mail een stellingname voorkomt, is dat niet noodzakelijk het standpunt van het agentschap. Rechtsgeldige beslissingen of officiele standpunten worden alleen per brief toegestuurd. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
