From owner-freebsd-xen@FreeBSD.ORG Mon Nov 25 11:07:01 2013 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5DE1A625 for ; Mon, 25 Nov 2013 11:07:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4C9592F6C for ; Mon, 25 Nov 2013 11:07:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id rAPB71qc090089 for ; Mon, 25 Nov 2013 11:07:01 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id rAPB70Nt090087 for freebsd-xen@FreeBSD.org; Mon, 25 Nov 2013 11:07:00 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 25 Nov 2013 11:07:00 GMT Message-Id: <201311251107.rAPB70Nt090087@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-xen@FreeBSD.org Subject: Current problem reports assigned to freebsd-xen@FreeBSD.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Nov 2013 11:07:01 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/183139 xen [xen] [patch] ifconfig options on xn0 lost after xen v o kern/180788 xen [xen] [panic] XEN PV kernel 9.2-BETA1 panics on boot o kern/180403 xen [xen] Problems with GENERIC and XENHVM kernels with Xe o kern/180402 xen [xen] XEN kernel does not load in XenClient 4.5.5 o kern/179814 xen [xen] mountroot fails with error=19 under Xen on 9-STA o kern/176471 xen [xen] xn driver crash on detach o kern/176053 xen [xen] [patch] i386: Correct wrong usage of vsnprintf() o kern/175954 xen [xen] XENHVM xn network driver extreme packet loss dur o kern/175822 xen [xen] FreeBSD 9.1 does not work with Xen 4.0 o kern/175757 xen [xen] [patch] xen pvhvm looses keyboard input from VNC o kern/171873 xen [xen] xn network device floods warning in dmesg o kern/171118 xen [xen] FreeBSD XENHVM guest doesn't shutdown cleanly o kern/166174 xen [xen] Problems ROOT MOUNT ERROR o kern/165418 xen [xen] Problems mounting root filesystem from XENHVM o kern/164630 xen [xen] XEN HVM kernel: run_interrupt_driven_hooks: stil o kern/164450 xen [xen] Failed to install FreeeBSD 9.0-RELEASE from CD i o kern/162677 xen [xen] FreeBSD not compatible with "Current Stable Xen" o kern/161318 xen [xen] sysinstall crashes with floating point exception o kern/155468 xen [xen] Xen PV i386 multi-kernel CPU system is not worki o kern/155353 xen [xen] [patch] put "nudging TOD" message under boot_ver o kern/154833 xen [xen]: xen 4.0 - DomU freebsd8.2RC3 i386, XEN kernel. o kern/154473 xen [xen] xen 4.0 - DomU freebsd8.1 i386, XEN kernel. Not o kern/154472 xen [xen] xen 4.0 - DomU freebsd8.1 i386 xen kernel reboot o kern/154428 xen [xen] xn0 network interface and PF - Massive performan o kern/153674 xen [xen] i386/XEN idle thread shows wrong percentages o kern/153672 xen [xen] [panic] i386/XEN panics under heavy fork load o kern/153620 xen [xen] Xen guest system clock drifts in AWS EC2 (FreeBS o kern/153477 xen [xen] XEN pmap code abuses vm page queue lock o kern/153150 xen [xen] xen/ec2: disable checksum offloading on interfac o kern/152228 xen [xen] [panic] Xen/PV panic with machdep.idle_mwait=1 o kern/144629 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143398 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143340 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor f kern/143069 xen [xen] [panic] Xen Kernel Panic - Memory modified after f kern/135667 xen ufs filesystem corruption on XEN DomU system f kern/135421 xen [xen] FreeBSD Xen PVM DomU network failure - netfronc. f kern/135178 xen [xen] Xen domU outgoing data transfer stall when TSO i p kern/135069 xen [xen] FreeBSD-current/Xen SMP doesn't function at all f i386/124516 xen [xen] FreeBSD-CURRENT Xen Kernel Segfaults when config o kern/118734 xen [xen] FreeBSD 6.3-RC1 and FreeBSD 7.0-BETA 4 fail to b 40 problems total. From owner-freebsd-xen@FreeBSD.ORG Fri Nov 29 15:28:23 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 17B59B0E for ; Fri, 29 Nov 2013 15:28:23 +0000 (UTC) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id D49841CF9 for ; Fri, 29 Nov 2013 15:28:22 +0000 (UTC) Received: from Mail-PC.tdx.co.uk (storm.tdx.co.uk [62.13.130.251]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id rATFNQQA026450 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 29 Nov 2013 15:23:27 GMT Date: Fri, 29 Nov 2013 15:23:26 +0000 From: Karl Pielorz To: freebsd-xen@freebsd.org Subject: Xen Guests / NTP best practice? Message-ID: <960417385DD53D94B3E2DF1C@Mail-PC.tdx.co.uk> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Nov 2013 15:28:23 -0000 Hi, We have a number of FreeBSD 9.x boxes now running under XenServer 6.2 Does anyone have any info / best practice / guides for what's best to use NTP / time sync wise? I've noticed that NTP isn't "overly happy" on some of these hosts (i.e. it doesn't seem to settle on some, or will run for a while - then de-sync). We have two local NTP servers (not virtualized) - should we be getting the guest to sync? - Can Xen keep the clock in sync for us (Xen itself is pointed at the two ntp servers) - or are there any options / configs we should consider using with NTP to keep time sync'd up? Thanks, -Karl From owner-freebsd-xen@FreeBSD.ORG Fri Nov 29 17:43:42 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 30449725 for ; Fri, 29 Nov 2013 17:43:42 +0000 (UTC) Received: from SMTP.CITRIX.COM (smtp.citrix.com [66.165.176.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 80E2A13F0 for ; Fri, 29 Nov 2013 17:43:40 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.93,798,1378857600"; d="scan'208";a="79261003" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 29 Nov 2013 17:43:33 +0000 Received: from [IPv6:::1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.342.4; Fri, 29 Nov 2013 12:43:32 -0500 Message-ID: <5298D244.3070905@citrix.com> Date: Fri, 29 Nov 2013 18:43:32 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: Karl Pielorz , Subject: Re: Xen Guests / NTP best practice? References: <960417385DD53D94B3E2DF1C@Mail-PC.tdx.co.uk> In-Reply-To: <960417385DD53D94B3E2DF1C@Mail-PC.tdx.co.uk> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-DLP: MIA2 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Nov 2013 17:43:42 -0000 On 29/11/13 16:23, Karl Pielorz wrote: > > Hi, > > We have a number of FreeBSD 9.x boxes now running under XenServer 6.2 > > Does anyone have any info / best practice / guides for what's best to > use NTP / time sync wise? > > I've noticed that NTP isn't "overly happy" on some of these hosts (i.e. > it doesn't seem to settle on some, or will run for a while - then de-sync). > > We have two local NTP servers (not virtualized) - should we be getting > the guest to sync? - Can Xen keep the clock in sync for us (Xen itself > is pointed at the two ntp servers) - or are there any options / configs > we should consider using with NTP to keep time sync'd up? There have been some improvements in 10 regarding timekeeping, now FreeBSD makes use of the PV timer and PV clock when running under HVM, which should be more stable. Could you try if your issues with ntp are reproducible on 10? Roger. From owner-freebsd-xen@FreeBSD.ORG Sat Nov 30 10:53:04 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2487F6EA for ; Sat, 30 Nov 2013 10:53:04 +0000 (UTC) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id D8DDE18D0 for ; Sat, 30 Nov 2013 10:53:03 +0000 (UTC) Received: from study64.tdx.co.uk (study64.tdx.co.uk [62.13.130.231]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id rAUAqxCa025674 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 30 Nov 2013 10:52:59 GMT Date: Sat, 30 Nov 2013 10:52:59 +0000 From: Karl Pielorz To: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= , freebsd-xen@freebsd.org Subject: Re: Xen Guests / NTP best practice? Message-ID: In-Reply-To: <5298D244.3070905@citrix.com> References: <960417385DD53D94B3E2DF1C@Mail-PC.tdx.co.uk> <5298D244.3070905@citrix.com> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Nov 2013 10:53:04 -0000 --On 29 November 2013 18:43:32 +0100 Roger Pau Monn=C3=A9=20 wrote: > There have been some improvements in 10 regarding timekeeping, now > FreeBSD makes use of the PV timer and PV clock when running under HVM, > which should be more stable. > > Could you try if your issues with ntp are reproducible on 10? Sure, I'll give 10 a go. Does the above mean for a VM you don't need to run = ntp? (i.e. it'll stay in sync with dom0 / the XenServer?) - or is ntp still = necessary? Likewise do you know if there is any recommended solution for 9.x (which is = the bulk of our VM's). Thanks, -Karl From owner-freebsd-xen@FreeBSD.ORG Sat Nov 30 11:03:48 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 620D41A2 for ; Sat, 30 Nov 2013 11:03:48 +0000 (UTC) Received: from SMTP02.CITRIX.COM (smtp02.citrix.com [66.165.176.63]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B01781B68 for ; Sat, 30 Nov 2013 11:03:22 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.93,802,1378857600"; d="scan'208";a="76965300" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 30 Nov 2013 11:03:08 +0000 Received: from [IPv6:::1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.342.4; Sat, 30 Nov 2013 06:03:07 -0500 Message-ID: <5299C5EA.3020605@citrix.com> Date: Sat, 30 Nov 2013 12:03:06 +0100 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: Karl Pielorz , Subject: Re: Xen Guests / NTP best practice? References: <960417385DD53D94B3E2DF1C@Mail-PC.tdx.co.uk> <5298D244.3070905@citrix.com> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-DLP: MIA2 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Nov 2013 11:03:48 -0000 On 30/11/13 11:52, Karl Pielorz wrote: > > > --On 29 November 2013 18:43:32 +0100 Roger Pau Monné > wrote: > >> There have been some improvements in 10 regarding timekeeping, now >> FreeBSD makes use of the PV timer and PV clock when running under HVM, >> which should be more stable. >> >> Could you try if your issues with ntp are reproducible on 10? > > Sure, I'll give 10 a go. Does the above mean for a VM you don't need to > run ntp? (i.e. it'll stay in sync with dom0 / the XenServer?) - or is > ntp still necessary? Well, if the Dom0 is keep in sync, the DomU clock should also be in sync, but I'm not sure how often does FreeBSD poll the underlying clock, so I would recommend running ntp even in that case (certainly it's not going to hurt). > Likewise do you know if there is any recommended solution for 9.x (which > is the bulk of our VM's). Apart from ntp/ntpdate, I cannot think of anything else. Backporting the changes from 10 is certainly not going to be easy. Roger.