From: John Soros <sorosj@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] lguest on 2.6.25
Date: Thu, 28 Aug 2008 10:21:27 +0200 [thread overview]
Message-ID: <20080828102127.542af38f@dazone> (raw)
In-Reply-To: <5bb2fcc60808271928m40da8c01ld9ee4dc0f94720e9@mail.gmail.com>
Hi again, 9fans
On Wed, 27 Aug 2008 21:28:42 -0500
"Alex Lee" <alexlee@uchicago.edu> wrote:
> On Tue, Aug 26, 2008 at 1:44 AM, John Soros <sorosj@gmail.com> wrote:
> > Ok, still, it would be great to know how to set the time, as my time is way off (by more than 4
> > hours). Best++
> > John
>
> Hi again,
>
> A couple of updates: I'm getting the same cron messages and time
> problems that John is seeing. I've made sure that timesync isn't
> running. My lguest time is about 3.5 hours ahead of host time.
>
> As for the load issue: The full cpu usage that I was seeing earlier
> actually stops after a several minutes.
This is what i've been experiencing. This is fine, from the linux host, the guest takes a lot of load in the begginning, but then it calms down, and the load only goes up once in a while. From inside the guest, though, the load looks like it's maxed out all the tim. This might be because of time issues, though.
As for the timezone issues, well, i have my timezon set up properly on the host, and in plan9 I did cp /adm/timezon/CET /adm/timezone/local.
>
> After booting, ^T^Tp shows genrandom as Running. Several minutes later
> the cpu usage drops to near idle, and genrandom goes to Wakeme. Then
> every now and then (I'm not sure if anything in particular triggers
> it, or if just randomly happens) I see the cpu usage jump again, and I
> can see that genrandom is once again Running. Then after several
> minutes it stops again.
>
> When genrandom is running, stats shows a load of around 3000.
> Otherwise, load is always around 2000.
>
> The problem looks similar to this:
> http://9fans.net/archive/2006/03/588 -- except that the lguest
> instance works fine while genrandom is running. Is this genrandom
> behavior anything out of the ordinary?
>
> Alex
>
>
John
next prev parent reply other threads:[~2008-08-28 8:21 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-24 23:23 Alex Lee
2008-08-25 4:26 ` ron minnich
2008-08-25 4:32 ` ron minnich
2008-08-25 4:58 ` Alex Lee
2008-08-25 9:03 ` John Soros
2008-08-25 10:56 ` erik quanstrom
2008-08-25 14:52 ` ron minnich
2008-08-25 14:52 ` ron minnich
2008-08-25 14:59 ` erik quanstrom
2008-08-25 15:09 ` ron minnich
2008-08-25 18:48 ` John Soros
2008-08-25 18:54 ` lucio
2008-08-25 20:39 ` John Soros
2008-08-25 21:27 ` John Soros
2008-08-25 23:53 ` [9fans] Anyone handy with Alpha assembler? Benjamin Huntsman
2008-08-26 15:24 ` Paweł Lasek
2008-08-26 17:56 ` Benjamin Huntsman
2008-08-26 22:03 ` Paweł Lasek
2008-08-26 23:09 ` Benjamin Huntsman
2008-08-25 22:44 ` [9fans] lguest on 2.6.25 ron minnich
2008-08-26 6:44 ` John Soros
2008-08-28 2:28 ` Alex Lee
2008-08-28 2:38 ` ron minnich
2008-08-28 12:06 ` erik quanstrom
2008-08-28 8:21 ` John Soros [this message]
2008-08-28 15:38 ` ron minnich
2008-08-28 16:50 ` John Soros
2008-08-28 16:59 ` erik quanstrom
2008-08-28 17:24 ` Alex Lee
2008-08-28 18:07 ` John Soros
2008-08-28 8:27 ` Richard Miller
2008-08-28 11:55 ` erik quanstrom
2008-08-28 17:34 ` Alex Lee
2008-08-28 2:39 ` ron minnich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080828102127.542af38f@dazone \
--to=sorosj@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).