From owner-freebsd-xen@FreeBSD.ORG Tue Jun 2 07:49:43 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 D9C931065672; Tue, 2 Jun 2009 07:49:43 +0000 (UTC) (envelope-from mister.olli@googlemail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 2E7408FC08; Tue, 2 Jun 2009 07:49:42 +0000 (UTC) (envelope-from mister.olli@googlemail.com) Received: by bwz9 with SMTP id 9so8125057bwz.43 for ; Tue, 02 Jun 2009 00:49:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:subject:from:reply-to:to:cc :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=8Y/Cj2RPd546CqrkiOWAENcKFYMn2TZ1Sj5KFA7AdX8=; b=roWblX2Y7ol6ZPeV28P3rnxidTllS92zbW9rwERA0rQpvfw35Ey77TITxrgnVVy9pG RMPvlLfcNjUCHPnp7MSAWbBBXcfgMvhPwchJKTGzlJCGOnpvUvyaZZyYHqrVORioqrJM 3ceQREgY3F4jhBHln+R/aB2UITaGjyYPl2+l8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=subject:from:reply-to:to:cc:in-reply-to:references:content-type :date:message-id:mime-version:x-mailer:content-transfer-encoding; b=lPIg6UF7O3/MJhgazKshCk66QCS1zWfTco9epM5QpBcIjxgVpxlhQrgIGAgNPPtDrI aEVeDuzzQcq4lGefzRZ+UQ16KdJ6Ioijex/fOGp6qGXxsEt2Ms0Gk+d5VGhxR/r+zy0Q h/Nk+jg1Rr4Yc2Pncsmw/Mil5rHJmZIq7JUac= Received: by 10.102.228.10 with SMTP id a10mr3772425muh.26.1243928982055; Tue, 02 Jun 2009 00:49:42 -0700 (PDT) Received: from ?192.168.220.100? (Zf9c8.z.pppool.de [89.61.249.200]) by mx.google.com with ESMTPS id e10sm6010453muf.44.2009.06.02.00.49.40 (version=SSLv3 cipher=RC4-MD5); Tue, 02 Jun 2009 00:49:40 -0700 (PDT) From: Mister Olli To: Adrian Chadd In-Reply-To: References: <1243774686.12279.7.camel@phoenix.blechhirn.net> Content-Type: text/plain Date: Tue, 02 Jun 2009 09:49:03 +0200 Message-Id: <1243928943.2351.5.camel@phoenix.blechhirn.net> Mime-Version: 1.0 X-Mailer: Evolution 2.24.5 Content-Transfer-Encoding: 7bit Cc: freebsd-xen@freebsd.org Subject: Re: Clock TOD issues (mostly) resolved? X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mister.olli@googlemail.com 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: Tue, 02 Jun 2009 07:49:44 -0000 Hi, > > - scp'ing the kernel file to the dom0 instance hanged after transfering > > ~ 1MB of data and did not finish. This now works perfect. I > > hadn't got the time to test larger network transfers. > > Good! Sorry on that, I just recognized that it's not fixed right now. Maybe Most probable I've tested with the wrong kernel, since I have a r kernel here to transfer my freshly build kernel to the host dom0. I just tested with r193225 and it didn't work. Transfer always stops after 2112kb of transfered data, no matter what kind of data I copy: ======================================================================== template-8_CURRENT# scp /boot/kernel/kernel dante@10.30.1.15:/tmp Password: kernel 46% 2112KB 268.4KB/s - stalled -^CKilled by signal 2. template-8_CURRENT# dd if=/dev/zero of=/tmp/more_data bs=1024k count=512 512+0 records in 512+0 records out 536870912 bytes transferred in 27.200000 secs (19737901 bytes/sec) template-8_CURRENT# scp /tmp/more_data dante@10.30.1.15:/tmp Password: more_data 0% 2112KB 662.8KB/s - stalled -^CKilled by signal 2. template-8_CURRENT# ======================================================================== Transfering smaller files (like SVN checkout) works like a charm within the domU. I also tested transfering 512MB of data from dom0 -> domU and it worked as expected. > > > - clock jumps fully disappeared for me. I can do a complete 'make > > buildworld' without any interruptions due to the time jump, even > > when I'm not using ntpd within the domU. > > Good! The time will still drift a little until a hypervisor wall clock > sync occurs (mostly due to a large enough change to the dom0 time); > I'll investigate that later. I'm curious to know exactly how Linux > DomU's manage to keep in lock-step with the dom0 time. Didn't recognize any heavy time drifts until now. I have less than 0.5 after ~14 hours uptime. This is great :-) Regards, --- Mr. Olli