Arrfab's Blog » Cluster http://www.arrfab.net/blog Linux tips and tricks ... Tue, 20 Jul 2010 12:54:32 +0000 http://wordpress.org/?v=2.8 en hourly 1 DRBD backported (or not) to 2.6.32 in EL6 ? http://www.arrfab.net/blog/?p=224 http://www.arrfab.net/blog/?p=224#comments Tue, 20 Jul 2010 12:54:32 +0000 fabian.arrotin http://www.arrfab.net/blog/?p=224 As some of you already know it, DRBD is now (since kernel 2.6.33) part of the mainline/upstream kernel. Some were expecting RHEL6 to come with that kernel (used for Fedora 13). The latest RHEL6beta2 still comes with 2.6.32, which doesn’t include DRBD support. Of course we still don’t know what the ‘frozen’ RHEL6 kernel will be but on the other hand, we know that Red Hat quite often ‘backports’ modules from newer kernel into the RHEL kernel. What about DRBD ? At the time of writing this blog post, it seems still undecided, but you can follow the DRBD RFE on Upstream Bugzilla to get a clue, or even comment on it if you have a bugzilla account to  make hear your voice. On the other hand, you can still be sure that even if DRBD isn’t part of EL6, CentOS will still ship it in the Extras repository, like for EL4/EL5 …

]]> http://www.arrfab.net/blog/?feed=rss2&p=224 0 virt-install / xen domU ‘out of memory’ issue http://www.arrfab.net/blog/?p=149 http://www.arrfab.net/blog/?p=149#comments Wed, 02 Sep 2009 14:34:12 +0000 fabian.arrotin http://www.arrfab.net/blog/?p=149 I had today to deploy two CentOS 5.3 xen dom0 on two blades and then some domU’s guests. Everything was fine except that when i used our traditionnal deploydomU script (which uses virt-install) it directly complained about memory issue. The exact message was ” ‘Out of memory’, “xc_dom_boot_mem_init: can’t allocate low memory for domain\n ” ” . Strange as I was sure that the dom0 had plenty of memory and the new guest was defined to use only 768Mb .. so what was the issue ? In fact, nothing related to memory : Our new machines get deployed through a pxe boot menu (with syslinux/pxelinux.0 and pxelinux.cfg) in the Labs zone, but a typo was inserted in that menu so that newer CentOS 5.3 x86_64 machines were in fact … using i386 repo !  ;-)

It took me 5 minutes to consult the great oracle (aka google) , find the same issue and look at both new nodes to confirm with `uname -a` that I tried to deploy a x86_64 domU on a i386 dom0 …

Hehehe, strange that the message is related to memory and not arch .. but several minutes later (and a coffee cup, machines being redeployed correctly *after* the pxelinux.cfg file was modified) everything was back to normal and x86_64 domU’s running fine … hope that it can help other people having the same ‘typo’ :-p

]]> http://www.arrfab.net/blog/?feed=rss2&p=149 0