++ 02/12/08 14:10 -0800 - Max Vohra:
In my experience, the 4gb fixup errors occur on a 64bit system with over 4GB
of memory and a 32 bit dom0 kernel, with PAE enabled, and TLS enabled in the
DomU. Moving /lib/tls to /lib/tls.disabled and running ldconfig in the domU
should fix the warning, but
In my experience, the 4gb fixup errors occur on a 64bit system with over 4GB
of memory and a 32 bit dom0 kernel, with PAE enabled, and TLS enabled in the
DomU. Moving /lib/tls to /lib/tls.disabled and running ldconfig in the domU
should fix the warning, but threading will be SLOW.
--
Max V.
On
Max Vohra [EMAIL PROTECTED] writes:
In my experience, the 4gb fixup errors occur on a 64bit system with over 4GB
of memory and a 32 bit dom0 kernel, with PAE enabled, and TLS enabled in the
DomU. Moving /lib/tls to /lib/tls.disabled and running ldconfig in the domU
should fix the warning, but
++ 27/11/08 15:48 +0100 - Aleksandar Ivanisevic:
I have the same problem with the same setup, so at least it is
reproducible ;)
Good to know. Do you experience any problem with a plain Xen domU
(provided by Centos, and thus without OpenVZ)?
Is this causing any real problems for you except messed
On Thu, Nov 27, 2008 at 03:48:07PM +0100, Aleksandar Ivanisevic wrote:
Is this causing any real problems for you except messed up console and
syslog filling with useless messgaes?
I think it causes performance degradation for the affected processes.
--
Marcin Owsiany [EMAIL PROTECTED]
