Xen project Mailing List

[Xen-users] problems with XenSpeicificGlibc

From: Steven Anderson <hikenboot@xxxxxxxxx>

Date: Wed, 23 Nov 2005 03:38:09 -0800 (PST)

Delivery-date: Wed, 23 Nov 2005 11:38:11 +0000

Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=0K/1tFc7KurYUOZBYhx40h5Wrd81/1gXCS+BacTmpAvje7m2Wr5OPqouJ9P7SzJ0OdY5KqY2vPViZTf0bWJCSg8A3SbTMgfMd9+7EJw6i/heyaUpa2vd+qYGshdY0V5AWbzq8tWahlD/kZYvnfbH1l+8FpY3gOTUK/qO1P1L1j0= ;

List-id: Xen user discussion <xen-users.lists.xensource.com>

Greetings!

does anyone know if the fedora kernel made at this site has the lib/tls patch...

http://people.redhat.com/riel/xen_for_fc4/

i still get the same message on boot about an offending process ...the one that redhat has posted gives dom0 allocation too small and they point to the url above as a working kernel without the offending process problem--/lib/tls which forces me to address the XenSpecificGlibc patch problem (at least thats what the boot message is telling me!)

I read something about recompiling glibc which has had the patches already integrated for eliminating the emulation in fedora by adding the notls option but nothing with specifics also i understand this breaks a lot of user mode programs. Does anyone know exactly which ones and how to fix them?

The root wiki i was following is here when I encountered the dom0 allocation too small error. I believe the root cause of that error is the lack of support of changing dom0 memory to somthing higher with the dom0_mem= boot option because it is hard coded.

---->http://www.fedoraproject.org/wiki/FedoraXenQuickstart#head-3a85df2e27189c12a2b8f045bfef3b2a759bb2ef

Thanks in advance!

Yahoo! FareChase - Search multiple travel sites in one click.

_______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users