-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Fabio A. Mazzarino wrote: > Antonine: > > I've downloaded a pre-compiled uml because I need it working for yesterday. Compiling a guest kernel should not take more than 10 mins on a standard pc. I do offer pre-compiled kernels for those that want to guest started real quick - this might be helpful (you can also use the configs as a starting point): http://uml.nagafix.co.uk/
> I plan to recompile uml later. Unffortunately the host is allocated in > a datacenter, so kernel compiling is a little bit tricky and I try to > avoid it. Sure. Antoine > Later, when I plan to have more free time, I'll do it and then I'll > make you know. > > Thanks again. > > Fabio. > > Antoine Martin escreveu: >> Fabio, >> >> I had a similar problem but this is now resolved. >> Have you tried updating the host and guest to recent kernels? >> >> Antoine >> >> >> Fabio A. Mazzarino wrote: >> >>> I need to build a LAMP server using UML. Apache and PHP5 work fine, but >>> MySQL don't. >>> >>> I've just found a similar problem here: >>> . >>> http://readlist.com/lists/lists.sourceforge.net/user-mode-linux-user/0/364.html >>> >>> But it seems to apply only to x86_64, not my case. >>> >>> Here are some information: >>> >>> host # uname -a >>> Linux loghost1 2.4.27-2-386 #1 Wed Aug 17 09:33:35 UTC 2005 i686 GNU/Linux >>> >>> host # linux --version >>> 2.6.18 >>> >>> guest # uname -a >>> Linux neo 2.6.18 #2 Wed Oct 4 19:34:37 CEST 2006 i686 GNU/Linux >>> >>> >>> guest # tail /var/log/syslog | grep mysqld >>> Apr 17 15:37:06 localhost mysqld[1516]: mysqld got signal 11; >>> Apr 17 15:37:06 localhost mysqld[1516]: This could be because you hit a >>> bug. It is also possible that this binary >>> Apr 17 15:37:06 localhost mysqld[1516]: or one of the libraries it was >>> linked against is corrupt, improperly built, >>> Apr 17 15:37:06 localhost mysqld[1516]: or misconfigured. This error can >>> also be caused by malfunctioning hardware. >>> Apr 17 15:37:06 localhost mysqld[1516]: We will try our best to scrape >>> up some info that will hopefully help diagnose >>> Apr 17 15:37:06 localhost mysqld[1516]: the problem, but since we have >>> already crashed, something is definitely wrong >>> Apr 17 15:37:06 localhost mysqld[1516]: and this may fail. >>> Apr 17 15:37:06 localhost mysqld[1516]: >>> Apr 17 15:37:06 localhost mysqld[1516]: key_buffer_size=0 >>> Apr 17 15:37:06 localhost mysqld[1516]: read_buffer_size=131072 >>> Apr 17 15:37:06 localhost mysqld[1516]: max_used_connections=0 >>> Apr 17 15:37:06 localhost mysqld[1516]: max_connections=100 >>> Apr 17 15:37:06 localhost mysqld[1516]: threads_connected=0 >>> Apr 17 15:37:06 localhost mysqld[1516]: It is possible that mysqld could >>> use up to >>> Apr 17 15:37:06 localhost mysqld[1516]: key_buffer_size + >>> (read_buffer_size + sort_buffer_size)*max_connections = 217599 K >>> Apr 17 15:37:06 localhost mysqld[1516]: bytes of memory >>> Apr 17 15:37:06 localhost mysqld[1516]: Hope that's ok; if not, decrease >>> some variables in the equation. >>> Apr 17 15:37:06 localhost mysqld[1516]: >>> Apr 17 15:37:06 localhost mysqld[1516]: thd=(nil) >>> Apr 17 15:37:06 localhost mysqld[1516]: Attempting backtrace. You can >>> use the following information to find out >>> Apr 17 15:37:06 localhost mysqld[1516]: where mysqld died. If you see no >>> messages after this, something went >>> Apr 17 15:37:06 localhost mysqld[1516]: terribly wrong... >>> Apr 17 15:37:06 localhost mysqld[1516]: Cannot determine thread, >>> fp=0x425fe158, backtrace may not be correct. >>> Apr 17 15:37:06 localhost mysqld[1516]: Stack range sanity check OK, >>> backtrace follows: >>> Apr 17 15:37:06 localhost mysqld[1516]: 0x81c0659 >>> Apr 17 15:37:06 localhost mysqld[1516]: (nil) >>> Apr 17 15:37:06 localhost mysqld[1516]: 0x4027b9ee >>> Apr 17 15:37:06 localhost mysqld[1516]: New value of fp=(nil) failed >>> sanity check, terminating stack trace! >>> Apr 17 15:37:06 localhost mysqld[1516]: Please read >>> http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow >>> instructions on how to resolve the stack trace. Resolved >>> Apr 17 15:37:06 localhost mysqld[1516]: stack trace is much more helpful >>> in diagnosing the problem, so please do >>> Apr 17 15:37:06 localhost mysqld[1516]: resolve it >>> Apr 17 15:37:06 localhost mysqld[1516]: The manual page at >>> http://www.mysql.com/doc/en/Crashing.html contains >>> Apr 17 15:37:06 localhost mysqld[1516]: information that should help you >>> find out what is causing the crash. >>> >>> What can be done? >>> >>> >> >> > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGJp8pGK2zHPGK1rsRClv+AJ9DJawebz3ZnalPRtAfk32SutQDmQCfU1e9 rQmCWcNFb1JUAeoT2sKZp5s= =I6et -----END PGP SIGNATURE----- ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ User-mode-linux-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
