From: BlaisorBlade <bla...@ya...> - 2004-04-30 17:09:39
|
Alle 22:03, gioved=EC 29 aprile 2004, Erik de Bruijn - LowVoice ha scritto: > Hi! > > I'm running some UML's in a production environment, it normally runs very > stable. But switching to an entirely 2.6.x kernel configuration (both host > and guest OS') gave some trouble. The 2.6.x guest kernels get a segfault = or > kernel panic nr 7 What does that "nr 7" mean? Post the error message. BUT BEFORE upgrade to=20 2.6.4 (see below)! >, only when ran in the chroot, and only after a while > (when stresstesting with bonnie or a forkbomb). There's a difference > between a chrooted environment for the usermode kernel, and one that has > access to the entire host filesystems (/proc, /dev and /tmp). > The chroot seems to work perfectly with a 2.4 kernel, but doesn't with 2.6 > kernel anymore. The .config of a problematic kernel can be sent to anyone > on request (but I won't add it here now). ave to look for a 2.4 kernel > config if needed, but I seems they all work allright. The same 2.6.3 > .config, and exactly the same binaries work stable without the extra > chroot. No, well, the problem is not the chroot. Even if you have not still=20 experienced it, any 2.6 UML patch has a big bug (kernel panic) that shows=20 exactly under fork-bombing. So please upgrade absolutely to 2.6.4 vanilla=20 kernel with 2.6.4-1 UML patch (if you need later kernels you need some more= =20 fixlets, search the -devel list). If you still have problems, then redo the= =20 report with the requested data (+ compiler version, distro and so on). > I found out about the need for /proc/cpuinfo by tracing the calls of a > running system. What other calls might be made, especially those that > aren't made every time or directly at startup time? Well, I think nothing (but strace is better than me; limits its output to t= he=20 open() syscall and you'll have a lot less junk output to check). Bye =2D-=20 Paolo Giarrusso, aka Blaisorblade Linux registered user n. 292729 |