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/noise

To: mail ignored <0.bugs.only.0@xxxxxxxxx>
Subject: Re: [Xen-users] ntpd under Xen Dom0 exhibits extremely high jitter/noise? runs stable/quiet under non-xen kernel.
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Wed, 13 Jan 2010 19:37:54 +0200
Cc: "Fajar A. Nugraha" <fajar@xxxxxxxxx>, Xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 13 Jan 2010 09:39:14 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <c67eed301001130923i2fdd1c64p7186282861ac7f78@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: <c67eed301001121814s37bc44bftf8e4f9a4485f1015@xxxxxxxxxxxxxx> <20100113071325.GU25902@xxxxxxxxxxx> <c67eed301001130844p751c8cehd943b07729e08ebd@xxxxxxxxxxxxxx> <20100113171349.GJ25902@xxxxxxxxxxx> <c67eed301001130923i2fdd1c64p7186282861ac7f78@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)
On Wed, Jan 13, 2010 at 09:23:46AM -0800, mail ignored wrote:
> 
> > You might want to give dom0 for example weight of 384 or 512,
> > so it'll have more weight than the guests (the default weight is 256).
> 
> missed the default value.  that explains that. thanks.
> 
> > dom0_vcpus=1 dom0_vcpus_pin
> 
> does that *presume* pin to cpu=0?
> 
> iiuc, i *should* be also able to
> 
>   dom0_vcpus=2 dom0_vcpus_pin
> 
> and specify that it pins to cpus=0&1?  or doe the pinning always use
> the lowest CPU #s?
> 

Yeah, "dom0_vcpus=2 dom0_vcpus_pin" should work.
You can verify it by running "xm vcpu-list" after reboot.

-- Pasi


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

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