Hello Ralf,
Well, rebuilding initrd is what solved exactly that problem in my
case, but of cause it might be different for other setups. (I have xen
3.0.2-2, compiled from source with PAE switch and running on debian
etch). Just in case you want to try it anyway, this is what I did after
renaming the tls directory:
depmod 2.6.16-xen
mkinitrd -o /boot/initrd.img-2.6.16-xen 2.6.16-xen
-- 
Seneca
You wrote at Samstag, 15. April 2006 21:50:
RS> Hi,
RS> a new initrd will not help. Have a look a this:
RS> ***************************************************************
RS> ***************************************************************
RS> ** WARNING: Currently emulating unsupported memory accesses **
RS> ** in /lib/tls glibc libraries. The emulation is **
RS> ** slow. To ensure full performance you should **
RS> ** install a 'xen-friendly' (nosegneg) version of **
RS> ** the library, or disable tls support by executing **
RS> ** the following as root: **
RS> ** mv /lib/tls /lib/tls.disabled **
RS> ** Offending process: hotplug (pid=276) **
RS> ***************************************************************
RS> ***************************************************************
RS> This message comes from "hotplug" ... so I have to compile hotplug
RS> without tls support to get rid of this boot message.
RS> Move /lib/tls to /ib/tls.disabled and ignore these messages.
RS> -ralf-
RS> Seneca wrote:
>> In case you are using a initrd you might have to recreate it after
>> /lib/tls was moved to /lib/tls.disabled.
>> 
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users