Hi all, I am new to Xen implementation. Please help me for this issue. First i will explain my setup, we have an remote server with Xen and we are uploading our images to that server and working on it.. for that we are paying. I have uploaded the slackware12.1 image to the Xen server. It is working fine but while booting time getting below warning *************************************************************** *************************************************************** * * WARNING: Currently emulating unsupported memory accesses ** * in /lib/tls glibc libraries. The emulation is ** * slow. To ensure full performance you should ** * install a ''xen-friendly'' (nosegneg) version of ** * the library, or disable tls support by executing ** * the following as root: ** * mv /lib/tls /lib/tls.disabled ** * Offending process: init (pid=1) ** *************************************************************** *************************************************************** I have rebuilt the glibc with "-mno-tls-direct-seg-refs" option and installed it then sysvinit, mdadm packages but still getting same warning. Please help me to resolve this issue.. Thanks in advance Sg.. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 8/6/08, Geetha, ANGLER - EIT <geetha@angleritech.com> wrote:> > Hi all, > > I am new to Xen implementation. Please help me for this issue. > > First i will explain my setup, we have an remote server with Xen and we > are uploading our images to that server and working on it.. for that we > are paying. > > I have uploaded the slackware12.1 image to the Xen server. It is working > fine but while booting time getting below warning > > *************************************************************** > *************************************************************** > > > * > > * WARNING: Currently emulating unsupported memory accesses > ** > * in /lib/tls glibc libraries. The emulation is ** > * slow. To ensure full performance you should ** > * install a ''xen-friendly'' (nosegneg) version of ** > * the library, or disable tls support by executing ** > * the following as root: ** > * mv /lib/tls /lib/tls.disabled ** > * Offending process: init (pid=1) ** > > *************************************************************** > *************************************************************** > > I have rebuilt the glibc with "-mno-tls-direct-seg-refs" option and > installed it then sysvinit, mdadm packages > > but still getting same warning. > > > Please help me to resolve this issue..i am not sure you have googled this issues because it is well known Anyway: Suggested patch http://lists.xensource.com/archives/html/xen-changelog/2006-10/msg00262.html @followink link. http://lists.xensource.com/archives/html/xen-changelog/2006-10/msg00262.html HTH> > Thanks in advance > Sg.. >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks for your response. I have googled about this issue, since i try to resolve this for 1 month.. Let me kow how to fix this patch, i am new to Xen with Slackware.. Please help me.. Moreover I am using Amazon EC2.. This is for your kind info! Thanks Sg.. -----Original Message----- From: Tej [mailto:bewith.tej@gmail.com] Sent: Wednesday, August 06, 2008 10:57 AM To: Geetha, ANGLER - EIT Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] xen-friendly glibc On 8/6/08, Geetha, ANGLER - EIT <geetha@angleritech.com> wrote:> > Hi all, > > I am new to Xen implementation. Please help me for this issue. > > First i will explain my setup, we have an remote server with Xen and > we are uploading our images to that server and working on it.. for > that we are paying. > > I have uploaded the slackware12.1 image to the Xen server. It is > working fine but while booting time getting below warning > > *************************************************************** > *************************************************************** > > > * > > * WARNING: Currently emulating unsupported memory accesses > ** > * in /lib/tls glibc libraries. The emulation is ** > * slow. To ensure full performance you should ** > * install a ''xen-friendly'' (nosegneg) version of ** > * the library, or disable tls support by executing ** > * the following as root: ** > * mv /lib/tls /lib/tls.disabled ** > * Offending process: init (pid=1) ** > > *************************************************************** > *************************************************************** > > I have rebuilt the glibc with "-mno-tls-direct-seg-refs" option and > installed it then sysvinit, mdadm packages > > but still getting same warning. > > > Please help me to resolve this issue..i am not sure you have googled this issues because it is well known Anyway: Suggested patch http://lists.xensource.com/archives/html/xen-changelog/2006-10/msg00262. html @followink link. http://lists.xensource.com/archives/html/xen-changelog/2006-10/msg00262. html HTH> > Thanks in advance > Sg.. >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, 2008-08-06 at 09:19 +0530, Geetha, ANGLER - EIT wrote:> *************************************************************** > *************************************************************** > > * WARNING: Currently emulating unsupported memory > accesses ** > * in /lib/tls glibc libraries. The emulation is ** > * slow. To ensure full performance you should ** > * install a ''xen-friendly'' (nosegneg) version of ** > * the library, or disable tls support by executing ** > * the following as root: ** > * mv /lib/tls /lib/tls.disabled ** > * Offending process: init (pid=1) ** > *************************************************************** > *************************************************************** > > I have rebuilt the glibc with "-mno-tls-direct-seg-refs" option and > installed it then sysvinit, mdadm packages > > but still getting same warning.This is because init was compiled and statically linked without xen friendly libc. Its perfectly harmless and can be ignored. If you want to make the warning go away, obtain the source to init (sysvinit) from your distro and rebuild/install it after installing xen friendly glibc. Its quite harmless and really not worth fixing. Cheers, --Tim -- Monkey + Typewriter = Echoreply ( http://echoreply.us ) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks for your response Tim. Is there xen friendly glibc available for Slackware? Already Xen running on remote server, i have created instance for my slackware guest os on it and uploaded on it.. While booting slackware guest getting this warning.. Regards, Sg.. -----Original Message----- From: Tim Post [mailto:echo@echoreply.us] Sent: Wednesday, August 06, 2008 12:10 PM To: Geetha, ANGLER - EIT Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] xen-friendly glibc On Wed, 2008-08-06 at 09:19 +0530, Geetha, ANGLER - EIT wrote:> *************************************************************** > *************************************************************** > > * WARNING: Currently emulating unsupported memory > accesses ** > * in /lib/tls glibc libraries. The emulation is ** > * slow. To ensure full performance you should ** > * install a ''xen-friendly'' (nosegneg) version of ** > * the library, or disable tls support by executing ** > * the following as root: ** > * mv /lib/tls /lib/tls.disabled ** > * Offending process: init (pid=1) ** > *************************************************************** > *************************************************************** > > I have rebuilt the glibc with "-mno-tls-direct-seg-refs" option and > installed it then sysvinit, mdadm packages > > but still getting same warning.This is because init was compiled and statically linked without xen friendly libc. Its perfectly harmless and can be ignored. If you want to make the warning go away, obtain the source to init (sysvinit) from your distro and rebuild/install it after installing xen friendly glibc. Its quite harmless and really not worth fixing. Cheers, --Tim -- Monkey + Typewriter = Echoreply ( http://echoreply.us ) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, 2008-08-06 at 12:27 +0530, Geetha, ANGLER - EIT wrote:> Thanks for your response Tim. > > Is there xen friendly glibc available for Slackware?Yikes! It has been a while since I''ve used Slackware. What version of libc is the guest using, exactly? I really would not worry about the warning, unless its just something fun for you to study and solve. Its really quite harmless. This is really trivial. Your init is statically linked against the libc used to when compiling it (thus making said libc a part of the program vs using shared objects). Unless you need to reduce boot time by a few seconds I really recommend just ignoring it. If you have disabled tls for dynamically linked programs (as you indicated that you have) its really a non issue. If some threading server throws the same warning, its cause for concern because its also likely statically linked (I doubt that you''d ever see that). A few of the core utilities _might_ produce that warning, don''t worry until you see some threading service issue the same. I hope that this helps. Cheers! --Tim> > Already Xen running on remote server, i have created instance for my > slackware guest os on it and uploaded on it.. > > While booting slackware guest getting this warning.. > > Regards, > Sg.. > > > > -----Original Message----- > From: Tim Post [mailto:echo@echoreply.us] > Sent: Wednesday, August 06, 2008 12:10 PM > To: Geetha, ANGLER - EIT > Cc: xen-users@lists.xensource.com > Subject: Re: [Xen-users] xen-friendly glibc > > On Wed, 2008-08-06 at 09:19 +0530, Geetha, ANGLER - EIT wrote: > > > *************************************************************** > > *************************************************************** > > > > * WARNING: Currently emulating unsupported memory > > accesses ** > > * in /lib/tls glibc libraries. The emulation is ** > > * slow. To ensure full performance you should ** > > * install a ''xen-friendly'' (nosegneg) version of ** > > * the library, or disable tls support by executing ** > > * the following as root: ** > > * mv /lib/tls /lib/tls.disabled ** > > * Offending process: init (pid=1) ** > > *************************************************************** > > *************************************************************** > > > > I have rebuilt the glibc with "-mno-tls-direct-seg-refs" option and > > installed it then sysvinit, mdadm packages > > > > but still getting same warning. > > This is because init was compiled and statically linked without xen > friendly libc. Its perfectly harmless and can be ignored. > > If you want to make the warning go away, obtain the source to init > (sysvinit) from your distro and rebuild/install it after installing xen > friendly glibc. > > Its quite harmless and really not worth fixing. > > Cheers, > --Tim > > > -- > Monkey + Typewriter = Echoreply ( http://echoreply.us ) >-- Monkey + Typewriter = Echoreply ( http://echoreply.us ) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks for your timely response Tim, It is very helpful for all slackware xen users. I am using slackware 12.0 and glibc version is 2.5. I bit of scared abot this issue, but I clear now from your explanation, but i have to disable this warning :) so i doing research on this.. Please help me.. Can you give me the url for Xen-friendly glibc for slackware? Thanks & Regards Sg.. On Wed, 2008-08-06 at 12:27 +0530, Geetha, ANGLER - EIT wrote:> Thanks for your response Tim. > > Is there xen friendly glibc available for Slackware?Yikes! It has been a while since I''ve used Slackware. What version of libc is the guest using, exactly? I really would not worry about the warning, unless its just something fun for you to study and solve. Its really quite harmless. This is really trivial. Your init is statically linked against the libc used to when compiling it (thus making said libc a part of the program vs using shared objects). Unless you need to reduce boot time by a few seconds I really recommend just ignoring it. If you have disabled tls for dynamically linked programs (as you indicated that you have) its really a non issue. If some threading server throws the same warning, its cause for concern because its also likely statically linked (I doubt that you''d ever see that). A few of the core utilities _might_ produce that warning, don''t worry until you see some threading service issue the same. I hope that this helps. Cheers! --Tim> > Already Xen running on remote server, i have created instance for my > slackware guest os on it and uploaded on it.. > > While booting slackware guest getting this warning.. > > Regards, > Sg.. > > > > -----Original Message----- > From: Tim Post [mailto:echo@xxxxxxxxxxxx] > Sent: Wednesday, August 06, 2008 12:10 PM > To: Geetha, ANGLER - EIT > Cc: xen-users@xxxxxxxxxxxxxxxxxxx > Subject: Re: [Xen-users] xen-friendly glibc > > On Wed, 2008-08-06 at 09:19 +0530, Geetha, ANGLER - EIT wrote: > > > *************************************************************** > > *************************************************************** > > > > * WARNING: Currently emulating unsupported memory > > accesses ** > > * in /lib/tls glibc libraries. The emulation is ** > > * slow. To ensure full performance you should ** > > * install a ''xen-friendly'' (nosegneg) version of ** > > * the library, or disable tls support by executing ** > > * the following as root: ** > > * mv /lib/tls /lib/tls.disabled ** > > * Offending process: init (pid=1) ** > > *************************************************************** > > *************************************************************** > > > > I have rebuilt the glibc with "-mno-tls-direct-seg-refs" option and > > installed it then sysvinit, mdadm packages > > > > but still getting same warning. > > This is because init was compiled and statically linked without xen > friendly libc. Its perfectly harmless and can be ignored. > > If you want to make the warning go away, obtain the source to init > (sysvinit) from your distro and rebuild/install it after installingxen> friendly glibc. > > Its quite harmless and really not worth fixing. > > Cheers, > --Tim > > > -- > Monkey + Typewriter = Echoreply ( http://echoreply.us ) >-- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, 2008-08-07 at 11:22 +0530, Geetha, ANGLER - EIT wrote:> Thanks for your timely response Tim, It is very helpful for all > slackware xen users.Hi, sorry for this rather late reply :)> > I am using slackware 12.0 and glibc version is 2.5. > > I bit of scared abot this issue, but I clear now from your explanation, > but i have to disable this warning :) so i doing research on this.. > > Please help me..Why do you have to disable the warning? Really, it is _completely_ harmless.> Can you give me the url for Xen-friendly glibc for slackware?I don''t know that one exists. If it doesn''t, you would have to dig up patches from some other distribution, get them to go in cleanly and hope to god that nothing breaks. I would not hack libc and then immediately put systems using it into production use, ever :) In essence, if you can''t find one from Slackware, you have to recompile libc yourself after doing semi-major surgery. Moving tls to tls.disabled prevents any other threading service from using those shared objects. You really do not need to worry about init. Has anything but init or other core utilities thrown this warning? Is your boss or client fixated on that warning? It would be easier to hack xen to disable it if pid == 1 (and a bit safer) prior to rebuilding init (or much less libc). Cheers, --Tim -- Monkey + Typewriter = Echoreply ( http://echoreply.us ) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks for your response Tim... Hmm.. It will be really tough to do that.. I rebuilt the glibc and installed new package... Then rebuilt sysvinit and installed it.. and reboot the mechine.. The warning got disappeared.. Here is dmesg , please find it and kindly give me your suggestions. Thanks and Regards Sg.. root@ami02:~# dmesg Linux version 2.6.16-xenU (builder@xenbat.amazonsa) (gcc version 4.0.1 20050727 (Red Hat 4.0.1-5)) #1 SMP Mon May 28 03:41:49 SAST 2007 BIOS-provided physical RAM map: Xen: 0000000000000000 - 000000006a400000 (usable) 980MB HIGHMEM available. 727MB LOWMEM available. NX (Execute Disable) protection: active On node 0 totalpages: 437248 DMA zone: 186366 pages, LIFO batch:31 DMA32 zone: 0 pages, LIFO batch:0 Normal zone: 0 pages, LIFO batch:0 HighMem zone: 250882 pages, LIFO batch:31 IRQ lockup detection disabled Built 1 zonelists Kernel command line: root=/dev/sda1 ro 4 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 4096 (order: 12, 65536 bytes) Xen reported: 2600.000 MHz processor. Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Software IO TLB disabled vmalloc area: ee000000-f53fe000, maxmem 2d7fe000 Memory: 1718700k/1748992k available (1958k kernel code, 20948k reserved, 620k data, 144k init, 1003528k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 5201.57 BogoMIPS (lpj=26007864) Mount-cache hash table entries: 512 CPU: After generic identify, caps: 178bc3f1 ebd3fbff 00000000 00000000 00002001 00000000 0000001f CPU: After vendor identify, caps: 178bc3f1 ebd3fbff 00000000 00000000 00002001 00000000 0000001f CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) CPU: After all inits, caps: 178bc3f1 ebd3fbff 00000000 00000010 00002001 00000000 0000001f Checking ''hlt'' instruction... OK. Brought up 1 CPUs migration_cost=0 Grant table initialized NET: Registered protocol family 16 Brought up 1 CPUs xen_mem: Initialising balloon driver. highmem bounce pool size: 64 pages VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Initializing Cryptographic API io scheduler noop registered io scheduler anticipatory registered (default) io scheduler deadline registered io scheduler cfq registered i8042.c: No controller found. RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize Xen virtual console successfully installed as tty1 Event-channel device installed. netfront: Initialising virtual ethernet driver. mice: PS/2 mouse device common for all mice md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 NET: Registered protocol family 2 Registering block device major 8 IP route cache hash table entries: 65536 (order: 6, 262144 bytes) TCP established hash table entries: 262144 (order: 9, 2097152 bytes) TCP bind hash table entries: 65536 (order: 7, 524288 bytes) TCP: Hash tables configured (established 262144 bind 65536) TCP reno registered TCP bic registered NET: Registered protocol family 1 NET: Registered protocol family 17 NET: Registered protocol family 15 Using IPI No-Shortcut mode md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Freeing unused kernel memory: 144k freed Adding 917496k swap on /dev/sda3. Priority:-1 extents:1 across:917496k EXT3 FS on sda1, internal journal kjournald starting. Commit interval 5 seconds EXT3-fs warning: checktime reached, running e2fsck is recommended EXT3 FS on sda2, internal journal EXT3-fs: mounted filesystem with ordered data mode. -----Original Message----- From: Tim Post [mailto:echo@echoreply.us] Sent: Friday, August 08, 2008 3:47 PM To: Geetha, ANGLER - EIT Cc: xen-users@lists.xensource.com Subject: RE: [Xen-users] xen-friendly glibc On Thu, 2008-08-07 at 11:22 +0530, Geetha, ANGLER - EIT wrote:> Thanks for your timely response Tim, It is very helpful for all > slackware xen users.Hi, sorry for this rather late reply :)> > I am using slackware 12.0 and glibc version is 2.5. > > I bit of scared abot this issue, but I clear now from your > explanation, but i have to disable this warning :) so i doing researchon this..> > Please help me..Why do you have to disable the warning? Really, it is _completely_ harmless.> Can you give me the url for Xen-friendly glibc for slackware?I don''t know that one exists. If it doesn''t, you would have to dig up patches from some other distribution, get them to go in cleanly and hope to god that nothing breaks. I would not hack libc and then immediately put systems using it into production use, ever :) In essence, if you can''t find one from Slackware, you have to recompile libc yourself after doing semi-major surgery. Moving tls to tls.disabled prevents any other threading service from using those shared objects. You really do not need to worry about init. Has anything but init or other core utilities thrown this warning? Is your boss or client fixated on that warning? It would be easier to hack xen to disable it if pid == 1 (and a bit safer) prior to rebuilding init (or much less libc). Cheers, --Tim -- Monkey + Typewriter = Echoreply ( http://echoreply.us ) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users