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] ntpd under Xen Dom0 exhibits extremely high jitter/nois

To: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-users] ntpd under Xen Dom0 exhibits extremely high jitter/noise? runs stable/quiet under non-xen kernel.
From: mail ignored <0.bugs.only.0@xxxxxxxxx>
Date: Wed, 13 Jan 2010 15:36:13 -0800
Cc: Xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 13 Jan 2010 15:36:55 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=7qZgS5xhp7jmB8Hs5GFcuwPKVrFBH9wHTgUDsUks1p8=; b=rH7ST4l5lq4GwyPbAjVF4slPqZiw15JY4RXzJLtn8HNXFhsnvZu80Hje7OXsM1RmVU Z82CPq4dcse67a/rxl32lyQ+ByVAuiP5UWBn3UqS/nkJeTX4qUWKrN/YUD2EvxX0ZfGJ eojV25Ut+nJNVy54XPo2pOSoWMca9i9snBXHs=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=xDlrRFwJ50Q943YZn3NZaASIR13ifsgiwQvhIXEPhwZtTOv3DeiL04cyP6j5AJB5My C/nat+CiM03SzqrpM256bbrwo2PwfuuQPlHc50yyH3SRMrM7w5elazoUek17u1ZLU21l IqQcIcR2Hc7CbXPgjIy2ZsE03lxPTULmQ3mIY=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <c67eed301001131410m7b11d912ode03a74a49ebbe5f@xxxxxxxxxxxxxx>
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <20100113071325.GU25902@xxxxxxxxxxx> <c67eed301001131006i47a6889fyb3ba6419dad67116@xxxxxxxxxxxxxx> <20100113180859.GO25902@xxxxxxxxxxx> <c67eed301001131010x28d9cd8bu2610195d3cbed57b@xxxxxxxxxxxxxx> <20100113181239.GP25902@xxxxxxxxxxx> <c67eed301001131025v4c530db0ic37af2636405477a@xxxxxxxxxxxxxx> <20100113183940.GS25902@xxxxxxxxxxx> <20100113203818.GU25902@xxxxxxxxxxx> <20100113215549.GA25902@xxxxxxxxxxx> <c67eed301001131410m7b11d912ode03a74a49ebbe5f@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, Jan 13, 2010 at 2:10 PM, mail ignored <0.bugs.only.0@xxxxxxxxx> wrote:
> now back to watching ntpq ...

after applying the suggestions above, we've still got excessive
offset/jitter ...

boot to,

  title xen
    root (hd0,0)
    kernel /xen.gz loglvl=all loglvl_guest=all dom0_mem=1024M
vga=gfx-1280x1024x32 console=vga,com1 com1=57600,8n1 iommu=1
cpufreq=xen:performance cpuidle dom0_max_vcpus=1 dom0_vcpus_pin
sched=credit
    module /vmlinuz-xen root=/dev/V0/ROOT rootfstype=ext4
rootflags=journal_checksum resume=/dev/V0/SWAP showopts splash=silent
selinux=0 SELINUX_INIT=NO elevator=cfq vga=0x31a console=tty0
console=xvc0,57600 iommu=off noirqdebug clocksource=xen
    module /initrd-xen

with,

 cat /proc/cpuinfo | grep MHz
  cpu MHz         : 2800.000
  cpu MHz         : 2800.000
  cpu MHz         : 2800.000
  cpu MHz         : 2800.000

 xenpm get-cpufreq-para | grep governor
  current_governor     : performance
  current_governor     : performance
  current_governor     : performance
  current_governor     : performance

 cat /etc/init.d/boot.local
  /usr/sbin/xenpm set-scaling-governor ondemand
  /usr/sbin/xenpm set-scaling-governor performance
  /usr/sbin/xm sched-credit -d Domain-0 -w 512

for DomU == "test_guest",

 cat /etc/xen/vm/test_guest.cfg
  ...
  cpus      = '1-3'
  vcpus     = 3
  localtime = 0
  ...


 xm list
   Name                                        ID   Mem VCPUs
State   Time(s)
   Domain-0                                     0  1022     1
r-----     55.1
   test_guest                                   1  1024     3
-b----      7.9

 xm vcpu-list Domain-0
  Name                                ID  VCPU   CPU State   Time(s)
CPU Affinity
  Domain-0                             0     0     0   r--      56.6 0

 xm vcpu-list test_guest
  Name                                ID  VCPU   CPU State   Time(s)
CPU Affinity
  test_guest                           1     0     3   -b-       3.6 1-3
  test_guest                           1     1     2   -b-       2.2 1-3
  test_guest                           1     2     1   -b-       2.1 1-3

 xm sched-credit -d Domain-0
  Name                                ID Weight  Cap
  Domain-0                             0    256    0

??? hrm.  checking,

 cat /etc/init.d/boot.local
  /usr/sbin/xenpm set-scaling-governor ondemand
  /usr/sbin/xenpm set-scaling-governor performance
  /usr/sbin/xm sched-credit -d Domain-0 -w 512

 xm dmesg | grep -i scheduler
  (XEN) Using scheduler: SMP Credit Scheduler (credit)

 xm sched-credit -d Domain-0 -w 512
 xm sched-credit -d Domain-0
  Name                                ID Weight  Cap
  Domain-0                             0    512    0

 xm sched-credit -d test_guest
  Name                                ID Weight  Cap
  test_guest                           1    256    0

 grep dom0 /etc/xen/xend-config.sxp
  (dom0-min-mem 0)
  (enable-dom0-ballooning no)
  (dom0-cpus 0)

after ~ 1/2 hour,

 uptime
  15:29pm  up   0:34,  1 user,  load average: 0.00, 0.00, 0.02

ntp sync has reached state=2 @ stratum=2, but i'm still seeing the
excessive Xen offset/jitter -- only under Xen, e.g.

 ntpq -p -c rv
        assID=0 status=06d4 leap_none, sync_ntp, 13 events, 
event_peer/strat_chg,
        version="ntpd 4.2.4p8@xxxxxxxx Tue Dec 15 14:06:22 UTC 2009 (1)",
        processor="x86_64", system="Linux/2.6.31.8-0.1-xen", leap=00, stratum=2,
        precision=-20, rootdelay=17.385, rootdispersion=125.916, peer=7611,
        refid=207.200.81.113,
        reftime=cef8d28b.247d36d5  Wed, Jan 13 2010 15:15:23.142, poll=6,
        clock=cef8d5e2.cd45b382  Wed, Jan 13 2010 15:29:38.801, state=2,
        offset=-90.707, frequency=-500.000, jitter=513.693, noise=25.184,
        stability=154.680, tai=0
             remote           refid      st t when poll reach   delay   offset  
jitter
        
==============================================================================
        +clock.fmt.he.ne .PPS.            1 u   37   64  377   16.531  -1495.9 
522.188
        +otc2.psu.edu    129.6.15.29      2 u   24   64  377  108.729  -1514.8 
516.844
        +clock.isc.org   .GPS.            1 u   31   64  377   20.388  -1509.1 
518.560
        +clock.sjc.he.ne .CDMA.           1 u   48   64  377   20.548  -1475.4 
514.975
        +zorro.sf-bay.or 216.218.254.202  2 u   48   64  377   19.124  -1476.2 
520.580
        *nist1.aol-ca.tr .ACTS.           1 u    6   64  377   26.142  -1543.1 
511.533

so CPU isolation is not involved ... ?

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

<Prev in Thread] Current Thread [Next in Thread>