RE: [Xen-users] 4gb seg fixup errors in Debian (usual hints don't seemto work)

[Fermín Galán Márquez <fermin.galan@xxxxxxx>]

Hello,

> I'm getting a lot of "4gb seg fixup error" messages in the console of my
> domU, that I would like to avoid (not only due to "aesthetic", it impacts
> the performance, as explained at
> http://wiki.xensource.com/xenwiki/XenFaq#head-
> e05786f1e0d6a833bc146a6096cab2d96f2b30ae). E.g.:
>
> 4gb seg fixup, process syslogd (pid 1107), cs:ip 73:b7efc5f0
> 4gb seg fixup, process syslogd (pid 1107), cs:ip 73:b7efc570
> 4gb seg fixup, process klogd (pid 1113), cs:ip 73:b7e2e5f0
> 4gb seg fixup, process klogd (pid 1113), cs:ip 73:b7eafd10
> printk: 38 messages suppressed.
> 4gb seg fixup, process named (pid 1128), cs:ip 73:b7bc5c1c

After a lot of painful debugging :), I think I finally have found the cause
of the problem and the solution.

The filesystem of domU virtual machines was using conventional libc6
(belonging to the libc6 Debian package):

domU:~# ldd /sbin/init | grep libc.so.6
        libc.so.6 => /lib/tls/libc.so.6 (0xb7e0f000)

So, I installed the libc6-xen package in the domU filesystem, that uses an
libc6 variant optimized for Xen. After that:

domU:~# ldd /sbin/init  | grep libc.so.6
        libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0xb7e36000)

And now warning messages have stopped!

In conclusion, my mistake was thinking that the libc6-xen package was only
needed in the dom0 filesystem, while it is also needed in domU ones. I send
this email, to avoid the same confusion in future users :)

Best regards,

--------------------
Fermín Galán Márquez
CTTC - Centre Tecnològic de Telecomunicacions de Catalunya
Parc Mediterrani de la Tecnologia, Av. del Canal Olímpic s/n, 08860
Castelldefels, Spain
Room 1.02
Tel : +34 93 645 29 12
Fax : +34 93 645 29 01
Email address: fermin dot galan at cttc dot es


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