Hi. I recently upgraded to fc6. I''m using the fc6 supplied xen packages. However, now all my VM''s are logging entries like: 4gb seg fixup, process sshd (pid 1162), cs:ip 73:008d8cfc printk: 185714 messages suppressed. It seems to be most all of the processes in each VM that are causing these to be generated. Any ideas? I''ve seen some mention of glibc and statically linked binaries, but there isn''t a "xen" glibc and a "fc6" glibc this time.. they are the same now, or no? Should this go to the fedora folks? Thanks, --Chad _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Hi. I recently upgraded to fc6. I''m using the fc6 supplied xenpackages.> However, now all my VM''s are logging entries like: > > 4gb seg fixup, process sshd (pid 1162), cs:ip 73:008d8cfc > printk: 185714 messages suppressed. > > It seems to be most all of the processes in each VM that are causingthese> to be generated. > > Any ideas? I''ve seen some mention of glibc and statically linkedbinaries,> but there isn''t a "xen" glibc and a "fc6" glibc this time.. they arethe> same now, or no?I haven''t played with fc6, but you may need to do the following: echo ''hwcap 0 nosegneg'' > /etc/ld.so.conf.d/libc6-xen.conf Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 10/31/06, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:> > > Hi. I recently upgraded to fc6. I''m using the fc6 supplied xen > packages. > > However, now all my VM''s are logging entries like: > > > > 4gb seg fixup, process sshd (pid 1162), cs:ip 73:008d8cfc > > printk: 185714 messages suppressed. > > > > It seems to be most all of the processes in each VM that are causing > these > > to be generated. > > > > Any ideas? I''ve seen some mention of glibc and statically linked > binaries, > > but there isn''t a "xen" glibc and a "fc6" glibc this time.. they are > the > > same now, or no? > > I haven''t played with fc6, but you may need to do the following: > > echo ''hwcap 0 nosegneg'' > /etc/ld.so.conf.d/libc6-xen.conf > > > Ian > >That stopped the error message. Is it anything to be concerned about? Thank you, --Chad _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > I haven''t played with fc6, but you may need to do the following: > > echo ''hwcap 0 nosegneg'' > /etc/ld.so.conf.d/libc6-xen.conf > > That stopped the error message.Good -- you''re now using the correct glibc.> Is it anything to be concerned about?Not any more :) Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 10/31/06, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:> > > > I haven''t played with fc6, but you may need to do the following: > > > > echo ''hwcap 0 nosegneg'' > /etc/ld.so.conf.d/libc6-xen.conf > > > > That stopped the error message. > > Good -- you''re now using the correct glibc. > > > Is it anything to be concerned about? > > Not any more :)On 10/31/06, Chad Oleary <oleary.chad@gmail.com> wrote:> Should this go to the fedora folks?So, yes, it would seem? As the spec file for the xen rpm should make the ld.so adjustment above, right? jerry _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users