can't reboot xen in slackware 12 after compiling glibc
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
#and I have copied xen.gz and xen-3.0-unstable.gz to /hda2/boot
#This message I got at reboot (xenproblem or slackware 12-problem?)
***************************************************************
** 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) **
***************************************************************
#Followed sugggestions below from the link
Does the directory /boot/xen-tree exist? Your initrd is apparently faulty.
If you recompile glibc then you'll probably need to re-compile your whole system in order for the binaries to run.
Distribution: I favor Slackware, CentOS and Debian
Posts: 25
Original Poster
Rep:
thank you for your reply
maybe I should compile glibc back then just by installing the original pkgtool packet glibc-2.5-i486-4.tgz?
Yes the tree does exist.
I have solved part of the problem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.