From owner-freebsd-xen@FreeBSD.ORG Mon Oct 26 11:07:11 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 CAF4E106568D for ; Mon, 26 Oct 2009 11:07:11 +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 B8A288FC12 for ; Mon, 26 Oct 2009 11:07:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n9QB7BeO043943 for ; Mon, 26 Oct 2009 11:07:11 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n9QB7BYe043941 for freebsd-xen@FreeBSD.org; Mon, 26 Oct 2009 11:07:11 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 26 Oct 2009 11:07:11 GMT Message-Id: <200910261107.n9QB7BYe043941@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, 26 Oct 2009 11:07:11 -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/136251 xen [xen] [patch] xn0 doesn't DHCP o kern/135421 xen [xen] FreeBSD Xen PVM DomU network failure - netfronc. o kern/135179 xen [xen] Xen domU does not properly reboot o kern/135178 xen [xen] Xen domU outgoing data transfer stall when TSO i o kern/135069 xen [xen] FreeBSD-current/Xen SMP doesn't function at all o kern/135008 xen [xen] FreeBSD-current/Xen timecounter jumps o kern/134926 xen [xen] [panic] FreeBSD-current Xen DomU networking pani 7 problems total. From owner-freebsd-xen@FreeBSD.ORG Tue Oct 27 13:18:46 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 00129106566B for ; Tue, 27 Oct 2009 13:18:45 +0000 (UTC) (envelope-from sysconfig@ossafe.org) Received: from mx2.the-ally.co.uk (mx2.the-ally.co.uk [95.154.227.236]) by mx1.freebsd.org (Postfix) with ESMTP id 8A1BB8FC22 for ; Tue, 27 Oct 2009 13:18:45 +0000 (UTC) Received: from mx2.the-ally.co.uk (localhost.localdomain [127.0.0.1]) by mx2.the-ally.co.uk (Postfix) with ESMTP id 8C8F4ED0997; Tue, 27 Oct 2009 13:18:43 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=ossafe.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s= selector1; bh=89/nYt1DIN7aV1iYpsnLMkRfL9c=; b=PgEVMXiY4sv6mXQHfj jOB4BfZQLiVMaBS+GEbJDAP/vmItbRucVANze9eNSnB1YeHTixduPks0EttSx/Q1 jmxIHjIysfKAWJGo/UQEzS+gAc+hvtDiR9tl7nuuqgVR5fQBAxE0gqOujuucd/gZ uPuVEe1XXZf4KpKKDVnQqYDlY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=ossafe.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=e6rMuG+luFWyErPzK5IPmmAFB+sEglqNfatDx1uoYr3PvSOJIdi qQJAEDhE/+DkiBjaAVVs4Kf62nKpfSZPzF++eAawLP2J+yt5aE8X+qkzxNpsyKM7 4l571yds5XEmdWxZl2HgMHeHIoqOAOlE+B/kaem4fiClk97qkfWpRUs4= Received: from [10.2.2.20] (unknown [10.2.2.20]) by mx2.the-ally.co.uk (Postfix) with ESMTP id 4E01CED0994; Tue, 27 Oct 2009 13:18:43 +0000 (GMT) Mime-Version: 1.0 (Apple Message framework v1076) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes From: Carsten Heesch In-Reply-To: <3941E1B9-6CD6-4D9A-AF1C-93401F571FCE@heesch.me.uk> Date: Tue, 27 Oct 2009 13:18:43 +0000 Content-Transfer-Encoding: 7bit Message-Id: <8C3C0877-F36E-45D1-BDEE-4EE22BD45205@ossafe.org> References: <850CF1B7-499E-4468-9045-19A2803E6D05@ossafe.org> <3941E1B9-6CD6-4D9A-AF1C-93401F571FCE@heesch.me.uk> To: Carsten Heesch X-Mailer: Apple Mail (2.1076) Cc: freebsd-xen@freebsd.org Subject: Re: Problem: Xen 3.3.1 with FreeBSD 8.0 RC1 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: Tue, 27 Oct 2009 13:18:46 -0000 Athough I seem to be talking to myself here, I have good news for RC2! It works! Just did an "freebsd-update -R 8.0-RC2 upgrade". Both GENERIC and XENHVM kernels work without any problems. Maybe somebody else can chime in an confirm that, too? Probably good for the developers to see positive feedback, while 8.0-RELEASE is coming closer :-) Cheers Carsten On 25 Oct 2009, at 00:31, Carsten Heesch wrote: > > I realised that it's still possible to use 8.0-BETA* as a target for > freebsd-update. So I investigated a bit further. For whatever it's > worth: > > The problems described earlier started with BETA-4. > > BETA-3 is fine with both GENERIC and XENHVM kernel, except that I > see this on the console and in dmesg every now and then (with both > kernels): > > > lock order reversal: > 1st 0xffffff8014810620 bufwait (bufwait) @ /usr/src/sys/kern/ > vfs_bio.c:2559 > 2nd 0xffffff00015a7c00 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ > ufs_dirhash.c:285 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > _witness_debugger() at _witness_debugger+0x2e > witness_checkorder() at witness_checkorder+0x81e > _sx_xlock() at _sx_xlock+0x55 > ufsdirhash_acquire() at ufsdirhash_acquire+0x33 > ufsdirhash_add() at ufsdirhash_add+0x19 > ufs_direnter() at ufs_direnter+0x88b > ufs_makeinode() at ufs_makeinode+0x31c > VOP_CREATE_APV() at VOP_CREATE_APV+0x8d > vn_open_cred() at vn_open_cred+0x423 > kern_openat() at kern_openat+0x179 > syscall() at syscall+0x1af > Xfast_syscall() at Xfast_syscall+0xe1 > --- syscall (5, FreeBSD ELF64, open), rip = 0x800e32dfc, rsp = > 0x7fffffffe608, rbp = 0x1a4 --- > > > I though this might be XENHVM kernel related, but it happens with > GENERIC kernel as well. Not sure if this is related to XEN at all. > > > > Cheers > Carsten > > > From owner-freebsd-xen@FreeBSD.ORG Tue Oct 27 17:07:47 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 4C50B1065670 for ; Tue, 27 Oct 2009 17:07:47 +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 1E91B8FC19 for ; Tue, 27 Oct 2009 17:07:46 +0000 (UTC) Received: from localhost (unknown [172.16.100.24]) by mail.barafranca.com (Postfix) with ESMTP id 38160B49; Tue, 27 Oct 2009 16:47:30 +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 1Lvke2D9sRBw; Tue, 27 Oct 2009 16:46:53 +0000 (UTC) Received: from [192.168.42.113] (a83-132-45-73.cpe.netcabo.pt [83.132.45.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.barafranca.com (Postfix) with ESMTPSA id D16CCB46; Tue, 27 Oct 2009 16:46:52 +0000 (UTC) Message-ID: <4AE723F4.10606@barafranca.com> Date: Tue, 27 Oct 2009 16:46:44 +0000 From: Hugo Silva User-Agent: Thunderbird 2.0.0.21 (X11/20090525) MIME-Version: 1.0 To: freebsd-xen@freebsd.org References: <850CF1B7-499E-4468-9045-19A2803E6D05@ossafe.org> <3941E1B9-6CD6-4D9A-AF1C-93401F571FCE@heesch.me.uk> <8C3C0877-F36E-45D1-BDEE-4EE22BD45205@ossafe.org> In-Reply-To: <8C3C0877-F36E-45D1-BDEE-4EE22BD45205@ossafe.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Problem: Xen 3.3.1 with FreeBSD 8.0 RC1 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: Tue, 27 Oct 2009 17:07:47 -0000 Carsten Heesch wrote: > Athough I seem to be talking to myself here, I have good news for RC2! > It works! > Just did an "freebsd-update -R 8.0-RC2 upgrade". Both GENERIC and > XENHVM kernels work without any problems. > > Maybe somebody else can chime in an confirm that, too? Probably good > for the developers to see positive feedback, while 8.0-RELEASE is > coming closer :-) > > > Cheers > Carsten > > > On 25 Oct 2009, at 00:31, Carsten Heesch wrote: > >> >> I realised that it's still possible to use 8.0-BETA* as a target for >> freebsd-update. So I investigated a bit further. For whatever it's >> worth: >> >> The problems described earlier started with BETA-4. >> >> BETA-3 is fine with both GENERIC and XENHVM kernel, except that I see >> this on the console and in dmesg every now and then (with both kernels): >> >> >> lock order reversal: >> 1st 0xffffff8014810620 bufwait (bufwait) @ >> /usr/src/sys/kern/vfs_bio.c:2559 >> 2nd 0xffffff00015a7c00 dirhash (dirhash) @ >> /usr/src/sys/ufs/ufs/ufs_dirhash.c:285 >> KDB: stack backtrace: >> db_trace_self_wrapper() at db_trace_self_wrapper+0x2a >> _witness_debugger() at _witness_debugger+0x2e >> witness_checkorder() at witness_checkorder+0x81e >> _sx_xlock() at _sx_xlock+0x55 >> ufsdirhash_acquire() at ufsdirhash_acquire+0x33 >> ufsdirhash_add() at ufsdirhash_add+0x19 >> ufs_direnter() at ufs_direnter+0x88b >> ufs_makeinode() at ufs_makeinode+0x31c >> VOP_CREATE_APV() at VOP_CREATE_APV+0x8d >> vn_open_cred() at vn_open_cred+0x423 >> kern_openat() at kern_openat+0x179 >> syscall() at syscall+0x1af >> Xfast_syscall() at Xfast_syscall+0xe1 >> --- syscall (5, FreeBSD ELF64, open), rip = 0x800e32dfc, rsp = >> 0x7fffffffe608, rbp = 0x1a4 --- >> >> >> I though this might be XENHVM kernel related, but it happens with >> GENERIC kernel as well. Not sure if this is related to XEN at all. >> >> >> >> Cheers >> Carsten >> >> >> > > _______________________________________________ > 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" I grabbed the 8.0-RC2/amd64iso to give this a spin; no luck here, it hangs after "Trying to mount root from ufs:/dev/md0". Also, I confirm the panics on boot with RC1. It's gone with RC2, but as I said, it gets stuck (for me, at least). My dom0 is NetBSD 5 / amd64. From owner-freebsd-xen@FreeBSD.ORG Tue Oct 27 17:57:41 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 AF8AD106566C for ; Tue, 27 Oct 2009 17:57:41 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-iw0-f190.google.com (mail-iw0-f190.google.com [209.85.223.190]) by mx1.freebsd.org (Postfix) with ESMTP id 74AC98FC08 for ; Tue, 27 Oct 2009 17:57:41 +0000 (UTC) Received: by iwn28 with SMTP id 28so319604iwn.3 for ; Tue, 27 Oct 2009 10:57:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=+7r7brc6CRyq0aFbvVyYXrjH3dBoTapMuwAe1LwVSZA=; b=O/gxUTeslPZ1XHKn5PqpGthEC1TfNv+oFYNnY7u2g38l8PBRpO0BveSjshTmFHNAt1 3GUKVlXBjB0TNnBaV0E2wHQw09B5z+L4EmpSwOKPMyhrS0016YLLeKOp33EWnw/0QCzx 8ShpC0xyXgG54KouTTxVrIRYgG4X5LCcImUPk= 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=Xtzl/hgEXweqVafyuj2BSfakuiwjjkV+VXsVapPNovbiBLHLQnT3D/ejX33FptsZ9i VpQUrt4KzqfZkXg93Yu394LsN+EpeaXFS69yqIu33CVFWBWfd24rdMzh01yas43rFwU3 YcqQmPey30dauj3podNhpETFbqP5PS+8nQOsU= MIME-Version: 1.0 Sender: adrian.chadd@gmail.com Received: by 10.231.25.199 with SMTP id a7mr1587681ibc.51.1256666260869; Tue, 27 Oct 2009 10:57:40 -0700 (PDT) In-Reply-To: <4AE723F4.10606@barafranca.com> References: <850CF1B7-499E-4468-9045-19A2803E6D05@ossafe.org> <3941E1B9-6CD6-4D9A-AF1C-93401F571FCE@heesch.me.uk> <8C3C0877-F36E-45D1-BDEE-4EE22BD45205@ossafe.org> <4AE723F4.10606@barafranca.com> Date: Wed, 28 Oct 2009 01:57:40 +0800 X-Google-Sender-Auth: 947549c3b8796db8 Message-ID: From: Adrian Chadd To: Hugo Silva Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-xen@freebsd.org Subject: Re: Problem: Xen 3.3.1 with FreeBSD 8.0 RC1 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: Tue, 27 Oct 2009 17:57:41 -0000 This sounds like you're running the domU with >1 CPU.. ? Adrian 2009/10/28 Hugo Silva : > Carsten Heesch wrote: >> >> Athough I seem to be talking to myself here, I have good news for RC2! It >> works! >> Just did an "freebsd-update -R 8.0-RC2 upgrade". Both GENERIC and XENHVM >> kernels work without any problems. >> >> Maybe somebody else can chime in an confirm that, too? Probably good for >> the developers to see positive feedback, while 8.0-RELEASE is coming closer >> :-) >> >> >> Cheers >> Carsten >> >> >> On 25 Oct 2009, at 00:31, Carsten Heesch wrote: >> >>> >>> I realised that it's still possible to use 8.0-BETA* as a target for >>> freebsd-update. So I investigated a bit further. For whatever it's worth: >>> >>> The problems described earlier started with BETA-4. >>> >>> BETA-3 is fine with both GENERIC and XENHVM kernel, except that I see >>> this on the console and in dmesg every now and then (with both kernels): >>> >>> >>> lock order reversal: >>> 1st 0xffffff8014810620 bufwait (bufwait) @ >>> /usr/src/sys/kern/vfs_bio.c:2559 >>> 2nd 0xffffff00015a7c00 dirhash (dirhash) @ >>> /usr/src/sys/ufs/ufs/ufs_dirhash.c:285 >>> KDB: stack backtrace: >>> db_trace_self_wrapper() at db_trace_self_wrapper+0x2a >>> _witness_debugger() at _witness_debugger+0x2e >>> witness_checkorder() at witness_checkorder+0x81e >>> _sx_xlock() at _sx_xlock+0x55 >>> ufsdirhash_acquire() at ufsdirhash_acquire+0x33 >>> ufsdirhash_add() at ufsdirhash_add+0x19 >>> ufs_direnter() at ufs_direnter+0x88b >>> ufs_makeinode() at ufs_makeinode+0x31c >>> VOP_CREATE_APV() at VOP_CREATE_APV+0x8d >>> vn_open_cred() at vn_open_cred+0x423 >>> kern_openat() at kern_openat+0x179 >>> syscall() at syscall+0x1af >>> Xfast_syscall() at Xfast_syscall+0xe1 >>> --- syscall (5, FreeBSD ELF64, open), rip = 0x800e32dfc, rsp = >>> 0x7fffffffe608, rbp = 0x1a4 --- >>> >>> >>> I though this might be XENHVM kernel related, but it happens with GENERIC >>> kernel as well. Not sure if this is related to XEN at all. >>> >>> >>> >>> Cheers >>> Carsten >>> >>> >>> >> >> _______________________________________________ >> 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" > > > I grabbed the 8.0-RC2/amd64iso to give this a spin; no luck here, it hangs > after "Trying to mount root from ufs:/dev/md0". Also, I confirm the panics > on boot with RC1. It's gone with RC2, but as I said, it gets stuck (for me, > at least). > > My dom0 is NetBSD 5 / amd64. > _______________________________________________ > 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 Tue Oct 27 18:23:36 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 2757E1065670 for ; Tue, 27 Oct 2009 18:23:36 +0000 (UTC) (envelope-from lab@gta.com) Received: from mailgate.gta.com (mailgate.gta.com [199.120.225.20]) by mx1.freebsd.org (Postfix) with SMTP id 3C8EE8FC19 for ; Tue, 27 Oct 2009 18:23:34 +0000 (UTC) Received: (qmail 12292 invoked by uid 1000); 27 Oct 2009 18:23:31 -0000 Date: 27 Oct 2009 18:23:31 -0000 Message-ID: <20091027182331.12291.qmail@mailgate.gta.com> From: Larry Baird To: freebsd-xen@freebsd.org Organization: Global Technology Associates In-Reply-To: <109927.135756.6915@localhost> User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.3-PRERELEASE (i386)) Subject: Re: Problem: Xen 3.3.1 with FreeBSD 8.0 RC1 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: Tue, 27 Oct 2009 18:23:36 -0000 I have two Citrix XenServer 5.5.0 servers. One with an Intel processor and one with an AMD processor. Current versions of FreebSD 8 and 9 run on the Intel processor. Both panic after displaying available memory on the AMD processor. Panic message is: panic: vm_fault: fault on nofault entry, addr: c428200 I guess I'll need to install FreeBSD 7 and then cvsup to FreeBSD 9 to really get any useful debug information. Larry -- ------------------------------------------------------------------------ Larry Baird | http://www.gta.com Global Technology Associates, Inc. | Orlando, FL Email: lab@gta.com | TEL 407-380-0220, FAX 407-380-6080 From owner-freebsd-xen@FreeBSD.ORG Thu Oct 29 10:48:10 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 C7AB8106566C for ; Thu, 29 Oct 2009 10:48:10 +0000 (UTC) (envelope-from paulw@macrolan.com) Received: from xavier1.macrolan.co.za (xavier1.macrolan.co.za [196.7.93.6]) by mx1.freebsd.org (Postfix) with ESMTP id 0B52B8FC17 for ; Thu, 29 Oct 2009 10:48:09 +0000 (UTC) Received: from localhost (vwfilter2.macrolan.co.za [196.7.127.102]) by xdeliver1.macrolan.co.za (Postfix) with ESMTP id 7F4E520636A2; Thu, 29 Oct 2009 12:32:14 +0200 (SAST) X-Virus-Scanned: Viruswall at macrolan.co.za Received: from xavier3.macrolan.co.za ([196.7.93.8]) by localhost (vwfilter2.macrolan.co.za [196.7.127.100]) (amavisd-new, port 10025) with LMTP id uQtRfDO6SiQx; Thu, 29 Oct 2009 12:32:13 +0200 (SAST) Received: from server.macrolan.com (macrolan-ho.macrolan.co.za [41.222.225.226]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) (Authenticated sender: macrolan@macrolan.co.za) by xavier3.macrolan.co.za (Postfix) with ESMTP id 5B36F6067402; Thu, 29 Oct 2009 12:32:11 +0200 (SAST) Received: from server.macrolan.com ([192.168.0.7]) by server.macrolan.com ([192.168.0.7]) with mapi; Thu, 29 Oct 2009 12:27:45 +0200 From: Paul Wollner To: 'Hugo Silva' , "freebsd-xen@freebsd.org" Date: Thu, 29 Oct 2009 12:27:44 +0200 Thread-Topic: Problem: Xen 3.3.1 with FreeBSD 8.0 RC1 Thread-Index: AcpXJ4UviWtB8eSlTl6ih/Kp0iAXfQBWv3YQ Message-ID: <1C91F622D1DF2347AF9354BEC77D76EAB2B7645150@server.macrolan.com> References: <850CF1B7-499E-4468-9045-19A2803E6D05@ossafe.org> <3941E1B9-6CD6-4D9A-AF1C-93401F571FCE@heesch.me.uk> <8C3C0877-F36E-45D1-BDEE-4EE22BD45205@ossafe.org> <4AE723F4.10606@barafranca.com> In-Reply-To: <4AE723F4.10606@barafranca.com> Accept-Language: en-US, en-ZA Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-ZA Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Subject: RE: Problem: Xen 3.3.1 with FreeBSD 8.0 RC1 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, 29 Oct 2009 10:48:10 -0000 I have installed amd64 8.0 RC2 on Citrix Xenserver. GENREIC and XENHVM both booted without problems. I just checked the output of dmesg and I see the following error: lock order reversal: 1st 0xffffff80000b0618 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:255= 9 2nd 0xffffff00017a6000 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhas= h.c:285 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x2e witness_checkorder() at witness_checkorder+0x81e _sx_xlock() at _sx_xlock+0x55 ufsdirhash_acquire() at ufsdirhash_acquire+0x33 ufsdirhash_add() at ufsdirhash_add+0x19 ufs_direnter() at ufs_direnter+0x88b ufs_makeinode() at ufs_makeinode+0x31c VOP_CREATE_APV() at VOP_CREATE_APV+0x8d vn_open_cred() at vn_open_cred+0x423 kern_openat() at kern_openat+0x179 syscall() at syscall+0x1af Xfast_syscall() at Xfast_syscall+0xe1 --- syscall (5, FreeBSD ELF64, open), rip =3D 0x80083757c, rsp =3D 0x7fffff= ffdb78, rbp =3D 0x8 --- -----Original Message----- From: owner-freebsd-xen@freebsd.org [mailto:owner-freebsd-xen@freebsd.org] = On Behalf Of Hugo Silva Sent: 27 October 2009 06:47 PM To: freebsd-xen@freebsd.org Subject: Re: Problem: Xen 3.3.1 with FreeBSD 8.0 RC1 Carsten Heesch wrote: > Athough I seem to be talking to myself here, I have good news for RC2! > It works! > Just did an "freebsd-update -R 8.0-RC2 upgrade". Both GENERIC and > XENHVM kernels work without any problems. > > Maybe somebody else can chime in an confirm that, too? Probably good > for the developers to see positive feedback, while 8.0-RELEASE is > coming closer :-) > > > Cheers > Carsten > > > On 25 Oct 2009, at 00:31, Carsten Heesch wrote: > >> >> I realised that it's still possible to use 8.0-BETA* as a target for >> freebsd-update. So I investigated a bit further. For whatever it's >> worth: >> >> The problems described earlier started with BETA-4. >> >> BETA-3 is fine with both GENERIC and XENHVM kernel, except that I see >> this on the console and in dmesg every now and then (with both kernels): >> >> >> lock order reversal: >> 1st 0xffffff8014810620 bufwait (bufwait) @ >> /usr/src/sys/kern/vfs_bio.c:2559 >> 2nd 0xffffff00015a7c00 dirhash (dirhash) @ >> /usr/src/sys/ufs/ufs/ufs_dirhash.c:285 >> KDB: stack backtrace: >> db_trace_self_wrapper() at db_trace_self_wrapper+0x2a >> _witness_debugger() at _witness_debugger+0x2e >> witness_checkorder() at witness_checkorder+0x81e >> _sx_xlock() at _sx_xlock+0x55 >> ufsdirhash_acquire() at ufsdirhash_acquire+0x33 >> ufsdirhash_add() at ufsdirhash_add+0x19 >> ufs_direnter() at ufs_direnter+0x88b >> ufs_makeinode() at ufs_makeinode+0x31c >> VOP_CREATE_APV() at VOP_CREATE_APV+0x8d >> vn_open_cred() at vn_open_cred+0x423 >> kern_openat() at kern_openat+0x179 >> syscall() at syscall+0x1af >> Xfast_syscall() at Xfast_syscall+0xe1 >> --- syscall (5, FreeBSD ELF64, open), rip =3D 0x800e32dfc, rsp =3D >> 0x7fffffffe608, rbp =3D 0x1a4 --- >> >> >> I though this might be XENHVM kernel related, but it happens with >> GENERIC kernel as well. Not sure if this is related to XEN at all. >> >> >> >> Cheers >> Carsten >> >> >> > > _______________________________________________ > 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" I grabbed the 8.0-RC2/amd64iso to give this a spin; no luck here, it hangs after "Trying to mount root from ufs:/dev/md0". Also, I confirm the panics on boot with RC1. It's gone with RC2, but as I said, it gets stuck (for me, at least). My dom0 is NetBSD 5 / amd64. _______________________________________________ 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 Thu Oct 29 23:27:13 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 A533B1065698 for ; Thu, 29 Oct 2009 23:27:13 +0000 (UTC) (envelope-from sysconfig@ossafe.org) Received: from mx2.the-ally.co.uk (mx2.the-ally.co.uk [95.154.227.236]) by mx1.freebsd.org (Postfix) with ESMTP id 624938FC15 for ; Thu, 29 Oct 2009 23:27:13 +0000 (UTC) Received: from mx2.the-ally.co.uk (localhost.localdomain [127.0.0.1]) by mx2.the-ally.co.uk (Postfix) with ESMTP id C75ACED0998 for ; Thu, 29 Oct 2009 23:27:11 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=ossafe.org; h=from :content-type:content-transfer-encoding:subject:date:message-id :to:mime-version; s=selector1; bh=N2rOdXykdS/ERoNLGjgQbbAb+P4=; b= qP+2nvcQ6qmhCq1MLgVxoA3AKNrsIEugACAn2bY4aX3rCL7enE4tr2PK8SvWgB4M MBy4ap5N58/CCWAbJCqNT+VNpVEux/WWlP4hrO/7MEfvT40pJK/4l/bN+Do+R+4r ox42i3dabEdrR5roxKykMCN3J94bRTlsXXrxx1mv0cc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=ossafe.org; h=from :content-type:content-transfer-encoding:subject:date:message-id :to:mime-version; q=dns; s=selector1; b=jyhOoDnRGxFy+7Kzlbig5vJa 4qiswJciKf7o9zqekYUEiduvp9b1cn/pIJ11Kzs71gfGDbcyLcFlsohSPByahVgL tA1QEXPgKbtGPArXPkyT1LbGDy7M8mDOclPapunGAEAtLzpm7levy/eTBUvuOOYs gWgM7sQIfSGl/gy50DM= Received: from [10.2.2.20] (unknown [10.2.2.20]) by mx2.the-ally.co.uk (Postfix) with ESMTP id 97C14ED0994 for ; Thu, 29 Oct 2009 23:27:11 +0000 (GMT) From: Carsten Heesch Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Date: Thu, 29 Oct 2009 23:27:11 +0000 Message-Id: <869459F8-7490-4270-84D0-A1168002E509@ossafe.org> To: freebsd-xen@freebsd.org Mime-Version: 1.0 (Apple Message framework v1076) X-Mailer: Apple Mail (2.1076) Subject: SCHED_ULE vs SCHED_4BSD for XENHVM domU 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, 29 Oct 2009 23:27:13 -0000 Hi guys, After FreeBSD 8.0-RC2 is working well (for me) on Xen 3.3.1, I somehow made an interesting observation: Even if the FreeBSD domU does absolutely nothing, each of the assigned vCPUs will be reported by xentop as using 15%-25% CPU time. It doesn't matter, if domU is running with 1 or 4 vCPUs. All of them float at the same level. On the same Xen box five other domU's (CentOS 5.2-5.4) have an idle CPU percentage of 0 to 0.5%. So I played a bit and figured out that changing the scheduler in the XENHVM kernel configuration from "option SCHED_ULE" to "option SCHED_4BSD" resolves this problem. The idle state of the FreeBSD domU is now identical to the CentOS domU's. However, this of course means using an old (maybe even deprecated?) scheduler, which moreover isn't the best choice for multiple (virtual) CPUs. The configuration I tested on is: Intel i7 920 Quad-Core with Hyperthreading (8 logical CPUs) Citrix XenServer 5.5 (based on CentOS 5.2, Xen 3.3.1) Any thoughts, ideas, solutions? Thanks! Carsten From owner-freebsd-xen@FreeBSD.ORG Thu Oct 29 23:31:14 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 F19D11065679 for ; Thu, 29 Oct 2009 23:31:14 +0000 (UTC) (envelope-from carsten@ossafe.org) Received: from mx2.the-ally.co.uk (mx2.the-ally.co.uk [95.154.227.236]) by mx1.freebsd.org (Postfix) with ESMTP id AED3F8FC15 for ; Thu, 29 Oct 2009 23:31:14 +0000 (UTC) Received: from mx2.the-ally.co.uk (localhost.localdomain [127.0.0.1]) by mx2.the-ally.co.uk (Postfix) with ESMTP id CE00EED0997 for ; Thu, 29 Oct 2009 23:12:19 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=ossafe.org; h=from :content-type:content-transfer-encoding:subject:date:message-id :to:mime-version; s=selector1; bh=N2rOdXykdS/ERoNLGjgQbbAb+P4=; b= nljkz2ac9zTiDrIegTJike+ggrxjH1zkAjr0apO8uCOMM8Po/5mQSdY/ECilnlG7 G+MRt3GZD4d+j0hQYITIrC1Z0sCp3dpucWiRpTRkACByKdq9jK7IXk+qh3bOA5Ll 9/qbYxxPvnjE1jpqcRaFz85zAYaYzboXAB7U0oZaA/E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=ossafe.org; h=from :content-type:content-transfer-encoding:subject:date:message-id :to:mime-version; q=dns; s=selector1; b=GsSrHgCLbYN25zJEOdHIu3yM 71I9200/7HPijk5hol6gSB4oOnDxq+vtfswvROYshfiV3Ftko85j56eUXMvBWvGI K3rIbUFPGNf4KThidn+hg72+wkGz3NkH3YvRKWGGg1mvXdkx5H5E0+b22qMT469b UFtIciUP/pdLAD+9h90= Received: from [10.2.2.20] (unknown [10.2.2.20]) by mx2.the-ally.co.uk (Postfix) with ESMTP id 9A0FDED0994 for ; Thu, 29 Oct 2009 23:12:19 +0000 (GMT) From: Carsten Heesch Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Date: Thu, 29 Oct 2009 23:12:19 +0000 Message-Id: To: freebsd-xen@freebsd.org Mime-Version: 1.0 (Apple Message framework v1076) X-Mailer: Apple Mail (2.1076) Subject: SCHED_ULE vs SCHED_4BSD for XENHVM domU 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, 29 Oct 2009 23:31:15 -0000 Hi guys, After FreeBSD 8.0-RC2 is working well (for me) on Xen 3.3.1, I somehow made an interesting observation: Even if the FreeBSD domU does absolutely nothing, each of the assigned vCPUs will be reported by xentop as using 15%-25% CPU time. It doesn't matter, if domU is running with 1 or 4 vCPUs. All of them float at the same level. On the same Xen box five other domU's (CentOS 5.2-5.4) have an idle CPU percentage of 0 to 0.5%. So I played a bit and figured out that changing the scheduler in the XENHVM kernel configuration from "option SCHED_ULE" to "option SCHED_4BSD" resolves this problem. The idle state of the FreeBSD domU is now identical to the CentOS domU's. However, this of course means using an old (maybe even deprecated?) scheduler, which moreover isn't the best choice for multiple (virtual) CPUs. The configuration I tested on is: Intel i7 920 Quad-Core with Hyperthreading (8 logical CPUs) Citrix XenServer 5.5 (based on CentOS 5.2, Xen 3.3.1) Any thoughts, ideas, solutions? Thanks! Carsten From owner-freebsd-xen@FreeBSD.ORG Thu Oct 29 23:33:25 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 BDB0A106566B for ; Thu, 29 Oct 2009 23:33:25 +0000 (UTC) (envelope-from sysconfig@ossafe.org) Received: from mx2.the-ally.co.uk (mx2.the-ally.co.uk [95.154.227.236]) by mx1.freebsd.org (Postfix) with ESMTP id 784568FC1D for ; Thu, 29 Oct 2009 23:33:25 +0000 (UTC) Received: from mx2.the-ally.co.uk (localhost.localdomain [127.0.0.1]) by mx2.the-ally.co.uk (Postfix) with ESMTP id F1819ED0997; Thu, 29 Oct 2009 23:33:23 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=ossafe.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s= selector1; bh=WCFRWOCkyrAy01F1YqnQfKNPa3Y=; b=RMwgQqdcZ+1svUVVXn HDbJ6PELMHxsVS/4FKvY2vGwJ5iK+GnAZhuaZ78H+CEWQCMwZqynRmv8vzQGwhbV 5gBiLvaw2o61ZvFD8FiaGNvN92YfqsXv1cJBJyeZwyAIbLh+oHOLbvFRDxVyCNYt oy1ifaoBzeDKCBxMeyrUIy2T0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=ossafe.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=ZEQdmHGZcLefLLVjtWadPAE8zpjPW1uYqY0Qh9XwanG/CbNj4/b Sm3gE6n1HfDGkE9HnCTo5ZOJouOaUhSd8d9Qqkp3XOkgO36ON6LVRPiAJ4q7MHkX ZR7m3vNMNeFPdxXhZJJq+eMuMKmxycNIMGwffbfZu7RY4tTxJfLsy80c= Received: from [10.2.2.20] (unknown [10.2.2.20]) by mx2.the-ally.co.uk (Postfix) with ESMTP id B2FAFED0994; Thu, 29 Oct 2009 23:33:23 +0000 (GMT) Mime-Version: 1.0 (Apple Message framework v1076) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes From: Carsten Heesch In-Reply-To: <869459F8-7490-4270-84D0-A1168002E509@ossafe.org> Date: Thu, 29 Oct 2009 23:33:23 +0000 Content-Transfer-Encoding: 7bit Message-Id: References: <869459F8-7490-4270-84D0-A1168002E509@ossafe.org> To: Carsten Heesch X-Mailer: Apple Mail (2.1076) Cc: freebsd-xen@freebsd.org Subject: Re: SCHED_ULE vs SCHED_4BSD for XENHVM domU 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, 29 Oct 2009 23:33:25 -0000 Oops, sorry for posting this twice. I thought it didn't go through with the first attempt. On 29 Oct 2009, at 23:27, Carsten Heesch wrote: > Hi guys, > > After FreeBSD 8.0-RC2 is working well (for me) on Xen 3.3.1, I > somehow made an interesting observation: > > Even if the FreeBSD domU does absolutely nothing, each of the > assigned vCPUs will be reported by xentop as using 15%-25% CPU time. > It doesn't matter, if domU is running with 1 or 4 vCPUs. All of them > float at the same level. > > On the same Xen box five other domU's (CentOS 5.2-5.4) have an idle > CPU percentage of 0 to 0.5%. > > So I played a bit and figured out that changing the scheduler in the > XENHVM kernel configuration from "option SCHED_ULE" to "option > SCHED_4BSD" resolves this problem. The idle state of the FreeBSD > domU is now identical to the CentOS domU's. > > However, this of course means using an old (maybe even deprecated?) > scheduler, which moreover isn't the best choice for multiple > (virtual) CPUs. > > The configuration I tested on is: > Intel i7 920 Quad-Core with Hyperthreading (8 logical CPUs) > Citrix XenServer 5.5 (based on CentOS 5.2, Xen 3.3.1) > > > Any thoughts, ideas, solutions? > > > Thanks! > > Carsten > > > _______________________________________________ > 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" Best regards, Carsten Heesch Mobile: +44 (0)7889-129998 Mail: carsten@heesch.me.uk Skype: carstenh74 From owner-freebsd-xen@FreeBSD.ORG Fri Oct 30 09:30:47 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 7826E1065695 for ; Fri, 30 Oct 2009 09:30:47 +0000 (UTC) (envelope-from mister.olli@googlemail.com) Received: from mail-ew0-f209.google.com (mail-ew0-f209.google.com [209.85.219.209]) by mx1.freebsd.org (Postfix) with ESMTP id 077648FC18 for ; Fri, 30 Oct 2009 09:30:46 +0000 (UTC) Received: by ewy5 with SMTP id 5so819279ewy.37 for ; Fri, 30 Oct 2009 02:30:45 -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=wx+bn2VdwRJj8os5zwSb+tvV6peQOcJ4GCSEuYabDvQ=; b=Tw7XEyu0eB5z4dG49HwbAobKbRg4xM7Uh0cJWa2Fsk9t/3lvlttDctqgNaexBrm4g4 pM8GsjzpuYAqp7eP3BNQT6qRin4Zf+O/D73LhArJeYVXvDfy8wdo7LUIvYDUxxXOx3YX CgTmD/Soor83Um4vKhVgNFu5VkdZsKnhXecow= 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=YkrQxnhVquSSLw/8muLjoUb8Kg9zGSYx4tFy545QIVxmGOMB03sp5/K/t72olLIAIa wnkVpd8czJMwi8k0FC52uVw2g7Ns1vGsaYU3Df0LjVzw5T6zer4fmLPYtO59bParokvK IueY7dQtjiohJkCUmmEAR8uKLWHN5NiPgQy0o= Received: by 10.210.15.14 with SMTP id 14mr125844ebo.49.1256895045619; Fri, 30 Oct 2009 02:30:45 -0700 (PDT) Received: from ?172.16.16.125? (dsl212102251105.4dsl.de [212.102.251.105]) by mx.google.com with ESMTPS id 10sm8234472eyz.3.2009.10.30.02.30.44 (version=SSLv3 cipher=RC4-MD5); Fri, 30 Oct 2009 02:30:44 -0700 (PDT) From: "Mr. Olli" To: Carsten Heesch In-Reply-To: References: Content-Type: text/plain Date: Fri, 30 Oct 2009 10:30:23 +0100 Message-Id: <1256895023.6479.42.camel@phoenix.blechhirn.net> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 Content-Transfer-Encoding: 7bit Cc: freebsd-xen@freebsd.org Subject: Re: SCHED_ULE vs SCHED_4BSD for XENHVM domU 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: Fri, 30 Oct 2009 09:30:47 -0000 Hi, I compiled FreeBSD8-RC2 from SVN revision 198456 with the XEN config file left unchanged. the domU is 32bit. I'm running on SCHED_ULE and the system consumes <1% vCPU (according to xentop) in idle status. My dom0 is a gentoo linux 32-bit with 2x athlonMP 1900+ and 4GB ram. greetz, ---- Mr. Olli On Thu, 2009-10-29 at 23:12 +0000, Carsten Heesch wrote: > Hi guys, > > After FreeBSD 8.0-RC2 is working well (for me) on Xen 3.3.1, I somehow > made an interesting observation: > > Even if the FreeBSD domU does absolutely nothing, each of the assigned > vCPUs will be reported by xentop as using 15%-25% CPU time. It doesn't > matter, if domU is running with 1 or 4 vCPUs. All of them float at the > same level. > > On the same Xen box five other domU's (CentOS 5.2-5.4) have an idle > CPU percentage of 0 to 0.5%. > > So I played a bit and figured out that changing the scheduler in the > XENHVM kernel configuration from "option SCHED_ULE" to "option > SCHED_4BSD" resolves this problem. The idle state of the FreeBSD domU > is now identical to the CentOS domU's. > > However, this of course means using an old (maybe even deprecated?) > scheduler, which moreover isn't the best choice for multiple > (virtual) CPUs. > > The configuration I tested on is: > Intel i7 920 Quad-Core with Hyperthreading (8 logical CPUs) > Citrix XenServer 5.5 (based on CentOS 5.2, Xen 3.3.1) > > > Any thoughts, ideas, solutions? > > > Thanks! > > Carsten > > > > _______________________________________________ > 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 Fri Oct 30 18:17:25 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 82BAD1065670 for ; Fri, 30 Oct 2009 18:17:25 +0000 (UTC) (envelope-from danilobaio@gmail.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 81D158FC17 for ; Fri, 30 Oct 2009 18:17:24 +0000 (UTC) Received: by bwz5 with SMTP id 5so3897437bwz.3 for ; Fri, 30 Oct 2009 11:17:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=nG5jFdEf6w+4agQDuQRY1QIkuXtGGN3+sfsVfjYTgjY=; b=GRsWC5phZBcnWJ2jL59RRss2Ij5wvm2D31VYH8NCXPP67o4x5bPVhb07qGdkAGfCnq 936Lam4GcALV5spNRYmNwzBuBrKB707DBsRxqPzDhlq+ADKpErs71fSkRRkbnxMgkymf 76RlCtxa/FRSxZSFc3H+gs1fktpUEF4nRlF0w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=N/YwymNa0Ie+ob5bxmhgIcJ2LgMJbglxxdDufEdb83SRfcIDtGPRCQzGnG3cDjQhGC ogwm17JTOjgT/AU2BjTXmVdfhUN//Y4wrnQj5JDz9VAFB76pM+VMs0YKaSWN4a8yMiYP sdX120y//vpOPFoCint3g++Z1tHe77K4THvyk= MIME-Version: 1.0 Received: by 10.204.154.207 with SMTP id p15mr1287392bkw.202.1256925054145; Fri, 30 Oct 2009 10:50:54 -0700 (PDT) In-Reply-To: References: Date: Fri, 30 Oct 2009 15:50:53 -0200 Message-ID: <5b9854910910301050j3d6d3ab8h5e9b35227b58304@mail.gmail.com> From: Danilo Baio To: freebsd-xen@freebsd.org Content-Type: multipart/mixed; boundary=0015174795725c964604772aab8a X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: SCHED_ULE vs SCHED_4BSD for XENHVM domU 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: Fri, 30 Oct 2009 18:17:25 -0000 --0015174795725c964604772aab8a Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Thu, Oct 29, 2009 at 9:12 PM, Carsten Heesch wrote: > Hi guys, > > After FreeBSD 8.0-RC2 is working well (for me) on Xen 3.3.1, I somehow ma= de > an interesting observation: > > Even if the FreeBSD domU does absolutely nothing, each of the assigned > vCPUs will be reported by xentop as using 15%-25% CPU time. It doesn't > matter, if domU is running with 1 or 4 vCPUs. All of them float at the sa= me > level. > > On the same Xen box five other domU's (CentOS 5.2-5.4) have an idle CPU > percentage of 0 to 0.5%. > > So I played a bit and figured out that changing the scheduler in the XENH= VM > kernel configuration from "option SCHED_ULE" to "option SCHED_4BSD" resol= ves > this problem. The idle state of the FreeBSD domU is now identical to the > CentOS domU's. > > However, this of course means using an old (maybe even deprecated?) > scheduler, which moreover isn't the best choice for multiple (virtual) > CPUs. > > The configuration I tested on is: > Intel i7 920 Quad-Core with Hyperthreading (8 logical CPUs) > Citrix XenServer 5.5 (based on CentOS 5.2, Xen 3.3.1) > > > Any thoughts, ideas, solutions? > > > Thanks! > > Carsten > > Hi, Same thing here. I've build 8.0-RC2 amd64 with kernel XENHVM for testing with a XenServer 5.0.0 that i have here. Only the memory information don't appear on the console of xencenter. And the processor 14% of use all the time. After build with SCHED_4BSD, 3% usage CPU. AMD64 - XENHVM freeba8# uname -a FreeBSD freeba8.localdomain 8.0-RC2 FreeBSD 8.0-RC2 #0: Fri Oct 30 15:18:43 BRST 2009 root@freeba8.localdomain:/usr/obj/usr/src/sys/XENHVM amd64 XenServer 5.0.0 (CentOS) Xen 3.2 Regards. --=20 Danilo Gon=E7alves Baio (dbaio) danilobaio (*) gmail . com +55 (44) 8801 1257 --0015174795725c964604772aab8a--