(Sorry about that, nothing POs me more on ntop than somebody assuming I
remember the details of their - among the dozens I see - configuration from
an email exchange, and here I am doing the same. Smack -- bad programmer,
I can't tell you how happy that makes me to have somebody else with
2.4.19/UML problems. Not, you understand, that I'm happy you're having
problems, but the somebody else has the same symptoms. It means I'm not
crazy -- well, not in THAT way.
Tigger is an older box. Intel 440BX, Dual Processor MB (Asus P2B-DS) with
one 800 MHz / 100 MHZ FSB cpu, not over clocked. RedHat 7.3 with a custom
kernel and some other software upgrades, but nothing too fancy. No kernel
patches that I remember. 576MB ram.
I use it for ntop development, so it boots into 6 different OSes depending
on what I need, but Linux is the primary one.
Tigger ran rock solid under 2.4.17 and then 2.4.19 until I fired up UML. (I
use UML to create pseudo-machines ur-tigger and ur-tigger2 with minimal
stuff installed to build and test .rpms without worrying about being root).
On ur-tigger, one rpm -ba out of 10 ran to completion (one more died just
after writing the .rpm file, but I couldn't trust it). Even some of the rpm
install tests on the "other" UML, ur-tigger2, bombed (NB: I only run one at
Almost no daemons runs on the host box (and basically nothing on the UMLs)
(I'd check, but Tigger is booted into FreeBSD right now).
Anyway, I kept the 2.4.19-5um install and have reverted the boot kernel to
my 2.4.17 - and again the UML machines are stable.
Let me know if you want my 2.4.17 .config file...
From: David Coulson [mailto:david@...]
Sent: Saturday, September 21, 2002 6:37 AM
Subject: Re: [uml-user] Further to the host stability comments
> See my previous message -- a uml machine under stress (building an rpm)
> caused the host to die.
> We're talking black screen dead (powered-down standby, I would have to
> reset to get anything).
Nod - I had to hunt around in my mail archives to find your eariler
post. I've been having similar problems with 2.4.19 (dead box, needs to
be power cycled to come back to live), so I'll give 2.4.17 a go later.
David Coulson http://davidcoulson.net/