On Sun, 24 Aug 2008 23:58:21 -0500
Alex Lee [EMAIL PROTECTED] wrote:
On Sun, Aug 24, 2008 at 11:32 PM, ron minnich [EMAIL PROTECTED] wrote:
[snip]
lguestnetwork is
see this line? It's a variable read in /rc/bin/cpurc. You can check
that script and see how it can be set so that
Hello,
I have gotten the lguest port working on the 2.6.25.0 kernel, it works mighty
fine here.
The load issue for me is only on plan9, on the host I can see with 'top' that
the lguest guest isn't consuming all the cpu, so this might ust be a plan9
problem. I have also seen quite a few
... and any great travel plans to share?
DaveL
Any Brits going to iwp9? ...
... and any great travel plans to share?
yes, and i must sort that out
-Steve
On Mon, Aug 25, 2008 at 3:56 AM, erik quanstrom [EMAIL PROTECTED] wrote:
Hello,
I have gotten the lguest port working on the 2.6.25.0 kernel, it works
mighty fine here.
The load issue for me is only on plan9, on the host I can see with 'top'
that the lguest guest isn't consuming all the
On Mon, Aug 25, 2008 at 7:52 AM, ron minnich [EMAIL PROTECTED] wrote:
On Mon, Aug 25, 2008 at 3:56 AM, erik quanstrom [EMAIL PROTECTED] wrote:
Hello,
I have gotten the lguest port working on the 2.6.25.0 kernel, it works
mighty fine here.
The load issue for me is only on plan9, on the host I
both the excessive load and these messages sound like a timesync problem.
yeah, that's really weird. One option is to set up the kernels without
any fancy timers -- just use the old PC timers.
do you think that's the problem?
time jumping backwards doesn't seem like something that could
be
On Mon, Aug 25, 2008 at 7:59 AM, erik quanstrom [EMAIL PROTECTED] wrote:
it any event, fixing timesync properly is likely to fix the excessive
load problem.
good to know. I probably jumped to the wrong conclusion.
ron
I'm currently enjoying cheap wine with some friends in Saloniki. If
you get a cheap ticket you can go to Volos from here with the bus (it
is much more comfortable than the train).
From the airport to the bus station you will have to travel to the
other side of the city, which can take quite some
... and any great travel plans to share?
Hardly a Brit and going via Italy, but I'll be there.
++L
Hello again,
Well, i don't think I am starting two timesync, ps a shows only one:
cpu% ps a |grep timesync
bootes 770:00 0:00 92K Preadtimesync
I also can not write to /dev/rtc, so the timesync part of cpurc fails, this
part in particular
=snip
if(! ps|grep -s
Well, i don't think I am starting two timesync, ps a shows only one:
If Xen is anything to go by, time keeping is a problem in
virtualisation. And Erik is misguiding you :-)
Thing is, if timesync is wresting with the clock as it seems to do if
two instances are running, it does consume a lot
Hello.
For one timesync couldn't write to the rtc, so I commented out the lines in
cpurc.
Well, here timesync is not the problem, time is reported incorrectly, and I do
not really know how to set it. I tried echoing unix time into '#r' and
/dev/rtc, with no luck:
$sysname# ls -l /dev/rtc
I just realized that even one timesync is too much. You should not
run any at all. The hardware clock is set from Linux and I don't even
allow it to be set. It makes no sense to do that.
So don't let timesync run.
thanks
ron
14 matches
Mail list logo
