WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Time/clock issues with Xen 3.0.3?

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Time/clock issues with Xen 3.0.3?
From: "Jerry Amundson" <jamundso@xxxxxxxxx>
Date: Wed, 29 Nov 2006 09:49:48 -0600
Delivery-date: Wed, 29 Nov 2006 07:50:07 -0800
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=sgkYlRza/udaYlML79cft0KFGugE2czJYIlt4+BNIcjr2HyPW9gO502Hp3Z0SsZLDnJmodSJ1VhtjIwq+hP5dh2ipgtClaWEQekzNsyYfB2F+y4gpSjjZ8phsjI0bVGWhV8RY0JA9zjlZrcvTPyRxkl8MeMKBpAf/g4XggFfpV4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <Pine.LNX.4.61.0611291528230.4658@xxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <1164436051.14311.291.camel@tower> <456C3B97.29127.65EB31B@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <Pine.LNX.4.61.0611281520550.3010@xxxxxxxxxxxxxxxx> <1164791993.8379.160.camel@tower> <2075804706-1164794458-cardhu_blackberry.rim.net-1858323300-@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <6d06ce20611290606i6a04c741wcab134d1cbf25694@xxxxxxxxxxxxxx> <Pine.LNX.4.61.0611291528230.4658@xxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On 11/29/06, marek cervenka <cervajs@xxxxxxxxxx> wrote:
> On Wed, 29 Nov 2006, Jerry Amundson wrote:
>
> > On 11/29/06, Chad Oleary < oleary.chad@xxxxxxxxx> wrote:
> >> ntp is to correct drift. It was not designed be the clock itself. If the.
> >> clock doesn't keep proper time, do you add more clocks to keep it correct?
> >> No, you fix the clock.
> >>
> >> Ntp has it's place. But, it doesn't work well with a broken clock. Throwing
> >> ntp at this is inappropriate.
> >
> > FWIW, the clock in my dom0 and domU's are perfectly in sync.
> > (2.6.16.29-xen_3.0.3.0 installed from 32-bit xensource.com rpm's)
>
> which xen scheduler?

Hmm. I've not had much hands-on with sched - how can I tell?
"xm sched-sedf" returns
Name                              ID Period(ms) Slice(ms) Lat(ms) Extra Weight
Domain-0                          -1      -0.0      -0.0    -0.0     -1     -1
dom1                              -1      -0.0      -0.0    -0.0     -1     -1
dom2                              -1      - 0.0      -0.0    -0.0     -1     -1


> how many domU?

Just 2, currently...

jerry
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users