From owner-freebsd-xen@FreeBSD.ORG Sun May 29 11:02:58 2011 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 03701106564A for ; Sun, 29 May 2011 11:02:58 +0000 (UTC) (envelope-from hugo@barafranca.com) Received: from mail.barafranca.com (mail.barafranca.com [67.213.67.47]) by mx1.freebsd.org (Postfix) with ESMTP id C9BD48FC0C for ; Sun, 29 May 2011 11:02:57 +0000 (UTC) Received: from localhost (unknown [172.16.100.24]) by mail.barafranca.com (Postfix) with ESMTP id DC2E8E6E for ; Sun, 29 May 2011 11:02:56 +0000 (UTC) X-Virus-Scanned: amavisd-new at barafranca.com Received: from mail.barafranca.com ([172.16.100.24]) by localhost (mail.barafranca.com [172.16.100.24]) (amavisd-new, port 10024) with ESMTP id ueuxTtYiVQqP for ; Sun, 29 May 2011 11:02:14 +0000 (UTC) Received: from [192.168.1.1] (a94-132-1-126.cpe.netcabo.pt [94.132.1.126]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.barafranca.com (Postfix) with ESMTPSA id 8556DE6B for ; Sun, 29 May 2011 11:02:14 +0000 (UTC) Message-ID: <4DE227B5.6000903@barafranca.com> Date: Sun, 29 May 2011 12:02:13 +0100 From: Hugo Silva User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-xen@freebsd.org References: <4DDBB66F.6030608@barafranca.com> <4DDC11AA.6030106@barafranca.com> <4DDD2C41.2000302@barafranca.com> In-Reply-To: <4DDD2C41.2000302@barafranca.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: xn_txeof: WARNING: response is -1! 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: Sun, 29 May 2011 11:02:58 -0000 On 05/25/11 17:20, Hugo Silva wrote: > On 05/24/11 21:14, Hugo Silva wrote: >> On 05/24/11 14:45, Hugo Silva wrote: >>> Trying to ssh to the VM produces the error in the subject line on the >>> FreeBSD domU; It's impossible to login. >>> >> >> Some more information for those looking to reproduce this: the above is >> with rxcsum and txcsum disabled in the xn interface: Without that, the >> ssh client on the other side would just say 'Disconnected: Packet corrupt'. >> >> With tx/rxsum disabled, the ssh client will seem to hang, while the >> server spits the xn_txeof message. >> >> >> I seem to recall that disabling TSO helped fix a similar error under >> Citrix XenServer, but alas. No difference. > > Same thing with i386 and full PV. Just tested, also in current. From owner-freebsd-xen@FreeBSD.ORG Sun May 29 13:37:28 2011 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 1E7C6106564A for ; Sun, 29 May 2011 13:37:27 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8D9AA8FC08 for ; Sun, 29 May 2011 13:37:27 +0000 (UTC) Received: by vxc34 with SMTP id 34so3090200vxc.13 for ; Sun, 29 May 2011 06:37:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=YAyUl4CmDciXSLqem1LwLQGMHUia1YISbIndlv2UA/I=; b=en0JcmIvD6X0ff2CknPRJWyUtU/93zqAUziM4tOjS6qLe0L4gMe9CCnCha/qlV0DCi yIMwZheeqaC/ixs54iRKuIFyj+HJonl0opxladVbYjFznfbEIJlbA5DBrBybt3AqPiUB BPoPrBCQkKLZg5NHVONukNbTrTAsimAxC5nBQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=ryioBxcfYQJecfS5DxbovMLWNcjZfUTDqr4fDZyG13qIQWEMnSm5fdmMwlJy7le+6B g38FZoaHc/w9FPKN/5Cyz3hQzO98mNic44I2r7FKZR8mpkFAjDrhH4Pk7Fqsv0L7aE4q YObBpZ6dqc1qO6kucAf1qyCr0ouGxnwLMvn0o= MIME-Version: 1.0 Received: by 10.52.67.105 with SMTP id m9mr5688400vdt.126.1306674669240; Sun, 29 May 2011 06:11:09 -0700 (PDT) Sender: kmacybsd@gmail.com Received: by 10.52.186.67 with HTTP; Sun, 29 May 2011 06:11:09 -0700 (PDT) In-Reply-To: <4DE227B5.6000903@barafranca.com> References: <4DDBB66F.6030608@barafranca.com> <4DDC11AA.6030106@barafranca.com> <4DDD2C41.2000302@barafranca.com> <4DE227B5.6000903@barafranca.com> Date: Sun, 29 May 2011 15:11:09 +0200 X-Google-Sender-Auth: KbhZwdgX6Euu0oNYYpXF1zKrHxQ Message-ID: From: "K. Macy" To: Hugo Silva Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-xen@freebsd.org Subject: Re: xn_txeof: WARNING: response is -1! 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: Sun, 29 May 2011 13:37:28 -0000 Just to verify, other guests (e.g. Linux || NetBSD) don't exhibit this problems? It sounds almost as if xend isn't configuring the domain properly. -Kip On Sun, May 29, 2011 at 1:02 PM, Hugo Silva wrote: > On 05/25/11 17:20, Hugo Silva wrote: >> On 05/24/11 21:14, Hugo Silva wrote: >>> On 05/24/11 14:45, Hugo Silva wrote: >>>> Trying to ssh to the VM produces the error in the subject line on the >>>> FreeBSD domU; It's impossible to login. >>>> >>> >>> Some more information for those looking to reproduce this: the above is >>> with rxcsum and txcsum disabled in the xn interface: Without that, the >>> ssh client on the other side would just say 'Disconnected: Packet corrupt'. >>> >>> With tx/rxsum disabled, the ssh client will seem to hang, while the >>> server spits the xn_txeof message. >>> >>> >>> I seem to recall that disabling TSO helped fix a similar error under >>> Citrix XenServer, but alas. No difference. >> >> Same thing with i386 and full PV. > > Just tested, also in current. > _______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" > From owner-freebsd-xen@FreeBSD.ORG Sun May 29 14:59:24 2011 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 B5AA1106564A for ; Sun, 29 May 2011 14:59:24 +0000 (UTC) (envelope-from hugo@barafranca.com) Received: from mail.barafranca.com (mail.barafranca.com [67.213.67.47]) by mx1.freebsd.org (Postfix) with ESMTP id 63EC08FC1C for ; Sun, 29 May 2011 14:59:24 +0000 (UTC) Received: from localhost (unknown [172.16.100.24]) by mail.barafranca.com (Postfix) with ESMTP id 97442A54; Sun, 29 May 2011 14:59:23 +0000 (UTC) X-Virus-Scanned: amavisd-new at barafranca.com Received: from mail.barafranca.com ([172.16.100.24]) by localhost (mail.barafranca.com [172.16.100.24]) (amavisd-new, port 10024) with ESMTP id vlLp6IeC1Abi; Sun, 29 May 2011 14:58:45 +0000 (UTC) Received: from [192.168.1.1] (a94-132-1-126.cpe.netcabo.pt [94.132.1.126]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.barafranca.com (Postfix) with ESMTPSA id CA8ACA4A; Sun, 29 May 2011 14:58:44 +0000 (UTC) Message-ID: <4DE25F25.6090309@barafranca.com> Date: Sun, 29 May 2011 15:58:45 +0100 From: Hugo Silva User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-xen@freebsd.org References: <4DDBB66F.6030608@barafranca.com> <4DDC11AA.6030106@barafranca.com> <4DDD2C41.2000302@barafranca.com> <4DE227B5.6000903@barafranca.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: xn_txeof: WARNING: response is -1! 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: Sun, 29 May 2011 14:59:24 -0000 On 05/29/11 14:11, K. Macy wrote: > Just to verify, other guests (e.g. Linux || NetBSD) don't exhibit this > problems? It sounds almost as if xend isn't configuring the domain > properly. > Hello, I'm not sure about Linux but a NetBSD 5.1 PV domU works fine. Others are running Linux PV on NetBSD afaik. Maybe http://www.freebsd.org/cgi/query-pr.cgi?pr=143340 is the same issue? (it may be of interest to note that pr is still open - maybe the patch does work and one less pr to worry about :)) I do get "packet corrupt" until txc and rxc are disabled, with both off then the xn_txeof warning is logged and the ssh connection seems to hang. Couldn't apply the patch in the link, the text appears to be mangled. I tried to correct it, but no luck. From owner-freebsd-xen@FreeBSD.ORG Mon May 30 05:25:52 2011 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 F2E75106566B for ; Mon, 30 May 2011 05:25:52 +0000 (UTC) (envelope-from other@ahhyes.net) Received: from ahhyes.net (srv.ahhyes.net [96.44.168.99]) by mx1.freebsd.org (Postfix) with ESMTP id E12728FC0C for ; Mon, 30 May 2011 05:25:52 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=ahhyes.net) by ahhyes.net with esmtp (Exim 4.76 (FreeBSD)) (envelope-from ) id 1QQuIH-00028t-Gh for freebsd-xen@freebsd.org; Mon, 30 May 2011 14:41:33 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 30 May 2011 14:41:33 +1000 From: Alex To: Message-ID: X-Sender: other@ahhyes.net User-Agent: Roundcube Webmail/0.5.1 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: other@ahhyes.net X-SA-Exim-Scanned: No (on ahhyes.net); SAEximRunCond expanded to false Subject: Clock drift issues 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: Mon, 30 May 2011 05:25:53 -0000 Hi Guys, Running 8.2-RELEASE/amd64 as the operating system on my VPS. Every couple of weeks I am finding myself having to log in and resync the clock as it's drifted (I am in Au (GMT+10)). Today again: ---------------------------- srv# date Mon May 30 14:21:16 EST 2011 srv# /etc/rc.d/ntpdate start Setting date via ntp. 30 May 14:37:41 ntpdate[8207]: step time server 203.171.85.237 offset 958.736122 sec srv# date Mon May 30 14:37:43 EST 2011 ----------------------------- Is there any fix for this? Thanks, Alex. From owner-freebsd-xen@FreeBSD.ORG Mon May 30 08:39:22 2011 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 0F705106566C for ; Mon, 30 May 2011 08:39:22 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) by mx1.freebsd.org (Postfix) with ESMTP id 2AE588FC29 for ; Mon, 30 May 2011 08:39:20 +0000 (UTC) Received: from mac2.unsane.co.uk (mac2.unsane.co.uk [10.10.10.191] (may be forged)) (authenticated bits=0) by unsane.co.uk (8.14.4/8.14.4) with ESMTP id p4U8d6GX069960 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 30 May 2011 09:39:07 +0100 (BST) (envelope-from vince@unsane.co.uk) Message-ID: <4DE357AA.3070007@unsane.co.uk> Date: Mon, 30 May 2011 09:39:06 +0100 From: Vincent Hoffman User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Alex References: In-Reply-To: X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-xen@freebsd.org Subject: Re: Clock drift issues 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: Mon, 30 May 2011 08:39:22 -0000 Try running ntpd rather than one off ntpdate? I have plenty of physical machines that need this anyway. Vince On 30/05/2011 05:41, Alex wrote: > Hi Guys, > > Running 8.2-RELEASE/amd64 as the operating system on my VPS. > > Every couple of weeks I am finding myself having to log in and resync > the clock as it's drifted (I am in Au (GMT+10)). > > > Today again: > > ---------------------------- > > srv# date > Mon May 30 14:21:16 EST 2011 > > srv# /etc/rc.d/ntpdate start > Setting date via ntp. > 30 May 14:37:41 ntpdate[8207]: step time server 203.171.85.237 offset > 958.736122 sec > > srv# date > Mon May 30 14:37:43 EST 2011 > > ----------------------------- > > > Is there any fix for this? > > Thanks, Alex. > > _______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" From owner-freebsd-xen@FreeBSD.ORG Mon May 30 08:46:33 2011 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 2D263106566C for ; Mon, 30 May 2011 08:46:33 +0000 (UTC) (envelope-from other@ahhyes.net) Received: from ahhyes.net (srv.ahhyes.net [96.44.168.99]) by mx1.freebsd.org (Postfix) with ESMTP id 193758FC15 for ; Mon, 30 May 2011 08:46:32 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=ahhyes.net) by ahhyes.net with esmtp (Exim 4.76 (FreeBSD)) (envelope-from ) id 1QQy7D-0002Oj-KV for freebsd-xen@freebsd.org; Mon, 30 May 2011 18:46:23 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 30 May 2011 18:46:18 +1000 From: Alex To: In-Reply-To: <4DE357AA.3070007@unsane.co.uk> References: <4DE357AA.3070007@unsane.co.uk> Message-ID: X-Sender: other@ahhyes.net User-Agent: Roundcube Webmail/0.5.1 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: other@ahhyes.net X-SA-Exim-Scanned: No (on ahhyes.net); SAEximRunCond expanded to false Subject: Re: Clock drift issues 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: Mon, 30 May 2011 08:46:33 -0000 Hi, The clock is Sync'd though, it should *stay* correct, right? So there is a bug? On Mon, 30 May 2011 09:39:06 +0100, Vincent Hoffman wrote: > Try running ntpd rather than one off ntpdate? > I have plenty of physical machines that need this anyway. > > > Vince > > On 30/05/2011 05:41, Alex wrote: >> Hi Guys, >> >> Running 8.2-RELEASE/amd64 as the operating system on my VPS. >> >> Every couple of weeks I am finding myself having to log in and >> resync >> the clock as it's drifted (I am in Au (GMT+10)). >> >> >> Today again: >> >> ---------------------------- >> >> srv# date >> Mon May 30 14:21:16 EST 2011 >> >> srv# /etc/rc.d/ntpdate start >> Setting date via ntp. >> 30 May 14:37:41 ntpdate[8207]: step time server 203.171.85.237 >> offset >> 958.736122 sec >> >> srv# date >> Mon May 30 14:37:43 EST 2011 >> >> ----------------------------- >> >> >> Is there any fix for this? >> >> Thanks, Alex. >> >> _______________________________________________ >> freebsd-xen@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-xen >> To unsubscribe, send any mail to >> "freebsd-xen-unsubscribe@freebsd.org" From owner-freebsd-xen@FreeBSD.ORG Mon May 30 10:27:47 2011 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 CF0791065670 for ; Mon, 30 May 2011 10:27:47 +0000 (UTC) (envelope-from snabb@epipe.com) Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:1828:0:3::2]) by mx1.freebsd.org (Postfix) with ESMTP id 95A678FC1B for ; Mon, 30 May 2011 10:27:47 +0000 (UTC) Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:1828:0:3::2]) by tiktik.epipe.com (8.14.4/8.14.4) with ESMTP id p4UARcXr047438 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 30 May 2011 10:27:38 GMT (envelope-from snabb@epipe.com) X-DKIM: Sendmail DKIM Filter v2.8.3 tiktik.epipe.com p4UARcXr047438 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=epipe.com; s=default; t=1306751258; x=1307356058; bh=PJeFqIchLfJayTIMBnyzw9URTK6a2xDafEXC5AHAZKw=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References: MIME-Version:Content-Type; b=IPTWAzKGNLI1VOQAw2IN/MYg5z1xkV/xPVxFELpGIVUq9OaJYtz2i3nkgs2pLu5jV o04VAqXRUM2f3K6ndNVpWdHi3Ws2ABc1dcPStfE0mz0wlng5GXdxiYdvQydnIe7BZZ p/77z12RCR6Jbwqg7YfT9CUv7JGigxQ3NjIrnVTo= Date: Mon, 30 May 2011 10:27:37 +0000 (UTC) From: Janne Snabb To: Alex In-Reply-To: Message-ID: References: <4DE357AA.3070007@unsane.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (tiktik.epipe.com [IPv6:2001:1828:0:3::2]); Mon, 30 May 2011 10:27:38 +0000 (UTC) Cc: freebsd-xen@freebsd.org Subject: Re: Clock drift issues 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: Mon, 30 May 2011 10:27:47 -0000 On Mon, 30 May 2011, Alex wrote: > The clock is Sync'd though, it should *stay* correct, right? So there is a > bug? My experience is also that the clock is not stable on FreeBSD 8.X guest on Xen and KVM HVM. It is unusable as a ntp server for other hosts and I need to run ntpd to prevent the guest clock from drifting and jumping. Some times I get syslog messages about the time going backwards, which is probably related: calcru: runtime went backwards from 41668 usec to 35093 usec for pid 96767 (bash) I have not tried this with the CURRENT kernel (which has new and configurable event timer infrastructure by mav@). (Linux guests are fine for running ntp server within Xen & KVM.) -- Janne Snabb / EPIPE Communications snabb@epipe.com - http://epipe.com/ From owner-freebsd-xen@FreeBSD.ORG Mon May 30 11:07:13 2011 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 C8C46106566C for ; Mon, 30 May 2011 11:07:13 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 9ED3F8FC22 for ; Mon, 30 May 2011 11:07:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p4UB7Dcd050586 for ; Mon, 30 May 2011 11:07:13 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p4UB7Dm1050584 for freebsd-xen@FreeBSD.org; Mon, 30 May 2011 11:07:13 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 30 May 2011 11:07:13 GMT Message-Id: <201105301107.p4UB7Dm1050584@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 Cc: Subject: Current problem reports assigned to freebsd-xen@FreeBSD.org 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: Mon, 30 May 2011 11:07:13 -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/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/154302 xen [xen] [panic] [patch] xn0: Error 2 parsing device/vif/ o kern/153789 xen [xen] [regression] FreeBSD 8.2-RC1 crashes under Solar 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 24 problems total. From owner-freebsd-xen@FreeBSD.ORG Wed Jun 1 08:00:06 2011 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 359481065670 for ; Wed, 1 Jun 2011 08:00:06 +0000 (UTC) (envelope-from sergi@estrafolari.com) Received: from xen-smtp01.srv.cat (xen-smtp01.srv.cat [212.36.75.101]) by mx1.freebsd.org (Postfix) with ESMTP id EB9CD8FC0A for ; Wed, 1 Jun 2011 08:00:05 +0000 (UTC) Received: from [192.168.0.30] (155.Red-88-2-251.staticIP.rima-tde.net [88.2.251.155]) (Authenticated sender: estrafolar02@noverificar) by xen-smtp01.srv.cat (Postfix) with ESMTPSA id 33225C0509 for ; Wed, 1 Jun 2011 09:44:18 +0200 (CEST) Message-ID: <4DE5EDD7.20105@estrafolari.com> Date: Wed, 01 Jun 2011 09:44:23 +0200 From: Sergi User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100515 Lightning/1.0b1 Icedove/3.0.4 MIME-Version: 1.0 To: freebsd-xen@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: fpudna: fpcurthread == curthread XXXX times 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: Wed, 01 Jun 2011 08:00:06 -0000 Hello, I'm working with full virtual FreeBSD 8.2-RELEASE-p1 domU under debian squeeze and xen-hypervisor-4.0-amd64. If I cfg this hvm with cpu > 4 : vcpus = 5 these messages block the server : fpudna: fpcurthread == curthread XXXX times The machine is pingable but I'm unable to ssh to it. On single user it works fine, fsck an so on ok, but when switching to multiuser these fpudna messages start flooding. I've googled but haven't found anything; something from 2005 about fpudna : http://lists.freebsd.org/pipermail/freebsd-amd64/2005-April/004413.html and this link, but I don't have the options he mentions enabled on the kernel : http://forums.freebsd.org/showthread.php?t=17979 Has anyone stepped on this behaviour before?, is there any workaround? The machine really seems to detect cpu's available and responds to keyboard on VNC, but it's impossible to see whats written down because of the messages flooding the screen. Thanks, regards, Sergi From owner-freebsd-xen@FreeBSD.ORG Wed Jun 1 08:56:01 2011 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 A75691065673 for ; Wed, 1 Jun 2011 08:56:01 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 2E0388FC20 for ; Wed, 1 Jun 2011 08:56:00 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id p518LuX8046549 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Jun 2011 11:21:56 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p518LuiO008386; Wed, 1 Jun 2011 11:21:56 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p518Lu6D008385; Wed, 1 Jun 2011 11:21:56 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 1 Jun 2011 11:21:56 +0300 From: Kostik Belousov To: Sergi Message-ID: <20110601082156.GB48734@deviant.kiev.zoral.com.ua> References: <4DE5EDD7.20105@estrafolari.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UCOOPUdJKgxUwY8X" Content-Disposition: inline In-Reply-To: <4DE5EDD7.20105@estrafolari.com> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-xen@freebsd.org Subject: Re: fpudna: fpcurthread == curthread XXXX times 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: Wed, 01 Jun 2011 08:56:01 -0000 --UCOOPUdJKgxUwY8X Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jun 01, 2011 at 09:44:23AM +0200, Sergi wrote: > Hello, >=20 > I'm working with full virtual FreeBSD 8.2-RELEASE-p1 domU under debian=20 > squeeze and xen-hypervisor-4.0-amd64. >=20 > If I cfg this hvm with cpu > 4 : >=20 > vcpus =3D 5 >=20 > these messages block the server : >=20 > fpudna: fpcurthread =3D=3D curthread XXXX times >=20 > The machine is pingable but I'm unable to ssh to it. >=20 > On single user it works fine, fsck an so on ok, but when switching to=20 > multiuser these fpudna messages start flooding. >=20 > I've googled but haven't found anything; something from 2005 about fpudna= : >=20 > http://lists.freebsd.org/pipermail/freebsd-amd64/2005-April/004413.html >=20 > and this link, but I don't have the options he mentions enabled on the=20 > kernel : >=20 > http://forums.freebsd.org/showthread.php?t=3D17979 >=20 > Has anyone stepped on this behaviour before?, is there any workaround? > The machine really seems to detect cpu's available and responds to keyboa= rd=20 > on VNC, but it's impossible to see whats written down because of the=20 > messages flooding the screen. You did not specified the architecture of the domu. From the message, I can guess that your guest is running amd64 kernel. There are slight differences in the handling of the FPU in i386 and amd64 that may matter there. The message you reported means that the FreeBSD kernel assumes that FPU is currently loaded with the context of the current thread, but the CR0.TS bit is set, meaning that FPU context is set for switch. AFAIR, HVM means that you run bare-metal kernel, right ? Most likely, it is some issue with Xen itself. I am curious whether the following will cause any usermode-visible regression for you: diff --git a/sys/amd64/amd64/fpu.c b/sys/amd64/amd64/fpu.c index 08e5e57..a5ee853 100644 --- a/sys/amd64/amd64/fpu.c +++ b/sys/amd64/amd64/fpu.c @@ -394,14 +394,8 @@ fpudna(void) struct pcb *pcb; =20 critical_enter(); - if (PCPU_GET(fpcurthread) =3D=3D curthread) { - printf("fpudna: fpcurthread =3D=3D curthread %d times\n", - ++err_count); - stop_emulating(); - critical_exit(); - return; - } - if (PCPU_GET(fpcurthread) !=3D NULL) { + if (PCPU_GET(fpcurthread) !=3D NULL && + PCPU_GET(fpcurthread) !=3D curthread) { printf("fpudna: fpcurthread =3D %p (%d), curthread =3D %p (%d)\n", PCPU_GET(fpcurthread), PCPU_GET(fpcurthread)->td_proc->p_pid, --UCOOPUdJKgxUwY8X Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk3l9qQACgkQC3+MBN1Mb4j4LwCfaBL3E8xsIOriJymvAkUW/7r+ lPgAni1f/Gl0DfSZmPPRjpolessNuhN0 =9QUR -----END PGP SIGNATURE----- --UCOOPUdJKgxUwY8X-- From owner-freebsd-xen@FreeBSD.ORG Wed Jun 1 09:36:33 2011 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 3162F106566B for ; Wed, 1 Jun 2011 09:36:33 +0000 (UTC) (envelope-from sergi@estrafolari.com) Received: from xen-smtp01.srv.cat (xen-smtp01.srv.cat [212.36.75.101]) by mx1.freebsd.org (Postfix) with ESMTP id B99CD8FC13 for ; Wed, 1 Jun 2011 09:36:29 +0000 (UTC) Received: from [192.168.0.30] (155.Red-88-2-251.staticIP.rima-tde.net [88.2.251.155]) (Authenticated sender: estrafolar02@noverificar) by xen-smtp01.srv.cat (Postfix) with ESMTPSA id 1D7547C049; Wed, 1 Jun 2011 11:36:28 +0200 (CEST) Message-ID: <4DE60820.1080409@estrafolari.com> Date: Wed, 01 Jun 2011 11:36:32 +0200 From: Sergi User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100515 Lightning/1.0b1 Icedove/3.0.4 MIME-Version: 1.0 To: Kostik Belousov References: <4DE5EDD7.20105@estrafolari.com> <20110601082156.GB48734@deviant.kiev.zoral.com.ua> In-Reply-To: <20110601082156.GB48734@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-xen@freebsd.org Subject: Re: fpudna: fpcurthread == curthread XXXX times 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: Wed, 01 Jun 2011 09:36:33 -0000 On 01/06/11 10:21, Kostik Belousov wrote: > On Wed, Jun 01, 2011 at 09:44:23AM +0200, Sergi wrote: > >> Hello, >> >> I'm working with full virtual FreeBSD 8.2-RELEASE-p1 domU under debian >> squeeze and xen-hypervisor-4.0-amd64. >> >> If I cfg this hvm with cpu> 4 : >> >> vcpus = 5 >> >> these messages block the server : >> >> fpudna: fpcurthread == curthread XXXX times >> >> The machine is pingable but I'm unable to ssh to it. >> >> On single user it works fine, fsck an so on ok, but when switching to >> multiuser these fpudna messages start flooding. >> >> I've googled but haven't found anything; something from 2005 about fpudna : >> >> http://lists.freebsd.org/pipermail/freebsd-amd64/2005-April/004413.html >> >> and this link, but I don't have the options he mentions enabled on the >> kernel : >> >> http://forums.freebsd.org/showthread.php?t=17979 >> >> Has anyone stepped on this behaviour before?, is there any workaround? >> The machine really seems to detect cpu's available and responds to keyboard >> on VNC, but it's impossible to see whats written down because of the >> messages flooding the screen. >> > You did not specified the architecture of the domu. From the message, I can > guess that your guest is running amd64 kernel. There are slight differences > in the handling of the FPU in i386 and amd64 that may matter there. > > The message you reported means that the FreeBSD kernel assumes that FPU > is currently loaded with the context of the current thread, but the > CR0.TS bit is set, meaning that FPU context is set for switch. > > AFAIR, HVM means that you run bare-metal kernel, right ? Most likely, > it is some issue with Xen itself. I am curious whether the following > will cause any usermode-visible regression for you: > > diff --git a/sys/amd64/amd64/fpu.c b/sys/amd64/amd64/fpu.c > index 08e5e57..a5ee853 100644 > --- a/sys/amd64/amd64/fpu.c > +++ b/sys/amd64/amd64/fpu.c > @@ -394,14 +394,8 @@ fpudna(void) > struct pcb *pcb; > > critical_enter(); > - if (PCPU_GET(fpcurthread) == curthread) { > - printf("fpudna: fpcurthread == curthread %d times\n", > - ++err_count); > - stop_emulating(); > - critical_exit(); > - return; > - } > - if (PCPU_GET(fpcurthread) != NULL) { > + if (PCPU_GET(fpcurthread) != NULL&& > + PCPU_GET(fpcurthread) != curthread) { > printf("fpudna: fpcurthread = %p (%d), curthread = %p (%d)\n", > PCPU_GET(fpcurthread), > PCPU_GET(fpcurthread)->td_proc->p_pid, > Hello, yes, sorry, amd64, and yes, hvm hardware virtual machine, not paravirtual. So, you mean patching fpu.c and recompiling the kernel, right?, I'm new to modifiying src files. Thanks for your help, Sergi From owner-freebsd-xen@FreeBSD.ORG Wed Jun 1 13:00:49 2011 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 6EC391065678 for ; Wed, 1 Jun 2011 13:00:49 +0000 (UTC) (envelope-from sergi@estrafolari.com) Received: from xen-smtp03.srv.cat (xen-smtp03.srv.cat [212.36.74.73]) by mx1.freebsd.org (Postfix) with ESMTP id 006768FC1B for ; Wed, 1 Jun 2011 13:00:48 +0000 (UTC) Received: from [192.168.0.30] (155.Red-88-2-251.staticIP.rima-tde.net [88.2.251.155]) (Authenticated sender: estrafolar02@noverificar) by xen-smtp03.srv.cat (Postfix) with ESMTPSA id D7F98C04C7; Wed, 1 Jun 2011 15:00:46 +0200 (CEST) Message-ID: <4DE63803.7090504@estrafolari.com> Date: Wed, 01 Jun 2011 15:00:51 +0200 From: Sergi User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100515 Lightning/1.0b1 Icedove/3.0.4 MIME-Version: 1.0 To: Kostik Belousov References: <4DE5EDD7.20105@estrafolari.com> <20110601082156.GB48734@deviant.kiev.zoral.com.ua> <4DE60820.1080409@estrafolari.com> In-Reply-To: <4DE60820.1080409@estrafolari.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-xen@freebsd.org Subject: Re: fpudna: fpcurthread == curthread XXXX times 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: Wed, 01 Jun 2011 13:00:49 -0000 On 01/06/11 11:36, Sergi wrote: > On 01/06/11 10:21, Kostik Belousov wrote: >> On Wed, Jun 01, 2011 at 09:44:23AM +0200, Sergi wrote: >>> Hello, >>> >>> I'm working with full virtual FreeBSD 8.2-RELEASE-p1 domU under debian >>> squeeze and xen-hypervisor-4.0-amd64. >>> >>> If I cfg this hvm with cpu> 4 : >>> >>> vcpus = 5 >>> >>> these messages block the server : >>> >>> fpudna: fpcurthread == curthread XXXX times >>> >>> The machine is pingable but I'm unable to ssh to it. >>> >>> On single user it works fine, fsck an so on ok, but when switching to >>> multiuser these fpudna messages start flooding. >>> >>> I've googled but haven't found anything; something from 2005 about >>> fpudna : >>> >>> >>> http://lists.freebsd.org/pipermail/freebsd-amd64/2005-April/004413.html >>> >>> and this link, but I don't have the options he mentions enabled on the >>> kernel : >>> >>> http://forums.freebsd.org/showthread.php?t=17979 >>> >>> Has anyone stepped on this behaviour before?, is there any workaround? >>> The machine really seems to detect cpu's available and responds to >>> keyboard >>> on VNC, but it's impossible to see whats written down because of the >>> messages flooding the screen. >> You did not specified the architecture of the domu. From the message, >> I can >> guess that your guest is running amd64 kernel. There are slight >> differences >> in the handling of the FPU in i386 and amd64 that may matter there. >> >> The message you reported means that the FreeBSD kernel assumes that FPU >> is currently loaded with the context of the current thread, but the >> CR0.TS bit is set, meaning that FPU context is set for switch. >> >> AFAIR, HVM means that you run bare-metal kernel, right ? Most likely, >> it is some issue with Xen itself. I am curious whether the following >> will cause any usermode-visible regression for you: >> >> diff --git a/sys/amd64/amd64/fpu.c b/sys/amd64/amd64/fpu.c >> index 08e5e57..a5ee853 100644 >> --- a/sys/amd64/amd64/fpu.c >> +++ b/sys/amd64/amd64/fpu.c >> @@ -394,14 +394,8 @@ fpudna(void) >> struct pcb *pcb; >> >> critical_enter(); >> - if (PCPU_GET(fpcurthread) == curthread) { >> - printf("fpudna: fpcurthread == curthread %d times\n", >> - ++err_count); >> - stop_emulating(); >> - critical_exit(); >> - return; >> - } >> - if (PCPU_GET(fpcurthread) != NULL) { >> + if (PCPU_GET(fpcurthread) != NULL&& >> + PCPU_GET(fpcurthread) != curthread) { >> printf("fpudna: fpcurthread = %p (%d), curthread = %p (%d)\n", >> PCPU_GET(fpcurthread), >> PCPU_GET(fpcurthread)->td_proc->p_pid, > Hello, > > yes, sorry, amd64, and yes, hvm hardware virtual machine, not > paravirtual. > > So, you mean patching fpu.c and recompiling the kernel, right?, I'm > new to modifiying src files. > > Thanks for your help, > Sergi > > > _______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" > Hello, well, I patched fpu.c, recompiled the kernel, and booted ok with 4 vcpu. Then I tried to boot with 5 vcpus and got : kernel trap 22 with interrupts disabled ... kernel trap 22 with interrupts disabled Fatal double fault rip = 0xffffffff8067865a rsp = 0xffffff8000000000 rbp = 0xffffff8000000040 cpuid = 4; apic id = 08 panic: double fault cpuid = 4 4 vcpus is the maximum number of vcpus I can use. How do you think I can debug this in order to provide more information? Thanks, regards, Sergi From owner-freebsd-xen@FreeBSD.ORG Wed Jun 1 21:36:33 2011 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 21EED106564A for ; Wed, 1 Jun 2011 21:36:33 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id AF0A38FC08 for ; Wed, 1 Jun 2011 21:36:32 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id p51LaGk8015943 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Jun 2011 00:36:16 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p51LaGoC012810; Thu, 2 Jun 2011 00:36:16 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p51LaG2o012809; Thu, 2 Jun 2011 00:36:16 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 2 Jun 2011 00:36:16 +0300 From: Kostik Belousov To: Sergi Message-ID: <20110601213616.GE48734@deviant.kiev.zoral.com.ua> References: <4DE5EDD7.20105@estrafolari.com> <20110601082156.GB48734@deviant.kiev.zoral.com.ua> <4DE60820.1080409@estrafolari.com> <4DE63803.7090504@estrafolari.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="W9261hGV6KsBFa7P" Content-Disposition: inline In-Reply-To: <4DE63803.7090504@estrafolari.com> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-xen@freebsd.org Subject: Re: fpudna: fpcurthread == curthread XXXX times 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: Wed, 01 Jun 2011 21:36:33 -0000 --W9261hGV6KsBFa7P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jun 01, 2011 at 03:00:51PM +0200, Sergi wrote: > On 01/06/11 11:36, Sergi wrote: > >On 01/06/11 10:21, Kostik Belousov wrote: > >>On Wed, Jun 01, 2011 at 09:44:23AM +0200, Sergi wrote: > >>>Hello, > >>> > >>>I'm working with full virtual FreeBSD 8.2-RELEASE-p1 domU under debian > >>>squeeze and xen-hypervisor-4.0-amd64. > >>> > >>>If I cfg this hvm with cpu> 4 : > >>> > >>> vcpus =3D 5 > >>> > >>>these messages block the server : > >>> > >>> fpudna: fpcurthread =3D=3D curthread XXXX times > >>> > >>>The machine is pingable but I'm unable to ssh to it. > >>> > >>>On single user it works fine, fsck an so on ok, but when switching to > >>>multiuser these fpudna messages start flooding. > >>> > >>>I've googled but haven't found anything; something from 2005 about=20 > >>>fpudna : > >>> > >>> =20 > >>>http://lists.freebsd.org/pipermail/freebsd-amd64/2005-April/004413.html > >>> > >>>and this link, but I don't have the options he mentions enabled on the > >>>kernel : > >>> > >>> http://forums.freebsd.org/showthread.php?t=3D17979 > >>> > >>>Has anyone stepped on this behaviour before?, is there any workaround? > >>>The machine really seems to detect cpu's available and responds to=20 > >>>keyboard > >>>on VNC, but it's impossible to see whats written down because of the > >>>messages flooding the screen. > >>You did not specified the architecture of the domu. From the message,= =20 > >>I can > >>guess that your guest is running amd64 kernel. There are slight=20 > >>differences > >>in the handling of the FPU in i386 and amd64 that may matter there. > >> > >>The message you reported means that the FreeBSD kernel assumes that FPU > >>is currently loaded with the context of the current thread, but the > >>CR0.TS bit is set, meaning that FPU context is set for switch. > >> > >>AFAIR, HVM means that you run bare-metal kernel, right ? Most likely, > >>it is some issue with Xen itself. I am curious whether the following > >>will cause any usermode-visible regression for you: > >> > >>diff --git a/sys/amd64/amd64/fpu.c b/sys/amd64/amd64/fpu.c > >>index 08e5e57..a5ee853 100644 > >>--- a/sys/amd64/amd64/fpu.c > >>+++ b/sys/amd64/amd64/fpu.c > >>@@ -394,14 +394,8 @@ fpudna(void) > >> struct pcb *pcb; > >> > >> critical_enter(); > >>- if (PCPU_GET(fpcurthread) =3D=3D curthread) { > >>- printf("fpudna: fpcurthread =3D=3D curthread %d times\n", > >>- ++err_count); > >>- stop_emulating(); > >>- critical_exit(); > >>- return; > >>- } > >>- if (PCPU_GET(fpcurthread) !=3D NULL) { > >>+ if (PCPU_GET(fpcurthread) !=3D NULL&& > >>+ PCPU_GET(fpcurthread) !=3D curthread) { > >> printf("fpudna: fpcurthread =3D %p (%d), curthread =3D %p (%d= )\n", > >> PCPU_GET(fpcurthread), > >> PCPU_GET(fpcurthread)->td_proc->p_pid, > >Hello, > > > >yes, sorry, amd64, and yes, hvm hardware virtual machine, not=20 > >paravirtual. > > > >So, you mean patching fpu.c and recompiling the kernel, right?, I'm=20 > >new to modifiying src files. > > > >Thanks for your help, > >Sergi > > > > > >_______________________________________________ > >freebsd-xen@freebsd.org mailing list > >http://lists.freebsd.org/mailman/listinfo/freebsd-xen > >To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" > > > Hello, >=20 > well, I patched fpu.c, recompiled the kernel, and booted ok with 4 vcpu. > Then I tried to boot with 5 vcpus and got : >=20 > kernel trap 22 with interrupts disabled > ... > kernel trap 22 with interrupts disabled > Fatal double fault > rip =3D 0xffffffff8067865a > rsp =3D 0xffffff8000000000 > rbp =3D 0xffffff8000000040 > cpuid =3D 4; apic id =3D 08 > panic: double fault > cpuid =3D 4 >=20 > 4 vcpus is the maximum number of vcpus I can use. >=20 > How do you think I can debug this in order to provide more information? At least you can add KDB/DDB to the kernel config and get a backtrace at panic. My feeling right now is that the issue is in the hypervisor, and not in the kernel. --W9261hGV6KsBFa7P Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk3msM8ACgkQC3+MBN1Mb4gq7wCaA0CaRHrWO3F2Y9NwI8VKIpb0 wzsAn1VpPFdgrZY++aSdOh6DRDF0s1oV =MA7t -----END PGP SIGNATURE----- --W9261hGV6KsBFa7P-- From owner-freebsd-xen@FreeBSD.ORG Thu Jun 2 07:22:30 2011 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 07A05106566B for ; Thu, 2 Jun 2011 07:22:30 +0000 (UTC) (envelope-from sergi@estrafolari.com) Received: from xen-smtp02.srv.cat (xen-smtp02.srv.cat [212.36.75.133]) by mx1.freebsd.org (Postfix) with ESMTP id 90ACF8FC12 for ; Thu, 2 Jun 2011 07:22:28 +0000 (UTC) Received: from [192.168.0.30] (155.Red-88-2-251.staticIP.rima-tde.net [88.2.251.155]) (Authenticated sender: estrafolar02@noverificar) by xen-smtp02.srv.cat (Postfix) with ESMTPSA id B92257C073; Thu, 2 Jun 2011 09:24:39 +0200 (CEST) Message-ID: <4DE73A39.2060609@estrafolari.com> Date: Thu, 02 Jun 2011 09:22:33 +0200 From: Sergi User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100515 Lightning/1.0b1 Icedove/3.0.4 MIME-Version: 1.0 To: Kostik Belousov References: <4DE5EDD7.20105@estrafolari.com> <20110601082156.GB48734@deviant.kiev.zoral.com.ua> <4DE60820.1080409@estrafolari.com> <4DE63803.7090504@estrafolari.com> <20110601213616.GE48734@deviant.kiev.zoral.com.ua> In-Reply-To: <20110601213616.GE48734@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-xen@freebsd.org Subject: Re: fpudna: fpcurthread == curthread XXXX times 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, 02 Jun 2011 07:22:30 -0000 On 01/06/11 23:36, Kostik Belousov wrote: > On Wed, Jun 01, 2011 at 03:00:51PM +0200, Sergi wrote: > >> On 01/06/11 11:36, Sergi wrote: >> >>> On 01/06/11 10:21, Kostik Belousov wrote: >>> >>>> On Wed, Jun 01, 2011 at 09:44:23AM +0200, Sergi wrote: >>>> >>>>> Hello, >>>>> >>>>> I'm working with full virtual FreeBSD 8.2-RELEASE-p1 domU under debian >>>>> squeeze and xen-hypervisor-4.0-amd64. >>>>> >>>>> If I cfg this hvm with cpu> 4 : >>>>> >>>>> vcpus = 5 >>>>> >>>>> these messages block the server : >>>>> >>>>> fpudna: fpcurthread == curthread XXXX times >>>>> >>>>> The machine is pingable but I'm unable to ssh to it. >>>>> >>>>> On single user it works fine, fsck an so on ok, but when switching to >>>>> multiuser these fpudna messages start flooding. >>>>> >>>>> I've googled but haven't found anything; something from 2005 about >>>>> fpudna : >>>>> >>>>> >>>>> http://lists.freebsd.org/pipermail/freebsd-amd64/2005-April/004413.html >>>>> >>>>> and this link, but I don't have the options he mentions enabled on the >>>>> kernel : >>>>> >>>>> http://forums.freebsd.org/showthread.php?t=17979 >>>>> >>>>> Has anyone stepped on this behaviour before?, is there any workaround? >>>>> The machine really seems to detect cpu's available and responds to >>>>> keyboard >>>>> on VNC, but it's impossible to see whats written down because of the >>>>> messages flooding the screen. >>>>> >>>> You did not specified the architecture of the domu. From the message, >>>> I can >>>> guess that your guest is running amd64 kernel. There are slight >>>> differences >>>> in the handling of the FPU in i386 and amd64 that may matter there. >>>> >>>> The message you reported means that the FreeBSD kernel assumes that FPU >>>> is currently loaded with the context of the current thread, but the >>>> CR0.TS bit is set, meaning that FPU context is set for switch. >>>> >>>> AFAIR, HVM means that you run bare-metal kernel, right ? Most likely, >>>> it is some issue with Xen itself. I am curious whether the following >>>> will cause any usermode-visible regression for you: >>>> >>>> diff --git a/sys/amd64/amd64/fpu.c b/sys/amd64/amd64/fpu.c >>>> index 08e5e57..a5ee853 100644 >>>> --- a/sys/amd64/amd64/fpu.c >>>> +++ b/sys/amd64/amd64/fpu.c >>>> @@ -394,14 +394,8 @@ fpudna(void) >>>> struct pcb *pcb; >>>> >>>> critical_enter(); >>>> - if (PCPU_GET(fpcurthread) == curthread) { >>>> - printf("fpudna: fpcurthread == curthread %d times\n", >>>> - ++err_count); >>>> - stop_emulating(); >>>> - critical_exit(); >>>> - return; >>>> - } >>>> - if (PCPU_GET(fpcurthread) != NULL) { >>>> + if (PCPU_GET(fpcurthread) != NULL&& >>>> + PCPU_GET(fpcurthread) != curthread) { >>>> printf("fpudna: fpcurthread = %p (%d), curthread = %p (%d)\n", >>>> PCPU_GET(fpcurthread), >>>> PCPU_GET(fpcurthread)->td_proc->p_pid, >>>> >>> Hello, >>> >>> yes, sorry, amd64, and yes, hvm hardware virtual machine, not >>> paravirtual. >>> >>> So, you mean patching fpu.c and recompiling the kernel, right?, I'm >>> new to modifiying src files. >>> >>> Thanks for your help, >>> Sergi >>> >>> >>> _______________________________________________ >>> freebsd-xen@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-xen >>> To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" >>> >>> >> Hello, >> >> well, I patched fpu.c, recompiled the kernel, and booted ok with 4 vcpu. >> Then I tried to boot with 5 vcpus and got : >> >> kernel trap 22 with interrupts disabled >> ... >> kernel trap 22 with interrupts disabled >> Fatal double fault >> rip = 0xffffffff8067865a >> rsp = 0xffffff8000000000 >> rbp = 0xffffff8000000040 >> cpuid = 4; apic id = 08 >> panic: double fault >> cpuid = 4 >> >> 4 vcpus is the maximum number of vcpus I can use. >> >> How do you think I can debug this in order to provide more information? >> > At least you can add KDB/DDB to the kernel config and get a backtrace > at panic. > > My feeling right now is that the issue is in the hypervisor, and not in > the kernel. > Hello, well, I'll try to add debugging to the kernel and see if I get somewhere. I'll post on the xen-user mailing-list to see if there is some issue known in the hypervisor. It's strange that nobody in this list has had this same issue. Thanks for your help, regards, Sergi