From owner-freebsd-xen@FreeBSD.ORG Mon Jul 22 16:23:55 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 67F64658; Mon, 22 Jul 2013 16:23:55 +0000 (UTC) (envelope-from jeroen@dckd.nl) Received: from positron.dckd.nl (positron.dckd.nl [IPv6:2a02:898:62:f6::63]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 27B572752; Mon, 22 Jul 2013 16:23:54 +0000 (UTC) Received: from doc.dckd.nl (doc.dckd.nl [145.99.178.214]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by positron.dckd.nl (Postfix) with ESMTPSA id 2BEE7F827F; Mon, 22 Jul 2013 18:23:52 +0200 (CEST) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: FreeBSD PVHVM call for testing From: Jeroen van der Ham In-Reply-To: Date: Mon, 22 Jul 2013 18:23:51 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <51AC4BFA-81D8-444A-9BD4-B002ED6315CC@dckd.nl> References: <519131D8.9010307@citrix.com> <519E54DE.5090304@citrix.com> <51B5E730.6070007@citrix.com> <51B9FF53.2020901@citrix.com> <4A595D02-7B79-4C6C-9356-55FA9E45EDDC@dckd.nl> <51ECED83.9020905@citrix.com> To: =?iso-8859-1?Q?Roger_Pau_Monn=E9?= X-Mailer: Apple Mail (2.1508) Cc: "freebsd-xen@freebsd.org" , "xen-users@lists.xen.org" , "Justin T. Gibbs" , "freebsd-virtualization@freebsd.org" , xen-devel X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 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, 22 Jul 2013 16:23:55 -0000 Hi, On 22 Jul 2013, at 10:40, Jeroen van der Ham wrote: >> Could you also try a HEAD XENHVM kernel (without my patches), to see = if >> the issue is related to my changes or to some bug already present in = HEAD? It seems I was worrying too soon. I have been putting the system through the wringer some more, and I now = believe that it has been caused by adding a new swap file. Just before I = rebooted my system I created a larger swap file to be used by = /etc/rc.d/add_swap. Right after I rebooted I started compiling and doing other things. And I = am getting the feeling that the system was still initialising that swap = file and was unable to provide swap space at that time. I've rebooted my system again with the PVHVM system, abused it even more = than I did before and I'm not seeing the same messages again, nor = getting any exaggerated sluggishness. So my apologies for the false alarm. Jeroen.