Hi Dan,
Nope. All you've done is update the linker cache. This means any new processes
you've spawned will use the correct libc. Any old processes will still have
the old (Xen unfriendly) libc mapped into memory. A reboot is the only way
to get everything using the new settings I'm afraid.
Cool after reboot i'm am getting those errors not in logs neither when connect to guest via console :)
So the solution
echo "hwcap 0 nosegneg" > /etc/ld.conf.so.d/nosegneg.conf
work for us.
NB, even with this change you'll see the 4gb fixup messages if you run any
mono processes - eg beagle or tomboy - this is a bug in the Mono VM for
which there isn't any fix yet.
We don't use mono process beagle or tomboy.
I very much appreciate your help :)
Thanks. Askar
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
-- Fedora-xen mailing list Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen
