From owner-freebsd-xen@FreeBSD.ORG Thu May 28 06:39:40 2009 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DCAD01065687 for ; Thu, 28 May 2009 06:39:40 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qy0-f173.google.com (mail-qy0-f173.google.com [209.85.221.173]) by mx1.freebsd.org (Postfix) with ESMTP id 9643D8FC17 for ; Thu, 28 May 2009 06:39:40 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by qyk3 with SMTP id 3so7406496qyk.3 for ; Wed, 27 May 2009 23:39:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=4U1HTn5jvMWlOJNyR8JC0IW94HiEp6YWFbtQ5MTV3uA=; b=eBfS+PK2Rx7vV2qebIBeLEzA464Lg+ryJC/PUrkfKZgX25yDl076QWASxleRZTdXrh 3AoYsHaknMS3yg0kMiEfrFuJH5lYrVKAuNE86xLJjqWg/5nCsi7xskUfcYs9OuS9bpM8 38YGAgtAMzX/VQox4e1exKi+V6tOm14hhIVyE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; b=ByQ4b3PqY6F287WR/+ps7YcqI1ugfLAUAtBkJrTQXQpS2Z3WdRtMuQkDCRFU64uvDu APd1neuAaZ/9AhOITznU5qpUY1/Y2fnRObC0kwYF+4T3Alf8vA3OP2GtxalxUS4dtr2e MgQag2Lijtlyk/gQ48n4XlqofU9mXs/M7gAVU= MIME-Version: 1.0 Sender: adrian.chadd@gmail.com Received: by 10.229.97.194 with SMTP id m2mr578558qcn.21.1243492779778; Wed, 27 May 2009 23:39:39 -0700 (PDT) Date: Thu, 28 May 2009 14:39:39 +0800 X-Google-Sender-Auth: 2a1c9e13fb4fba0b Message-ID: From: Adrian Chadd To: freebsd-xen@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Update: Xen, networking, RTC and clocks X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 28 May 2009 06:39:41 -0000 G'day, I've committed a basic Xen Hypervisor RTC to FreeBSD-current. The time is now correctly synced to the hypervisor TOD clock. I've figured out the "weirdness" in the running clock and time of day changes. Updates to the Dom0 clock will touch the hypervisor clock. The current -current logic doesn't read the Xen hypervisor TOD and so a drift of > 1 second seems to set the -current TOD clock to the wrong value (actually, the "hypervisor start" TOD. :) I've also fixed some memory exhaustion issues in the netfront driver. It now doesn't panic for me under stress. Anyway. I'd appreciate it if people updated to the latest -current and tested Xen out. Thanks, Adrian