From owner-freebsd-xen@FreeBSD.ORG Mon May 20 11:06:58 2013 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4F4B770E for ; Mon, 20 May 2013 11:06:58 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id E83B6DCF for ; Mon, 20 May 2013 11:06:57 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r4KB6vGm083130 for ; Mon, 20 May 2013 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r4KB6vla083128 for freebsd-xen@FreeBSD.org; Mon, 20 May 2013 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 20 May 2013 11:06:57 GMT Message-Id: <201305201106.r4KB6vla083128@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 Subject: Current problem reports assigned to freebsd-xen@FreeBSD.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 May 2013 11:06:58 -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/176471 xen [xen] xn driver crash on detach o kern/176053 xen [xen] [patch] i386: Correct wrong usage of vsnprintf() o kern/175954 xen [xen] XENHVM xn network driver extreme packet loss dur o kern/175822 xen [xen] FreeBSD 9.1 does not work with Xen 4.0 o kern/175757 xen [xen] [patch] xen pvhvm looses keyboard input from VNC o kern/171873 xen [xen] xn network device floods warning in dmesg o kern/171118 xen [xen] FreeBSD XENHVM guest doesn't shutdown cleanly o kern/166174 xen [xen] Problems ROOT MOUNT ERROR o kern/165418 xen [xen] Problems mounting root filesystem from XENHVM o kern/164630 xen [xen] XEN HVM kernel: run_interrupt_driven_hooks: stil o kern/164450 xen [xen] Failed to install FreeeBSD 9.0-RELEASE from CD i o kern/162677 xen [xen] FreeBSD not compatible with "Current Stable Xen" o kern/161318 xen [xen] sysinstall crashes with floating point exception 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/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 35 problems total. From owner-freebsd-xen@FreeBSD.ORG Tue May 21 14:00:01 2013 Return-Path: Delivered-To: freebsd-xen@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BF7F0DEF for ; Tue, 21 May 2013 14:00:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 980102B3 for ; Tue, 21 May 2013 14:00:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r4LE01CF018689 for ; Tue, 21 May 2013 14:00:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r4LE01wR018688; Tue, 21 May 2013 14:00:01 GMT (envelope-from gnats) Date: Tue, 21 May 2013 14:00:01 GMT Message-Id: <201305211400.r4LE01wR018688@freefall.freebsd.org> To: freebsd-xen@FreeBSD.org Cc: From: Adam McDougall Subject: Re: kern/176471: [xen] xn driver crash on detach X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Adam McDougall 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, 21 May 2013 14:00:01 -0000 The following reply was made to PR kern/176471; it has been noted by GNATS. From: Adam McDougall To: bug-followup@FreeBSD.org, pete@helenius.fi Cc: Subject: Re: kern/176471: [xen] xn driver crash on detach Date: Tue, 21 May 2013 09:57:06 -0400 This patch is working well for me as well, using it on 9.1-stable. Can we get it committed? Thanks. From owner-freebsd-xen@FreeBSD.ORG Tue May 21 15:00:05 2013 Return-Path: Delivered-To: freebsd-xen@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A2F87D88 for ; Tue, 21 May 2013 15:00:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 7BFA286F for ; Tue, 21 May 2013 15:00:05 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r4LF01J5029963 for ; Tue, 21 May 2013 15:00:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r4LF01VN029962; Tue, 21 May 2013 15:00:01 GMT (envelope-from gnats) Date: Tue, 21 May 2013 15:00:01 GMT Message-Id: <201305211500.r4LF01VN029962@freefall.freebsd.org> To: freebsd-xen@FreeBSD.org Cc: From: "Mark Felder" Subject: Re: kern/176471: [xen] xn driver crash on detach X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Mark Felder 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, 21 May 2013 15:00:05 -0000 The following reply was made to PR kern/176471; it has been noted by GNATS. From: "Mark Felder" To: bug-followup@freebsd.org, pete@helenius.fi Cc: Subject: Re: kern/176471: [xen] xn driver crash on detach Date: Tue, 21 May 2013 09:52:28 -0500 I've been running this in production since March 1st with no problems. I also would like to see this committed ASAP. From owner-freebsd-xen@FreeBSD.ORG Tue May 21 18:58:46 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1DD9E372; Tue, 21 May 2013 18:58:46 +0000 (UTC) (envelope-from konrad.wilk@oracle.com) Received: from userp1050.oracle.com (userp1050.oracle.com [156.151.31.82]) by mx1.freebsd.org (Postfix) with ESMTP id D04A869C; Tue, 21 May 2013 18:58:44 +0000 (UTC) Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by userp1050.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r4LHeKtE015857 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 21 May 2013 17:40:20 GMT Received: from acsinet22.oracle.com (acsinet22.oracle.com [141.146.126.238]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r4LHeAnH023917 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 21 May 2013 17:40:10 GMT Received: from aserz7021.oracle.com (aserz7021.oracle.com [141.146.126.230]) by acsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r4LHeAOT029243 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 21 May 2013 17:40:11 GMT Received: from abhmt116.oracle.com (abhmt116.oracle.com [141.146.116.68]) by aserz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r4LHeAO7024106; Tue, 21 May 2013 17:40:10 GMT Received: from phenom.dumpdata.com (/50.195.21.189) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 21 May 2013 10:40:10 -0700 Received: by phenom.dumpdata.com (Postfix, from userid 1000) id 6B1141BF781; Tue, 21 May 2013 13:40:09 -0400 (EDT) Date: Tue, 21 May 2013 13:40:09 -0400 From: Konrad Rzeszutek Wilk To: Roger Pau =?iso-8859-1?Q?Monn=E9?= Subject: Re: [Xen-devel] FreeBSD PVHVM call for testing Message-ID: <20130521174009.GA5011@phenom.dumpdata.com> References: <519131D8.9010307@citrix.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <519131D8.9010307@citrix.com> User-Agent: Mutt/1.5.21 (2010-09-15) Content-Transfer-Encoding: quoted-printable X-Source-IP: userp1040.oracle.com [156.151.31.81] Cc: "freebsd-xen@freebsd.org" , xen-devel , "freebsd-virtualization@freebsd.org" , "xen-users@lists.xen.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 May 2013 18:58:46 -0000 On Mon, May 13, 2013 at 08:32:56PM +0200, Roger Pau Monn=E9 wrote: > Hello, >=20 > Recently Justin T Gibbs, Will Andrews and myself have been working on > improving the Xen support in FreeBSD. The main goal of this was to brin= g > full PVHVM support to FreeBSD, right now FreeBSD is only using PV > interfaces for disk and network interfaces when running as a HVM guest. > The main benefits of this changes are that Xen virtual interrupts (even= t > channels) are now delivered to the guest using a vector callback > injection, that is a per-cpu mechanism that allows each vCPU to have > different interrupts assigned, so for example network and disk > interrupts are delivered to different vCPUs in order to improve > performance. With this changes FreeBSD also uses PV timers when running > as an HVM guest, which should provide better time keeping and reduce th= e > virtualization overhead, since emulated timers are no longer used. PV > IPIs can also be used inside a HVM guest, but this will be implemented > later. >=20 > Right now the code is in a state where it can be tested by users, so we > would like to encourage FreeBSD and Xen users to test it and provide > feedback. >=20 > The code is available in the following git repository, under the branch > pvhvm_v5: >=20 > http://xenbits.xen.org/gitweb/?p=3Dpeople/royger/freebsd.git;a=3Dsummar= y >=20 > Also, I've created a wiki page that explains how to set up a FreeBSD > PVHVM for testing: >=20 > http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM I tried on my Linux box to do this: HEAD is now at 9b25356... xen-netfront: fix detach of network interfaces konrad@phenom:~/git/freebsd$ make kernel-toolchain && make buildkernel KE= RNCONF=3DXENHVM && make installkernel KERNCONF=3DXENHVM Makefile:123: *** missing separator. Stop. As I thought it would compile the same way you can compile NetBSD - that = is even on non-BSD distros. Is that not the case? Should I only do this unde= r a FreeBSD guest? From owner-freebsd-xen@FreeBSD.ORG Wed May 22 11:41:06 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 23DCB3CD; Wed, 22 May 2013 11:41:06 +0000 (UTC) (envelope-from roger.pau@citrix.com) Received: from SMTP.EU.CITRIX.COM (smtp.eu.citrix.com [46.33.159.39]) by mx1.freebsd.org (Postfix) with ESMTP id 94868151; Wed, 22 May 2013 11:41:04 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.87,719,1363132800"; d="scan'208";a="4848072" Received: from lonpex01cl01.citrite.net ([10.30.203.101]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 22 May 2013 11:41:04 +0000 Received: from [192.168.1.30] (10.30.203.1) by LONPEX01CL01.citrite.net (10.30.203.101) with Microsoft SMTP Server id 14.2.342.3; Wed, 22 May 2013 12:41:02 +0100 Message-ID: <519CAECE.9040706@citrix.com> Date: Wed, 22 May 2013 13:41:02 +0200 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Konrad Rzeszutek Wilk Subject: Re: [Xen-devel] FreeBSD PVHVM call for testing References: <519131D8.9010307@citrix.com> <20130521174009.GA5011@phenom.dumpdata.com> In-Reply-To: <20130521174009.GA5011@phenom.dumpdata.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Originating-IP: [10.30.203.1] Cc: "freebsd-xen@freebsd.org" , xen-devel , "freebsd-virtualization@freebsd.org" , "xen-users@lists.xen.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 May 2013 11:41:06 -0000 On 21/05/13 19:40, Konrad Rzeszutek Wilk wrote: > On Mon, May 13, 2013 at 08:32:56PM +0200, Roger Pau Monné wrote: >> Hello, >> >> Recently Justin T Gibbs, Will Andrews and myself have been working on >> improving the Xen support in FreeBSD. The main goal of this was to bring >> full PVHVM support to FreeBSD, right now FreeBSD is only using PV >> interfaces for disk and network interfaces when running as a HVM guest. >> The main benefits of this changes are that Xen virtual interrupts (event >> channels) are now delivered to the guest using a vector callback >> injection, that is a per-cpu mechanism that allows each vCPU to have >> different interrupts assigned, so for example network and disk >> interrupts are delivered to different vCPUs in order to improve >> performance. With this changes FreeBSD also uses PV timers when running >> as an HVM guest, which should provide better time keeping and reduce the >> virtualization overhead, since emulated timers are no longer used. PV >> IPIs can also be used inside a HVM guest, but this will be implemented >> later. >> >> Right now the code is in a state where it can be tested by users, so we >> would like to encourage FreeBSD and Xen users to test it and provide >> feedback. >> >> The code is available in the following git repository, under the branch >> pvhvm_v5: >> >> http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=summary >> >> Also, I've created a wiki page that explains how to set up a FreeBSD >> PVHVM for testing: >> >> http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM > > I tried on my Linux box to do this: > > > HEAD is now at 9b25356... xen-netfront: fix detach of network interfaces > konrad@phenom:~/git/freebsd$ make kernel-toolchain && make buildkernel KERNCONF=XENHVM && make installkernel KERNCONF=XENHVM > Makefile:123: *** missing separator. Stop. > > > As I thought it would compile the same way you can compile NetBSD - that is > even on non-BSD distros. Is that not the case? Should I only do this under > a FreeBSD guest? I have never tried to run the FreeBSD build system under something different than FreeBSD, also keep in mind that installkernel will place a bunch of FreeBSD files on your Linux box if you manage to run it. The error itself can probably be fixed by installing and using BSD make (bmake), but anyway you need a FreeBSD HVM DomU in order to test the kernel, so why not do the compilation on it? From owner-freebsd-xen@FreeBSD.ORG Wed May 22 11:45:13 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id EB4E04FE; Wed, 22 May 2013 11:45:13 +0000 (UTC) (envelope-from roger.pau@citrix.com) Received: from SMTP.EU.CITRIX.COM (smtp.eu.citrix.com [46.33.159.39]) by mx1.freebsd.org (Postfix) with ESMTP id 419E51B5; Wed, 22 May 2013 11:45:12 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.87,719,1363132800"; d="scan'208";a="4848238" Received: from lonpex01cl03.citrite.net ([10.30.203.103]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 22 May 2013 11:45:12 +0000 Received: from [192.168.1.30] (10.30.203.1) by LONPEX01CL03.citrite.net (10.30.203.103) with Microsoft SMTP Server id 14.2.342.3; Wed, 22 May 2013 12:45:11 +0100 Message-ID: <519CAFC7.1070908@citrix.com> Date: Wed, 22 May 2013 13:45:11 +0200 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Colin Percival Subject: Re: FreeBSD PVHVM call for testing References: <519131D8.9010307@citrix.com> <51952BAE.6010609@freebsd.org> <51957D42.9060801@citrix.com> <51959ED9.6040405@freebsd.org> <51974EC9.9030204@citrix.com> <5197A1EA.2040404@freebsd.org> In-Reply-To: <5197A1EA.2040404@freebsd.org> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Originating-IP: [10.30.203.1] Cc: "freebsd-xen@freebsd.org" , xen-devel , "freebsd-virtualization@freebsd.org" , "xen-users@lists.xen.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 May 2013 11:45:14 -0000 On 18/05/13 17:44, Colin Percival wrote: > On 05/18/13 02:50, Roger Pau Monné wrote: >> On 17/05/13 05:07, Colin Percival wrote: >>> On 05/16/13 17:43, Roger Pau Monné wrote: >>>> Thanks for testing this on EC2, could you post the full dmesg? So I can >>>> see the hypervisor version and if the PV timer is loaded or not. >>> >>> Here's what I get on a cc2.8xlarge with boot_verbose=YES: >> >> I've pushed a new branch to my repository, pvhvm_v7 that should work, >> there was a bug with PCI event channel interrupt set up. I've tested >> with 3.4 and seems OK, but of course it doesn't support the vector >> callback injection. > > That seems to work. dmesg is attached. Are there any particular tests > you'd like me to run? I have not tested ZFS, that might be a good one. If you are running this on Xen 3.4 the behaviour should be the same as without this patches, so there shouldn't be many differences. If you could try that on Xen 4.0 at least (if I remember correctly that's when the vector callback was introduced), you should see the PV timer getting attached, and a performance increase. > If anyone else wants to play with this, you can launch ami-e75c358e in the > EC2 us-east-1 region. > From owner-freebsd-xen@FreeBSD.ORG Wed May 22 12:21:26 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E127D6F2; Wed, 22 May 2013 12:21:26 +0000 (UTC) (envelope-from konrad.wilk@oracle.com) Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by mx1.freebsd.org (Postfix) with ESMTP id BDA248B8; Wed, 22 May 2013 12:21:26 +0000 (UTC) Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r4MCLLiY029665 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 22 May 2013 12:21:22 GMT Received: from aserz7022.oracle.com (aserz7022.oracle.com [141.146.126.231]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r4MCLMk1000201 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 22 May 2013 12:21:23 GMT Received: from abhmt115.oracle.com (abhmt115.oracle.com [141.146.116.67]) by aserz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r4MCLMhb019701; Wed, 22 May 2013 12:21:22 GMT Received: from konrad-lan.dumpdata.com (/10.154.121.43) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 22 May 2013 05:21:22 -0700 Date: Wed, 22 May 2013 08:21:19 -0400 From: Konrad Rzeszutek Wilk To: Roger Pau =?iso-8859-1?Q?Monn=E9?= Subject: Re: [Xen-devel] FreeBSD PVHVM call for testing Message-ID: <20130522122119.GD3162@konrad-lan.dumpdata.com> References: <519131D8.9010307@citrix.com> <20130521174009.GA5011@phenom.dumpdata.com> <519CAECE.9040706@citrix.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <519CAECE.9040706@citrix.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: ucsinet22.oracle.com [156.151.31.94] Cc: "freebsd-xen@freebsd.org" , xen-devel , "freebsd-virtualization@freebsd.org" , "xen-users@lists.xen.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 May 2013 12:21:26 -0000 On Wed, May 22, 2013 at 01:41:02PM +0200, Roger Pau Monné wrote: > On 21/05/13 19:40, Konrad Rzeszutek Wilk wrote: > > On Mon, May 13, 2013 at 08:32:56PM +0200, Roger Pau Monné wrote: > >> Hello, > >> > >> Recently Justin T Gibbs, Will Andrews and myself have been working on > >> improving the Xen support in FreeBSD. The main goal of this was to bring > >> full PVHVM support to FreeBSD, right now FreeBSD is only using PV > >> interfaces for disk and network interfaces when running as a HVM guest. > >> The main benefits of this changes are that Xen virtual interrupts (event > >> channels) are now delivered to the guest using a vector callback > >> injection, that is a per-cpu mechanism that allows each vCPU to have > >> different interrupts assigned, so for example network and disk > >> interrupts are delivered to different vCPUs in order to improve > >> performance. With this changes FreeBSD also uses PV timers when running > >> as an HVM guest, which should provide better time keeping and reduce the > >> virtualization overhead, since emulated timers are no longer used. PV > >> IPIs can also be used inside a HVM guest, but this will be implemented > >> later. > >> > >> Right now the code is in a state where it can be tested by users, so we > >> would like to encourage FreeBSD and Xen users to test it and provide > >> feedback. > >> > >> The code is available in the following git repository, under the branch > >> pvhvm_v5: > >> > >> http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=summary > >> > >> Also, I've created a wiki page that explains how to set up a FreeBSD > >> PVHVM for testing: > >> > >> http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM > > > > I tried on my Linux box to do this: > > > > > > HEAD is now at 9b25356... xen-netfront: fix detach of network interfaces > > konrad@phenom:~/git/freebsd$ make kernel-toolchain && make buildkernel KERNCONF=XENHVM && make installkernel KERNCONF=XENHVM > > Makefile:123: *** missing separator. Stop. > > > > > > As I thought it would compile the same way you can compile NetBSD - that is > > even on non-BSD distros. Is that not the case? Should I only do this under > > a FreeBSD guest? > > I have never tried to run the FreeBSD build system under something > different than FreeBSD, also keep in mind that installkernel will place > a bunch of FreeBSD files on your Linux box if you manage to run it. The > error itself can probably be fixed by installing and using BSD make > (bmake), but anyway you need a FreeBSD HVM DomU in order to test the > kernel, so why not do the compilation on it? Oh, sure. Just thought that the NetBSD method (which also allows one to build the kernel and the iso) was the same on FreeBSd. Will of course install first the HVM domU and do it again. > From owner-freebsd-xen@FreeBSD.ORG Wed May 22 15:27:21 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id AA79EDC9 for ; Wed, 22 May 2013 15:27:21 +0000 (UTC) (envelope-from ykohut@onapp.com) Received: from mail-ea0-x235.google.com (mail-ea0-x235.google.com [IPv6:2a00:1450:4013:c01::235]) by mx1.freebsd.org (Postfix) with ESMTP id 3105BDC2 for ; Wed, 22 May 2013 15:27:20 +0000 (UTC) Received: by mail-ea0-f181.google.com with SMTP id a11so1226002eae.40 for ; Wed, 22 May 2013 08:27:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to:x-mailer:x-gm-message-state; bh=oUWEwIJ3t38+zPldr9E+ypvwxb3MPC1MIw4SuwB2qG4=; b=AcD2gslmtSQVpuEQ9EIH7Ly5sHvtZGPwMze+KP8IvfFFjQV/F8OmZs6jzYyQosRKe6 vG5Cb4tAHgVSOEKhcK6JkF55AC1YUZ2iPktlDHUYkpYGaegmT0Qq71nEc1xzK8v8seN3 IBDPpTvuX0k1KR9PnksvXcSVeF7VaS9jDDipDcTUTvSdLLYQgU4GwnxAEW+HHiFf6Qyx 1xwUCyIJMZafm3D0pDZef1gbJqez/LDMbYdGknwJ1REQE0KzqW0n6mBWN/RiGe0jbcvT snH7hyDpLZFcAH+0qQnClaEAhrNQJMyEqdRSPehUXgzN1fKfN2LJSGldsVoFpLQSiN50 iN5Q== X-Received: by 10.15.107.77 with SMTP id ca53mr19687223eeb.40.1369236440021; Wed, 22 May 2013 08:27:20 -0700 (PDT) Received: from [192.168.128.192] (ext.vps.lviv.ua. [194.44.160.178]) by mx.google.com with ESMTPSA id bp51sm10903796eeb.5.2013.05.22.08.27.17 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 22 May 2013 08:27:18 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: FreeBSD PVHVM call for testing From: Yuriy Kohut In-Reply-To: <519131D8.9010307@citrix.com> Date: Wed, 22 May 2013 18:27:16 +0300 Message-Id: <7C420745-BAC0-4BD0-AB60-E3BC7F8BA2A7@onapp.com> References: <519131D8.9010307@citrix.com> To: =?iso-8859-1?Q?Roger_Pau_Monn=E9?= X-Mailer: Apple Mail (2.1503) X-Gm-Message-State: ALoCoQly9Qny+NsIA/B1tBYpY7MCe7ACTkKXHVo2b2UbvyMW1pRR1LtVKV884uGZUzrT6xAh9fS2 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-xen@freebsd.org" , xen-devel , "freebsd-virtualization@freebsd.org" , "xen-users@lists.xen.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 May 2013 15:27:21 -0000 Hi, I've just successfully run FreeBSD 9.1 based guest with 'pvhvm_v8' based = kernel under Xen 3.4.4. Hypervisor details: # xm info host : ******* release : 2.6.18-348.2.1.el5xen version : #1 SMP Tue Mar 5 17:05:33 EST 2013 machine : x86_64 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2128 hw_caps : = bfebfbff:28100800:00000000:00000340:009ce3bd:00000000:00000001:00000000 virt_caps : hvm total_memory : 6135 free_memory : 262 node_to_cpu : node0:0-3 node_to_memory : node0:262 xen_major : 3 xen_minor : 4 xen_extra : .4 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 = hvm-3.0-x86_32p hvm-3.0-x86_64=20 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=3D0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-52) cc_compile_by : root cc_compile_domain : ****** cc_compile_date : Wed Sep 5 18:01:10 EEST 2012 xend_config_format : 4 DomU details: # xm list --long h283bpm53f9rnx (domain (domid 61) (on_crash restart) (uuid a2cbcba9-1d66-87ce-6d2f-412e70eab051) (bootloader_args ) (vcpus 2) (name h283bpm53f9rnx) (on_poweroff destroy) (on_reboot restart) (cpus (() ())) (bootloader ) (maxmem 1024) (memory 1024) (shadow_memory 10) (features ) (on_xend_start ignore) (on_xend_stop ignore) (start_time 1369235607.92) (cpu_time 31.914003553) (online_vcpus 2) (image (hvm (kernel ) (videoram 4) (hpet 0) (stdvga 0) (loader /usr/lib/xen/boot/hvmloader) (vncunused 1) (xen_platform_pci 1) (boot cd) (rtc_timeoffset 7202) (pci ()) (pae 1) (vpt_align 1) (hap 1) (viridian 0) (acpi 1) (localtime 0) (timer_mode 1) (vnc 1) (nographic 0) (guest_os_type default) (pci_msitranslate 1) (apic 1) (monitor 0) (usbdevice tablet) (device_model /usr/lib64/xen/bin/qemu-dm) (pci_power_mgmt 0) (usb 0) (xauthority /root/.Xauthority) (isa 0) (notes (SUSPEND_CANCEL 1)) ) ) (status 2) (state -b----) (store_mfn 1044476) (device (vif (bridge xnh5getjoj54ke) (uuid 6133c146-48ea-b7a5-0263-fda98e1a30fe) (script /etc/xen/scripts/vif-bridge) (ip 83.170.81.183) (mac 00:16:3e:a4:02:5a) (vifname t2vd5w22msrv5d) (backend 0) ) ) (device (vbd (protocol x86_64-abi) (uuid dd857cd1-2a4c-ea21-a5a5-e95d811f607a) (bootable 1) (dev hda:disk) (uname phy:/dev/9yblt1m70pdtdp/ddfhogyred6bby) (mode w) (backend 0) (bootable 1) (VDI ) ) ) (device (vbd (protocol x86_64-abi) (uuid 19cae15c-354d-77cb-57ec-dc313f1d05ba) (bootable 0) (dev hdb:disk) (uname phy:/dev/9yblt1m70pdtdp/dhnnwhs6jh9kdd) (mode w) (backend 0) (bootable 0) (VDI ) ) ) (device (vbd (protocol x86_64-abi) (uuid 2b97ec8c-0cc5-7197-f510-63c272449680) (bootable 0) (dev hdc:disk) (uname phy:/dev/9yblt1m70pdtdp/d1jilc7s7jxsaq) (mode w) (backend 0) (bootable 0) (VDI ) ) ) (device (vbd (protocol x86_64-abi) (uuid 1b472270-1ef3-2f49-81f1-031cc00c0eb7) (bootable 0) (dev hdd:cdrom) (uname file:/tools/freebsd/boot-freebsd-generic.iso) (mode r) (backend 0) (bootable 0) (VDI ) ) ) (device (vfb (vncunused 1) (vnc 1) (uuid b3defeea-4acc-1408-9b22-71547a64e705) (location 0.0.0.0:5900) ) ) (device (console (protocol vt100) (location 4) (uuid 58a089ce-a4d0-037e-23e8-9df37b2bd5da) ) ) ) DomU from "inside": # uname -a FreeBSD yurak1.vm 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r+03cdadc: Wed = May 22 17:47:40 EEST 2013 = root@yurak1.vm:/usr/obj/data/freebsd/sys/XENHVM amd64 I'll also set up one (hope will have some time) under Xen 4.2.2 = tomorrow. --- Yura On May 13, 2013, at 21:32 PM, Roger Pau Monn=E9 = wrote: > Hello, >=20 > Recently Justin T Gibbs, Will Andrews and myself have been working on > improving the Xen support in FreeBSD. The main goal of this was to = bring > full PVHVM support to FreeBSD, right now FreeBSD is only using PV > interfaces for disk and network interfaces when running as a HVM = guest. > The main benefits of this changes are that Xen virtual interrupts = (event > channels) are now delivered to the guest using a vector callback > injection, that is a per-cpu mechanism that allows each vCPU to have > different interrupts assigned, so for example network and disk > interrupts are delivered to different vCPUs in order to improve > performance. With this changes FreeBSD also uses PV timers when = running > as an HVM guest, which should provide better time keeping and reduce = the > virtualization overhead, since emulated timers are no longer used. PV > IPIs can also be used inside a HVM guest, but this will be implemented > later. >=20 > Right now the code is in a state where it can be tested by users, so = we > would like to encourage FreeBSD and Xen users to test it and provide > feedback. >=20 > The code is available in the following git repository, under the = branch > pvhvm_v5: >=20 > http://xenbits.xen.org/gitweb/?p=3Dpeople/royger/freebsd.git;a=3Dsummary= >=20 > Also, I've created a wiki page that explains how to set up a FreeBSD > PVHVM for testing: >=20 > http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM > _______________________________________________ > 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 Wed May 22 17:20:01 2013 Return-Path: Delivered-To: freebsd-xen@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A4CCD401 for ; Wed, 22 May 2013 17:20:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 976A87E2 for ; Wed, 22 May 2013 17:20:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r4MHK1eg044319 for ; Wed, 22 May 2013 17:20:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r4MHK131044318; Wed, 22 May 2013 17:20:01 GMT (envelope-from gnats) Date: Wed, 22 May 2013 17:20:01 GMT Message-Id: <201305221720.r4MHK131044318@freefall.freebsd.org> To: freebsd-xen@FreeBSD.org Cc: From: dfilter@FreeBSD.ORG (dfilter service) Subject: Re: kern/176471: commit references a PR X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: dfilter service 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, 22 May 2013 17:20:01 -0000 The following reply was made to PR kern/176471; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/176471: commit references a PR Date: Wed, 22 May 2013 17:13:21 +0000 (UTC) Author: gibbs Date: Wed May 22 17:13:03 2013 New Revision: 250913 URL: http://svnweb.freebsd.org/changeset/base/250913 Log: Correct panic on detach of Xen PV network interfaces. dev/xen/netfront: In netif_free(), properly stop the interface and drain any pending timers prior to disconnecting from the backend device. Remove all media and detach our interface object from the system prior to deleting it. PR: kern/176471 Submitted by: Roger Pau Monne Reviewed by: gibbs MFC after: 1 week Modified: head/sys/dev/xen/netfront/netfront.c Modified: head/sys/dev/xen/netfront/netfront.c ============================================================================== --- head/sys/dev/xen/netfront/netfront.c Wed May 22 16:33:28 2013 (r250912) +++ head/sys/dev/xen/netfront/netfront.c Wed May 22 17:13:03 2013 (r250913) @@ -2171,10 +2171,14 @@ netfront_detach(device_t dev) static void netif_free(struct netfront_info *info) { + XN_LOCK(info); + xn_stop(info); + XN_UNLOCK(info); + callout_drain(&info->xn_stat_ch); netif_disconnect_backend(info); -#if 0 - close_netdev(info); -#endif + ifmedia_removeall(&info->sc_media); + ether_ifdetach(info->xn_ifp); + if_free(info->xn_ifp); } static void _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-xen@FreeBSD.ORG Wed May 22 20:04:18 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D3E1BA0A for ; Wed, 22 May 2013 20:04:18 +0000 (UTC) (envelope-from bounces+73574-0602-freebsd-xen=freebsd.org@sendgrid.me) Received: from o3.shared.sendgrid.net (o3.shared.sendgrid.net [208.117.48.85]) by mx1.freebsd.org (Postfix) with SMTP id DD0358BA for ; Wed, 22 May 2013 20:04:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.info; h=from :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpapi; bh=ZJE8v9kiKSxmOtiXJP0nwz fzzlg=; b=uVRCWQzit22/foP/L1irOqPZgxP63c6UwrYcQFVDJBdABTeoD3skoe WyM/0I0JwnNvGES52hnGb80w5gI7Re8a4aBv2/n4H6HiZlmnYwb1EmHpYDb2WG2u SiKaqg1fwW/1J4mGrG7JPNAd+PC6st29ha4um+LlSWsXsvIGyFvUA= Received: by 10.4.35.220 with SMTP id mf8.16697.519D24C01 Wed, 22 May 2013 20:04:16 +0000 (UTC) Received: from mail.tarsnap.com (unknown [10.60.208.17]) by mi23 (SG) with ESMTP id 13ecdd78e5a.6921.191969 for ; Wed, 22 May 2013 15:04:16 -0500 (CST) Received: (qmail 81284 invoked from network); 22 May 2013 20:04:09 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by ec2-107-20-205-189.compute-1.amazonaws.com with ESMTP; 22 May 2013 20:04:09 -0000 Received: (qmail 2862 invoked from network); 22 May 2013 20:03:53 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by clamshell.daemonology.net with SMTP; 22 May 2013 20:03:53 -0000 Message-ID: <519D24A9.3050407@freebsd.org> Date: Wed, 22 May 2013 13:03:53 -0700 From: Colin Percival User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130406 Thunderbird/17.0.5 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= Subject: Re: FreeBSD PVHVM call for testing References: <519131D8.9010307@citrix.com> <51952BAE.6010609@freebsd.org> <51957D42.9060801@citrix.com> <51959ED9.6040405@freebsd.org> <51974EC9.9030204@citrix.com> <5197A1EA.2040404@freebsd.org> <519CAFC7.1070908@citrix.com> In-Reply-To: <519CAFC7.1070908@citrix.com> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 content-transfer-encoding: quoted-printable X-SG-EID: RUbAm5H8PjswBj/QH+sYVehaJogg3iBnZcyVi1bw/IzO9Dd9pXLW3JH+WVePeTTOfyhMKW2Y+dVwZjT4RadfKpYTAEh0F+osL0mFZsefOhvGA587EcehCRXah/7CwtQw Cc: "freebsd-xen@freebsd.org" , xen-devel , "freebsd-virtualization@freebsd.org" , "xen-users@lists.xen.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 May 2013 20:04:18 -0000 On 05/22/13 04:45, Roger Pau Monn=E9 wrote:=0D > On 18/05/13 17:44, Colin Percival wrote:=0D >> That seems to work. dmesg is attached. Are there any particular tests= =0D >> you'd like me to run?=0D > =0D > I have not tested ZFS, that might be a good one. If you are running this= =0D > on Xen 3.4 the behaviour should be the same as without this patches, so= =0D > there shouldn't be many differences.=0D =0D I don't use ZFS personally, so I'm not sure exactly what tests to run on it= ;=0D hopefully someone else can take care of that.=0D =0D > If you could try that on Xen 4.0 at least (if I remember correctly=0D > that's when the vector callback was introduced), you should see the PV=0D > timer getting attached, and a performance increase.=0D =0D Testing on a cr1.8xlarge EC2 instance, I get Xen 4.2, but it ends up with= =0D a panic -- console output below. I can get a backtrace and possibly even= =0D a dump if those would help.=0D =0D Booting [/boot/kernel/kernel]...=0D -\|/-\|GDB: no debug ports present=0D KDB: debugger backends: ddb=0D KDB: current backend: ddb=0D SMAP type=3D01 base=3D0000000000000000 len=3D000000000009e000=0D SMAP type=3D02 base=3D000000000009e000 len=3D0000000000002000=0D SMAP type=3D02 base=3D00000000000e0000 len=3D0000000000020000=0D SMAP type=3D01 base=3D0000000000100000 len=3D00000000eff00000=0D SMAP type=3D02 base=3D00000000fc000000 len=3D0000000004000000=0D SMAP type=3D01 base=3D0000000100000000 len=3D0000003c19000000=0D Table 'FACP' at 0xfc014980=0D Table 'APIC' at 0xfc014a80=0D APIC: Found table at 0xfc014a80=0D APIC: Using the MADT enumerator.=0D MADT: Found CPU APIC ID 0 ACPI ID 0: enabled=0D SMP: Added CPU 0 (AP)=0D MADT: Found CPU APIC ID 2 ACPI ID 1: enabled=0D SMP: Added CPU 2 (AP)=0D MADT: Found CPU APIC ID 4 ACPI ID 2: enabled=0D SMP: Added CPU 4 (AP)=0D MADT: Found CPU APIC ID 6 ACPI ID 3: enabled=0D SMP: Added CPU 6 (AP)=0D MADT: Found CPU APIC ID 8 ACPI ID 4: enabled=0D SMP: Added CPU 8 (AP)=0D MADT: Found CPU APIC ID 10 ACPI ID 5: enabled=0D SMP: Added CPU 10 (AP)=0D MADT: Found CPU APIC ID 12 ACPI ID 6: enabled=0D SMP: Added CPU 12 (AP)=0D MADT: Found CPU APIC ID 14 ACPI ID 7: enabled=0D SMP: Added CPU 14 (AP)=0D MADT: Found CPU APIC ID 32 ACPI ID 8: enabled=0D SMP: Added CPU 32 (AP)=0D MADT: Found CPU APIC ID 34 ACPI ID 9: enabled=0D SMP: Added CPU 34 (AP)=0D MADT: Found CPU APIC ID 36 ACPI ID 10: enabled=0D SMP: Added CPU 36 (AP)=0D MADT: Found CPU APIC ID 38 ACPI ID 11: enabled=0D SMP: Added CPU 38 (AP)=0D MADT: Found CPU APIC ID 40 ACPI ID 12: enabled=0D SMP: Added CPU 40 (AP)=0D MADT: Found CPU APIC ID 42 ACPI ID 13: enabled=0D SMP: Added CPU 42 (AP)=0D MADT: Found CPU APIC ID 44 ACPI ID 14: enabled=0D SMP: Added CPU 44 (AP)=0D MADT: Found CPU APIC ID 46 ACPI ID 15: enabled=0D SMP: Added CPU 46 (AP)=0D MADT: Found CPU APIC ID 1 ACPI ID 16: enabled=0D SMP: Added CPU 1 (AP)=0D MADT: Found CPU APIC ID 3 ACPI ID 17: enabled=0D SMP: Added CPU 3 (AP)=0D MADT: Found CPU APIC ID 5 ACPI ID 18: enabled=0D SMP: Added CPU 5 (AP)=0D MADT: Found CPU APIC ID 7 ACPI ID 19: enabled=0D SMP: Added CPU 7 (AP)=0D MADT: Found CPU APIC ID 9 ACPI ID 20: enabled=0D SMP: Added CPU 9 (AP)=0D MADT: Found CPU APIC ID 11 ACPI ID 21: enabled=0D SMP: Added CPU 11 (AP)=0D MADT: Found CPU APIC ID 13 ACPI ID 22: enabled=0D SMP: Added CPU 13 (AP)=0D MADT: Found CPU APIC ID 15 ACPI ID 23: enabled=0D SMP: Added CPU 15 (AP)=0D MADT: Found CPU APIC ID 33 ACPI ID 24: enabled=0D SMP: Added CPU 33 (AP)=0D MADT: Found CPU APIC ID 35 ACPI ID 25: enabled=0D SMP: Added CPU 35 (AP)=0D MADT: Found CPU APIC ID 37 ACPI ID 26: enabled=0D SMP: Added CPU 37 (AP)=0D MADT: Found CPU APIC ID 39 ACPI ID 27: enabled=0D SMP: Added CPU 39 (AP)=0D MADT: Found CPU APIC ID 41 ACPI ID 28: enabled=0D SMP: Added CPU 41 (AP)=0D MADT: Found CPU APIC ID 43 ACPI ID 29: enabled=0D SMP: Added CPU 43 (AP)=0D MADT: Found CPU APIC ID 45 ACPI ID 30: enabled=0D SMP: Added CPU 45 (AP)=0D MADT: Found CPU APIC ID 47 ACPI ID 31: enabled=0D SMP: Added CPU 47 (AP)=0D MADT: Found CPU APIC ID 0 ACPI ID 32: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 33: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 34: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 35: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 36: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 37: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 38: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 39: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 40: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 41: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 42: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 43: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 44: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 45: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 46: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 47: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 48: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 49: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 50: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 51: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 52: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 53: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 54: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 55: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 56: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 57: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 58: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 59: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 60: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 61: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 62: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 63: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 64: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 65: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 66: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 67: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 68: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 69: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 70: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 71: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 72: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 73: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 74: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 75: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 76: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 77: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 78: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 79: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 80: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 81: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 82: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 83: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 84: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 85: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 86: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 87: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 88: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 89: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 90: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 91: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 92: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 93: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 94: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 95: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 96: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 97: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 98: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 99: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 100: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 101: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 102: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 103: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 104: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 105: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 106: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 107: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 108: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 109: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 110: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 111: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 112: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 113: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 114: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 115: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 116: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 117: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 118: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 119: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 120: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 121: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 122: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 123: disabled MADT: Found CPU APIC ID 0 ACPI ID 124: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 125: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 126: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 127: disabled=0D Copyright (c) 1992-2013 The FreeBSD Project.=0D Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994=0D The Regents of the University of California. All rights reserved.=0D FreeBSD is a registered trademark of The FreeBSD Foundation.=0D FreeBSD 10.0-CURRENT #0 r+9b25356: Sat May 18 14:46:16 UTC 2013=0D root@ip-10-140-132-115:/usr/obj/usr/src/sys/XENHVM amd64=0D FreeBSD clang version 3.3 (trunk 178860) 20130405=0D WARNING: WITNESS option enabled, expect reduced performance.=0D XEN: Hypervisor version 4.2 detected.=0D XEN: Disabling emulated block and network devices=0D Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff81912000.=0D Hypervisor: Origin =3D "XenVMMXenVMM"=0D Calibrating TSC clock ... TSC clock: 2600048761 Hz=0D CPU: Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz (2600.05-MHz K8-class CPU)=0D Origin =3D "GenuineIntel" Id =3D 0x206d7 Family =3D 0x6 Model =3D 0x2d= Stepping =3D 7=0D =0D Features=3D0x1783fbff=0D =0D Features2=3D0x9fba2203=0D AMD Features=3D0x28100800=0D AMD Features2=3D0x1=0D real memory =3D 262144000000 (250000 MB)=0D Physical memory chunk(s):=0D 0x0000000000001000 - 0x0000000000099fff, 626688 bytes (153 pages)=0D 0x0000000000100000 - 0x00000000001fffff, 1048576 bytes (256 pages)=0D 0x0000000001a2a000 - 0x00000000efffffff, 3999096832 bytes (976342 pages)=0D 0x0000000100000000 - 0x0000003b8ae37fff, 251438268416 bytes (61386296 pages= )=0D avail memory =3D 244393709568 (233072 MB)=0D Event timer "LAPIC" quality 400=0D ACPI APIC Table: =0D INTR: Adding local APIC 1 as a target=0D INTR: Adding local APIC 2 as a target=0D INTR: Adding local APIC 3 as a target=0D INTR: Adding local APIC 4 as a target=0D INTR: Adding local APIC 5 as a target=0D INTR: Adding local APIC 6 as a target=0D INTR: Adding local APIC 7 as a target=0D INTR: Adding local APIC 8 as a target=0D INTR: Adding local APIC 9 as a target=0D INTR: Adding local APIC 10 as a target=0D INTR: Adding local APIC 11 as a target=0D INTR: Adding local APIC 12 as a target=0D INTR: Adding local APIC 13 as a target=0D INTR: Adding local APIC 14 as a target=0D INTR: Adding local APIC 15 as a target=0D INTR: Adding local APIC 32 as a target=0D INTR: Adding local APIC 33 as a target=0D INTR: Adding local APIC 34 as a target=0D INTR: Adding local APIC 35 as a target=0D INTR: Adding local APIC 36 as a target=0D INTR: Adding local APIC 37 as a target=0D INTR: Adding local APIC 38 as a target=0D INTR: Adding local APIC 39 as a target=0D INTR: Adding local APIC 40 as a target=0D INTR: Adding local APIC 41 as a target=0D INTR: Adding local APIC 42 as a target=0D INTR: Adding local APIC 43 as a target=0D INTR: Adding local APIC 44 as a target=0D INTR: Adding local APIC 45 as a target=0D INTR: Adding local APIC 46 as a target=0D INTR: Adding local APIC 47 as a target=0D FreeBSD/SMP: Multiprocessor System Detected: 32 CPUs=0D FreeBSD/SMP: 2 package(s) x 8 core(s) x 2 SMT threads=0D cpu0 (BSP): APIC ID: 0=0D cpu1 (AP): APIC ID: 1=0D cpu2 (AP): APIC ID: 2=0D cpu3 (AP): APIC ID: 3=0D cpu4 (AP): APIC ID: 4=0D cpu5 (AP): APIC ID: 5=0D cpu6 (AP): APIC ID: 6=0D cpu7 (AP): APIC ID: 7=0D cpu8 (AP): APIC ID: 8=0D cpu9 (AP): APIC ID: 9=0D cpu10 (AP): APIC ID: 10=0D cpu11 (AP): APIC ID: 11=0D cpu12 (AP): APIC ID: 12=0D cpu13 (AP): APIC ID: 13=0D cpu14 (AP): APIC ID: 14=0D cpu15 (AP): APIC ID: 15=0D cpu16 (AP): APIC ID: 32=0D cpu17 (AP): APIC ID: 33=0D cpu18 (AP): APIC ID: 34=0D cpu19 (AP): APIC ID: 35=0D cpu20 (AP): APIC ID: 36=0D cpu21 (AP): APIC ID: 37=0D cpu22 (AP): APIC ID: 38=0D cpu23 (AP): APIC ID: 39=0D cpu24 (AP): APIC ID: 40=0D cpu25 (AP): APIC ID: 41=0D cpu26 (AP): APIC ID: 42=0D cpu27 (AP): APIC ID: 43=0D cpu28 (AP): APIC ID: 44=0D cpu29 (AP): APIC ID: 45=0D cpu30 (AP): APIC ID: 46=0D cpu31 (AP): APIC ID: 47=0D x86bios: IVT 0x000000-0x0004ff at 0xfffffe0000000000=0D x86bios: SSEG 0x001000-0x001fff at 0xffffff80005e3000=0D x86bios: EBDA 0x09f000-0x09ffff at 0xfffffe000009f000=0D x86bios: ROM 0x0a0000-0x0fefff at 0xfffffe00000a0000=0D APIC: CPU 0 has ACPI ID 0=0D APIC: CPU 1 has ACPI ID 16=0D APIC: CPU 2 has ACPI ID 1=0D APIC: CPU 3 has ACPI ID 17=0D APIC: CPU 4 has ACPI ID 2=0D APIC: CPU 5 has ACPI ID 18=0D APIC: CPU 6 has ACPI ID 3=0D APIC: CPU 7 has ACPI ID 19=0D APIC: CPU 8 has ACPI ID 4=0D APIC: CPU 9 has ACPI ID 20=0D APIC: CPU 10 has ACPI ID 5=0D APIC: CPU 11 has ACPI ID 21=0D APIC: CPU 12 has ACPI ID 6=0D APIC: CPU 13 has ACPI ID 22=0D APIC: CPU 14 has ACPI ID 7=0D APIC: CPU 15 has ACPI ID 23=0D APIC: CPU 16 has ACPI ID 8=0D APIC: CPU 17 has ACPI ID 24=0D APIC: CPU 18 has ACPI ID 9=0D APIC: CPU 19 has ACPI ID 25=0D APIC: CPU 20 has ACPI ID 10=0D APIC: CPU 21 has ACPI ID 26=0D APIC: CPU 22 has ACPI ID 11=0D APIC: CPU 23 has ACPI ID 27=0D APIC: CPU 24 has ACPI ID 12=0D APIC: CPU 25 has ACPI ID 28=0D APIC: CPU 26 has ACPI ID 13=0D APIC: CPU 27 has ACPI ID 29=0D APIC: CPU 28 has ACPI ID 14=0D APIC: CPU 29 has ACPI ID 30=0D APIC: CPU 30 has ACPI ID 15=0D APIC: CPU 31 has ACPI ID 31=0D random device not loaded; using insecure entropy=0D ULE: setup cpu 0=0D ULE: setup cpu 1=0D ULE: setup cpu 2=0D ULE: setup cpu 3=0D ULE: setup cpu 4=0D ULE: setup cpu 5=0D ULE: setup cpu 6=0D ULE: setup cpu 7=0D ULE: setup cpu 8=0D ULE: setup cpu 9=0D ULE: setup cpu 10=0D ULE: setup cpu 11=0D ULE: setup cpu 12=0D ULE: setup cpu 13=0D ULE: setup cpu 14=0D ULE: setup cpu 15=0D ULE: setup cpu 16=0D ULE: setup cpu 17=0D ULE: setup cpu 18=0D ULE: setup cpu 19=0D ULE: setup cpu 20=0D ULE: setup cpu 21=0D ULE: setup cpu 22=0D ULE: setup cpu 23=0D ULE: setup cpu 24=0D ULE: setup cpu 25=0D ULE: setup cpu 26=0D ULE: setup cpu 27=0D ULE: setup cpu 28=0D ULE: setup cpu 29=0D ULE: setup cpu 30=0D ULE: setup cpu 31=0D ACPI: RSDP 0xea020 00024 (v02 Xen)=0D ACPI: XSDT 0xfc015920 0005C (v01 Xen HVM 00000000 HVML 00000000)=0D ACPI: FACP 0xfc014980 000F4 (v04 Xen HVM 00000000 HVML 00000000)=0D ACPI: DSDT 0xfc0035e0 11315 (v02 Xen HVM 00000000 INTL 20090123)=0D ACPI: FACS 0xfc0035a0 00040=0D ACPI: APIC 0xfc014a80 00460 (v02 Xen HVM 00000000 HVML 00000000)=0D ACPI: SRAT 0xfc014f60 008A8 (v01 Xen HVM 00000000 HVML 00000000)=0D ACPI: HPET 0xfc015830 00038 (v01 Xen HVM 00000000 HVML 00000000)=0D ACPI: WAET 0xfc015870 00028 (v01 Xen HVM 00000000 HVML 00000000)=0D ACPI: SSDT 0xfc0158a0 00031 (v02 Xen HVM 00000000 INTL 20090123)=0D ACPI: SSDT 0xfc0158e0 00031 (v02 Xen HVM 00000000 INTL 20090123)=0D MADT: Found IO APIC ID 1, Interrupt 0 at 0xfec00000=0D ioapic0: Changing APIC ID to 1=0D ioapic0: Routing external 8259A's -> intpin 0=0D MADT: Interrupt override: source 0, irq 2=0D ioapic0: Routing IRQ 0 -> intpin 2=0D MADT: Interrupt override: source 5, irq 5=0D ioapic0: intpin 5 trigger: level=0D ioapic0: intpin 5 polarity: low=0D MADT: Interrupt override: source 10, irq 10=0D ioapic0: intpin 10 trigger: level=0D ioapic0: intpin 10 polarity: low=0D MADT: Interrupt override: source 11, irq 11=0D ioapic0: intpin 11 trigger: level=0D ioapic0: intpin 11 polarity: low=0D MADT: Forcing active-low polarity and level trigger for SCI=0D ioapic0: intpin 9 polarity: low=0D ioapic0: intpin 9 trigger: level=0D ioapic0 irqs 0-47 on motherboard=0D cpu0 BSP:=0D ID: 0x00000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D Event-channel device installed.=0D snd_unit_init() u=3D0x00ff8000 [512] d=3D0x00007c00 [32] c=3D0x000003ff [10= 24]=0D feeder_register: snd_unit=3D-1 snd_maxautovchans=3D16 latency=3D5 feeder_ra= te_min=3D1=0D feeder_rate_max=3D2016000 feeder_rate_round=3D25=0D wlan: <802.11 Link Layer>=0D null: =0D nfslock: pseudo-device=0D random: =0D VESA: INT 0x10 vector 0xc000:0x836e=0D VESA: information block=0D 0000 56 45 53 41 00 02 f5 82 00 c0 00 00 00 00 40 00=0D 0010 00 02 40 00 00 01 f5 82 00 c0 f5 82 00 c0 0e 83=0D 0020 00 c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0040 01 01 10 01 11 01 12 01 03 01 13 01 14 01 15 01=0D 0050 05 01 16 01 17 01 18 01 07 01 19 01 1a 01 ff ff 0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 00c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 00d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 00e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 00f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0110 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0120 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0130 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0140 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0150 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0160 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0170 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0180 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0190 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 01a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 01b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 01c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 01d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 01e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 01f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D VESA: 15 mode(s) found=0D VESA: v2.0, 4096k memory, flags:0x0, mode table:0xffffff80005fd040 (2000040= )=0D VESA: VGABIOS Cirrus extension=0D VESA: VGABIOS Cirrus extension VGABIOS Cirrus extension 1.0=0D io: =0D kbd: new array size 4=0D kbd1 at kbdmux0=0D mem: =0D hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2=0D hpt27xx: RocketRAID 27xx controller driver v1.0=0D xen_et0: on motherboard=0D Event timer "XENTIMER" frequency 1000000000 Hz quality 950=0D Timecounter "XENTIMER" frequency 1000000000 Hz quality 950=0D xen_et0: registered as a time-of-day clock (resolution 10000000us, adjustme= nt=0D 5.000000000s)=0D acpi0: on motherboard=0D ACPI: All ACPI Tables successfully acquired=0D ioapic0: routing intpin 9 (ISA IRQ 9) to lapic 0 vector 48=0D acpi0: Power Button (fixed)=0D acpi0: Sleep Button (fixed)=0D acpi0: reservation of 0, a0000 (3) failed=0D cpu0: Processor \_SB_.PR00 (ACPI ID 0) -> APIC ID 0=0D cpu0: on acpi0=0D cpu0: switching to generic Cx mode=0D cpu1: Processor \_SB_.PR01 (ACPI ID 1) -> APIC ID 2=0D cpu1: on acpi0=0D cpu2: Processor \_SB_.PR02 (ACPI ID 2) -> APIC ID 4=0D cpu2: on acpi0=0D cpu3: Processor \_SB_.PR03 (ACPI ID 3) -> APIC ID 6=0D cpu3: on acpi0=0D cpu4: Processor \_SB_.PR04 (ACPI ID 4) -> APIC ID 8=0D cpu4: on acpi0=0D cpu5: Processor \_SB_.PR05 (ACPI ID 5) -> APIC ID 10=0D cpu5: on acpi0=0D cpu6: Processor \_SB_.PR06 (ACPI ID 6) -> APIC ID 12=0D cpu6: on acpi0=0D cpu7: Processor \_SB_.PR07 (ACPI ID 7) -> APIC ID 14=0D cpu7: on acpi0=0D cpu8: Processor \_SB_.PR08 (ACPI ID 8) -> APIC ID 16=0D cpu8: on acpi0=0D cpu9: Processor \_SB_.PR09 (ACPI ID 9) -> APIC ID 18=0D cpu9: on acpi0=0D cpu10: Processor \_SB_.PR0A (ACPI ID 10) -> APIC ID 20=0D cpu10: on acpi0=0D cpu11: Processor \_SB_.PR0B (ACPI ID 11) -> APIC ID 22=0D cpu11: on acpi0=0D cpu12: Processor \_SB_.PR0C (ACPI ID 12) -> APIC ID 24=0D cpu12: on acpi0=0D cpu13: Processor \_SB_.PR0D (ACPI ID 13) -> APIC ID 26=0D cpu13: on acpi0=0D cpu14: Processor \_SB_.PR0E (ACPI ID 14) -> APIC ID 28=0D cpu14: on acpi0=0D cpu15: Processor \_SB_.PR0F (ACPI ID 15) -> APIC ID 30=0D cpu15: on acpi0=0D cpu16: Processor \_SB_.PR10 (ACPI ID 16) -> APIC ID 1=0D cpu16: on acpi0=0D cpu17: Processor \_SB_.PR11 (ACPI ID 17) -> APIC ID 3=0D cpu17: on acpi0=0D cpu18: Processor \_SB_.PR12 (ACPI ID 18) -> APIC ID 5=0D cpu18: on acpi0=0D cpu19: Processor \_SB_.PR13 (ACPI ID 19) -> APIC ID 7=0D cpu19: on acpi0=0D cpu20: Processor \_SB_.PR14 (ACPI ID 20) -> APIC ID 9=0D cpu20: on acpi0=0D cpu21: Processor \_SB_.PR15 (ACPI ID 21) -> APIC ID 11=0D cpu21: on acpi0=0D cpu22: Processor \_SB_.PR16 (ACPI ID 22) -> APIC ID 13=0D cpu22: on acpi0=0D cpu23: Processor \_SB_.PR17 (ACPI ID 23) -> APIC ID 15=0D cpu23: on acpi0=0D cpu24: Processor \_SB_.PR18 (ACPI ID 24) -> APIC ID 17=0D cpu24: on acpi0=0D cpu25: Processor \_SB_.PR19 (ACPI ID 25) -> APIC ID 19=0D cpu25: on acpi0=0D cpu26: Processor \_SB_.PR1A (ACPI ID 26) -> APIC ID 21=0D cpu26: on acpi0=0D cpu27: Processor \_SB_.PR1B (ACPI ID 27) -> APIC ID 23=0D cpu27: on acpi0=0D cpu28: Processor \_SB_.PR1C (ACPI ID 28) -> APIC ID 25=0D cpu28: on acpi0=0D cpu29: Processor \_SB_.PR1D (ACPI ID 29) -> APIC ID 27=0D cpu29: on acpi0=0D cpu30: Processor \_SB_.PR1E (ACPI ID 30) -> APIC ID 29=0D cpu30: on acpi0=0D cpu31: Processor \_SB_.PR1F (ACPI ID 31) -> APIC ID 31=0D cpu31: on acpi0=0D ACPI: Processor \_SB_.PR20 (ACPI ID 32) ignored=0D ACPI: Processor \_SB_.PR21 (ACPI ID 33) ignored=0D ACPI: Processor \_SB_.PR22 (ACPI ID 34) ignored=0D ACPI: Processor \_SB_.PR23 (ACPI ID 35) ignored=0D ACPI: Processor \_SB_.PR24 (ACPI ID 36) ignored=0D ACPI: Processor \_SB_.PR25 (ACPI ID 37) ignored=0D ACPI: Processor \_SB_.PR26 (ACPI ID 38) ignored=0D ACPI: Processor \_SB_.PR27 (ACPI ID 39) ignored=0D ACPI: Processor \_SB_.PR28 (ACPI ID 40) ignored=0D ACPI: Processor \_SB_.PR29 (ACPI ID 41) ignored=0D ACPI: Processor \_SB_.PR2A (ACPI ID 42) ignored=0D ACPI: Processor \_SB_.PR2B (ACPI ID 43) ignored=0D ACPI: Processor \_SB_.PR2C (ACPI ID 44) ignored=0D ACPI: Processor \_SB_.PR2D (ACPI ID 45) ignored=0D ACPI: Processor \_SB_.PR2E (ACPI ID 46) ignored=0D ACPI: Processor \_SB_.PR2F (ACPI ID 47) ignored=0D ACPI: Processor \_SB_.PR30 (ACPI ID 48) ignored=0D ACPI: Processor \_SB_.PR31 (ACPI ID 49) ignored=0D ACPI: Processor \_SB_.PR32 (ACPI ID 50) ignored=0D ACPI: Processor \_SB_.PR33 (ACPI ID 51) ignored=0D ACPI: Processor \_SB_.PR34 (ACPI ID 52) ignored=0D ACPI: Processor \_SB_.PR35 (ACPI ID 53) ignored=0D ACPI: Processor \_SB_.PR36 (ACPI ID 54) ignored=0D ACPI: Processor \_SB_.PR37 (ACPI ID 55) ignored=0D ACPI: Processor \_SB_.PR38 (ACPI ID 56) ignored=0D ACPI: Processor \_SB_.PR39 (ACPI ID 57) ignored=0D ACPI: Processor \_SB_.PR3A (ACPI ID 58) ignored=0D ACPI: Processor \_SB_.PR3B (ACPI ID 59) ignored=0D ACPI: Processor \_SB_.PR3C (ACPI ID 60) ignored=0D ACPI: Processor \_SB_.PR3D (ACPI ID 61) ignored=0D ACPI: Processor \_SB_.PR3E (ACPI ID 62) ignored=0D ACPI: Processor \_SB_.PR3F (ACPI ID 63) ignored=0D ACPI: Processor \_SB_.PR40 (ACPI ID 64) ignored=0D ACPI: Processor \_SB_.PR41 (ACPI ID 65) ignored=0D ACPI: Processor \_SB_.PR42 (ACPI ID 66) ignored=0D ACPI: Processor \_SB_.PR43 (ACPI ID 67) ignored=0D ACPI: Processor \_SB_.PR44 (ACPI ID 68) ignored=0D ACPI: Processor \_SB_.PR45 (ACPI ID 69) ignored=0D ACPI: Processor \_SB_.PR46 (ACPI ID 70) ignored=0D ACPI: Processor \_SB_.PR47 (ACPI ID 71) ignored=0D ACPI: Processor \_SB_.PR48 (ACPI ID 72) ignored=0D ACPI: Processor \_SB_.PR49 (ACPI ID 73) ignored=0D ACPI: Processor \_SB_.PR4A (ACPI ID 74) ignored=0D ACPI: Processor \_SB_.PR4B (ACPI ID 75) ignored=0D ACPI: Processor \_SB_.PR4C (ACPI ID 76) ignored=0D ACPI: Processor \_SB_.PR4D (ACPI ID 77) ignored=0D ACPI: Processor \_SB_.PR4E (ACPI ID 78) ignored=0D ACPI: Processor \_SB_.PR4F (ACPI ID 79) ignored=0D ACPI: Processor \_SB_.PR50 (ACPI ID 80) ignored=0D ACPI: Processor \_SB_.PR51 (ACPI ID 81) ignored=0D ACPI: Processor \_SB_.PR52 (ACPI ID 82) ignored=0D ACPI: Processor \_SB_.PR53 (ACPI ID 83) ignored=0D ACPI: Processor \_SB_.PR54 (ACPI ID 84) ignored=0D ACPI: Processor \_SB_.PR55 (ACPI ID 85) ignored=0D ACPI: Processor \_SB_.PR56 (ACPI ID 86) ignored=0D ACPI: Processor \_SB_.PR57 (ACPI ID 87) ignored=0D ACPI: Processor \_SB_.PR58 (ACPI ID 88) ignored=0D ACPI: Processor \_SB_.PR59 (ACPI ID 89) ignored=0D ACPI: Processor \_SB_.PR5A (ACPI ID 90) ignored=0D ACPI: Processor \_SB_.PR5B (ACPI ID 91) ignored=0D ACPI: Processor \_SB_.PR5C (ACPI ID 92) ignored=0D ACPI: Processor \_SB_.PR5D (ACPI ID 93) ignored=0D ACPI: Processor \_SB_.PR5E (ACPI ID 94) ignored=0D ACPI: Processor \_SB_.PR5F (ACPI ID 95) ignored=0D ACPI: Processor \_SB_.PR60 (ACPI ID 96) ignored=0D ACPI: Processor \_SB_.PR61 (ACPI ID 97) ignored ACPI: Processor \_SB_.PR62 (ACPI ID 98) ignored=0D ACPI: Processor \_SB_.PR63 (ACPI ID 99) ignored=0D ACPI: Processor \_SB_.PR64 (ACPI ID 100) ignored=0D ACPI: Processor \_SB_.PR65 (ACPI ID 101) ignored=0D ACPI: Processor \_SB_.PR66 (ACPI ID 102) ignored=0D ACPI: Processor \_SB_.PR67 (ACPI ID 103) ignored=0D ACPI: Processor \_SB_.PR68 (ACPI ID 104) ignored=0D ACPI: Processor \_SB_.PR69 (ACPI ID 105) ignored=0D ACPI: Processor \_SB_.PR6A (ACPI ID 106) ignored=0D ACPI: Processor \_SB_.PR6B (ACPI ID 107) ignored=0D ACPI: Processor \_SB_.PR6C (ACPI ID 108) ignored=0D ACPI: Processor \_SB_.PR6D (ACPI ID 109) ignored=0D ACPI: Processor \_SB_.PR6E (ACPI ID 110) ignored=0D ACPI: Processor \_SB_.PR6F (ACPI ID 111) ignored=0D ACPI: Processor \_SB_.PR70 (ACPI ID 112) ignored=0D ACPI: Processor \_SB_.PR71 (ACPI ID 113) ignored=0D ACPI: Processor \_SB_.PR72 (ACPI ID 114) ignored=0D ACPI: Processor \_SB_.PR73 (ACPI ID 115) ignored=0D ACPI: Processor \_SB_.PR74 (ACPI ID 116) ignored=0D ACPI: Processor \_SB_.PR75 (ACPI ID 117) ignored=0D ACPI: Processor \_SB_.PR76 (ACPI ID 118) ignored=0D ACPI: Processor \_SB_.PR77 (ACPI ID 119) ignored=0D ACPI: Processor \_SB_.PR78 (ACPI ID 120) ignored=0D ACPI: Processor \_SB_.PR79 (ACPI ID 121) ignored=0D ACPI: Processor \_SB_.PR7A (ACPI ID 122) ignored=0D ACPI: Processor \_SB_.PR7B (ACPI ID 123) ignored=0D ACPI: Processor \_SB_.PR7C (ACPI ID 124) ignored=0D ACPI: Processor \_SB_.PR7D (ACPI ID 125) ignored=0D ACPI: Processor \_SB_.PR7E (ACPI ID 126) ignored=0D ACPI: Processor \_SB_.PR7F (ACPI ID 127) ignored=0D hpet0: iomem 0xfed00000-0xfed003ff on acpi0=0D hpet0: vendor 0x8086, rev 0x1, 62500000Hz 64bit, 3 timers, legacy route=0D hpet0: t0: irqs 0x00f00000 (0), 64bit, periodic=0D hpet0: t1: irqs 0x00f00000 (0), 64bit, periodic=0D hpet0: t2: irqs 0x00f00000 (0), 64bit, periodic=0D Timecounter "HPET" frequency 62500000 Hz quality 950=0D attimer0: port 0x40-0x43 irq 0 on acpi0=0D Timecounter "i8254" frequency 1193182 Hz quality 0=0D ioapic0: routing intpin 2 (ISA IRQ 0) to lapic 0 vector 49=0D Event timer "i8254" frequency 1193182 Hz quality 100=0D atrtc0: port 0x70-0x71 irq 8 on acpi0=0D atrtc0: not installed as time-of-day clock: clock xen_et has higher resolut= ion=0D ioapic0: routing intpin 8 (ISA IRQ 8) to lapic 0 vector 50=0D Event timer "RTC" frequency 32768 Hz quality 0=0D ACPI timer: 1/18 1/17 1/21 1/18 1/18 1/16 1/20 1/22 1/21 1/22 -> 10=0D Timecounter "ACPI-fast" frequency 3579545 Hz quality 900=0D acpi_timer0: <32-bit timer at 3.579545MHz> port 0xb008-0xb00b on acpi0=0D pci_link0: Index IRQ Rtd Ref IRQs=0D Initial Probe 0 5 N 0 5 10 11=0D Validation 0 5 N 0 5 10 11=0D After Disable 0 255 N 0 5 10 11=0D pci_link1: Index IRQ Rtd Ref IRQs=0D Initial Probe 0 10 N 0 5 10 11=0D Validation 0 10 N 0 5 10 11=0D After Disable 0 255 N 0 5 10 11=0D pci_link2: Index IRQ Rtd Ref IRQs=0D Initial Probe 0 11 N 0 5 10 11=0D Validation 0 11 N 0 5 10 11=0D After Disable 0 255 N 0 5 10 11=0D pci_link3: Index IRQ Rtd Ref IRQs=0D Initial Probe 0 5 N 0 5 10 11=0D Validation 0 5 N 0 5 10 11=0D After Disable 0 255 N 0 5 10 11=0D pcib0: port 0xcf8-0xcff on acpi0=0D pcib0: decoding 4 range 0-0xcf7=0D pcib0: decoding 4 range 0xd00-0xffff=0D pcib0: decoding 3 range 0xa0000-0xbffff=0D pcib0: decoding 3 range 0xf0000000-0xfbffffff=0D pci0: on pcib0=0D pci0: domain=3D0, physical bus=3D0=0D found-> vendor=3D0x8086, dev=3D0x1237, revid=3D0x02=0D domain=3D0, bus=3D0, slot=3D0, func=3D0=0D class=3D06-00-00, hdrtype=3D0x00, mfdev=3D0=0D cmdreg=3D0x0004, statreg=3D0x0000, cachelnsz=3D0 (dwords)=0D lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns)=0D found-> vendor=3D0x8086, dev=3D0x7000, revid=3D0x00=0D domain=3D0, bus=3D0, slot=3D1, func=3D0=0D class=3D06-01-00, hdrtype=3D0x00, mfdev=3D1=0D cmdreg=3D0x0007, statreg=3D0x0200, cachelnsz=3D0 (dwords)=0D lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns)=0D found-> vendor=3D0x8086, dev=3D0x7010, revid=3D0x00=0D domain=3D0, bus=3D0, slot=3D1, func=3D1=0D class=3D01-01-80, hdrtype=3D0x00, mfdev=3D0=0D cmdreg=3D0x0005, statreg=3D0x0280, cachelnsz=3D0 (dwords)=0D lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns)=0D pcib0: allocated type 4 (0x1f0-0x1f7) for rid 10 of pci0:0:1:1=0D pcib0: allocated type 4 (0x3f6-0x3f6) for rid 14 of pci0:0:1:1=0D pcib0: allocated type 4 (0x170-0x177) for rid 18 of pci0:0:1:1=0D pcib0: allocated type 4 (0x376-0x376) for rid 1c of pci0:0:1:1=0D map[20]: type I/O Port, range 32, base 0xc100, size 4, enabled=0D pcib0: allocated type 4 (0xc100-0xc10f) for rid 20 of pci0:0:1:1=0D found-> vendor=3D0x8086, dev=3D0x7113, revid=3D0x01=0D domain=3D0, bus=3D0, slot=3D1, func=3D3=0D class=3D06-80-00, hdrtype=3D0x00, mfdev=3D0=0D cmdreg=3D0x0004, statreg=3D0x0000, cachelnsz=3D0 (dwords)=0D lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns)=0D intpin=3Da, irq=3D10=0D pcib0: matched entry for 0.1.INTA=0D pcib0: slot 1 INTA hardwired to IRQ 20=0D found-> vendor=3D0x1013, dev=3D0x00b8, revid=3D0x00=0D domain=3D0, bus=3D0, slot=3D2, func=3D0=0D class=3D03-00-00, hdrtype=3D0x00, mfdev=3D0=0D cmdreg=3D0x0007, statreg=3D0x0000, cachelnsz=3D0 (dwords)=0D lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns)=0D map[10]: type Prefetchable Memory, range 32, base 0xf0000000, size 25, ena= bled=0D pcib0: allocated type 3 (0xf0000000-0xf1ffffff) for rid 10 of pci0:0:2:0=0D map[14]: type Memory, range 32, base 0xf3000000, size 12, enabled=0D pcib0: allocated type 3 (0xf3000000-0xf3000fff) for rid 14 of pci0:0:2:0=0D found-> vendor=3D0x5853, dev=3D0x0001, revid=3D0x01=0D domain=3D0, bus=3D0, slot=3D3, func=3D0=0D class=3Dff-80-00, hdrtype=3D0x00, mfdev=3D0=0D cmdreg=3D0x0007, statreg=3D0x0000, cachelnsz=3D0 (dwords)=0D lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns)=0D intpin=3Da, irq=3D5=0D map[10]: type I/O Port, range 32, base 0xc000, size 8, enabled=0D pcib0: allocated type 4 (0xc000-0xc0ff) for rid 10 of pci0:0:3:0=0D map[14]: type Prefetchable Memory, range 32, base 0xf2000000, size 24, ena= bled=0D pcib0: allocated type 3 (0xf2000000-0xf2ffffff) for rid 14 of pci0:0:3:0=0D pcib0: matched entry for 0.3.INTA=0D pcib0: slot 3 INTA hardwired to IRQ 28=0D isab0: at device 1.0 on pci0=0D isa0: on isab0=0D atapci0: port=0D 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc100-0xc10f at device 1.1 on pci0=0D ata0: at channel 0 on atapci0=0D ioapic0: routing intpin 14 (ISA IRQ 14) to lapic 0 vector 51=0D ata1: at channel 1 on atapci0=0D ioapic0: routing intpin 15 (ISA IRQ 15) to lapic 0 vector 52=0D pci0: at device 1.3 (no driver attached)=0D vgapci0: mem=0D 0xf0000000-0xf1ffffff,0xf3000000-0xf3000fff at device 2.0 on pci0=0D xenpci0: port 0xc000-0xc0ff mem 0xf2000000-0xf2ffffff= irq=0D 28 at device 3.0 on pci0=0D ioapic0: routing intpin 28 (PCI IRQ 28) to lapic 0 vector 53=0D xenstore0: on xenpci0=0D Grant table initialized=0D psmcpnp0: irq 12 on acpi0=0D atkbdc0: port 0x60,0x64 irq 1 on acpi0=0D atkbd0: irq 1 on atkbdc0=0D atkbd: the current kbd controller command byte 0061=0D atkbd: keyboard ID 0x41ab (2)=0D kbdc: RESET_KBD return code:00fa=0D kbdc: RESET_KBD status:00aa=0D kbd0 at atkbd0=0D kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x1d0000=0D ioapic0: routing intpin 1 (ISA IRQ 1) to lapic 0 vector 54=0D atkbd0: [GIANT-LOCKED]=0D psm0: current command byte:0061=0D kbdc: TEST_AUX_PORT status:0000=0D kbdc: RESET_AUX return code:00fa=0D kbdc: RESET_AUX status:00aa=0D kbdc: RESET_AUX ID:0000=0D kbdc: RESET_AUX return code:00fa=0D kbdc: RESET_AUX status:00aa=0D kbdc: RESET_AUX ID:0000=0D psm: status 00 02 64=0D psm: status 00 00 64=0D psm: status 00 03 64=0D psm: status 00 03 64=0D psm: data 08 00 00=0D psm: status 00 02 64=0D psm0: irq 12 on atkbdc0=0D ioapic0: routing intpin 12 (ISA IRQ 12) to lapic 0 vector 55=0D psm0: [GIANT-LOCKED]=0D psm0: model IntelliMouse Explorer, device ID 4-00, 5 buttons=0D psm0: config:00000000, flags:00000008, packet size:4=0D psm0: syncmask:08, syncbits:00=0D fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0= =0D fdc0: does not respond=0D device_attach: fdc0 attach returned 6=0D uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 ioapic0: routing intpin 4 (ISA IRQ 4) to lapic 0 vector 56=0D uart0: fast interrupt=0D uart0: console (9600,n,8,1)=0D ACPI: Enabled 2 GPEs in block 00 to 0F=0D acpi0: wakeup code va 0xffffffc2cdff7000 pa 0x4000=0D ex_isa_identify()=0D pcib0: allocated type 3 (0xa0000-0xa07ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa0800-0xa0fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa1000-0xa17ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa1800-0xa1fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa2000-0xa27ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa2800-0xa2fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa3000-0xa37ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa3800-0xa3fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa4000-0xa47ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa4800-0xa4fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa5000-0xa57ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa5800-0xa5fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa6000-0xa67ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa6800-0xa6fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa7000-0xa77ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa7800-0xa7fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa8000-0xa87ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa8800-0xa8fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa9000-0xa97ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa9800-0xa9fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xaa000-0xaa7ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xaa800-0xaafff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xab000-0xab7ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xab800-0xabfff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xac000-0xac7ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xac800-0xacfff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xad000-0xad7ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xad800-0xadfff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xae000-0xae7ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xae800-0xaefff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xaf000-0xaf7ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xaf800-0xaffff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb0000-0xb07ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb0800-0xb0fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb1000-0xb17ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb1800-0xb1fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb2000-0xb27ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb2800-0xb2fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb3000-0xb37ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb3800-0xb3fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb4000-0xb47ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb4800-0xb4fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb5000-0xb57ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb5800-0xb5fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb6000-0xb67ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb6800-0xb6fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb7000-0xb77ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb7800-0xb7fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb8000-0xb87ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb8800-0xb8fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb9000-0xb97ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb9800-0xb9fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xba000-0xba7ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xba800-0xbafff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xbb000-0xbb7ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xbb800-0xbbfff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xbc000-0xbc7ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xbc800-0xbcfff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xbd000-0xbd7ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xbd800-0xbdfff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xbe000-0xbe7ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xbe800-0xbefff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xbf000-0xbf7ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xbf800-0xbffff) for rid 0 of orm0=0D ahc_isa_identify 0: ioport 0xc00 alloc failed=0D ahc_isa_identify 1: ioport 0x1c00 alloc failed=0D ahc_isa_identify 2: ioport 0x2c00 alloc failed=0D ahc_isa_identify 3: ioport 0x3c00 alloc failed=0D ahc_isa_identify 4: ioport 0x4c00 alloc failed=0D ahc_isa_identify 5: ioport 0x5c00 alloc failed=0D ahc_isa_identify 6: ioport 0x6c00 alloc failed=0D ahc_isa_identify 7: ioport 0x7c00 alloc failed=0D ahc_isa_identify 8: ioport 0x8c00 alloc failed=0D ahc_isa_identify 9: ioport 0x9c00 alloc failed=0D ahc_isa_identify 10: ioport 0xac00 alloc failed=0D ahc_isa_identify 11: ioport 0xbc00 alloc failed=0D ahc_isa_identify 12: ioport 0xcc00 alloc failed=0D ahc_isa_identify 13: ioport 0xdc00 alloc failed=0D ahc_isa_identify 14: ioport 0xec00 alloc failed=0D isa_probe_children: disabling PnP devices=0D atkbdc: atkbdc0 already exists; skipping it=0D atrtc: atrtc0 already exists; skipping it=0D attimer: attimer0 already exists; skipping it=0D sc: sc0 already exists; skipping it=0D uart: uart0 already exists; skipping it=0D isa_probe_children: probing non-PnP devices=0D sc0: at flags 0x100 on isa0=0D sc0: VGA <16 virtual consoles, flags=3D0x100>=0D sc0: fb0, kbd1, terminal emulator: scteken (teken terminal)=0D vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0= =0D pcib0: allocated type 4 (0x3c0-0x3df) for rid 0 of vga0=0D pcib0: allocated type 3 (0xa0000-0xbffff) for rid 0 of vga0=0D fdc0: No FDOUT register!=0D fdc0 failed to probe at port 0x3f0 irq 6 drq 2 on isa0=0D ppc0: cannot reserve I/O port range=0D ppc0 failed to probe at irq 7 on isa0=0D pcib0: allocated type 4 (0x2f8-0x2ff) for rid 0 of uart1=0D uart1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0=0D wbwd0 failed to probe on isa0=0D isa_probe_children: probing PnP devices=0D Device configuration finished.=0D procfs registered=0D Timecounters tick every 10.000 msec=0D vlan: initialized, using hash tables with chaining=0D tcp_init: net.inet.tcp.tcbhashsize auto tuned to 2097152=0D lo0: bpf attached=0D hptrr: no controller detected.=0D hpt27xx: no controller detected.=0D xenbusb_front0: on xenstore0=0D ata0: reset tp1 mask=3D03 ostat0=3D00 ostat1=3D00=0D ata0: stat0=3D0x00 err=3D0x00 lsb=3D0x00 msb=3D0x00=0D ata0: stat1=3D0x00 err=3D0x00 lsb=3D0x00 msb=3D0x00=0D ata0: reset tp2 stat0=3D00 stat1=3D00 devices=3D0x0=0D ata1: reset tp1 mask=3D03 ostat0=3D00 ostat1=3D00=0D ata1: stat0=3D0x00 err=3D0x00 lsb=3D0x00 msb=3D0x00=0D ata1: stat1=3D0x00 err=3D0x00 lsb=3D0x00 msb=3D0x00=0D ata1: reset tp2 stat0=3D00 stat1=3D00 devices=3D0x0=0D xn0: at device/vif/0 on xenbusb_front0=0D xn0: bpf attached=0D xn0: Ethernet address: 22:00:0a:94:b4:ba=0D xenbusb_back0: on xenstore0=0D xctrl0: on xenstore0=0D xn0: backend features: feature-sg feature-gso-tcp4=0D xbd0: 10240MB at device/vbd/768 on xenbusb_front0=0D xbd0: attaching as ad0=0D xbd0: disk supports cache flush using: barriers=0D GEOM: new disk ad0=0D xbd1: 122866MB at device/vbd/51728 on xenbusb_front0= =0D xbd1: disk supports cache flush using: flush=0D xbd2: 122866MB at device/vbd/51744 on xenbusb_front0= =0D xbd2: disk supports cache flush using: flush=0D SMP: AP CPU #29 Launched!=0D cpu29 AP:=0D ID: 0x2d000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #24 Launched!=0D cpu24 AP:=0D ID: 0x28000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #21 Launched!=0D cpu21 AP:=0D ID: 0x25000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #3 Launched!=0D cpu3 AP:=0D ID: 0x03000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #2 Launched!=0D cpu2 AP:=0D ID: 0x02000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #6 Launched!=0D cpu6 AP:=0D ID: 0x06000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #7 Launched!=0D cpu7 AP:=0D ID: 0x07000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #23 Launched!=0D cpu23 AP:=0D ID: 0x27000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #1 Launched!=0D cpu1 AP:=0D ID: 0x01000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #18 Launched!=0D cpu18 AP:=0D ID: 0x22000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #25 Launched!=0D cpu25 AP:=0D ID: 0x29000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #16 Launched!=0D cpu16 AP:=0D ID: 0x20000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #28 Launched!=0D cpu28 AP:=0D ID: 0x2c000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #10 Launched!=0D cpu10 AP:=0D ID: 0x0a000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #27 Launched!=0D cpu27 AP:=0D ID: 0x2b000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #12 Launched!=0D cpu12 AP:=0D ID: 0x0c000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #30 Launched!=0D cpu30 AP:=0D ID: 0x2e000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #31 Launched!=0D cpu31 AP:=0D ID: 0x2f000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #19 Launched!=0D cpu19 AP:=0D ID: 0x23000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #15 Launched!=0D cpu15 AP:=0D ID: 0x0f000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #17 Launched!=0D cpu17 AP:=0D ID: 0x21000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #14 Launched!=0D cpu14 AP:=0D ID: 0x0e000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #20 Launched!=0D cpu20 AP:=0D ID: 0x24000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #22 Launched!=0D cpu22 AP:=0D ID: 0x26000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #4 Launched!=0D cpu4 AP:=0D ID: 0x04000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #8 Launched!=0D cpu8 AP:=0D ID: 0x08000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #13 Launched!=0D cpu13 AP:=0D ID: 0x0d000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #11 Launched!=0D cpu11 AP:=0D ID: 0x0b000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #5 Launched!=0D cpu5 AP:=0D ID: 0x05000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #26 Launched!=0D cpu26 AP:=0D ID: 0x2a000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #9 Launched!=0D cpu9 AP:=0D ID: 0x09000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D panic: xen_et0: Error -22 setting singleshot timer to 766317887512893=0D =0D cpuid =3D 8=0D KDB: enter: panic=0D [ thread pid 11 tid 100011 ]=0D Stopped at kdb_enter+0x3e: movq $0,kdb_why=0D db>=0D =0D -- =0D Colin Percival=0D Security Officer Emeritus, FreeBSD | The power to serve=0D Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid= =0D From owner-freebsd-xen@FreeBSD.ORG Thu May 23 09:06:23 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1FEE198F; Thu, 23 May 2013 09:06:23 +0000 (UTC) (envelope-from roger.pau@citrix.com) Received: from SMTP.EU.CITRIX.COM (smtp.eu.citrix.com [46.33.159.39]) by mx1.freebsd.org (Postfix) with ESMTP id 07866E91; Thu, 23 May 2013 09:06:21 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.87,726,1363132800"; d="scan'208";a="4887773" Received: from lonpex01cl01.citrite.net ([10.30.203.101]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 23 May 2013 09:06:19 +0000 Received: from [192.168.1.30] (10.30.203.1) by LONPEX01CL01.citrite.net (10.30.203.101) with Microsoft SMTP Server id 14.2.342.3; Thu, 23 May 2013 10:06:19 +0100 Message-ID: <519DDC0A.9000201@citrix.com> Date: Thu, 23 May 2013 11:06:18 +0200 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Colin Percival Subject: Re: FreeBSD PVHVM call for testing References: <519131D8.9010307@citrix.com> <51952BAE.6010609@freebsd.org> <51957D42.9060801@citrix.com> <51959ED9.6040405@freebsd.org> <51974EC9.9030204@citrix.com> <5197A1EA.2040404@freebsd.org> <519CAFC7.1070908@citrix.com> <519D24A9.3050407@freebsd.org> In-Reply-To: <519D24A9.3050407@freebsd.org> Content-Type: multipart/mixed; boundary="------------000309090701090501040108" X-Originating-IP: [10.30.203.1] Cc: "freebsd-xen@freebsd.org" , xen-devel , "freebsd-virtualization@freebsd.org" , "xen-users@lists.xen.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 09:06:23 -0000 --------------000309090701090501040108 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit On 22/05/13 22:03, Colin Percival wrote: > On 05/22/13 04:45, Roger Pau Monné wrote: >> On 18/05/13 17:44, Colin Percival wrote: >>> That seems to work. dmesg is attached. Are there any particular tests >>> you'd like me to run? >> >> I have not tested ZFS, that might be a good one. If you are running this >> on Xen 3.4 the behaviour should be the same as without this patches, so >> there shouldn't be many differences. > > I don't use ZFS personally, so I'm not sure exactly what tests to run on it; > hopefully someone else can take care of that. > >> If you could try that on Xen 4.0 at least (if I remember correctly >> that's when the vector callback was introduced), you should see the PV >> timer getting attached, and a performance increase. > > Testing on a cr1.8xlarge EC2 instance, I get Xen 4.2, but it ends up with > a panic -- console output below. I can get a backtrace and possibly even > a dump if those would help. Hello Colin, Thanks for the test, I've been using Xen 4.2 (and 4.3) without problems so far. By looking at the Xen code, the only reason the timer setup could return -22 (EINVAL), is that we try to set the timer for a different vCPU than the one we are running on. I've been able to boot a 32 vCPU DomU on my 8way box using Xen 4.2.1 (using both qemu-xen and qemu-xen-traditional device models), so I'm unsure if this could be due to some patch Amazon applies to Xen. Could you try the following patch and post the error message? I would like to see if the cpuid reported by kdb and the vCPU that we are trying to set the timer are the same. Booting... GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2013 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-CURRENT #68: Wed May 22 19:00:14 CEST 2013 root@:/usr/obj/usr/src/sys/XENHVM amd64 FreeBSD clang version 3.3 (trunk 178860) 20130405 WARNING: WITNESS option enabled, expect reduced performance. XEN: Hypervisor version 4.2 detected. CPU: Intel(R) Xeon(R) CPU W3550 @ 3.07GHz (3066.83-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x106a5 Family = 0x6 Model = 0x1a Stepping = 5 Features=0x1783fbff Features2=0x81b82201 AMD Features=0x28100800 AMD Features2=0x1 real memory = 4286578688 (4088 MB) avail memory = 3961323520 (3777 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 32 CPUs FreeBSD/SMP: 2 package(s) x 16 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 cpu4 (AP): APIC ID: 8 cpu5 (AP): APIC ID: 10 cpu6 (AP): APIC ID: 12 cpu7 (AP): APIC ID: 14 cpu8 (AP): APIC ID: 16 cpu9 (AP): APIC ID: 18 cpu10 (AP): APIC ID: 20 cpu11 (AP): APIC ID: 22 cpu12 (AP): APIC ID: 24 cpu13 (AP): APIC ID: 26 cpu14 (AP): APIC ID: 28 cpu15 (AP): APIC ID: 30 cpu16 (AP): APIC ID: 32 cpu17 (AP): APIC ID: 34 cpu18 (AP): APIC ID: 36 cpu19 (AP): APIC ID: 38 cpu20 (AP): APIC ID: 40 cpu21 (AP): APIC ID: 42 cpu22 (AP): APIC ID: 44 cpu23 (AP): APIC ID: 46 cpu24 (AP): APIC ID: 48 cpu25 (AP): APIC ID: 50 cpu26 (AP): APIC ID: 52 cpu27 (AP): APIC ID: 54 cpu28 (AP): APIC ID: 56 cpu29 (AP): APIC ID: 58 cpu30 (AP): APIC ID: 60 cpu31 (AP): APIC ID: 62 random device not loaded; using insecure entropy ioapic0: Changing APIC ID to 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-47 on motherboard kbd1 at kbdmux0 xen_et0: on motherboard Event timer "XENTIMER" frequency 1000000000 Hz quality 950 Timecounter "XENTIMER" frequency 1000000000 Hz quality 950 acpi0: on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) acpi0: reservation of 0, a0000 (3) failed cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 cpu4: on acpi0 cpu5: on acpi0 cpu6: on acpi0 cpu7: on acpi0 cpu8: on acpi0 cpu9: on acpi0 cpu10: on acpi0 cpu11: on acpi0 cpu12: on acpi0 cpu13: on acpi0 cpu14: on acpi0 cpu15: on acpi0 cpu16: on acpi0 cpu17: on acpi0 cpu18: on acpi0 cpu19: on acpi0 cpu20: on acpi0 cpu21: on acpi0 cpu22: on acpi0 cpu23: on acpi0 cpu24: on acpi0 cpu25: on acpi0 cpu26: on acpi0 cpu27: on acpi0 cpu28: on acpi0 cpu29: on acpi0 cpu30: on acpi0 cpu31: on acpi0 hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 62500000 Hz quality 950 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x71 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <32-bit timer at 3.579545MHz> port 0xb008-0xb00b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc300-0xc30f at device 1.1 on pci0 ata0: at channel 0 on atapci0 ata1: at channel 1 on atapci0 pci0: at device 1.3 (no driver attached) vgapci0: mem 0xf0000000-0xf1ffffff,0xf3030000-0xf3030fff at device 2.0 on pci0 xenpci0: port 0xc000-0xc0ff mem 0xf2000000-0xf2ffffff irq 28 at device 3.0 on pci0 xenstore0: on xenpci0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: console (9600,n,8,1) ppc0: port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 qpi0: on motherboard sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fdc0: No FDOUT register! Timecounters tick every 10.000 msec xenbusb_front0: on xenstore0 xenbusb_add_device: Device device/suspend/event-channel ignored. State 6 cd0 at ata1 bus 0 scbus1 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 16.700MB/s transfers (WDMA2, ATAPI 12bytes, PIO 65534bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present xn0: at device/vif/0 on xenbusb_front0 xn0: Ethernet address: 00:16:3e:47:d4:52 xn1: at device/vif/1 on xenbusb_front0 xn1: Ethernet address: 00:16:3e:47:d4:53 xenbusb_back0: on xenstore0 xctrl0: on xenstore0 xn0: backend features: feature-sg feature-gso-tcp4 xn1: backend features: feature-sg feature-gso-tcp4 xbd0: 20480MB at device/vbd/768 on xenbusb_front0 xbd0: attaching as ad0 xbd0: disk supports cache flush using: flush SMP: AP CPU #25 Launched! SMP: AP CPU #23 Launched! SMP: AP CPU #27 Launched! SMP: AP CPU #15 Launched! SMP: AP CPU #9 Launched! SMP: AP CPU #5 Launched! SMP: AP CPU #30 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #22 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #29 Launched! SMP: AP CPU #10 Launched! SMP: AP CPU #19 Launched! SMP: AP CPU #13 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #17 Launched! SMP: AP CPU #18 Launched! SMP: AP CPU #11 Launched! SMP: AP CPU #28 Launched! SMP: AP CPU #12 Launched! SMP: AP CPU #31 Launched! SMP: AP CPU #20 Launched! SMP: AP CPU #24 Launched! SMP: AP CPU #7 Launched! SMP: AP CPU #16 Launched! SMP: AP CPU #14 Launched! SMP: AP CPU #6 Launched! SMP: AP CPU #8 Launched! SMP: AP CPU #26 Launched! SMP: AP CPU #4 Launched! SMP: AP CPU #21 Launched! WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from ufs:/dev/ad0p2 [rw]... Setting hostuuid: c9230f36-1a54-489e-877c-1d15b8f463e9. Setting hostid: 0xd52252c7. Entropy harvesting: interrupts ethernet point_to_point kickstart. Starting file system checks: /dev/ad0p2: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad0p2: clean, 1690868 free (11852 frags, 209877 blocks, 0.2% fragmentation) Mounting local file systems:. Writing entropy file:. xn0: link state changed to DOWN xn0: link state changed to UP Starting Network: lo0 xn0 xn1. lo0: flags=8049 metric 0 mtu 16384 options=600003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 inet 127.0.0.1 netmask 0xff000000 nd6 options=21 xn0: flags=8843 metric 0 mtu 1500 options=503 ether 00:16:3e:47:d4:52 nd6 options=29 media: Ethernet manual status: active xn1: flags=8802 metric 0 mtu 1500 options=503 ether 00:16:3e:47:d4:53 nd6 options=29 media: Ethernet manual status: active Starting devd. Starting Network: xn1. xn1: flags=8802 metric 0 mtu 1500 options=503 ether 00:16:3e:47:d4:53 nd6 options=29 media: Ethernet manual status: active Starting dhclient. DHCPREQUEST on xn0 to 255.255.255.255 port 67 DHCPACK from 192.168.1.1 bound to 192.168.1.107 -- renewal in 43200 seconds. add net ::ffff:0.0.0.0: gateway ::1 add net ::0.0.0.0: gateway ::1 add net fe80::: gateway ::1 add net ff02::: gateway ::1 ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib 32-bit compatibility ldconfig path: /usr/lib32 Creating and/or trimming log files. Starting syslogd. Starting watchdogd. watchdogd: patting the dog: Operation not supported /etc/rc: WARNING: failed to start watchdogd No core dumps found. lock order reversal: 1st 0xffffff80f7627d80 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:3070 2nd 0xfffffe0027c18000 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:284 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xffffff8121720450 kdb_backtrace() at kdb_backtrace+0x39/frame 0xffffff8121720500 witness_checkorder() at witness_checkorder+0xc3f/frame 0xffffff8121720580 _sx_xlock() at _sx_xlock+0x75/frame 0xffffff81217205c0 ufsdirhash_add() at ufsdirhash_add+0x3b/frame 0xffffff8121720600 ufs_direnter() at ufs_direnter+0x688/frame 0xffffff81217206c0 ufs_mkdir() at ufs_mkdir+0x863/frame 0xffffff81217208c0 VOP_MKDIR_APV() at VOP_MKDIR_APV+0xf0/frame 0xffffff81217208f0 kern_mkdirat() at kern_mkdirat+0x21a/frame 0xffffff8121720ae0 amd64_syscall() at amd64_syscall+0x265/frame 0xffffff8121720bf0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xffffff8121720bf0 --- syscall (136, FreeBSD ELF64, sys_mkdir), rip = 0x80092faaa, rsp = 0x7fffffffd788, rbp = 0x7fffffffdc70 --- Clearing /tmp (X related). Updating motd:. Configuring syscons: keymap blanktime. Performing sanity check on sshd configuration. Starting sshd. Starting cron. Starting background file system checks in 60 seconds. Thu May 23 10:08:04 CEST 2013 FreeBSD/amd64 (Amnesiac) (ttyu0) --------------000309090701090501040108 Content-Type: text/plain; charset="UTF-8"; x-mac-type=0; x-mac-creator=0; name="timer_panic.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="timer_panic.patch" diff --git a/sys/dev/xen/timer/timer.c b/sys/dev/xen/timer/timer.c index 7083e46..4cb49b0 100644 --- a/sys/dev/xen/timer/timer.c +++ b/sys/dev/xen/timer/timer.c @@ -418,8 +418,8 @@ xentimer_et_start(struct eventtimer *et, } while (error == -ETIME); if (error) - panic("%s: Error %d setting singleshot timer to %"PRIu64"\n", - device_get_nameunit(sc->dev), error, next_time); + panic("%s: Error %d setting singleshot timer to %"PRIu64" for vCPU#%d\n", + device_get_nameunit(sc->dev), error, next_time, cpu); pcpu->timer = next_time; return (error); --------------000309090701090501040108-- From owner-freebsd-xen@FreeBSD.ORG Thu May 23 12:57:49 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 108ACAFD; Thu, 23 May 2013 12:57:49 +0000 (UTC) (envelope-from jeroen@dckd.nl) Received: from positron.dckd.nl (positron.dckd.nl [IPv6:2a02:898:62:f6::63]) by mx1.freebsd.org (Postfix) with ESMTP id CD087EBB; Thu, 23 May 2013 12:57:48 +0000 (UTC) Received: from wireless32-239.cwi.nl (zandbak.wlan.cwi.nl [192.16.197.194]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by positron.dckd.nl (Postfix) with ESMTPSA id E0B38F80D0; Thu, 23 May 2013 14:57:39 +0200 (CEST) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: FreeBSD PVHVM call for testing From: Jeroen van der Ham In-Reply-To: <519131D8.9010307@citrix.com> Date: Thu, 23 May 2013 14:57:38 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <616EE8A8-78BA-46E6-90AA-4A22160289DF@dckd.nl> References: <519131D8.9010307@citrix.com> To: =?iso-8859-1?Q?Roger_Pau_Monn=E9?= X-Mailer: Apple Mail (2.1503) Cc: "freebsd-xen@freebsd.org" , xen-devel , "freebsd-virtualization@freebsd.org" , "xen-users@lists.xen.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 12:57:49 -0000 Hi, On 13 May 2013, at 20:32, Roger Pau Monn=E9 = wrote: > Right now the code is in a state where it can be tested by users, so = we > would like to encourage FreeBSD and Xen users to test it and provide > feedback. I've just been able to install it on a VPS using the latest pvhvm_v9 = branch. This is good news, because the system I had before actually had trouble = with the HVM kernel from 9.1 [0]. I'm going to leave this running for a while and do some more tests on = it. Jeroen. [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D175822 From owner-freebsd-xen@FreeBSD.ORG Thu May 23 13:02:37 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 33016CFA; Thu, 23 May 2013 13:02:37 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) by mx1.freebsd.org (Postfix) with ESMTP id E81B3F24; Thu, 23 May 2013 13:02:36 +0000 (UTC) Received: by mail-ob0-f178.google.com with SMTP id v19so3786022obq.23 for ; Thu, 23 May 2013 06:02:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=AuREKu3QLwjJdxAB7fX9c4N5Z7KoN/xz+1z+nPAeq7I=; b=wzaf3xSQIUsrVtD0x8C+aPIwI7uECq68e3XnMwpRPSjUAAVv15lT/4hC/L45UKYi6A 62rUQ8v6lP8mwjMz7I2BfygEHfgM+4OMyJwaU3c5IL9wQFqXyM92PC/GfuCVzXPe5c6e lZKOk8ksK8WvDuu8Bdc1hge154fwZJbgHvzEEnJIuTQCjjwG7wVCmYElsw7whChXb6Ll ors8O7h/WDguCeoOlL6J0StGyJixNrOAZs1suruwYKcw2jva/Ue1HX8alEVxbj1C4XeJ KrNl6p0KslwJYXtzeVyjXVlLRpJ33/F5rhXC9PjU08fRaWieN02g481/c2Zsng/ZS5Fa U0nw== MIME-Version: 1.0 X-Received: by 10.60.103.148 with SMTP id fw20mr8034920oeb.37.1369314156550; Thu, 23 May 2013 06:02:36 -0700 (PDT) Received: by 10.76.96.49 with HTTP; Thu, 23 May 2013 06:02:36 -0700 (PDT) In-Reply-To: <616EE8A8-78BA-46E6-90AA-4A22160289DF@dckd.nl> References: <519131D8.9010307@citrix.com> <616EE8A8-78BA-46E6-90AA-4A22160289DF@dckd.nl> Date: Thu, 23 May 2013 09:02:36 -0400 Message-ID: Subject: Re: FreeBSD PVHVM call for testing From: Outback Dingo To: Jeroen van der Ham Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-xen@freebsd.org" , "xen-users@lists.xen.org" , xen-devel , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 13:02:37 -0000 On Thu, May 23, 2013 at 8:57 AM, Jeroen van der Ham wrote: > Hi, > > On 13 May 2013, at 20:32, Roger Pau Monn=E9 wrote: > > Right now the code is in a state where it can be tested by users, so we > > would like to encourage FreeBSD and Xen users to test it and provide > > feedback. > > I've just been able to install it on a VPS using the latest pvhvm_v9 > branch. > This is good news, because the system I had before actually had trouble > with the HVM kernel from 9.1 [0]. > > I'm going to leave this running for a while and do some more tests on it. > > Jeroen. > Curious if this would work under XEN XCP (Xen Cloud Platform) > > [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D175822 > > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscribe@freebsd.org" > From owner-freebsd-xen@FreeBSD.ORG Thu May 23 13:20:51 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id F1D7A776; Thu, 23 May 2013 13:20:50 +0000 (UTC) (envelope-from jeroen@dckd.nl) Received: from positron.dckd.nl (positron.dckd.nl [94.142.246.99]) by mx1.freebsd.org (Postfix) with ESMTP id B9504BB; Thu, 23 May 2013 13:20:50 +0000 (UTC) Received: from wireless32-239.cwi.nl (zandbak.wlan.cwi.nl [192.16.197.194]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by positron.dckd.nl (Postfix) with ESMTPSA id 97007F80D0; Thu, 23 May 2013 15:20:48 +0200 (CEST) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: FreeBSD PVHVM call for testing From: Jeroen van der Ham In-Reply-To: <519131D8.9010307@citrix.com> Date: Thu, 23 May 2013 15:20:47 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <647F6650-AEED-4784-8A45-98324860EE0A@dckd.nl> References: <519131D8.9010307@citrix.com> To: =?iso-8859-1?Q?Roger_Pau_Monn=E9?= X-Mailer: Apple Mail (2.1503) Cc: "freebsd-xen@freebsd.org" , xen-devel , "freebsd-virtualization@freebsd.org" , "xen-users@lists.xen.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 13:20:51 -0000 On 13 May 2013, at 20:32, Roger Pau Monn=E9 = wrote: > Also, I've created a wiki page that explains how to set up a FreeBSD > PVHVM for testing: >=20 > http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM You mention on that page that it is easier to install on 10.0-CURRENT = snapshots. What are the issues with installing this on 9.1? Is it possible? Jeroen. From owner-freebsd-xen@FreeBSD.ORG Thu May 23 13:31:02 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 586449C2; Thu, 23 May 2013 13:31:02 +0000 (UTC) (envelope-from roger.pau@citrix.com) Received: from SMTP.EU.CITRIX.COM (smtp.eu.citrix.com [46.33.159.39]) by mx1.freebsd.org (Postfix) with ESMTP id C8D1613A; Thu, 23 May 2013 13:31:01 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.87,728,1363132800"; d="scan'208";a="4899385" Received: from lonpex01cl03.citrite.net ([10.30.203.103]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 23 May 2013 13:30:54 +0000 Received: from [192.168.1.30] (10.30.203.1) by LONPEX01CL03.citrite.net (10.30.203.103) with Microsoft SMTP Server id 14.2.342.3; Thu, 23 May 2013 14:30:53 +0100 Message-ID: <519E1A0C.3070609@citrix.com> Date: Thu, 23 May 2013 15:30:52 +0200 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Jeroen van der Ham Subject: Re: FreeBSD PVHVM call for testing References: <519131D8.9010307@citrix.com> <647F6650-AEED-4784-8A45-98324860EE0A@dckd.nl> In-Reply-To: <647F6650-AEED-4784-8A45-98324860EE0A@dckd.nl> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Originating-IP: [10.30.203.1] Cc: "freebsd-xen@freebsd.org" , xen-devel , "freebsd-virtualization@freebsd.org" , "xen-users@lists.xen.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 13:31:02 -0000 On 23/05/13 15:20, Jeroen van der Ham wrote: > > On 13 May 2013, at 20:32, Roger Pau Monné wrote: >> Also, I've created a wiki page that explains how to set up a FreeBSD >> PVHVM for testing: >> >> http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM > > > You mention on that page that it is easier to install on 10.0-CURRENT snapshots. > What are the issues with installing this on 9.1? Is it possible? I don't think it is recommended to use a HEAD (10) kernel with a 9.1 userland. You can always install a 9.1 and then do a full update with the source on my repository. From owner-freebsd-xen@FreeBSD.ORG Thu May 23 13:33:29 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2B758A53; Thu, 23 May 2013 13:33:29 +0000 (UTC) (envelope-from roger.pau@citrix.com) Received: from SMTP.EU.CITRIX.COM (smtp.eu.citrix.com [46.33.159.39]) by mx1.freebsd.org (Postfix) with ESMTP id 9A928157; Thu, 23 May 2013 13:33:28 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.87,728,1363132800"; d="scan'208";a="4899548" Received: from lonpex01cl02.citrite.net ([10.30.203.102]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 23 May 2013 13:33:27 +0000 Received: from [192.168.1.30] (10.30.203.1) by LONPEX01CL02.citrite.net (10.30.203.102) with Microsoft SMTP Server id 14.2.342.3; Thu, 23 May 2013 14:33:26 +0100 Message-ID: <519E1AA6.2060808@citrix.com> Date: Thu, 23 May 2013 15:33:26 +0200 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Jeroen van der Ham Subject: Re: FreeBSD PVHVM call for testing References: <519131D8.9010307@citrix.com> <616EE8A8-78BA-46E6-90AA-4A22160289DF@dckd.nl> In-Reply-To: <616EE8A8-78BA-46E6-90AA-4A22160289DF@dckd.nl> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Originating-IP: [10.30.203.1] Cc: "freebsd-xen@freebsd.org" , xen-devel , "freebsd-virtualization@freebsd.org" , "xen-users@lists.xen.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 13:33:29 -0000 On 23/05/13 14:57, Jeroen van der Ham wrote: > Hi, > > On 13 May 2013, at 20:32, Roger Pau Monné wrote: >> Right now the code is in a state where it can be tested by users, so we >> would like to encourage FreeBSD and Xen users to test it and provide >> feedback. > > I've just been able to install it on a VPS using the latest pvhvm_v9 branch. The branch pvhvm_v9 contains an initial implementation of PV IPIs for amd64. I've now finished it and I'm going to port it to i386 also, and push a new branch to the repository. > This is good news, because the system I had before actually had trouble with the HVM kernel from 9.1 [0]. > > I'm going to leave this running for a while and do some more tests on it. > > Jeroen. > > > [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=175822 > From owner-freebsd-xen@FreeBSD.ORG Thu May 23 14:02:45 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 0B2DAFCC for ; Thu, 23 May 2013 14:02:45 +0000 (UTC) (envelope-from jwest@ezwind.net) Received: from ezwind.net (bobby.ezwind.net [199.188.211.146]) by mx1.freebsd.org (Postfix) with ESMTP id D5CA3319 for ; Thu, 23 May 2013 14:02:44 +0000 (UTC) Received: from LENOVOD6B52A6B by ezwind.net (MDaemon.PRO.v8.1.3.R) with ESMTP id 47-md50000145883.msg for ; Thu, 23 May 2013 09:02:00 -0500 From: "Jay West" To: Subject: tcp offloading Date: Thu, 23 May 2013 09:02:01 -0500 Message-ID: <001901ce57be$192d3940$4b87abc0$@ezwind.net> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 thread-index: Ac5XvN1FrbyqULTdS+avbtL3zOzoYw== Content-Language: en-us X-Authenticated-Sender: jwest@ezwind.net X-MDRemoteIP: 66.128.111.62 X-Return-Path: jwest@ezwind.net X-MDaemon-Deliver-To: freebsd-xen@freebsd.org X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on bobby.ezwind.net X-Spam-Status: No, score=-4.7 required=6.1 tests=BAYES_00,HTML_MESSAGE autolearn=disabled version=3.0.4 X-Spam-Level: X-Spam-Processed: gateway.ezwind.net, Thu, 23 May 2013 09:02:02 -0500 X-MDAV-Processed: gateway.ezwind.net, Thu, 23 May 2013 09:02:05 -0500 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 14:02:45 -0000 Environment is Citrix Xenserver Advanced, with (mostly) freebsd 9.1 64bit HVM with PV drivers. I've heard much mention around the net that in pretty much all cases, TCP offloading should be disabled inside the VM. I have also seen other posts that TCP offloading should be disabled on the Dom0. So my question is; for best performance should TCP offloading be disabled in the VM, or the Xenserver (dom0), or should it be disabled in BOTH? Anyone have a definitive answer? Jay West EZwind.net PO Box 460474 Saint Louis, MO 63146 Voice: (314) 262-4143 ext 1000 Toll Free: (866) 343-2589 Fax: (314) 558-9284 jwest@ezwind.net -------------------------------------------- This e-mail transmission may contain information that is proprietary, privileged and/or confidential and is intended exclusively for the person(s) to whom it is addressed. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient's designees is strictly prohibited. If you are not the intended recipient or their designee, please notify the sender immediately by return e-mail and delete all copies. From owner-freebsd-xen@FreeBSD.ORG Thu May 23 15:02:23 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 53270408; Thu, 23 May 2013 15:02:23 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-oa0-f46.google.com (mail-oa0-f46.google.com [209.85.219.46]) by mx1.freebsd.org (Postfix) with ESMTP id 14CFB945; Thu, 23 May 2013 15:02:22 +0000 (UTC) Received: by mail-oa0-f46.google.com with SMTP id h2so4522982oag.5 for ; Thu, 23 May 2013 08:02:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=dBaNkOyQR/sOztNDdpdvUTT0wgCsBQkrbzQFb+yii88=; b=cDBPAdcM8mpuvMYeBJb7ZT7H9y02DIlkCnV5zacrwqROdpcEF+USmWo32jr9Nb8jiJ iijHfFNdB1bKvIWWV+/LqkPP5n0VWtRUOnEpkImzTcK5swDkYJ0/tfXCuyPdFpk+YNUH LXnknat8TQ+rm8R4RD+oZj09rz7/HQKY3OJh3QoWBIHvhYSuKSxoY4pIof6YG1kTGL5I IWQ5OABmiiFDVbSQ2mzxWLxYrc1SEW1/azXIly9E0aBpfGbhLVIt3pdQW4Tde98aGEeW ZD5nTvtsMmWRmg9uvFc6tNQXpsPyf5KUV9EDFpDK84Uv0lmo0mJkxIMzb1MhdQki2HKS g8Pw== MIME-Version: 1.0 X-Received: by 10.182.65.100 with SMTP id w4mr6523072obs.70.1369321342346; Thu, 23 May 2013 08:02:22 -0700 (PDT) Received: by 10.76.96.49 with HTTP; Thu, 23 May 2013 08:02:21 -0700 (PDT) In-Reply-To: <519E1AA6.2060808@citrix.com> References: <519131D8.9010307@citrix.com> <616EE8A8-78BA-46E6-90AA-4A22160289DF@dckd.nl> <519E1AA6.2060808@citrix.com> Date: Thu, 23 May 2013 11:02:21 -0400 Message-ID: Subject: Re: FreeBSD PVHVM call for testing From: Outback Dingo To: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-xen@freebsd.org" , "xen-users@lists.xen.org" , xen-devel , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 15:02:23 -0000 On Thu, May 23, 2013 at 9:33 AM, Roger Pau Monn=E9 wr= ote: > On 23/05/13 14:57, Jeroen van der Ham wrote: > > Hi, > > > > On 13 May 2013, at 20:32, Roger Pau Monn=E9 wrot= e: > >> Right now the code is in a state where it can be tested by users, so w= e > >> would like to encourage FreeBSD and Xen users to test it and provide > >> feedback. > > > > I've just been able to install it on a VPS using the latest pvhvm_v9 > branch. > > The branch pvhvm_v9 contains an initial implementation of PV IPIs for > amd64. I've now finished it and I'm going to port it to i386 also, and > push a new branch to the repository. > curious as the from what rev you guys forked your XENPVM work from HEAD, so i can assure Ive not lost some fixes, new commits from upstream > > > This is good news, because the system I had before actually had trouble > with the HVM kernel from 9.1 [0]. > > > > I'm going to leave this running for a while and do some more tests on i= t. > > > > Jeroen. > > > > > > [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D175822 > > > > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscribe@freebsd.org" > From owner-freebsd-xen@FreeBSD.ORG Thu May 23 16:30:33 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 699F0F33; Thu, 23 May 2013 16:30:33 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) by mx1.freebsd.org (Postfix) with ESMTP id 2ABAAEFB; Thu, 23 May 2013 16:30:33 +0000 (UTC) Received: by mail-ob0-f176.google.com with SMTP id wp18so4171004obc.21 for ; Thu, 23 May 2013 09:30:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=q/Th8dxC64WNgD2eq0dL4k56EtWOsjmKNW3K2ukeTTU=; b=gZ4XlE6P3r+LTAzW8fxZOHLcbRu5+Jwh9OSCNcjPPlYpolJpi4Tn2tHtPRf4I7wfSM 7coybzRtqg46QWCkyjKVqouI3h/ZuK7JcNTFADJCJpWUDvz9WguZC79H56tpwg34b6HF hZH+Yc+ec5k4Yp94vYwzLhhKeJAGx6WcXfIrVHtMgVhZsZ2015I4JmK4z/9KGGtM2xBL 9zPvgtjxLpRE+hjo05C2zo6j1CjiURtccqF75We1xfraR4hLxAUFljVylmJslbfGcf7A loEXBijC9jNAMoTS5XIW4kHGz828429KxHfFsYYawYtRxtxMk2IxrRuTQK9aPLK/CN/L z2UA== MIME-Version: 1.0 X-Received: by 10.60.121.2 with SMTP id lg2mr9081588oeb.89.1369326632706; Thu, 23 May 2013 09:30:32 -0700 (PDT) Received: by 10.76.96.49 with HTTP; Thu, 23 May 2013 09:30:32 -0700 (PDT) In-Reply-To: <519E1AA6.2060808@citrix.com> References: <519131D8.9010307@citrix.com> <616EE8A8-78BA-46E6-90AA-4A22160289DF@dckd.nl> <519E1AA6.2060808@citrix.com> Date: Thu, 23 May 2013 12:30:32 -0400 Message-ID: Subject: Re: FreeBSD PVHVM call for testing From: Outback Dingo To: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-xen@freebsd.org" , "xen-users@lists.xen.org" , xen-devel , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 16:30:33 -0000 On Thu, May 23, 2013 at 9:33 AM, Roger Pau Monn=E9 wr= ote: > On 23/05/13 14:57, Jeroen van der Ham wrote: > > Hi, > > > > On 13 May 2013, at 20:32, Roger Pau Monn=E9 wrot= e: > >> Right now the code is in a state where it can be tested by users, so w= e > >> would like to encourage FreeBSD and Xen users to test it and provide > >> feedback. > > > > I've just been able to install it on a VPS using the latest pvhvm_v9 > branch. > > The branch pvhvm_v9 contains an initial implementation of PV IPIs for > amd64. I've now finished it and I'm going to port it to i386 also, and > push a new branch to the repository. > > > This is good news, because the system I had before actually had trouble > with the HVM kernel from 9.1 [0]. > > > > I'm going to leave this running for a while and do some more tests on i= t. > > > > Jeroen. > > > > > > [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D175822 > > > > I built the rev_9 branch on a XCP host and rebooted, however I am seeing on boot after ugen0.2: at usbus0 run_interrupt_driven_hooks: still waiting after 60 seconds for xenbus_nop_confighook_cb run_interrupt_driven_hooks: still waiting after 120 seconds for xenbus_nop_confighook_cb run_interrupt_driven_hooks: still waiting after 180 seconds for xenbus_nop_confighook_cb run_interrupt_driven_hooks: still waiting after 240 seconds for xenbus_nop_confighook_cb run_interrupt_driven_hooks: still waiting after 300 seconds for xenbus_nop_confighook_cb panic: run_interrupt_driven_confighooks: waited too long cpuid =3D 0 KDB: enter: panic [ thread pid 0 tid 100000 ] Stropped at kdb_enter +0x3b: movq $0,0xad6522(%rip) db> _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscribe@freebsd.org" > From owner-freebsd-xen@FreeBSD.ORG Thu May 23 16:48:17 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 61785905; Thu, 23 May 2013 16:48:17 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-vb0-x231.google.com (mail-vb0-x231.google.com [IPv6:2607:f8b0:400c:c02::231]) by mx1.freebsd.org (Postfix) with ESMTP id 10413FEB; Thu, 23 May 2013 16:48:16 +0000 (UTC) Received: by mail-vb0-f49.google.com with SMTP id q13so119392vbe.36 for ; Thu, 23 May 2013 09:48:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=COq5YYK3tAFybQ7cwhh3/QQfTD+5j28+uLT47JpR5co=; b=GJs89rxhuGIuGnvF2sRJfvsHTD9fQzBsDm9koYa9d+xRzU6DbnDTxOuJounSUeXbqM u7cg19+QlhGPi/ys8W/LsBJNjkKrizq31cxAFIRrwmWfWnurtqjmYl28Nh8/WAz36KYN jqCnqjp/rsBS8UIpAnnjZI1tLsx+U35KC9Evc5S2Ynu0S/ydhgGOK8egxrB1UK+cikEF LjBtNyS8WpbuGla93uIO95uykga6Z6323n65YJ/m3zQWTk8rZbY/QiYw3JmOUyu+M2mD iYyY026zytSDuhL1mJ2gsZ/YtM4sWYFpay6odRmkDZjaw+FX6m3BHHeIXH0LwkFSb/RT lwiw== MIME-Version: 1.0 X-Received: by 10.52.156.65 with SMTP id wc1mr1960932vdb.10.1369327696119; Thu, 23 May 2013 09:48:16 -0700 (PDT) Received: by 10.52.109.196 with HTTP; Thu, 23 May 2013 09:48:15 -0700 (PDT) In-Reply-To: References: <519131D8.9010307@citrix.com> <616EE8A8-78BA-46E6-90AA-4A22160289DF@dckd.nl> <519E1AA6.2060808@citrix.com> Date: Thu, 23 May 2013 20:48:15 +0400 Message-ID: Subject: Re: FreeBSD PVHVM call for testing From: Sergey Kandaurov To: Outback Dingo Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-xen@freebsd.org" , "xen-users@lists.xen.org" , xen-devel , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 16:48:17 -0000 On 23 May 2013 20:30, Outback Dingo wrote: > On Thu, May 23, 2013 at 9:33 AM, Roger Pau Monn=E9 = wrote: > >> On 23/05/13 14:57, Jeroen van der Ham wrote: >> > Hi, >> > >> > On 13 May 2013, at 20:32, Roger Pau Monn=E9 wro= te: >> >> Right now the code is in a state where it can be tested by users, so = we >> >> would like to encourage FreeBSD and Xen users to test it and provide >> >> feedback. >> > >> > I've just been able to install it on a VPS using the latest pvhvm_v9 >> branch. >> >> The branch pvhvm_v9 contains an initial implementation of PV IPIs for >> amd64. I've now finished it and I'm going to port it to i386 also, and >> push a new branch to the repository. >> >> > This is good news, because the system I had before actually had troubl= e >> with the HVM kernel from 9.1 [0]. >> > >> > I'm going to leave this running for a while and do some more tests on = it. >> > >> > Jeroen. >> > >> > >> > [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D175822 >> > >> >> I built the rev_9 branch on a XCP host and rebooted, however I am seeing > > on boot after ugen0.2: at usbus0 > > run_interrupt_driven_hooks: still waiting after 60 seconds for > xenbus_nop_confighook_cb > run_interrupt_driven_hooks: still waiting after 120 seconds for > xenbus_nop_confighook_cb > run_interrupt_driven_hooks: still waiting after 180 seconds for > xenbus_nop_confighook_cb > run_interrupt_driven_hooks: still waiting after 240 seconds for > xenbus_nop_confighook_cb > run_interrupt_driven_hooks: still waiting after 300 seconds for > xenbus_nop_confighook_cb > panic: run_interrupt_driven_confighooks: waited too long > cpuid =3D 0 > KDB: enter: panic > [ thread pid 0 tid 100000 ] > Stropped at kdb_enter +0x3b: movq $0,0xad6522(%rip) > db> Can you recheck this on stock HEAD? >From your description this looks like a rather old bug seen with 8.2 or above and XCP (referenced in PR kern/164630). You can trigger it when e.g. booting with empty cdrom. --=20 wbr, pluknet From owner-freebsd-xen@FreeBSD.ORG Thu May 23 16:48:20 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 64901906; Thu, 23 May 2013 16:48:20 +0000 (UTC) (envelope-from roger.pau@citrix.com) Received: from SMTP.EU.CITRIX.COM (smtp.eu.citrix.com [46.33.159.39]) by mx1.freebsd.org (Postfix) with ESMTP id D38B4FEC; Thu, 23 May 2013 16:48:19 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.87,729,1363132800"; d="scan'208";a="4910741" Received: from lonpex01cl02.citrite.net ([10.30.203.102]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 23 May 2013 16:48:19 +0000 Received: from [192.168.1.30] (10.30.203.1) by LONPEX01CL02.citrite.net (10.30.203.102) with Microsoft SMTP Server id 14.2.342.3; Thu, 23 May 2013 17:48:17 +0100 Message-ID: <519E4850.1090305@citrix.com> Date: Thu, 23 May 2013 18:48:16 +0200 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Outback Dingo Subject: Re: FreeBSD PVHVM call for testing References: <519131D8.9010307@citrix.com> <616EE8A8-78BA-46E6-90AA-4A22160289DF@dckd.nl> <519E1AA6.2060808@citrix.com> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Originating-IP: [10.30.203.1] Cc: "freebsd-xen@freebsd.org" , "xen-users@lists.xen.org" , xen-devel , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 16:48:20 -0000 On 23/05/13 18:30, Outback Dingo wrote: > > > > On Thu, May 23, 2013 at 9:33 AM, Roger Pau Monné > wrote: > > On 23/05/13 14:57, Jeroen van der Ham wrote: > > Hi, > > > > On 13 May 2013, at 20:32, Roger Pau Monné > wrote: > >> Right now the code is in a state where it can be tested by users, > so we > >> would like to encourage FreeBSD and Xen users to test it and provide > >> feedback. > > > > I've just been able to install it on a VPS using the latest > pvhvm_v9 branch. > > The branch pvhvm_v9 contains an initial implementation of PV IPIs for > amd64. I've now finished it and I'm going to port it to i386 also, and > push a new branch to the repository. > > > This is good news, because the system I had before actually had > trouble with the HVM kernel from 9.1 [0]. > > > > I'm going to leave this running for a while and do some more tests > on it. > > > > Jeroen. > > > > > > [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=175822 > > > > I built the rev_9 branch on a XCP host and rebooted, however I am seeing > > on boot after ugen0.2: at usbus0 > > run_interrupt_driven_hooks: still waiting after 60 seconds for > xenbus_nop_confighook_cb > run_interrupt_driven_hooks: still waiting after 120 seconds for > xenbus_nop_confighook_cb > run_interrupt_driven_hooks: still waiting after 180 seconds for > xenbus_nop_confighook_cb > run_interrupt_driven_hooks: still waiting after 240 seconds for > xenbus_nop_confighook_cb > run_interrupt_driven_hooks: still waiting after 300 seconds for > xenbus_nop_confighook_cb > panic: run_interrupt_driven_confighooks: waited too long > cpuid = 0 > KDB: enter: panic > [ thread pid 0 tid 100000 ] > Stropped at kdb_enter +0x3b: movq $0,0xad6522(%rip) > db> >From what I've read on the list, it seems like you cannot boot the PVHVM kernel if you have a cdrom attached to the guest, could you try disabling the cdrom and booting again? From owner-freebsd-xen@FreeBSD.ORG Thu May 23 17:02:46 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 00BC6B6A; Thu, 23 May 2013 17:02:45 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-ob0-x234.google.com (mail-ob0-x234.google.com [IPv6:2607:f8b0:4003:c01::234]) by mx1.freebsd.org (Postfix) with ESMTP id B43F0FF; Thu, 23 May 2013 17:02:45 +0000 (UTC) Received: by mail-ob0-f180.google.com with SMTP id xk17so4279500obc.11 for ; Thu, 23 May 2013 10:02:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=CcRCuFP4GqI7hGlrLM4M1EoyyrLIubMpnUL6F/qymN0=; b=khTFc34V1opL/dtac3oEkekdRXL7zZmArrN8kkBr1kSEda6mjCZQRX1lSc2h+jELDM iAPXIXViz1MczEgPJBKuuspbg/WzZ0XkWIMv9NaNgBPaovWwu/2jsxEVTm0c2lBZvXcz pVpHNvgyKdlYrAKwvMykz2IKz/1DggsekfVdH978iDRswNjgtayuwdj7+knSEyzePyD5 02uE+A0qwRBZAoXgMmekoR2wYcqYl9M0y5RmTFU+dsta/aspFPR+HOo1VtoirW2jtYP1 Vh+6i3i6srA4J+6S5Rn/NBrEdl7+0O/2MwmvNho5VKSoGk1RVwFYLZB9GM3bi/ADP0Ln mx1w== MIME-Version: 1.0 X-Received: by 10.60.93.67 with SMTP id cs3mr8729773oeb.88.1369328565214; Thu, 23 May 2013 10:02:45 -0700 (PDT) Received: by 10.76.96.49 with HTTP; Thu, 23 May 2013 10:02:45 -0700 (PDT) In-Reply-To: <519E4850.1090305@citrix.com> References: <519131D8.9010307@citrix.com> <616EE8A8-78BA-46E6-90AA-4A22160289DF@dckd.nl> <519E1AA6.2060808@citrix.com> <519E4850.1090305@citrix.com> Date: Thu, 23 May 2013 13:02:45 -0400 Message-ID: Subject: Re: FreeBSD PVHVM call for testing From: Outback Dingo To: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-xen@freebsd.org" , "xen-users@lists.xen.org" , xen-devel , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 17:02:46 -0000 On Thu, May 23, 2013 at 12:48 PM, Roger Pau Monn=E9 w= rote: > On 23/05/13 18:30, Outback Dingo wrote: > > > > > > > > On Thu, May 23, 2013 at 9:33 AM, Roger Pau Monn=E9 > > wrote: > > > > On 23/05/13 14:57, Jeroen van der Ham wrote: > > > Hi, > > > > > > On 13 May 2013, at 20:32, Roger Pau Monn=E9 > > wrote: > > >> Right now the code is in a state where it can be tested by users= , > > so we > > >> would like to encourage FreeBSD and Xen users to test it and > provide > > >> feedback. > > > > > > I've just been able to install it on a VPS using the latest > > pvhvm_v9 branch. > > > > The branch pvhvm_v9 contains an initial implementation of PV IPIs f= or > > amd64. I've now finished it and I'm going to port it to i386 also, > and > > push a new branch to the repository. > > > > > This is good news, because the system I had before actually had > > trouble with the HVM kernel from 9.1 [0]. > > > > > > I'm going to leave this running for a while and do some more test= s > > on it. > > > > > > Jeroen. > > > > > > > > > [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D175822 > > > > > > > I built the rev_9 branch on a XCP host and rebooted, however I am seein= g > > > > on boot after ugen0.2: at usbus0 > > > > run_interrupt_driven_hooks: still waiting after 60 seconds for > > xenbus_nop_confighook_cb > > run_interrupt_driven_hooks: still waiting after 120 seconds for > > xenbus_nop_confighook_cb > > run_interrupt_driven_hooks: still waiting after 180 seconds for > > xenbus_nop_confighook_cb > > run_interrupt_driven_hooks: still waiting after 240 seconds for > > xenbus_nop_confighook_cb > > run_interrupt_driven_hooks: still waiting after 300 seconds for > > xenbus_nop_confighook_cb > > panic: run_interrupt_driven_confighooks: waited too long > > cpuid =3D 0 > > KDB: enter: panic > > [ thread pid 0 tid 100000 ] > > Stropped at kdb_enter +0x3b: movq $0,0xad6522(%rip) > > db> > > From what I've read on the list, it seems like you cannot boot the PVHVM > kernel if you have a cdrom attached to the guest, could you try > disabling the cdrom and booting again? > > great how does one go about disabling the cdrom, i get some disk parameters needs to be removed from the vm template before boot From owner-freebsd-xen@FreeBSD.ORG Thu May 23 17:22:35 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9C07913F; Thu, 23 May 2013 17:22:35 +0000 (UTC) (envelope-from jeroen@dckd.nl) Received: from positron.dckd.nl (positron.dckd.nl [94.142.246.99]) by mx1.freebsd.org (Postfix) with ESMTP id 2CD201F3; Thu, 23 May 2013 17:22:34 +0000 (UTC) Received: from [10.87.136.62] (unknown [88.128.80.6]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by positron.dckd.nl (Postfix) with ESMTPSA id 824DCF80D1; Thu, 23 May 2013 19:22:31 +0200 (CEST) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: FreeBSD PVHVM call for testing From: Jeroen van der Ham In-Reply-To: Date: Thu, 23 May 2013 19:22:27 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <0BBCBA0B-F4A6-4775-A172-D051D9363665@dckd.nl> References: <519131D8.9010307@citrix.com> <616EE8A8-78BA-46E6-90AA-4A22160289DF@dckd.nl> <519E1AA6.2060808@citrix.com> <519E4850.1090305@citrix.com> To: Outback Dingo X-Mailer: Apple Mail (2.1503) Cc: "freebsd-xen@freebsd.org" , "xen-users@lists.xen.org" , xen-devel , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 17:22:35 -0000 Hi, Just remove this line (or pointing to a similar file from the template: = (It's part of the disks definition: > 'file:/root/freebsd-10.iso,hdc:cdrom,r', Jeroen. On 23 May 2013, at 19:02, Outback Dingo wrote: > On Thu, May 23, 2013 at 12:48 PM, Roger Pau Monn=E9 = wrote: >=20 >> On 23/05/13 18:30, Outback Dingo wrote: >>>=20 >>>=20 >>>=20 >>> On Thu, May 23, 2013 at 9:33 AM, Roger Pau Monn=E9 = >> > wrote: >>>=20 >>> On 23/05/13 14:57, Jeroen van der Ham wrote: >>>> Hi, >>>>=20 >>>> On 13 May 2013, at 20:32, Roger Pau Monn=E9 >> > wrote: >>>>> Right now the code is in a state where it can be tested by users, >>> so we >>>>> would like to encourage FreeBSD and Xen users to test it and >> provide >>>>> feedback. >>>>=20 >>>> I've just been able to install it on a VPS using the latest >>> pvhvm_v9 branch. >>>=20 >>> The branch pvhvm_v9 contains an initial implementation of PV IPIs = for >>> amd64. I've now finished it and I'm going to port it to i386 = also, >> and >>> push a new branch to the repository. >>>=20 >>>> This is good news, because the system I had before actually had >>> trouble with the HVM kernel from 9.1 [0]. >>>>=20 >>>> I'm going to leave this running for a while and do some more tests >>> on it. >>>>=20 >>>> Jeroen. >>>>=20 >>>>=20 >>>> [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D175822 >>>>=20 >>>=20 >>> I built the rev_9 branch on a XCP host and rebooted, however I am = seeing >>>=20 >>> on boot after ugen0.2: at usbus0 >>>=20 >>> run_interrupt_driven_hooks: still waiting after 60 seconds for >>> xenbus_nop_confighook_cb >>> run_interrupt_driven_hooks: still waiting after 120 seconds for >>> xenbus_nop_confighook_cb >>> run_interrupt_driven_hooks: still waiting after 180 seconds for >>> xenbus_nop_confighook_cb >>> run_interrupt_driven_hooks: still waiting after 240 seconds for >>> xenbus_nop_confighook_cb >>> run_interrupt_driven_hooks: still waiting after 300 seconds for >>> xenbus_nop_confighook_cb >>> panic: run_interrupt_driven_confighooks: waited too long >>> cpuid =3D 0 >>> KDB: enter: panic >>> [ thread pid 0 tid 100000 ] >>> Stropped at kdb_enter +0x3b: movq $0,0xad6522(%rip) >>> db> >>=20 >> =46rom what I've read on the list, it seems like you cannot boot the = PVHVM >> kernel if you have a cdrom attached to the guest, could you try >> disabling the cdrom and booting again? >>=20 >>=20 > great how does one go about disabling the cdrom, i get some disk = parameters > needs to be removed from the vm template before boot From owner-freebsd-xen@FreeBSD.ORG Thu May 23 17:29:35 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A599C220; Thu, 23 May 2013 17:29:35 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) by mx1.freebsd.org (Postfix) with ESMTP id 63EC2233; Thu, 23 May 2013 17:29:35 +0000 (UTC) Received: by mail-ob0-f172.google.com with SMTP id tb18so4314576obb.31 for ; Thu, 23 May 2013 10:29:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=IPfAvq43MWutjGg2jg4rwSlvF/1KXgvwHKFYSfJGQ1o=; b=uEVEdTCJfxBAZoPdqXJWzbwVxcHhDYsPqavjKKyfQD8kdn1QvvLQoGCjH/PzOQiWxw it9vwSLFxPFESG5Vln5WuWz6ZZ3xD4iEqOs6FBh/BLCnL5xC3c2GQoR2j1q5uqNj7h66 YFLS+OJjeaypVSVCl5OPUnyl6DSdEPbusUEmQkKVbjUPEJzp4+MeQX6S+IFJ6E9W11aU QAornEDRiwuuV42vZR0e6fuYWgdu/l5qHARJo4WWax15y2fluNICtmWHbwpInp7PYxiR U0ZniMIa9CDCUa0cFA8d0npFSs9fTs1k7LRm//w8aCB3XKqNOtwTuuo0DKYC4IA5SKs3 D+Hw== MIME-Version: 1.0 X-Received: by 10.182.241.194 with SMTP id wk2mr9010237obc.77.1369330174995; Thu, 23 May 2013 10:29:34 -0700 (PDT) Received: by 10.76.96.49 with HTTP; Thu, 23 May 2013 10:29:34 -0700 (PDT) In-Reply-To: <0BBCBA0B-F4A6-4775-A172-D051D9363665@dckd.nl> References: <519131D8.9010307@citrix.com> <616EE8A8-78BA-46E6-90AA-4A22160289DF@dckd.nl> <519E1AA6.2060808@citrix.com> <519E4850.1090305@citrix.com> <0BBCBA0B-F4A6-4775-A172-D051D9363665@dckd.nl> Date: Thu, 23 May 2013 13:29:34 -0400 Message-ID: Subject: Re: FreeBSD PVHVM call for testing From: Outback Dingo To: Jeroen van der Ham Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-xen@freebsd.org" , "xen-users@lists.xen.org" , xen-devel , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 17:29:35 -0000 On Thu, May 23, 2013 at 1:22 PM, Jeroen van der Ham wrote: > Hi, > > Just remove this line (or pointing to a similar file from the template: > (It's part of the disks definition: > > > 'file:/root/freebsd-10.iso,hdc:cdrom,r', > > Thanks, but this is XCP not a generic XEN server where there are vm config files under /etc/xen/ in XCP they dont exists > Jeroen. > > On 23 May 2013, at 19:02, Outback Dingo wrote: > > > On Thu, May 23, 2013 at 12:48 PM, Roger Pau Monn=E9 >wrote: > > > >> On 23/05/13 18:30, Outback Dingo wrote: > >>> > >>> > >>> > >>> On Thu, May 23, 2013 at 9:33 AM, Roger Pau Monn=E9 >>> > wrote: > >>> > >>> On 23/05/13 14:57, Jeroen van der Ham wrote: > >>>> Hi, > >>>> > >>>> On 13 May 2013, at 20:32, Roger Pau Monn=E9 >>> > wrote: > >>>>> Right now the code is in a state where it can be tested by users, > >>> so we > >>>>> would like to encourage FreeBSD and Xen users to test it and > >> provide > >>>>> feedback. > >>>> > >>>> I've just been able to install it on a VPS using the latest > >>> pvhvm_v9 branch. > >>> > >>> The branch pvhvm_v9 contains an initial implementation of PV IPIs > for > >>> amd64. I've now finished it and I'm going to port it to i386 also, > >> and > >>> push a new branch to the repository. > >>> > >>>> This is good news, because the system I had before actually had > >>> trouble with the HVM kernel from 9.1 [0]. > >>>> > >>>> I'm going to leave this running for a while and do some more tests > >>> on it. > >>>> > >>>> Jeroen. > >>>> > >>>> > >>>> [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D175822 > >>>> > >>> > >>> I built the rev_9 branch on a XCP host and rebooted, however I am > seeing > >>> > >>> on boot after ugen0.2: at usbus0 > >>> > >>> run_interrupt_driven_hooks: still waiting after 60 seconds for > >>> xenbus_nop_confighook_cb > >>> run_interrupt_driven_hooks: still waiting after 120 seconds for > >>> xenbus_nop_confighook_cb > >>> run_interrupt_driven_hooks: still waiting after 180 seconds for > >>> xenbus_nop_confighook_cb > >>> run_interrupt_driven_hooks: still waiting after 240 seconds for > >>> xenbus_nop_confighook_cb > >>> run_interrupt_driven_hooks: still waiting after 300 seconds for > >>> xenbus_nop_confighook_cb > >>> panic: run_interrupt_driven_confighooks: waited too long > >>> cpuid =3D 0 > >>> KDB: enter: panic > >>> [ thread pid 0 tid 100000 ] > >>> Stropped at kdb_enter +0x3b: movq $0,0xad6522(%rip) > >>> db> > >> > >> From what I've read on the list, it seems like you cannot boot the PVH= VM > >> kernel if you have a cdrom attached to the guest, could you try > >> disabling the cdrom and booting again? > >> > >> > > great how does one go about disabling the cdrom, i get some disk > parameters > > needs to be removed from the vm template before boot > > From owner-freebsd-xen@FreeBSD.ORG Thu May 23 17:41:54 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id F19346BD; Thu, 23 May 2013 17:41:54 +0000 (UTC) (envelope-from roger.pau@citrix.com) Received: from SMTP.EU.CITRIX.COM (smtp.eu.citrix.com [46.33.159.39]) by mx1.freebsd.org (Postfix) with ESMTP id 6E0EF2A3; Thu, 23 May 2013 17:41:53 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.87,729,1363132800"; d="scan'208";a="4914017" Received: from lonpex01cl01.citrite.net ([10.30.203.101]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 23 May 2013 17:41:52 +0000 Received: from [192.168.1.30] (10.30.203.1) by LONPEX01CL01.citrite.net (10.30.203.101) with Microsoft SMTP Server id 14.2.342.3; Thu, 23 May 2013 18:41:51 +0100 Message-ID: <519E54DE.5090304@citrix.com> Date: Thu, 23 May 2013 19:41:50 +0200 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: "freebsd-xen@freebsd.org" Subject: Re: FreeBSD PVHVM call for testing References: <519131D8.9010307@citrix.com> In-Reply-To: <519131D8.9010307@citrix.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.30.203.1] Cc: "xen-users@lists.xen.org" , "freebsd-virtualization@freebsd.org" , xen-devel X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 17:41:55 -0000 Hello, I've pushed a new branch, pvhvm_v10 that contains a PV IPI implementation for both amd64 and i386. I've also updated the wiki to point to the pvhvm_v10 branch: http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=shortlog;h=refs/heads/pvhvm_v10 I've updated my tree to latest HEAD, so now branch pvhvm_v10 is on top of this commit: commit b44da0fb82647f2cfb06f65a6695c7e36c98828c Author: gber Date: Thu May 23 12:24:46 2013 +0000 Rework and organize pmap_enter_locked() function. pmap_enter_locked() implementation was very ambiguous and confusing. Rearrange it so that each part of the mapping creation is separated. Avoid walking through the redundant conditions. Extract vector_page specific PTE setup from normal PTE setting. Submitted by: Zbigniew Bodek Sponsored by: The FreeBSD Foundation, Semihalf Thanks for the testing, Roger. From owner-freebsd-xen@FreeBSD.ORG Thu May 23 17:44:09 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C4D7B7A9 for ; Thu, 23 May 2013 17:44:09 +0000 (UTC) (envelope-from feld@feld.me) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id 96721319 for ; Thu, 23 May 2013 17:44:09 +0000 (UTC) Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 667AA20852 for ; Thu, 23 May 2013 13:44:07 -0400 (EDT) Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute3.internal (MEProxy); Thu, 23 May 2013 13:44:07 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=feld.me; h= content-type:to:subject:references:date:mime-version :content-transfer-encoding:from:message-id:in-reply-to; s= mesmtp; bh=LKicrGNGlf11FbKmHgUMx3v08Gw=; b=gAxk73NAnyolm/Xado+3b JK7Bw3XNRTWjR4dcHRhJSCndmBOu2fCIM8VoaPXXF+rEWfrWV0WRJ9XkLB7DFDnG tln8JaTO5WCwhw3dhHgoZC3iP5XkCuX6lPTK1V6uY+gCzgH8ozQLE/qNXZT2NFpM 5JTcLiRqLKFiDI5vU+BOa4= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:to:subject:references:date :mime-version:content-transfer-encoding:from:message-id :in-reply-to; s=smtpout; bh=LKicrGNGlf11FbKmHgUMx3v08Gw=; b=S+qv R/elky8QvmFis5ZgOWol8EfxFdHl6lplbU1C+oeHR+YW0V85dJJhOaP5H7q0JZ2s 7kXJLZcT406zvmGyqzxvuqYOU6RNv/F04Wpsvb6TLZMgZKrLzlJHcCO0Ku0feish kws7v/ndkQTXLoiThqPK/XVX+GCOlXvVwQ09Kzs= X-Sasl-enc: iQO9ow99OETXF0mSKnihI0RgEZjqvSWgbCDXMWwYiliS 1369331047 Received: from tech304.office.supranet.net (unknown [66.170.8.18]) by mail.messagingengine.com (Postfix) with ESMTPA id 32429200180 for ; Thu, 23 May 2013 13:44:07 -0400 (EDT) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: freebsd-xen@freebsd.org Subject: Re: FreeBSD PVHVM call for testing References: <519131D8.9010307@citrix.com> <616EE8A8-78BA-46E6-90AA-4A22160289DF@dckd.nl> <519E1AA6.2060808@citrix.com> <519E4850.1090305@citrix.com> <0BBCBA0B-F4A6-4775-A172-D051D9363665@dckd.nl> Date: Thu, 23 May 2013 12:44:06 -0500 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Mark Felder" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.15 (FreeBSD) X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 17:44:09 -0000 On Thu, 23 May 2013 12:29:34 -0500, Outback Dingo wrote: > > Thanks, but this is XCP not a generic XEN server where there are vm > config > files under /etc/xen/ in XCP they dont exists This should cover it http://support.citrix.com/article/CTX132411 From owner-freebsd-xen@FreeBSD.ORG Thu May 23 17:49:04 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8516FA95 for ; Thu, 23 May 2013 17:49:04 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) by mx1.freebsd.org (Postfix) with ESMTP id 520C636F for ; Thu, 23 May 2013 17:49:04 +0000 (UTC) Received: by mail-ob0-f182.google.com with SMTP id va2so4334943obc.13 for ; Thu, 23 May 2013 10:49:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ltWTj/Fz43rjr/wI/b1aF0DwYRzD+Kfzijnf3VY0+UQ=; b=KCILK9wmp6cIzjwf9Pzi7xqL0XQoopujkaKQ2b+Bv73SPc6+V9p55SoYFyxSixbaqD cTfvmfXL97UN0LqSeFqLoFAPmOstdT2l5+tmHPRE/Yq4r7T0bsMa+l2dFNlhY+cRcxr0 BtvpxZJnqCLHtHRFaLa4IC7yvdzsZ5/8Jax5edP/KLzOr8jcZAGFfdCJjqVcmAaZBEUA dv49MXSz/Uh6cgSujspGrUVkEvcq1+spxPjSPBsPblh3godA+txA6O4y1WSQ/Kl7A4T0 WYIQBKGzz4GAyyWNwrJMXgdfCL5hiVwlsVH2xM5DeCa7T+tQ4aAiKF17OKsHxBKn61AD 5HqA== MIME-Version: 1.0 X-Received: by 10.60.103.148 with SMTP id fw20mr8976158oeb.37.1369331343396; Thu, 23 May 2013 10:49:03 -0700 (PDT) Received: by 10.76.96.49 with HTTP; Thu, 23 May 2013 10:49:03 -0700 (PDT) In-Reply-To: References: <519131D8.9010307@citrix.com> <616EE8A8-78BA-46E6-90AA-4A22160289DF@dckd.nl> <519E1AA6.2060808@citrix.com> <519E4850.1090305@citrix.com> <0BBCBA0B-F4A6-4775-A172-D051D9363665@dckd.nl> Date: Thu, 23 May 2013 13:49:03 -0400 Message-ID: Subject: Re: FreeBSD PVHVM call for testing From: Outback Dingo To: Mark Felder Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 17:49:04 -0000 On Thu, May 23, 2013 at 1:44 PM, Mark Felder wrote: > On Thu, 23 May 2013 12:29:34 -0500, Outback Dingo > wrote: > > >> Thanks, but this is XCP not a generic XEN server where there are vm config >> files under /etc/xen/ in XCP they dont exists >> > > This should cover it > > http://support.citrix.com/**article/CTX132411 > > actually this tells you how to remove/eject the virtual iso, not the cdrom device from the VM itself in XCP > ______________________________**_________________ > 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 May 23 18:01:26 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2804F5AE for ; Thu, 23 May 2013 18:01:26 +0000 (UTC) (envelope-from bounces+73574-0602-freebsd-xen=freebsd.org@sendgrid.me) Received: from o3.shared.sendgrid.net (o3.shared.sendgrid.net [208.117.48.85]) by mx1.freebsd.org (Postfix) with SMTP id B9D6D68A for ; Thu, 23 May 2013 18:01:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.info; h=from :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpapi; bh=TlvGihTJifu9mqncmD/w5g cuB/4=; b=CXcBOsXDxrpVPCXRANeOBFN5tA2Q24wEF6WCI5t+ppDKoNpGRF/qKX 9z6sjHx1PxxokB0/9Fmswoukmc6ntTZaTGrrQ7nnpxjMKqZBYyUPYXBR/ypp6c45 lIMwOPrmcKSCSM1Qv5jKasxehZEKpDWTX27slrjuokrQ7ruBJpPUw= Received: by 10.16.240.26 with SMTP id mf103.23010.519E597413 Thu, 23 May 2013 18:01:24 +0000 (UTC) Received: from mail.tarsnap.com (unknown [10.60.208.15]) by mi18 (SG) with ESMTP id 13ed28d7000.1443.14e2e7 for ; Thu, 23 May 2013 13:01:24 -0500 (CST) Received: (qmail 27015 invoked from network); 23 May 2013 18:01:23 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by ec2-107-20-205-189.compute-1.amazonaws.com with ESMTP; 23 May 2013 18:01:23 -0000 Received: (qmail 5676 invoked from network); 23 May 2013 18:01:04 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by clamshell.daemonology.net with SMTP; 23 May 2013 18:01:04 -0000 Message-ID: <519E5960.40707@freebsd.org> Date: Thu, 23 May 2013 11:01:04 -0700 From: Colin Percival User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130406 Thunderbird/17.0.5 MIME-Version: 1.0 To: Jay West Subject: Re: tcp offloading References: <001901ce57be$192d3940$4b87abc0$@ezwind.net> In-Reply-To: <001901ce57be$192d3940$4b87abc0$@ezwind.net> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SG-EID: RUbAm5H8PjswBj/QH+sYVehaJogg3iBnZcyVi1bw/Iz/t9H7UeRbvmsQkpgiMRcODtNrFZBM3fvbX4t/zetqtkjdwmjlfIvTUVmo3EgDNJHZV6llsRsbLXuwQpki6X6p Cc: freebsd-xen@freebsd.org, Andre Oppermann X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 18:01:26 -0000 On 05/23/13 07:02, Jay West wrote: > Environment is Citrix Xenserver Advanced, with (mostly) freebsd 9.1 64bit > HVM with PV drivers. > > I've heard much mention around the net that in pretty much all cases, TCP > offloading should be disabled inside the VM. I have also seen other posts > that TCP offloading should be disabled on the Dom0. > > So my question is; for best performance should TCP offloading be disabled in > the VM, or the Xenserver (dom0), or should it be disabled in BOTH? There's an incompatibility between FreeBSD's TCP stack, TSO, and the Linux Xen netback driver: With TSO enabled on netfront, we can generate longer mbuf chains than the Linux netback is able to handle. I have an ugly patch for this on EC2, but andre will be fixing this better in the near future. For now I recommend # ifconfig xn0 -tso unless you need multi-Gbps networking performance. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid From owner-freebsd-xen@FreeBSD.ORG Thu May 23 18:16:42 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7C4F4126 for ; Thu, 23 May 2013 18:16:42 +0000 (UTC) (envelope-from feld@feld.me) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id 4B9C6850 for ; Thu, 23 May 2013 18:16:41 +0000 (UTC) Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 4333D20C6F; Thu, 23 May 2013 14:16:34 -0400 (EDT) Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute4.internal (MEProxy); Thu, 23 May 2013 14:16:39 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=feld.me; h= content-type:to:cc:subject:references:date:mime-version :content-transfer-encoding:from:message-id:in-reply-to; s= mesmtp; bh=9+xZr0bEJZRNqKACB+0cHX+DOaY=; b=Yhz53aCbcK0QZQXRqi4w+ 8XmA/IH9TyWls7Iph6N3E7NMtJosge3FZwS+kYor/P3Ps1DG/nfxrVzYQLHO4d1D agmbGOwE8UIAr1r87GvqjxmqXNH+FLOUVE35caZYY/CisX2J7mokLLsGs8TG83rk dHKMPH546uIinYUByE0y98= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:to:cc:subject:references :date:mime-version:content-transfer-encoding:from:message-id :in-reply-to; s=smtpout; bh=9+xZr0bEJZRNqKACB+0cHX+DOaY=; b=loKk rk5jxKlTEnwmcTr5yCPcef/czM03UzHK8fECxe0eL+QuRBemHe8VRbamvyzD+n4I jKUEt/cZ3zFev62QKx19z3Yh8O5gjLAV/kUORkxrZ73jSR2aIvawe3V436HGdRkT fUYPnviHdt61Abp0bqn5wKb9VPfuY8qUCalIrS4= X-Sasl-enc: CGYhA3b1XLynbhnJg07f/yxFCGDTthzv0kfj1eaRd8au 1369332994 Received: from tech304.office.supranet.net (unknown [66.170.8.18]) by mail.messagingengine.com (Postfix) with ESMTPA id A70A72001B4; Thu, 23 May 2013 14:16:34 -0400 (EDT) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: "Outback Dingo" Subject: Re: FreeBSD PVHVM call for testing References: <519131D8.9010307@citrix.com> <616EE8A8-78BA-46E6-90AA-4A22160289DF@dckd.nl> <519E1AA6.2060808@citrix.com> <519E4850.1090305@citrix.com> <0BBCBA0B-F4A6-4775-A172-D051D9363665@dckd.nl> Date: Thu, 23 May 2013 13:16:34 -0500 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Mark Felder" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.15 (FreeBSD) Cc: freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 18:16:42 -0000 On Thu, 23 May 2013 12:49:03 -0500, Outback Dingo wrote: > actually this tells you how to remove/eject the virtual iso, not the > cdrom > device from the VM itself in XCP > gah! you're completely right! However, the bottom picture with the red box showing "click here to create a dvd drive" is what you should see when you DO destroy the dvd drive device. It should be something like xe vbd-list vm-name-label=VM_NAME the device saying "empty (RO): TRUE is the dvd rom, get the uuid xe vbd-destroy uuid=uuid_of_that_device From owner-freebsd-xen@FreeBSD.ORG Thu May 23 19:09:41 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D1DD3E6 for ; Thu, 23 May 2013 19:09:41 +0000 (UTC) (envelope-from bounces+73574-0602-freebsd-xen=freebsd.org@sendgrid.me) Received: from o3.shared.sendgrid.net (o3.shared.sendgrid.net [208.117.48.85]) by mx1.freebsd.org (Postfix) with SMTP id CC7FFAA9 for ; Thu, 23 May 2013 19:09:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.info; h=from :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpapi; bh=RGyyWjrWYyxmFaErXWRib1 atsug=; b=UKBYvwMENojNZB0Y/oDKIbNp4Nh/F/+kSpj8VCx/2FkYSzfOxq23El P1gWZHio+wcLXXl3NGN5cJtLS+v9bDCrU0vKgP5eBGSuYon7Q9kCkzGieEZxQVS5 wMBa8hTkuOmB+aBdl4g1y9j1ynsTo/wMRkPvISCJragFaEOoYCXO4= Received: by 10.4.35.240 with SMTP id mf66.8037.519E69731 Thu, 23 May 2013 19:09:39 +0000 (UTC) Received: from mail.tarsnap.com (unknown [10.60.208.13]) by mi1 (SG) with ESMTP id 13ed2cbe8b3.7328.6fcf23 for ; Thu, 23 May 2013 14:09:38 -0500 (CST) Received: (qmail 29334 invoked from network); 23 May 2013 19:09:32 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by ec2-107-20-205-189.compute-1.amazonaws.com with ESMTP; 23 May 2013 19:09:32 -0000 Received: (qmail 5906 invoked from network); 23 May 2013 19:09:12 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by clamshell.daemonology.net with SMTP; 23 May 2013 19:09:12 -0000 Message-ID: <519E6958.6020606@freebsd.org> Date: Thu, 23 May 2013 12:09:12 -0700 From: Colin Percival User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130406 Thunderbird/17.0.5 MIME-Version: 1.0 To: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= Subject: Re: FreeBSD PVHVM call for testing References: <519131D8.9010307@citrix.com> <51952BAE.6010609@freebsd.org> <51957D42.9060801@citrix.com> <51959ED9.6040405@freebsd.org> <51974EC9.9030204@citrix.com> <5197A1EA.2040404@freebsd.org> <519CAFC7.1070908@citrix.com> <519D24A9.3050407@freebsd.org> <519DDC0A.9000201@citrix.com> In-Reply-To: <519DDC0A.9000201@citrix.com> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=UTF-8 content-transfer-encoding: quoted-printable X-SG-EID: RUbAm5H8PjswBj/QH+sYVehaJogg3iBnZcyVi1bw/Izk7O7RH6Ur+EZTC2oiHF2IJuynvFvQtI/EK/2EL6K4N2xuHjln6YGrn9MbneIwV1esApUdz/MpBawtyScGUVTA Cc: "freebsd-xen@freebsd.org" , xen-devel , "freebsd-virtualization@freebsd.org" , "xen-users@lists.xen.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 19:09:41 -0000 On 05/23/13 02:06, Roger Pau Monn=C3=A9 wrote:=0D > On 22/05/13 22:03, Colin Percival wrote:=0D >> Testing on a cr1.8xlarge EC2 instance, I get Xen 4.2, but it ends up wit= h=0D >> a panic -- console output below. I can get a backtrace and possibly eve= n=0D >> a dump if those would help.=0D > =0D > Thanks for the test, I've been using Xen 4.2 (and 4.3) without problems = =0D > so far. By looking at the Xen code, the only reason the timer setup =0D > could return -22 (EINVAL), is that we try to set the timer for a =0D > different vCPU than the one we are running on.=0D > =0D > I've been able to boot a 32 vCPU DomU on my 8way box using Xen 4.2.1 =0D > (using both qemu-xen and qemu-xen-traditional device models), so I'm =0D > unsure if this could be due to some patch Amazon applies to Xen. Could = =0D > you try the following patch and post the error message? I would like to = =0D > see if the cpuid reported by kdb and the vCPU that we are trying to set = =0D > the timer are the same.=0D =0D Looks like there's agreement about the cpuids here. Anything else I should= =0D try testing?=0D =0D SMAP type=3D01 base=3D0000000000000000 len=3D000000000009e000=0D SMAP type=3D02 base=3D000000000009e000 len=3D0000000000002000=0D SMAP type=3D02 base=3D00000000000e0000 len=3D0000000000020000=0D SMAP type=3D01 base=3D0000000000100000 len=3D00000000eff00000=0D SMAP type=3D02 base=3D00000000fc000000 len=3D0000000004000000=0D SMAP type=3D01 base=3D0000000100000000 len=3D0000003c19000000=0D Table 'FACP' at 0xfc014980=0D Table 'APIC' at 0xfc014a80=0D APIC: Found table at 0xfc014a80=0D APIC: Using the MADT enumerator.=0D MADT: Found CPU APIC ID 0 ACPI ID 0: enabled=0D SMP: Added CPU 0 (AP)=0D MADT: Found CPU APIC ID 2 ACPI ID 1: enabled=0D SMP: Added CPU 2 (AP)=0D MADT: Found CPU APIC ID 4 ACPI ID 2: enabled=0D SMP: Added CPU 4 (AP)=0D MADT: Found CPU APIC ID 6 ACPI ID 3: enabled=0D SMP: Added CPU 6 (AP)=0D MADT: Found CPU APIC ID 8 ACPI ID 4: enabled=0D SMP: Added CPU 8 (AP)=0D MADT: Found CPU APIC ID 10 ACPI ID 5: enabled=0D SMP: Added CPU 10 (AP)=0D MADT: Found CPU APIC ID 12 ACPI ID 6: enabled=0D SMP: Added CPU 12 (AP)=0D MADT: Found CPU APIC ID 14 ACPI ID 7: enabled=0D SMP: Added CPU 14 (AP)=0D MADT: Found CPU APIC ID 32 ACPI ID 8: enabled=0D SMP: Added CPU 32 (AP)=0D MADT: Found CPU APIC ID 34 ACPI ID 9: enabled=0D SMP: Added CPU 34 (AP)=0D MADT: Found CPU APIC ID 36 ACPI ID 10: enabled=0D SMP: Added CPU 36 (AP)=0D MADT: Found CPU APIC ID 38 ACPI ID 11: enabled=0D SMP: Added CPU 38 (AP)=0D MADT: Found CPU APIC ID 40 ACPI ID 12: enabled=0D SMP: Added CPU 40 (AP)=0D MADT: Found CPU APIC ID 42 ACPI ID 13: enabled=0D SMP: Added CPU 42 (AP)=0D MADT: Found CPU APIC ID 44 ACPI ID 14: enabled=0D SMP: Added CPU 44 (AP)=0D MADT: Found CPU APIC ID 46 ACPI ID 15: enabled=0D SMP: Added CPU 46 (AP)=0D MADT: Found CPU APIC ID 1 ACPI ID 16: enabled=0D SMP: Added CPU 1 (AP)=0D MADT: Found CPU APIC ID 3 ACPI ID 17: enabled=0D SMP: Added CPU 3 (AP)=0D MADT: Found CPU APIC ID 5 ACPI ID 18: enabled=0D SMP: Added CPU 5 (AP)=0D MADT: Found CPU APIC ID 7 ACPI ID 19: enabled=0D SMP: Added CPU 7 (AP)=0D MADT: Found CPU APIC ID 9 ACPI ID 20: enabled=0D SMP: Added CPU 9 (AP)=0D MADT: Found CPU APIC ID 11 ACPI ID 21: enabled=0D SMP: Added CPU 11 (AP)=0D MADT: Found CPU APIC ID 13 ACPI ID 22: enabled=0D SMP: Added CPU 13 (AP)=0D MADT: Found CPU APIC ID 15 ACPI ID 23: enabled=0D SMP: Added CPU 15 (AP)=0D MADT: Found CPU APIC ID 33 ACPI ID 24: enabled=0D SMP: Added CPU 33 (AP)=0D MADT: Found CPU APIC ID 35 ACPI ID 25: enabled=0D SMP: Added CPU 35 (AP)=0D MADT: Found CPU APIC ID 37 ACPI ID 26: enabled=0D SMP: Added CPU 37 (AP)=0D MADT: Found CPU APIC ID 39 ACPI ID 27: enabled=0D SMP: Added CPU 39 (AP)=0D MADT: Found CPU APIC ID 41 ACPI ID 28: enabled=0D SMP: Added CPU 41 (AP)=0D MADT: Found CPU APIC ID 43 ACPI ID 29: enabled=0D SMP: Added CPU 43 (AP)=0D MADT: Found CPU APIC ID 45 ACPI ID 30: enabled=0D SMP: Added CPU 45 (AP)=0D MADT: Found CPU APIC ID 47 ACPI ID 31: enabled=0D SMP: Added CPU 47 (AP)=0D MADT: Found CPU APIC ID 0 ACPI ID 32: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 33: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 34: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 35: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 36: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 37: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 38: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 39: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 40: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 41: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 42: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 43: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 44: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 45: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 46: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 47: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 48: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 49: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 50: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 51: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 52: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 53: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 54: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 55: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 56: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 57: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 58: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 59: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 60: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 61: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 62: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 63: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 64: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 65: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 66: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 67: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 68: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 69: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 70: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 71: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 72: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 73: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 74: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 75: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 76: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 77: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 78: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 79: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 80: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 81: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 82: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 83: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 84: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 85: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 86: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 87: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 88: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 89: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 90: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 91: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 92: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 93: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 94: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 95: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 96: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 97: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 98: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 99: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 100: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 101: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 102: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 103: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 104: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 105: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 106: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 107: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 108: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 109: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 110: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 111: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 112: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 113: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 114: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 115: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 116: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 117: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 118: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 119: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 120: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 121: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 122: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 123: disabled MADT: Found CPU APIC ID 0 ACPI ID 124: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 125: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 126: disabled=0D MADT: Found CPU APIC ID 0 ACPI ID 127: disabled=0D Copyright (c) 1992-2013 The FreeBSD Project.=0D Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994=0D The Regents of the University of California. All rights reserved.=0D FreeBSD is a registered trademark of The FreeBSD Foundation.=0D FreeBSD 10.0-CURRENT #2 r+9b25356-dirty: Thu May 23 18:49:22 UTC 2013=0D root@ip-10-148-177-216:/usr/obj/usr/src/sys/XENHVM amd64=0D FreeBSD clang version 3.3 (trunk 178860) 20130405=0D WARNING: WITNESS option enabled, expect reduced performance.=0D XEN: Hypervisor version 4.2 detected.=0D XEN: Disabling emulated block and network devices=0D Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff818ca000.=0D Hypervisor: Origin =3D "XenVMMXenVMM"=0D Calibrating TSC clock ... TSC clock: 2600046368 Hz=0D CPU: Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz (2600.05-MHz K8-class CPU)=0D Origin =3D "GenuineIntel" Id =3D 0x206d7 Family =3D 0x6 Model =3D 0x2d= Stepping =3D 7=0D =0D Features=3D0x1783fbff=0D =0D Features2=3D0x9fba2203=0D AMD Features=3D0x28100800=0D AMD Features2=3D0x1=0D real memory =3D 262144000000 (250000 MB)=0D Physical memory chunk(s):=0D 0x0000000000001000 - 0x0000000000099fff, 626688 bytes (153 pages)=0D 0x0000000000100000 - 0x00000000001fffff, 1048576 bytes (256 pages)=0D 0x00000000019e1000 - 0x00000000efffffff, 3999395840 bytes (976415 pages)=0D 0x0000000100000000 - 0x0000003b8ae37fff, 251438268416 bytes (61386296 pages= )=0D avail memory =3D 244393992192 (233072 MB)=0D Event timer "LAPIC" quality 400=0D ACPI APIC Table: =0D INTR: Adding local APIC 1 as a target=0D INTR: Adding local APIC 2 as a target=0D INTR: Adding local APIC 3 as a target=0D INTR: Adding local APIC 4 as a target=0D INTR: Adding local APIC 5 as a target=0D INTR: Adding local APIC 6 as a target=0D INTR: Adding local APIC 7 as a target=0D INTR: Adding local APIC 8 as a target=0D INTR: Adding local APIC 9 as a target=0D INTR: Adding local APIC 10 as a target=0D INTR: Adding local APIC 11 as a target=0D INTR: Adding local APIC 12 as a target=0D INTR: Adding local APIC 13 as a target=0D INTR: Adding local APIC 14 as a target=0D INTR: Adding local APIC 15 as a target=0D INTR: Adding local APIC 32 as a target=0D INTR: Adding local APIC 33 as a target=0D INTR: Adding local APIC 34 as a target=0D INTR: Adding local APIC 35 as a target=0D INTR: Adding local APIC 36 as a target=0D INTR: Adding local APIC 37 as a target=0D INTR: Adding local APIC 38 as a target=0D INTR: Adding local APIC 39 as a target=0D INTR: Adding local APIC 40 as a target=0D INTR: Adding local APIC 41 as a target=0D INTR: Adding local APIC 42 as a target=0D INTR: Adding local APIC 43 as a target=0D INTR: Adding local APIC 44 as a target=0D INTR: Adding local APIC 45 as a target=0D INTR: Adding local APIC 46 as a target=0D INTR: Adding local APIC 47 as a target=0D FreeBSD/SMP: Multiprocessor System Detected: 32 CPUs=0D FreeBSD/SMP: 2 package(s) x 8 core(s) x 2 SMT threads=0D cpu0 (BSP): APIC ID: 0=0D cpu1 (AP): APIC ID: 1=0D cpu2 (AP): APIC ID: 2=0D cpu3 (AP): APIC ID: 3=0D cpu4 (AP): APIC ID: 4=0D cpu5 (AP): APIC ID: 5=0D cpu6 (AP): APIC ID: 6=0D cpu7 (AP): APIC ID: 7=0D cpu8 (AP): APIC ID: 8=0D cpu9 (AP): APIC ID: 9=0D cpu10 (AP): APIC ID: 10=0D cpu11 (AP): APIC ID: 11=0D cpu12 (AP): APIC ID: 12=0D cpu13 (AP): APIC ID: 13=0D cpu14 (AP): APIC ID: 14=0D cpu15 (AP): APIC ID: 15=0D cpu16 (AP): APIC ID: 32=0D cpu17 (AP): APIC ID: 33=0D cpu18 (AP): APIC ID: 34=0D cpu19 (AP): APIC ID: 35=0D cpu20 (AP): APIC ID: 36=0D cpu21 (AP): APIC ID: 37=0D cpu22 (AP): APIC ID: 38=0D cpu23 (AP): APIC ID: 39=0D cpu24 (AP): APIC ID: 40=0D cpu25 (AP): APIC ID: 41=0D cpu26 (AP): APIC ID: 42=0D cpu27 (AP): APIC ID: 43=0D cpu28 (AP): APIC ID: 44=0D cpu29 (AP): APIC ID: 45=0D cpu30 (AP): APIC ID: 46=0D cpu31 (AP): APIC ID: 47=0D APIC: CPU 0 has ACPI ID 0=0D APIC: CPU 1 has ACPI ID 16=0D APIC: CPU 2 has ACPI ID 1=0D APIC: CPU 3 has ACPI ID 17=0D APIC: CPU 4 has ACPI ID 2=0D APIC: CPU 5 has ACPI ID 18=0D APIC: CPU 6 has ACPI ID 3=0D APIC: CPU 7 has ACPI ID 19=0D APIC: CPU 8 has ACPI ID 4=0D APIC: CPU 9 has ACPI ID 20=0D APIC: CPU 10 has ACPI ID 5=0D APIC: CPU 11 has ACPI ID 21=0D APIC: CPU 12 has ACPI ID 6=0D APIC: CPU 13 has ACPI ID 22=0D APIC: CPU 14 has ACPI ID 7=0D APIC: CPU 15 has ACPI ID 23=0D APIC: CPU 16 has ACPI ID 8=0D APIC: CPU 17 has ACPI ID 24=0D APIC: CPU 18 has ACPI ID 9=0D APIC: CPU 19 has ACPI ID 25=0D APIC: CPU 20 has ACPI ID 10=0D APIC: CPU 21 has ACPI ID 26=0D APIC: CPU 22 has ACPI ID 11=0D APIC: CPU 23 has ACPI ID 27=0D APIC: CPU 24 has ACPI ID 12=0D APIC: CPU 25 has ACPI ID 28=0D APIC: CPU 26 has ACPI ID 13=0D APIC: CPU 27 has ACPI ID 29=0D APIC: CPU 28 has ACPI ID 14=0D APIC: CPU 29 has ACPI ID 30=0D APIC: CPU 30 has ACPI ID 15=0D APIC: CPU 31 has ACPI ID 31=0D x86bios: IVT 0x000000-0x0004ff at 0xfffffe0000000000=0D x86bios: SSEG 0x001000-0x001fff at 0xffffff80005e3000=0D x86bios: EBDA 0x09f000-0x09ffff at 0xfffffe000009f000=0D x86bios: ROM 0x0a0000-0x0fefff at 0xfffffe00000a0000=0D random device not loaded; using insecure entropy=0D ULE: setup cpu 0=0D ULE: setup cpu 1=0D ULE: setup cpu 2=0D ULE: setup cpu 3=0D ULE: setup cpu 4=0D ULE: setup cpu 5=0D ULE: setup cpu 6=0D ULE: setup cpu 7=0D ULE: setup cpu 8=0D ULE: setup cpu 9=0D ULE: setup cpu 10=0D ULE: setup cpu 11=0D ULE: setup cpu 12=0D ULE: setup cpu 13=0D ULE: setup cpu 14=0D ULE: setup cpu 15=0D ULE: setup cpu 16=0D ULE: setup cpu 17=0D ULE: setup cpu 18=0D ULE: setup cpu 19=0D ULE: setup cpu 20=0D ULE: setup cpu 21=0D ULE: setup cpu 22=0D ULE: setup cpu 23=0D ULE: setup cpu 24=0D ULE: setup cpu 25=0D ULE: setup cpu 26=0D ULE: setup cpu 27=0D ULE: setup cpu 28=0D ULE: setup cpu 29=0D ULE: setup cpu 30=0D ULE: setup cpu 31=0D ACPI: RSDP 0xea020 00024 (v02 Xen)=0D ACPI: XSDT 0xfc015920 0005C (v01 Xen HVM 00000000 HVML 00000000)=0D ACPI: FACP 0xfc014980 000F4 (v04 Xen HVM 00000000 HVML 00000000)=0D ACPI: DSDT 0xfc0035e0 11315 (v02 Xen HVM 00000000 INTL 20090123)=0D ACPI: FACS 0xfc0035a0 00040=0D ACPI: APIC 0xfc014a80 00460 (v02 Xen HVM 00000000 HVML 00000000)=0D ACPI: SRAT 0xfc014f60 008A8 (v01 Xen HVM 00000000 HVML 00000000)=0D ACPI: HPET 0xfc015830 00038 (v01 Xen HVM 00000000 HVML 00000000)=0D ACPI: WAET 0xfc015870 00028 (v01 Xen HVM 00000000 HVML 00000000)=0D ACPI: SSDT 0xfc0158a0 00031 (v02 Xen HVM 00000000 INTL 20090123)=0D ACPI: SSDT 0xfc0158e0 00031 (v02 Xen HVM 00000000 INTL 20090123)=0D MADT: Found IO APIC ID 1, Interrupt 0 at 0xfec00000=0D ioapic0: Changing APIC ID to 1=0D ioapic0: Routing external 8259A's -> intpin 0=0D MADT: Interrupt override: source 0, irq 2=0D ioapic0: Routing IRQ 0 -> intpin 2=0D MADT: Interrupt override: source 5, irq 5=0D ioapic0: intpin 5 trigger: level=0D ioapic0: intpin 5 polarity: low=0D MADT: Interrupt override: source 10, irq 10=0D ioapic0: intpin 10 trigger: level=0D ioapic0: intpin 10 polarity: low=0D MADT: Interrupt override: source 11, irq 11=0D ioapic0: intpin 11 trigger: level=0D ioapic0: intpin 11 polarity: low=0D MADT: Forcing active-low polarity and level trigger for SCI=0D ioapic0: intpin 9 polarity: low=0D ioapic0: intpin 9 trigger: level=0D ioapic0 irqs 0-47 on motherboard=0D cpu0 BSP:=0D ID: 0x00000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D wlan: <802.11 Link Layer>=0D Event-channel device installed.=0D snd_unit_init() u=3D0x00ff8000 [512] d=3D0x00007c00 [32] c=3D0x000003ff [10= 24]=0D feeder_register: snd_unit=3D-1 snd_maxautovchans=3D16 latency=3D5 feeder_ra= te_min=3D1=0D feeder_rate_max=3D2016000 feeder_rate_round=3D25=0D kbd: new array size 4=0D kbd1 at kbdmux0=0D mem: =0D nfslock: pseudo-device=0D null: =0D random: =0D VESA: INT 0x10 vector 0xc000:0x836e=0D VESA: information block=0D 0000 56 45 53 41 00 02 f5 82 00 c0 00 00 00 00 40 00=0D 0010 00 02 40 00 00 01 f5 82 00 c0 f5 82 00 c0 0e 83=0D 0020 00 c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0040 01 01 10 01 11 01 12 01 03 01 13 01 14 01 15 01 0050 05 01 16 01 17 01 18 01 07 01 19 01 1a 01 ff ff=0D 0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 00c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 00d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 00e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 00f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0110 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0120 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0130 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0140 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0150 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0160 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0170 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0180 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 0190 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 01a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 01b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 01c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 01d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 01e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D 01f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00=0D VESA: 15 mode(s) found=0D VESA: v2.0, 4096k memory, flags:0x0, mode table:0xffffff80005fd040 (2000040= )=0D VESA: VGABIOS Cirrus extension=0D VESA: VGABIOS Cirrus extension VGABIOS Cirrus extension 1.0=0D io: =0D hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2=0D hpt27xx: RocketRAID 27xx controller driver v1.0=0D xen_et0: on motherboard=0D Event timer "XENTIMER" frequency 1000000000 Hz quality 950=0D Timecounter "XENTIMER" frequency 1000000000 Hz quality 950=0D xen_et0: registered as a time-of-day clock (resolution 10000000us, adjustme= nt=0D 5.000000000s)=0D acpi0: on motherboard=0D ACPI: All ACPI Tables successfully acquired=0D ioapic0: routing intpin 9 (ISA IRQ 9) to lapic 0 vector 48=0D acpi0: Power Button (fixed)=0D acpi0: Sleep Button (fixed)=0D acpi0: reservation of 0, a0000 (3) failed=0D cpu0: Processor \_SB_.PR00 (ACPI ID 0) -> APIC ID 0=0D cpu0: on acpi0=0D cpu0: switching to generic Cx mode=0D cpu1: Processor \_SB_.PR01 (ACPI ID 1) -> APIC ID 2=0D cpu1: on acpi0=0D cpu2: Processor \_SB_.PR02 (ACPI ID 2) -> APIC ID 4=0D cpu2: on acpi0=0D cpu3: Processor \_SB_.PR03 (ACPI ID 3) -> APIC ID 6=0D cpu3: on acpi0=0D cpu4: Processor \_SB_.PR04 (ACPI ID 4) -> APIC ID 8=0D cpu4: on acpi0=0D cpu5: Processor \_SB_.PR05 (ACPI ID 5) -> APIC ID 10=0D cpu5: on acpi0=0D cpu6: Processor \_SB_.PR06 (ACPI ID 6) -> APIC ID 12=0D cpu6: on acpi0=0D cpu7: Processor \_SB_.PR07 (ACPI ID 7) -> APIC ID 14=0D cpu7: on acpi0=0D cpu8: Processor \_SB_.PR08 (ACPI ID 8) -> APIC ID 16=0D cpu8: on acpi0=0D cpu9: Processor \_SB_.PR09 (ACPI ID 9) -> APIC ID 18=0D cpu9: on acpi0=0D cpu10: Processor \_SB_.PR0A (ACPI ID 10) -> APIC ID 20=0D cpu10: on acpi0=0D cpu11: Processor \_SB_.PR0B (ACPI ID 11) -> APIC ID 22=0D cpu11: on acpi0=0D cpu12: Processor \_SB_.PR0C (ACPI ID 12) -> APIC ID 24=0D cpu12: on acpi0=0D cpu13: Processor \_SB_.PR0D (ACPI ID 13) -> APIC ID 26=0D cpu13: on acpi0=0D cpu14: Processor \_SB_.PR0E (ACPI ID 14) -> APIC ID 28=0D cpu14: on acpi0=0D cpu15: Processor \_SB_.PR0F (ACPI ID 15) -> APIC ID 30=0D cpu15: on acpi0=0D cpu16: Processor \_SB_.PR10 (ACPI ID 16) -> APIC ID 1=0D cpu16: on acpi0=0D cpu17: Processor \_SB_.PR11 (ACPI ID 17) -> APIC ID 3=0D cpu17: on acpi0=0D cpu18: Processor \_SB_.PR12 (ACPI ID 18) -> APIC ID 5=0D cpu18: on acpi0=0D cpu19: Processor \_SB_.PR13 (ACPI ID 19) -> APIC ID 7=0D cpu19: on acpi0=0D cpu20: Processor \_SB_.PR14 (ACPI ID 20) -> APIC ID 9=0D cpu20: on acpi0=0D cpu21: Processor \_SB_.PR15 (ACPI ID 21) -> APIC ID 11=0D cpu21: on acpi0=0D cpu22: Processor \_SB_.PR16 (ACPI ID 22) -> APIC ID 13=0D cpu22: on acpi0=0D cpu23: Processor \_SB_.PR17 (ACPI ID 23) -> APIC ID 15=0D cpu23: on acpi0=0D cpu24: Processor \_SB_.PR18 (ACPI ID 24) -> APIC ID 17=0D cpu24: on acpi0=0D cpu25: Processor \_SB_.PR19 (ACPI ID 25) -> APIC ID 19=0D cpu25: on acpi0=0D cpu26: Processor \_SB_.PR1A (ACPI ID 26) -> APIC ID 21=0D cpu26: on acpi0=0D cpu27: Processor \_SB_.PR1B (ACPI ID 27) -> APIC ID 23=0D cpu27: on acpi0=0D cpu28: Processor \_SB_.PR1C (ACPI ID 28) -> APIC ID 25=0D cpu28: on acpi0=0D cpu29: Processor \_SB_.PR1D (ACPI ID 29) -> APIC ID 27=0D cpu29: on acpi0=0D cpu30: Processor \_SB_.PR1E (ACPI ID 30) -> APIC ID 29=0D cpu30: on acpi0=0D cpu31: Processor \_SB_.PR1F (ACPI ID 31) -> APIC ID 31=0D cpu31: on acpi0=0D ACPI: Processor \_SB_.PR20 (ACPI ID 32) ignored=0D ACPI: Processor \_SB_.PR21 (ACPI ID 33) ignored=0D ACPI: Processor \_SB_.PR22 (ACPI ID 34) ignored=0D ACPI: Processor \_SB_.PR23 (ACPI ID 35) ignored=0D ACPI: Processor \_SB_.PR24 (ACPI ID 36) ignored=0D ACPI: Processor \_SB_.PR25 (ACPI ID 37) ignored=0D ACPI: Processor \_SB_.PR26 (ACPI ID 38) ignored=0D ACPI: Processor \_SB_.PR27 (ACPI ID 39) ignored=0D ACPI: Processor \_SB_.PR28 (ACPI ID 40) ignored=0D ACPI: Processor \_SB_.PR29 (ACPI ID 41) ignored=0D ACPI: Processor \_SB_.PR2A (ACPI ID 42) ignored=0D ACPI: Processor \_SB_.PR2B (ACPI ID 43) ignored=0D ACPI: Processor \_SB_.PR2C (ACPI ID 44) ignored=0D ACPI: Processor \_SB_.PR2D (ACPI ID 45) ignored=0D ACPI: Processor \_SB_.PR2E (ACPI ID 46) ignored=0D ACPI: Processor \_SB_.PR2F (ACPI ID 47) ignored=0D ACPI: Processor \_SB_.PR30 (ACPI ID 48) ignored=0D ACPI: Processor \_SB_.PR31 (ACPI ID 49) ignored=0D ACPI: Processor \_SB_.PR32 (ACPI ID 50) ignored=0D ACPI: Processor \_SB_.PR33 (ACPI ID 51) ignored=0D ACPI: Processor \_SB_.PR34 (ACPI ID 52) ignored=0D ACPI: Processor \_SB_.PR35 (ACPI ID 53) ignored=0D ACPI: Processor \_SB_.PR36 (ACPI ID 54) ignored=0D ACPI: Processor \_SB_.PR37 (ACPI ID 55) ignored=0D ACPI: Processor \_SB_.PR38 (ACPI ID 56) ignored=0D ACPI: Processor \_SB_.PR39 (ACPI ID 57) ignored=0D ACPI: Processor \_SB_.PR3A (ACPI ID 58) ignored=0D ACPI: Processor \_SB_.PR3B (ACPI ID 59) ignored=0D ACPI: Processor \_SB_.PR3C (ACPI ID 60) ignored=0D ACPI: Processor \_SB_.PR3D (ACPI ID 61) ignored=0D ACPI: Processor \_SB_.PR3E (ACPI ID 62) ignored=0D ACPI: Processor \_SB_.PR3F (ACPI ID 63) ignored=0D ACPI: Processor \_SB_.PR40 (ACPI ID 64) ignored=0D ACPI: Processor \_SB_.PR41 (ACPI ID 65) ignored=0D ACPI: Processor \_SB_.PR42 (ACPI ID 66) ignored=0D ACPI: Processor \_SB_.PR43 (ACPI ID 67) ignored=0D ACPI: Processor \_SB_.PR44 (ACPI ID 68) ignored=0D ACPI: Processor \_SB_.PR45 (ACPI ID 69) ignored=0D ACPI: Processor \_SB_.PR46 (ACPI ID 70) ignored=0D ACPI: Processor \_SB_.PR47 (ACPI ID 71) ignored=0D ACPI: Processor \_SB_.PR48 (ACPI ID 72) ignored=0D ACPI: Processor \_SB_.PR49 (ACPI ID 73) ignored=0D ACPI: Processor \_SB_.PR4A (ACPI ID 74) ignored=0D ACPI: Processor \_SB_.PR4B (ACPI ID 75) ignored=0D ACPI: Processor \_SB_.PR4C (ACPI ID 76) ignored=0D ACPI: Processor \_SB_.PR4D (ACPI ID 77) ignored=0D ACPI: Processor \_SB_.PR4E (ACPI ID 78) ignored=0D ACPI: Processor \_SB_.PR4F (ACPI ID 79) ignored=0D ACPI: Processor \_SB_.PR50 (ACPI ID 80) ignored=0D ACPI: Processor \_SB_.PR51 (ACPI ID 81) ignored=0D ACPI: Processor \_SB_.PR52 (ACPI ID 82) ignored=0D ACPI: Processor \_SB_.PR53 (ACPI ID 83) ignored=0D ACPI: Processor \_SB_.PR54 (ACPI ID 84) ignored=0D ACPI: Processor \_SB_.PR55 (ACPI ID 85) ignored=0D ACPI: Processor \_SB_.PR56 (ACPI ID 86) ignored=0D ACPI: Processor \_SB_.PR57 (ACPI ID 87) ignored=0D ACPI: Processor \_SB_.PR58 (ACPI ID 88) ignored=0D ACPI: Processor \_SB_.PR59 (ACPI ID 89) ignored=0D ACPI: Processor \_SB_.PR5A (ACPI ID 90) ignored=0D ACPI: Processor \_SB_.PR5B (ACPI ID 91) ignored=0D ACPI: Processor \_SB_.PR5C (ACPI ID 92) ignored=0D ACPI: Processor \_SB_.PR5D (ACPI ID 93) ignored=0D ACPI: Processor \_SB_.PR5E (ACPI ID 94) ignored=0D ACPI: Processor \_SB_.PR5F (ACPI ID 95) ignored=0D ACPI: Processor \_SB_.PR60 (ACPI ID 96) ignored=0D ACPI: Processor \_SB_.PR61 (ACPI ID 97) ignored ACPI: Processor \_SB_.PR62 (ACPI ID 98) ignored=0D ACPI: Processor \_SB_.PR63 (ACPI ID 99) ignored=0D ACPI: Processor \_SB_.PR64 (ACPI ID 100) ignored=0D ACPI: Processor \_SB_.PR65 (ACPI ID 101) ignored=0D ACPI: Processor \_SB_.PR66 (ACPI ID 102) ignored=0D ACPI: Processor \_SB_.PR67 (ACPI ID 103) ignored=0D ACPI: Processor \_SB_.PR68 (ACPI ID 104) ignored=0D ACPI: Processor \_SB_.PR69 (ACPI ID 105) ignored=0D ACPI: Processor \_SB_.PR6A (ACPI ID 106) ignored=0D ACPI: Processor \_SB_.PR6B (ACPI ID 107) ignored=0D ACPI: Processor \_SB_.PR6C (ACPI ID 108) ignored=0D ACPI: Processor \_SB_.PR6D (ACPI ID 109) ignored=0D ACPI: Processor \_SB_.PR6E (ACPI ID 110) ignored=0D ACPI: Processor \_SB_.PR6F (ACPI ID 111) ignored=0D ACPI: Processor \_SB_.PR70 (ACPI ID 112) ignored=0D ACPI: Processor \_SB_.PR71 (ACPI ID 113) ignored=0D ACPI: Processor \_SB_.PR72 (ACPI ID 114) ignored=0D ACPI: Processor \_SB_.PR73 (ACPI ID 115) ignored=0D ACPI: Processor \_SB_.PR74 (ACPI ID 116) ignored=0D ACPI: Processor \_SB_.PR75 (ACPI ID 117) ignored=0D ACPI: Processor \_SB_.PR76 (ACPI ID 118) ignored=0D ACPI: Processor \_SB_.PR77 (ACPI ID 119) ignored=0D ACPI: Processor \_SB_.PR78 (ACPI ID 120) ignored=0D ACPI: Processor \_SB_.PR79 (ACPI ID 121) ignored=0D ACPI: Processor \_SB_.PR7A (ACPI ID 122) ignored=0D ACPI: Processor \_SB_.PR7B (ACPI ID 123) ignored=0D ACPI: Processor \_SB_.PR7C (ACPI ID 124) ignored=0D ACPI: Processor \_SB_.PR7D (ACPI ID 125) ignored=0D ACPI: Processor \_SB_.PR7E (ACPI ID 126) ignored=0D ACPI: Processor \_SB_.PR7F (ACPI ID 127) ignored=0D hpet0: iomem 0xfed00000-0xfed003ff on acpi0=0D hpet0: vendor 0x8086, rev 0x1, 62500000Hz 64bit, 3 timers, legacy route=0D hpet0: t0: irqs 0x00f00000 (0), 64bit, periodic=0D hpet0: t1: irqs 0x00f00000 (0), 64bit, periodic=0D hpet0: t2: irqs 0x00f00000 (0), 64bit, periodic=0D Timecounter "HPET" frequency 62500000 Hz quality 950=0D attimer0: port 0x40-0x43 irq 0 on acpi0=0D Timecounter "i8254" frequency 1193182 Hz quality 0=0D ioapic0: routing intpin 2 (ISA IRQ 0) to lapic 0 vector 49=0D Event timer "i8254" frequency 1193182 Hz quality 100=0D atrtc0: port 0x70-0x71 irq 8 on acpi0=0D atrtc0: not installed as time-of-day clock: clock xen_et has higher resolut= ion=0D ioapic0: routing intpin 8 (ISA IRQ 8) to lapic 0 vector 50=0D Event timer "RTC" frequency 32768 Hz quality 0=0D ACPI timer: 1/20 1/19 1/19 1/20 1/19 1/23 1/20 1/19 1/18 1/17 -> 10=0D Timecounter "ACPI-fast" frequency 3579545 Hz quality 900=0D acpi_timer0: <32-bit timer at 3.579545MHz> port 0xb008-0xb00b on acpi0=0D pci_link0: Index IRQ Rtd Ref IRQs=0D Initial Probe 0 5 N 0 5 10 11=0D Validation 0 5 N 0 5 10 11=0D After Disable 0 255 N 0 5 10 11=0D pci_link1: Index IRQ Rtd Ref IRQs=0D Initial Probe 0 10 N 0 5 10 11=0D Validation 0 10 N 0 5 10 11=0D After Disable 0 255 N 0 5 10 11=0D pci_link2: Index IRQ Rtd Ref IRQs=0D Initial Probe 0 11 N 0 5 10 11=0D Validation 0 11 N 0 5 10 11=0D After Disable 0 255 N 0 5 10 11=0D pci_link3: Index IRQ Rtd Ref IRQs=0D Initial Probe 0 5 N 0 5 10 11=0D Validation 0 5 N 0 5 10 11=0D After Disable 0 255 N 0 5 10 11=0D pcib0: port 0xcf8-0xcff on acpi0=0D pcib0: decoding 4 range 0-0xcf7=0D pcib0: decoding 4 range 0xd00-0xffff=0D pcib0: decoding 3 range 0xa0000-0xbffff=0D pcib0: decoding 3 range 0xf0000000-0xfbffffff=0D pci0: on pcib0=0D pci0: domain=3D0, physical bus=3D0=0D found-> vendor=3D0x8086, dev=3D0x1237, revid=3D0x02=0D domain=3D0, bus=3D0, slot=3D0, func=3D0=0D class=3D06-00-00, hdrtype=3D0x00, mfdev=3D0=0D cmdreg=3D0x0004, statreg=3D0x0000, cachelnsz=3D0 (dwords)=0D lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns)=0D found-> vendor=3D0x8086, dev=3D0x7000, revid=3D0x00=0D domain=3D0, bus=3D0, slot=3D1, func=3D0=0D class=3D06-01-00, hdrtype=3D0x00, mfdev=3D1=0D cmdreg=3D0x0007, statreg=3D0x0200, cachelnsz=3D0 (dwords)=0D lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns)=0D found-> vendor=3D0x8086, dev=3D0x7010, revid=3D0x00=0D domain=3D0, bus=3D0, slot=3D1, func=3D1=0D class=3D01-01-80, hdrtype=3D0x00, mfdev=3D0=0D cmdreg=3D0x0005, statreg=3D0x0280, cachelnsz=3D0 (dwords)=0D lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns)=0D pcib0: allocated type 4 (0x1f0-0x1f7) for rid 10 of pci0:0:1:1=0D pcib0: allocated type 4 (0x3f6-0x3f6) for rid 14 of pci0:0:1:1=0D pcib0: allocated type 4 (0x170-0x177) for rid 18 of pci0:0:1:1=0D pcib0: allocated type 4 (0x376-0x376) for rid 1c of pci0:0:1:1=0D map[20]: type I/O Port, range 32, base 0xc100, size 4, enabled=0D pcib0: allocated type 4 (0xc100-0xc10f) for rid 20 of pci0:0:1:1=0D found-> vendor=3D0x8086, dev=3D0x7113, revid=3D0x01=0D domain=3D0, bus=3D0, slot=3D1, func=3D3=0D class=3D06-80-00, hdrtype=3D0x00, mfdev=3D0=0D cmdreg=3D0x0004, statreg=3D0x0000, cachelnsz=3D0 (dwords)=0D lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns)=0D intpin=3Da, irq=3D10=0D pcib0: matched entry for 0.1.INTA=0D pcib0: slot 1 INTA hardwired to IRQ 20=0D found-> vendor=3D0x1013, dev=3D0x00b8, revid=3D0x00=0D domain=3D0, bus=3D0, slot=3D2, func=3D0=0D class=3D03-00-00, hdrtype=3D0x00, mfdev=3D0=0D cmdreg=3D0x0007, statreg=3D0x0000, cachelnsz=3D0 (dwords)=0D lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns)=0D map[10]: type Prefetchable Memory, range 32, base 0xf0000000, size 25, ena= bled=0D pcib0: allocated type 3 (0xf0000000-0xf1ffffff) for rid 10 of pci0:0:2:0=0D map[14]: type Memory, range 32, base 0xf3000000, size 12, enabled=0D pcib0: allocated type 3 (0xf3000000-0xf3000fff) for rid 14 of pci0:0:2:0=0D found-> vendor=3D0x5853, dev=3D0x0001, revid=3D0x01=0D domain=3D0, bus=3D0, slot=3D3, func=3D0=0D class=3Dff-80-00, hdrtype=3D0x00, mfdev=3D0=0D cmdreg=3D0x0007, statreg=3D0x0000, cachelnsz=3D0 (dwords)=0D lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns)=0D intpin=3Da, irq=3D5=0D map[10]: type I/O Port, range 32, base 0xc000, size 8, enabled=0D pcib0: allocated type 4 (0xc000-0xc0ff) for rid 10 of pci0:0:3:0=0D map[14]: type Prefetchable Memory, range 32, base 0xf2000000, size 24, ena= bled=0D pcib0: allocated type 3 (0xf2000000-0xf2ffffff) for rid 14 of pci0:0:3:0=0D pcib0: matched entry for 0.3.INTA=0D pcib0: slot 3 INTA hardwired to IRQ 28=0D isab0: at device 1.0 on pci0=0D isa0: on isab0=0D atapci0: port=0D 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc100-0xc10f at device 1.1 on pci0=0D ata0: at channel 0 on atapci0=0D ioapic0: routing intpin 14 (ISA IRQ 14) to lapic 0 vector 51=0D ata1: at channel 1 on atapci0=0D ioapic0: routing intpin 15 (ISA IRQ 15) to lapic 0 vector 52=0D pci0: at device 1.3 (no driver attached)=0D vgapci0: mem=0D 0xf0000000-0xf1ffffff,0xf3000000-0xf3000fff at device 2.0 on pci0=0D xenpci0: port 0xc000-0xc0ff mem 0xf2000000-0xf2ffffff= irq=0D 28 at device 3.0 on pci0=0D ioapic0: routing intpin 28 (PCI IRQ 28) to lapic 0 vector 53=0D xenstore0: on xenpci0=0D Grant table initialized=0D psmcpnp0: irq 12 on acpi0=0D atkbdc0: port 0x60,0x64 irq 1 on acpi0=0D atkbd0: irq 1 on atkbdc0=0D atkbd: the current kbd controller command byte 0061=0D atkbd: keyboard ID 0x41ab (2)=0D kbdc: RESET_KBD return code:00fa=0D kbdc: RESET_KBD status:00aa=0D kbd0 at atkbd0=0D kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x1d0000=0D ioapic0: routing intpin 1 (ISA IRQ 1) to lapic 0 vector 54=0D atkbd0: [GIANT-LOCKED]=0D psm0: current command byte:0061=0D kbdc: TEST_AUX_PORT status:0000=0D kbdc: RESET_AUX return code:00fa=0D kbdc: RESET_AUX status:00aa=0D kbdc: RESET_AUX ID:0000=0D kbdc: RESET_AUX return code:00fa=0D kbdc: RESET_AUX status:00aa=0D kbdc: RESET_AUX ID:0000=0D psm: status 00 02 64=0D psm: status 00 00 64=0D psm: status 00 03 64=0D psm: status 00 03 64=0D psm: data 08 00 00=0D psm: status 00 02 64=0D psm0: irq 12 on atkbdc0=0D ioapic0: routing intpin 12 (ISA IRQ 12) to lapic 0 vector 55=0D psm0: [GIANT-LOCKED]=0D psm0: model IntelliMouse Explorer, device ID 4-00, 5 buttons=0D psm0: config:00000000, flags:00000008, packet size:4=0D psm0: syncmask:08, syncbits:00=0D fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0= =0D fdc0: does not respond=0D device_attach: fdc0 attach returned 6=0D uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 ioapic0: routing intpin 4 (ISA IRQ 4) to lapic 0 vector 56=0D uart0: fast interrupt=0D uart0: console (9600,n,8,1)=0D ACPI: Enabled 2 GPEs in block 00 to 0F=0D acpi0: wakeup code va 0xffffffc2ce049000 pa 0x30000=0D ahc_isa_identify 0: ioport 0xc00 alloc failed=0D ahc_isa_identify 1: ioport 0x1c00 alloc failed=0D ahc_isa_identify 2: ioport 0x2c00 alloc failed=0D ahc_isa_identify 3: ioport 0x3c00 alloc failed=0D ahc_isa_identify 4: ioport 0x4c00 alloc failed=0D ahc_isa_identify 5: ioport 0x5c00 alloc failed=0D ahc_isa_identify 6: ioport 0x6c00 alloc failed=0D ahc_isa_identify 7: ioport 0x7c00 alloc failed=0D ahc_isa_identify 8: ioport 0x8c00 alloc failed=0D ahc_isa_identify 9: ioport 0x9c00 alloc failed=0D ahc_isa_identify 10: ioport 0xac00 alloc failed=0D ahc_isa_identify 11: ioport 0xbc00 alloc failed=0D ahc_isa_identify 12: ioport 0xcc00 alloc failed=0D ahc_isa_identify 13: ioport 0xdc00 alloc failed=0D ahc_isa_identify 14: ioport 0xec00 alloc failed=0D pcib0: allocated type 3 (0xa0000-0xa07ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa0800-0xa0fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa1000-0xa17ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa1800-0xa1fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa2000-0xa27ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa2800-0xa2fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa3000-0xa37ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa3800-0xa3fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa4000-0xa47ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa4800-0xa4fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa5000-0xa57ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa5800-0xa5fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa6000-0xa67ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa6800-0xa6fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa7000-0xa77ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa7800-0xa7fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa8000-0xa87ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa8800-0xa8fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa9000-0xa97ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xa9800-0xa9fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xaa000-0xaa7ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xaa800-0xaafff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xab000-0xab7ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xab800-0xabfff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xac000-0xac7ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xac800-0xacfff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xad000-0xad7ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xad800-0xadfff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xae000-0xae7ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xae800-0xaefff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xaf000-0xaf7ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xaf800-0xaffff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb0000-0xb07ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb0800-0xb0fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb1000-0xb17ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb1800-0xb1fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb2000-0xb27ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb2800-0xb2fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb3000-0xb37ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb3800-0xb3fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb4000-0xb47ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb4800-0xb4fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb5000-0xb57ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb5800-0xb5fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb6000-0xb67ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb6800-0xb6fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb7000-0xb77ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb7800-0xb7fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb8000-0xb87ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb8800-0xb8fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb9000-0xb97ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xb9800-0xb9fff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xba000-0xba7ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xba800-0xbafff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xbb000-0xbb7ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xbb800-0xbbfff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xbc000-0xbc7ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xbc800-0xbcfff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xbd000-0xbd7ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xbd800-0xbdfff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xbe000-0xbe7ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xbe800-0xbefff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xbf000-0xbf7ff) for rid 0 of orm0=0D pcib0: allocated type 3 (0xbf800-0xbffff) for rid 0 of orm0=0D ex_isa_identify()=0D isa_probe_children: disabling PnP devices=0D atkbdc: atkbdc0 already exists; skipping it=0D atrtc: atrtc0 already exists; skipping it=0D attimer: attimer0 already exists; skipping it=0D sc: sc0 already exists; skipping it=0D uart: uart0 already exists; skipping it=0D isa_probe_children: probing non-PnP devices=0D sc0: at flags 0x100 on isa0=0D sc0: VGA <16 virtual consoles, flags=3D0x100>=0D sc0: fb0, kbd1, terminal emulator: scteken (teken terminal)=0D vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0= =0D pcib0: allocated type 4 (0x3c0-0x3df) for rid 0 of vga0=0D pcib0: allocated type 3 (0xa0000-0xbffff) for rid 0 of vga0=0D fdc0: No FDOUT register!=0D fdc0 failed to probe at port 0x3f0 irq 6 drq 2 on isa0=0D ppc0: cannot reserve I/O port range=0D ppc0 failed to probe at irq 7 on isa0=0D pcib0: allocated type 4 (0x2f8-0x2ff) for rid 0 of uart1=0D uart1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0=0D wbwd0 failed to probe on isa0=0D isa_probe_children: probing PnP devices=0D Device configuration finished.=0D procfs registered=0D Timecounters tick every 10.000 msec=0D vlan: initialized, using hash tables with chaining=0D tcp_init: net.inet.tcp.tcbhashsize auto tuned to 2097152=0D lo0: bpf attached=0D hptrr: no controller detected.=0D hpt27xx: no controller detected.=0D xctrl0: on xenstore0=0D ata0: reset tp1 mask=3D03 ostat0=3D00 ostat1=3D00=0D xenbusb_front0: on xenstore0=0D ata0: stat0=3D0x00 err=3D0x00 lsb=3D0x00 msb=3D0x00=0D ata0: stat1=3D0x00 err=3D0x00 lsb=3D0x00 msb=3D0x00=0D ata0: reset tp2 stat0=3D00 stat1=3D00 devices=3D0x0=0D ata1: reset tp1 mask=3D03 ostat0=3D00 ostat1=3D00=0D ata1: stat0=3D0x00 err=3D0x00 lsb=3D0x00 msb=3D0x00=0D ata1: stat1=3D0x00 err=3D0x00 lsb=3D0x00 msb=3D0x00=0D ata1: reset tp2 stat0=3D00 stat1=3D00 devices=3D0x0=0D xn0: at device/vif/0 on xenbusb_front0=0D xn0: bpf attached=0D xn0: Ethernet address: 22:00:0a:94:b5:05=0D xenbusb_back0: on xenstore0=0D xn0: backend features: feature-sg feature-gso-tcp4=0D xbd0: 10240MB at device/vbd/768 on xenbusb_front0=0D xbd0: attaching as ad0=0D xbd0: disk supports cache flush using: barriers=0D GEOM: new disk ad0=0D xbd1: 122866MB at device/vbd/51728 on xenbusb_front0= =0D xbd1: disk supports cache flush using: flush=0D xbd2: 122866MB at device/vbd/51744 on xenbusb_front0= =0D xbd2: disk supports cache flush using: flush=0D SMP: AP CPU #4 Launched!=0D cpu4 AP:=0D ID: 0x04000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #1 Launched!=0D cpu1 AP:=0D ID: 0x01000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #10 Launched!=0D cpu10 AP:=0D ID: 0x0a000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #11 Launched!=0D cpu11 AP:=0D ID: 0x0b000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 SMP: AP CPU #16 Launched!=0D cpu16 AP:=0D ID: 0x20000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #22 Launched!=0D cpu22 AP:=0D ID: 0x26000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #23 Launched!=0D cpu23 AP:=0D ID: 0x27000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #19 Launched!=0D cpu19 AP:=0D ID: 0x23000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #17 Launched!=0D cpu17 AP:=0D ID: 0x21000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #7 Launched!=0D cpu7 AP:=0D ID: 0x07000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #27 Launched!=0D cpu27 AP:=0D ID: 0x2b000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #26 Launched!=0D cpu26 AP:=0D ID: 0x2a000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #25 Launched!=0D cpu25 AP:=0D ID: 0x29000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #3 Launched!=0D cpu3 AP:=0D ID: 0x03000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #2 Launched!=0D cpu2 AP:=0D ID: 0x02000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #21 Launched!=0D cpu21 AP:=0D ID: 0x25000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #20 Launched!=0D cpu20 AP:=0D ID: 0x24000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #29 Launched!=0D cpu29 AP:=0D ID: 0x2d000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #31 Launched!=0D cpu31 AP:=0D ID: 0x2f000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #18 Launched!=0D cpu18 AP:=0D ID: 0x22000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #30 Launched!=0D cpu30 AP:=0D ID: 0x2e000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #13 Launched!=0D cpu13 AP:=0D ID: 0x0d000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #24 Launched!=0D cpu24 AP:=0D ID: 0x28000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #28 Launched!=0D cpu28 AP:=0D ID: 0x2c000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #8 Launched!=0D cpu8 AP:=0D ID: 0x08000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #14 Launched!=0D cpu14 AP:=0D ID: 0x0e000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #5 Launched!=0D cpu5 AP:=0D ID: 0x05000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #12 Launched!=0D cpu12 AP:=0D ID: 0x0c000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #15 Launched!=0D cpu15 AP:=0D ID: 0x0f000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #6 Launched!=0D cpu6 AP:=0D ID: 0x06000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D SMP: AP CPU #9 Launched!=0D cpu9 AP:=0D ID: 0x09000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff=0D lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff=0D timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400=0D ioapic0: routing intpin 1 (ISA IRQ 1) to lapic 1 vector 48=0D panic: xen_et0: Error -22 setting singleshot timer to 506167555095805 for v= CPU#1=0D =0D cpuid =3D 1=0D KDB: stack backtrace:=0D #0 0xffffffff808e6ed0 at kdb_backtrace+0x60=0D #1 0xffffffff808b22b6 at vpanic+0x126=0D #2 0xffffffff808b2343 at panic+0x43=0D #3 0xffffffff807a445a at xentimer_et_start+0xca=0D #4 0xffffffff80cb365d at loadtimer+0xfd=0D #5 0xffffffff80cb38d7 at cpu_new_callout+0xc7=0D #6 0xffffffff808c5ca1 at callout_process+0x2c1=0D #7 0xffffffff80cb25d5 at handleevents+0x185=0D #8 0xffffffff80cb324b at cpu_initclocks_ap+0xcb=0D #9 0xffffffff80c2fc84 at init_secondary+0x474=0D Uptime: 3s=0D Automatic reboot in 15 seconds - press a key on the console to abort=0D --> Press a key on the console to reboot,=0D --> or switch off the system now.=0D =0D -- =0D Colin Percival=0D Security Officer Emeritus, FreeBSD | The power to serve=0D Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid= =0D From owner-freebsd-xen@FreeBSD.ORG Thu May 23 22:58:14 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 8F9A8AA3 for ; Thu, 23 May 2013 22:58:14 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) by mx1.freebsd.org (Postfix) with ESMTP id 5C4AC79E for ; Thu, 23 May 2013 22:58:14 +0000 (UTC) Received: by mail-ob0-f174.google.com with SMTP id fb19so4757287obc.33 for ; Thu, 23 May 2013 15:58:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=X+BxTvLKcLEU9JrMVgGeG6MQb/1E7fEv91XHI11Hxgw=; b=qvSDlGJCiEtWt8WdM9GTgDQ7DvqwWZX6SXdK1mf/H9FcW1Je/4QTKXevy8fNBhNWyh YqLSZtJMA6k6iFwNBWb3SmoWeCHnT/Js6UirBpGWomoKvnAx1XXehfJa7Lc2C6nQn5vq m+RINxsD5JIY7XMaWWVLEmH/5ieJRDCIuJ2E/ru6g1+JGvyadAd3SRNMvCCMPVrYokW7 lY7eD8KaPzjt8Uby4vZfxChr6lXwWHFubbYq5Mjm/3F+j0s9SNYW/4pvzAdV12AlBFx3 /DxVfVeAami+TEn1eJPa5ju7MZoqUTfIfMr3g+jdD8GpODOkSBtPMLbXlMaRFT60polz AxSg== MIME-Version: 1.0 X-Received: by 10.60.103.148 with SMTP id fw20mr9863483oeb.37.1369349893014; Thu, 23 May 2013 15:58:13 -0700 (PDT) Received: by 10.76.96.49 with HTTP; Thu, 23 May 2013 15:58:12 -0700 (PDT) In-Reply-To: References: <519131D8.9010307@citrix.com> <616EE8A8-78BA-46E6-90AA-4A22160289DF@dckd.nl> <519E1AA6.2060808@citrix.com> <519E4850.1090305@citrix.com> <0BBCBA0B-F4A6-4775-A172-D051D9363665@dckd.nl> Date: Thu, 23 May 2013 18:58:12 -0400 Message-ID: Subject: Re: FreeBSD PVHVM call for testing From: Outback Dingo To: Mark Felder Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 22:58:14 -0000 On Thu, May 23, 2013 at 2:16 PM, Mark Felder wrote: > On Thu, 23 May 2013 12:49:03 -0500, Outback Dingo > wrote: > >> actually this tells you how to remove/eject the virtual iso, not the cdrom >> device from the VM itself in XCP >> >> > gah! you're completely right! However, the bottom picture with the red box > showing "click here to create a dvd drive" is what you should see when you > DO destroy the dvd drive device. > > It should be something like > > xe vbd-list vm-name-label=VM_NAME > > the device saying "empty (RO): TRUE is the dvd rom, get the uuid > > xe vbd-destroy uuid=uuid_of_that_device > And we have a winner......... This does in fact now boot and run on XCP 1.6 once you remove the cdrom device. Thanks to Mark for the correct method. 4 VMs happily cruising along now From owner-freebsd-xen@FreeBSD.ORG Thu May 23 23:24:11 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 595F7FA2; Thu, 23 May 2013 23:24:11 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-oa0-f54.google.com (mail-oa0-f54.google.com [209.85.219.54]) by mx1.freebsd.org (Postfix) with ESMTP id 19F3C893; Thu, 23 May 2013 23:24:10 +0000 (UTC) Received: by mail-oa0-f54.google.com with SMTP id o17so5330513oag.27 for ; Thu, 23 May 2013 16:24:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=dQT53M2E956TQ1XyVeS5O/DlT8ol9JZlEbziLij30JU=; b=u8zBkY+mH4NOvh7h4YjughaX7VxmxRN4KDdhIzMuFLsx8R94KLyWZoTi765BZIYFdX uVz9/wUc41pc4wK/GBRNn0vKeh6hOD0hJGgrVl3aDTo2tZlDj8M+7J+Tu0/F6L8Vtt4M Dc7PyCX/Uxyddp1FTpBcleDbaujV+knbsFs9l7LATv1jPpYPH4qsHqosaJnm5Wd1mg+u +G1rsHJOP8zO6vZqbPhXtUcK/vpmrBmTaCEYzB92e8KaNA5+d3yuCfqhpeVr6buTAakL r0wT9YsiHmr63+HmZ6uWW7YEXwArg5uFLtW91MR/UE46zO1pyzlcaxKPnvApdcxFY4IW eViQ== MIME-Version: 1.0 X-Received: by 10.182.226.162 with SMTP id rt2mr10250638obc.9.1369351450257; Thu, 23 May 2013 16:24:10 -0700 (PDT) Received: by 10.76.96.49 with HTTP; Thu, 23 May 2013 16:24:10 -0700 (PDT) In-Reply-To: <519131D8.9010307@citrix.com> References: <519131D8.9010307@citrix.com> Date: Thu, 23 May 2013 19:24:10 -0400 Message-ID: Subject: Re: FreeBSD PVHVM call for testing From: Outback Dingo To: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-xen@freebsd.org" , xen-devel , "freebsd-virtualization@freebsd.org" , "xen-users@lists.xen.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 23:24:11 -0000 On Mon, May 13, 2013 at 2:32 PM, Roger Pau Monn=E9 wr= ote: > Hello, > > Recently Justin T Gibbs, Will Andrews and myself have been working on > improving the Xen support in FreeBSD. The main goal of this was to bring > full PVHVM support to FreeBSD, right now FreeBSD is only using PV > interfaces for disk and network interfaces when running as a HVM guest. > The main benefits of this changes are that Xen virtual interrupts (event > channels) are now delivered to the guest using a vector callback > injection, that is a per-cpu mechanism that allows each vCPU to have > different interrupts assigned, so for example network and disk > interrupts are delivered to different vCPUs in order to improve > performance. With this changes FreeBSD also uses PV timers when running > as an HVM guest, which should provide better time keeping and reduce the > virtualization overhead, since emulated timers are no longer used. PV > IPIs can also be used inside a HVM guest, but this will be implemented > later. > > Right now the code is in a state where it can be tested by users, so we > would like to encourage FreeBSD and Xen users to test it and provide > feedback. > > The code is available in the following git repository, under the branch > pvhvm_v5: > > http://xenbits.xen.org/gitweb/?p=3Dpeople/royger/freebsd.git;a=3Dsummary > > Also, I've created a wiki page that explains how to set up a FreeBSD > PVHVM for testing: > > http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM Hey Guys, Huge KUDOS to some great work, Ive gotten 4 VMs booting from zfsonroot with the rev_9 finally under XCP 1.6 after getting through removal of the cdrom device from VMs, they are booted and running supremely nice now. IO for zfs filesystems is much better inside the VMs now, even with 4mb compared to what it was. This is a huge move forward and personally I just wanted to say thanks for this and all the work you put into it. The VMs appear quite stable for me, and are pleasantly responsive with low mem on zpools. Great job and again..... Thanks. Keep up the great effort. > > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscribe@freebsd.org" > From owner-freebsd-xen@FreeBSD.ORG Fri May 24 08:34:15 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C9C38397 for ; Fri, 24 May 2013 08:34:15 +0000 (UTC) (envelope-from ykohut@onapp.com) Received: from mail-we0-x235.google.com (mail-we0-x235.google.com [IPv6:2a00:1450:400c:c03::235]) by mx1.freebsd.org (Postfix) with ESMTP id 2AEBD902 for ; Fri, 24 May 2013 08:34:14 +0000 (UTC) Received: by mail-we0-f181.google.com with SMTP id u57so2634490wes.40 for ; Fri, 24 May 2013 01:34:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to:x-mailer:x-gm-message-state; bh=p8Uw/h/ipnM6B3fbZBpjyAalqTBZqwXTo59t/KAf/M0=; b=kATu2f3YWnnIjjWsY1rrGybe3NN6CXS5rY5Um/GMlclVc2tqPLGvhj4Eqw/RXhxHw/ Ov2PRV4GBytg56WWKSPBFzbUHXfsvRCtUDdok0EMqz3uz3l9VU2a7px5LcFYkf+iQZw5 SchxT6RdMg6GckExShvm7s3aSaiVfnT48Hjmw9Cl5kVdFU89miX+cwmWqTqUmykcrm6V d7Ot2bJ1JRBmNj+Nlv6Fju/6cPgjIdfv7F1NkoC54MrY/bSf58RRCoO23o0rpiuDEA7B q/N70xFiKktediwYXKRfXGLc5Gn1jOGf4Ez/8siGB83XkY3GCl8sE5KS9e3pxHjTwI3o eHrA== X-Received: by 10.180.105.161 with SMTP id gn1mr31616954wib.5.1369384454232; Fri, 24 May 2013 01:34:14 -0700 (PDT) Received: from [192.168.128.192] (ext.vps.lviv.ua. [194.44.160.178]) by mx.google.com with ESMTPSA id hl6sm22624233wib.2.2013.05.24.01.34.12 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 May 2013 01:34:13 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: FreeBSD PVHVM call for testing From: Yuriy Kohut In-Reply-To: <7C420745-BAC0-4BD0-AB60-E3BC7F8BA2A7@onapp.com> Date: Fri, 24 May 2013 11:34:10 +0300 Message-Id: References: <519131D8.9010307@citrix.com> <7C420745-BAC0-4BD0-AB60-E3BC7F8BA2A7@onapp.com> To: =?iso-8859-1?Q?Roger_Pau_Monn=E9?= X-Mailer: Apple Mail (2.1503) X-Gm-Message-State: ALoCoQmauTWMULH01zr1irOBgNKL96kTj7MOLCScPDYhD9uwGedxzYuOQzut9N6/PwKq9ilEJmcV Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-xen@freebsd.org" , xen-devel , "freebsd-virtualization@freebsd.org" , "xen-users@lists.xen.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 08:34:15 -0000 Hi, I've just successfully run FreeBSD 9.1 based guest with 'pvhvm_v8' based = kernel under Xen 4.2.2. So I couldn't confirm any issue with the kernel both on Xen 3.4.4 and = 4.2.2. Nice Job. Hypervisor details: # xm info host : ******** release : 3.8.7-1.el6xen version : #1 SMP Tue Apr 16 13:14:14 EEST 2013 machine : x86_64 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 1995 hw_caps : = bfebfbff:28100800:00000000:00003b40:009ce3bd:00000000:00000001:00000000 virt_caps : hvm total_memory : 16374 free_memory : 7194 free_cpus : 0 xen_major : 4 xen_minor : 2 xen_extra : .2 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 = hvm-3.0-x86_32p hvm-3.0-x86_64=20 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=3D0xffff800000000000 xen_changeset : unavailable xen_commandline : dom0_mem=3D409600 cc_compiler : gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-3) cc_compile_by : mockbuild cc_compile_domain : ******** cc_compile_date : Tue May 7 19:26:49 EST 2013 xend_config_format : 4 DomU details: # xm list --long f2tbrxodmgk9ng (domain (domid 146) (cpu_weight 400) (cpu_cap 0) (pool_name Pool-0) (bootloader '') (vcpus 4) (cpus (() () () ())) (on_poweroff destroy) (description '') (on_crash restart) (uuid 355cfb26-4793-f85a-e330-7b6bfcae49b5) (bootloader_args '') (name f2tbrxodmgk9ng) (on_reboot restart) (maxmem 1024) (memory 1024) (shadow_memory 12) (features '') (on_xend_start ignore) (on_xend_stop ignore) (start_time 1369384081.34) (cpu_time 59.956655605) (online_vcpus 4) (image (hvm (kernel '') (superpages 0) (videoram 4) (hpet 0) (stdvga 0) (loader /usr/lib/xen/boot/hvmloader) (xen_platform_pci 1) (nestedhvm 0) (rtc_timeoffset 10801) (pci ()) (hap 1) (localtime 0) (timer_mode 1) (pci_msitranslate 1) (oos 1) (apic 1) (usbdevice tablet) (vpt_align 1) (vncunused 1) (boot cd) (pae 1) (viridian 0) (acpi 1) (vnc 1) (nographic 0) (nomigrate 0) (usb 0) (tsc_mode 0) (guest_os_type default) (device_model /usr/lib64/xen/bin/qemu-dm) (pci_power_mgmt 0) (xauthority /root/.Xauthority) (isa 0) (notes (SUSPEND_CANCEL 1)) ) ) (status 2) (state -b----) (store_mfn 1044476) (device (vif (bridge nnl9l2z5l3q3d8) (uuid daeabd68-05a0-f25b-ba65-394627505b50) (script /etc/xen/scripts/vif-bridge) (ip 109.123.91.166) (mac 00:16:3e:e8:88:49) (vifname qgdvmt5h6d2l9s) (backend 0) ) ) (device (console (protocol vt100) (location 7) (uuid c670a71d-4c3b-1fcb-974a-587f17740a6c) ) ) (device (vbd (protocol x86_64-abi) (uuid 9067929c-9b48-99c6-5526-e771d43f427c) (bootable 1) (dev hda:disk) (uname phy:/dev/fv4zl7t2h5wbeq/o76ciuubu0r986) (mode w) (backend 0) (VDI '') ) ) (device (vbd (protocol x86_64-abi) (uuid 2ae3630e-0e8e-04e4-8caf-ac4d1e9fd402) (bootable 0) (dev hdb:disk) (uname phy:/dev/fv4zl7t2h5wbeq/xi0nw7u4zo0bu9) (mode w) (backend 0) (VDI '') ) ) (device (vbd (protocol x86_64-abi) (uuid 33d3e25c-0c1c-ced6-c8b6-5a706ab0d403) (bootable 0) (dev hdc:cdrom) (uname file:/tools/freebsd/boot-freebsd-generic.iso) (mode r) (backend 0) (VDI '') ) ) (device (vfb (vncunused 1) (vnc 1) (uuid 438a2ffd-bec7-1e54-bb0b-4fdd400517cf) (location 0.0.0.0:5908) ) ) ) DomU from "inside": # uname -a FreeBSD yurak2.vm 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r+03cdadc: Thu = May 23 18:55:33 AST 2013 root@yurak2.vm:/usr/obj/freebsd/sys/XENHVM = amd64 --- Yura On May 22, 2013, at 18:27 PM, Yuriy Kohut wrote: > Hi, >=20 > I've just successfully run FreeBSD 9.1 based guest with 'pvhvm_v8' = based kernel under Xen 3.4.4. >=20 > Hypervisor details: > # xm info > host : ******* > release : 2.6.18-348.2.1.el5xen > version : #1 SMP Tue Mar 5 17:05:33 EST 2013 > machine : x86_64 > nr_cpus : 4 > nr_nodes : 1 > cores_per_socket : 4 > threads_per_core : 1 > cpu_mhz : 2128 > hw_caps : = bfebfbff:28100800:00000000:00000340:009ce3bd:00000000:00000001:00000000 > virt_caps : hvm > total_memory : 6135 > free_memory : 262 > node_to_cpu : node0:0-3 > node_to_memory : node0:262 > xen_major : 3 > xen_minor : 4 > xen_extra : .4 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 = hvm-3.0-x86_32p hvm-3.0-x86_64=20 > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=3D0xffff800000000000 > xen_changeset : unavailable > cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-52) > cc_compile_by : root > cc_compile_domain : ****** > cc_compile_date : Wed Sep 5 18:01:10 EEST 2012 > xend_config_format : 4 >=20 >=20 > DomU details: > # xm list --long h283bpm53f9rnx > (domain > (domid 61) > (on_crash restart) > (uuid a2cbcba9-1d66-87ce-6d2f-412e70eab051) > (bootloader_args ) > (vcpus 2) > (name h283bpm53f9rnx) > (on_poweroff destroy) > (on_reboot restart) > (cpus (() ())) > (bootloader ) > (maxmem 1024) > (memory 1024) > (shadow_memory 10) > (features ) > (on_xend_start ignore) > (on_xend_stop ignore) > (start_time 1369235607.92) > (cpu_time 31.914003553) > (online_vcpus 2) > (image > (hvm > (kernel ) > (videoram 4) > (hpet 0) > (stdvga 0) > (loader /usr/lib/xen/boot/hvmloader) > (vncunused 1) > (xen_platform_pci 1) > (boot cd) > (rtc_timeoffset 7202) > (pci ()) > (pae 1) > (vpt_align 1) > (hap 1) > (viridian 0) > (acpi 1) > (localtime 0) > (timer_mode 1) > (vnc 1) > (nographic 0) > (guest_os_type default) > (pci_msitranslate 1) > (apic 1) > (monitor 0) > (usbdevice tablet) > (device_model /usr/lib64/xen/bin/qemu-dm) > (pci_power_mgmt 0) > (usb 0) > (xauthority /root/.Xauthority) > (isa 0) > (notes (SUSPEND_CANCEL 1)) > ) > ) > (status 2) > (state -b----) > (store_mfn 1044476) > (device > (vif > (bridge xnh5getjoj54ke) > (uuid 6133c146-48ea-b7a5-0263-fda98e1a30fe) > (script /etc/xen/scripts/vif-bridge) > (ip 83.170.81.183) > (mac 00:16:3e:a4:02:5a) > (vifname t2vd5w22msrv5d) > (backend 0) > ) > ) > (device > (vbd > (protocol x86_64-abi) > (uuid dd857cd1-2a4c-ea21-a5a5-e95d811f607a) > (bootable 1) > (dev hda:disk) > (uname phy:/dev/9yblt1m70pdtdp/ddfhogyred6bby) > (mode w) > (backend 0) > (bootable 1) > (VDI ) > ) > ) > (device > (vbd > (protocol x86_64-abi) > (uuid 19cae15c-354d-77cb-57ec-dc313f1d05ba) > (bootable 0) > (dev hdb:disk) > (uname phy:/dev/9yblt1m70pdtdp/dhnnwhs6jh9kdd) > (mode w) > (backend 0) > (bootable 0) > (VDI ) > ) > ) > (device > (vbd > (protocol x86_64-abi) > (uuid 2b97ec8c-0cc5-7197-f510-63c272449680) > (bootable 0) > (dev hdc:disk) > (uname phy:/dev/9yblt1m70pdtdp/d1jilc7s7jxsaq) > (mode w) > (backend 0) > (bootable 0) > (VDI ) > ) > ) > (device > (vbd > (protocol x86_64-abi) > (uuid 1b472270-1ef3-2f49-81f1-031cc00c0eb7) > (bootable 0) > (dev hdd:cdrom) > (uname file:/tools/freebsd/boot-freebsd-generic.iso) > (mode r) > (backend 0) > (bootable 0) > (VDI ) > ) > ) > (device > (vfb > (vncunused 1) > (vnc 1) > (uuid b3defeea-4acc-1408-9b22-71547a64e705) > (location 0.0.0.0:5900) > ) > ) > (device > (console > (protocol vt100) > (location 4) > (uuid 58a089ce-a4d0-037e-23e8-9df37b2bd5da) > ) > ) > ) >=20 >=20 > DomU from "inside": > # uname -a > FreeBSD yurak1.vm 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r+03cdadc: Wed = May 22 17:47:40 EEST 2013 = root@yurak1.vm:/usr/obj/data/freebsd/sys/XENHVM amd64 >=20 >=20 > I'll also set up one (hope will have some time) under Xen 4.2.2 = tomorrow. > --- > Yura >=20 > On May 13, 2013, at 21:32 PM, Roger Pau Monn=E9 = wrote: >=20 >> Hello, >>=20 >> Recently Justin T Gibbs, Will Andrews and myself have been working on >> improving the Xen support in FreeBSD. The main goal of this was to = bring >> full PVHVM support to FreeBSD, right now FreeBSD is only using PV >> interfaces for disk and network interfaces when running as a HVM = guest. >> The main benefits of this changes are that Xen virtual interrupts = (event >> channels) are now delivered to the guest using a vector callback >> injection, that is a per-cpu mechanism that allows each vCPU to have >> different interrupts assigned, so for example network and disk >> interrupts are delivered to different vCPUs in order to improve >> performance. With this changes FreeBSD also uses PV timers when = running >> as an HVM guest, which should provide better time keeping and reduce = the >> virtualization overhead, since emulated timers are no longer used. PV >> IPIs can also be used inside a HVM guest, but this will be = implemented >> later. >>=20 >> Right now the code is in a state where it can be tested by users, so = we >> would like to encourage FreeBSD and Xen users to test it and provide >> feedback. >>=20 >> The code is available in the following git repository, under the = branch >> pvhvm_v5: >>=20 >> http://xenbits.xen.org/gitweb/?p=3Dpeople/royger/freebsd.git;a=3Dsummar= y >>=20 >> Also, I've created a wiki page that explains how to set up a FreeBSD >> PVHVM for testing: >>=20 >> http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM >> _______________________________________________ >> 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" >=20 From owner-freebsd-xen@FreeBSD.ORG Fri May 24 10:11:32 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id ADDE97EA; Fri, 24 May 2013 10:11:32 +0000 (UTC) (envelope-from roger.pau@citrix.com) Received: from SMTP.EU.CITRIX.COM (smtp.eu.citrix.com [46.33.159.39]) by mx1.freebsd.org (Postfix) with ESMTP id 02BE514B; Fri, 24 May 2013 10:11:31 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.87,734,1363132800"; d="scan'208";a="4956152" Received: from lonpex01cl03.citrite.net ([10.30.203.103]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 24 May 2013 10:11:29 +0000 Received: from [192.168.1.30] (10.30.203.1) by LONPEX01CL03.citrite.net (10.30.203.103) with Microsoft SMTP Server id 14.2.342.3; Fri, 24 May 2013 11:11:28 +0100 Message-ID: <519F3CD0.5090405@citrix.com> Date: Fri, 24 May 2013 12:11:28 +0200 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Colin Percival Subject: Re: FreeBSD PVHVM call for testing References: <519131D8.9010307@citrix.com> <51952BAE.6010609@freebsd.org> <51957D42.9060801@citrix.com> <51959ED9.6040405@freebsd.org> <51974EC9.9030204@citrix.com> <5197A1EA.2040404@freebsd.org> <519CAFC7.1070908@citrix.com> <519D24A9.3050407@freebsd.org> <519DDC0A.9000201@citrix.com> <519E6958.6020606@freebsd.org> In-Reply-To: <519E6958.6020606@freebsd.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Originating-IP: [10.30.203.1] Cc: "freebsd-xen@freebsd.org" , xen-devel , "freebsd-virtualization@freebsd.org" , "xen-users@lists.xen.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 10:11:32 -0000 On 23/05/13 21:09, Colin Percival wrote: > On 05/23/13 02:06, Roger Pau Monné wrote: >> On 22/05/13 22:03, Colin Percival wrote: >>> Testing on a cr1.8xlarge EC2 instance, I get Xen 4.2, but it ends up with >>> a panic -- console output below. I can get a backtrace and possibly even >>> a dump if those would help. >> >> Thanks for the test, I've been using Xen 4.2 (and 4.3) without problems >> so far. By looking at the Xen code, the only reason the timer setup >> could return -22 (EINVAL), is that we try to set the timer for a >> different vCPU than the one we are running on. >> >> I've been able to boot a 32 vCPU DomU on my 8way box using Xen 4.2.1 >> (using both qemu-xen and qemu-xen-traditional device models), so I'm >> unsure if this could be due to some patch Amazon applies to Xen. Could >> you try the following patch and post the error message? I would like to >> see if the cpuid reported by kdb and the vCPU that we are trying to set >> the timer are the same. > > Looks like there's agreement about the cpuids here. Anything else I should > try testing? Thanks for the test, this is what I expected. I'm a little bit out of ideas since I'm not able to reproduce this on upstream Xen 4.2. Without knowing what's happening inside the hypervisor it's hard to tell what's wrong. It would be interesting to try if the same happens with a Linux PVHVM (not PV) running on the same instance type. From owner-freebsd-xen@FreeBSD.ORG Fri May 24 14:14:12 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D6FBD567; Fri, 24 May 2013 14:14:12 +0000 (UTC) (envelope-from konrad.wilk@oracle.com) Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by mx1.freebsd.org (Postfix) with ESMTP id 96855CA; Fri, 24 May 2013 14:14:12 +0000 (UTC) Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r4OEE1dZ031292 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 24 May 2013 14:14:02 GMT Received: from userz7022.oracle.com (userz7022.oracle.com [156.151.31.86]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r4OEE2Nk004993 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 24 May 2013 14:14:03 GMT Received: from abhmt107.oracle.com (abhmt107.oracle.com [141.146.116.59]) by userz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r4OEE2LY007424; Fri, 24 May 2013 14:14:02 GMT Received: from phenom.dumpdata.com (/50.195.21.189) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 24 May 2013 07:14:02 -0700 Received: by phenom.dumpdata.com (Postfix, from userid 1000) id E439D1BF781; Fri, 24 May 2013 10:14:00 -0400 (EDT) Date: Fri, 24 May 2013 10:14:00 -0400 From: Konrad Rzeszutek Wilk To: Roger Pau =?iso-8859-1?Q?Monn=E9?= Subject: Re: [Xen-devel] FreeBSD PVHVM call for testing Message-ID: <20130524141400.GB3900@phenom.dumpdata.com> References: <519131D8.9010307@citrix.com> <519E54DE.5090304@citrix.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <519E54DE.5090304@citrix.com> User-Agent: Mutt/1.5.21 (2010-09-15) Content-Transfer-Encoding: quoted-printable X-Source-IP: ucsinet21.oracle.com [156.151.31.93] Cc: "freebsd-xen@freebsd.org" , xen-devel , "freebsd-virtualization@freebsd.org" , "xen-users@lists.xen.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 14:14:12 -0000 On Thu, May 23, 2013 at 07:41:50PM +0200, Roger Pau Monn=E9 wrote: > Hello, >=20 > I've pushed a new branch, pvhvm_v10 that contains a PV IPI > implementation for both amd64 and i386. I've also updated the wiki to > point to the pvhvm_v10 branch: I feel a bit stupid to ask this, but how I install 'gmake'? Doing 'pkg_ad= d -r gmake' tells me there is no package (perhaps I am using a too modern version of = FreeBSD (FreeBSD-10.0-CURRENT-amd64-20130512-r250582-release.iso)? The Wiki mentions how to install git but that fails b/c it can't find gma= ke. From owner-freebsd-xen@FreeBSD.ORG Fri May 24 14:16:55 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 93B4E7C2; Fri, 24 May 2013 14:16:55 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-ob0-x229.google.com (mail-ob0-x229.google.com [IPv6:2607:f8b0:4003:c01::229]) by mx1.freebsd.org (Postfix) with ESMTP id 2A902F9; Fri, 24 May 2013 14:16:55 +0000 (UTC) Received: by mail-ob0-f169.google.com with SMTP id 16so5162415obc.14 for ; Fri, 24 May 2013 07:16:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=YY8JHQq6gO6kuXdY/Cdl423DNhEV1Jc6AWzEhcCretg=; b=u0wCDjaf4S+kPjzlTqmPk77zf1Poh6Yb4PnCuJjJp1J5wENThkE1dO/WjIaXpfhH9M ryZyYGrX+hwJ5CGERJ3Rwd8F+q0N5Vlg3D9lE7hMmUhucRak9d4VarzpSL8hSgcS+pVK d8KZpeXdKEJCpiD/bUvUng3FYqo/JKj/UqGZeS06dJvCG4KCf153LiiB+18wGn0YGqIA JYQjeutk03ZL85gneTUfZa59SU4XBvP73ZrIgnSBNAI2AN49jDRK134Y/1yYLyVKKykN 5IEba09pTwyLETo7yCVjCHP6AZDnefIbqcZQnSAatSQZiDADFhsSTizAPyppDMBANPOz cETQ== MIME-Version: 1.0 X-Received: by 10.60.103.148 with SMTP id fw20mr11696497oeb.37.1369405014798; Fri, 24 May 2013 07:16:54 -0700 (PDT) Received: by 10.76.96.49 with HTTP; Fri, 24 May 2013 07:16:54 -0700 (PDT) In-Reply-To: <20130524141400.GB3900@phenom.dumpdata.com> References: <519131D8.9010307@citrix.com> <519E54DE.5090304@citrix.com> <20130524141400.GB3900@phenom.dumpdata.com> Date: Fri, 24 May 2013 10:16:54 -0400 Message-ID: Subject: Re: [Xen-devel] FreeBSD PVHVM call for testing From: Outback Dingo To: Konrad Rzeszutek Wilk Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-xen@freebsd.org" , "xen-users@lists.xen.org" , xen-devel , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 14:16:55 -0000 On Fri, May 24, 2013 at 10:14 AM, Konrad Rzeszutek Wilk < konrad.wilk@oracle.com> wrote: > On Thu, May 23, 2013 at 07:41:50PM +0200, Roger Pau Monn=E9 wrote: > > Hello, > > > > I've pushed a new branch, pvhvm_v10 that contains a PV IPI > > implementation for both amd64 and i386. I've also updated the wiki to > > point to the pvhvm_v10 branch: > > I feel a bit stupid to ask this, but how I install 'gmake'? Doing 'pkg_ad= d > -r gmake' > tells me there is no package (perhaps I am using a too modern version of > FreeBSD > (FreeBSD-10.0-CURRENT-amd64-20130512-r250582-release.iso)? > > The Wiki mentions how to install git but that fails b/c it can't find > gmake. > on 10-CURRENT you need to use pkg or build from ports/devel/gmake > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscribe@freebsd.org" > From owner-freebsd-xen@FreeBSD.ORG Fri May 24 14:21:42 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 239DC9B8; Fri, 24 May 2013 14:21:42 +0000 (UTC) (envelope-from roger.pau@citrix.com) Received: from SMTP.EU.CITRIX.COM (smtp.eu.citrix.com [46.33.159.39]) by mx1.freebsd.org (Postfix) with ESMTP id 26BA814C; Fri, 24 May 2013 14:21:40 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.87,735,1363132800"; d="scan'208";a="4967520" Received: from lonpex01cl02.citrite.net ([10.30.203.102]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/AES128-SHA; 24 May 2013 14:21:32 +0000 Received: from [192.168.1.30] (10.30.203.1) by LONPEX01CL02.citrite.net (10.30.203.102) with Microsoft SMTP Server id 14.2.342.3; Fri, 24 May 2013 15:21:31 +0100 Message-ID: <519F776A.6090608@citrix.com> Date: Fri, 24 May 2013 16:21:30 +0200 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Konrad Rzeszutek Wilk Subject: Re: [Xen-devel] FreeBSD PVHVM call for testing References: <519131D8.9010307@citrix.com> <519E54DE.5090304@citrix.com> <20130524141400.GB3900@phenom.dumpdata.com> In-Reply-To: <20130524141400.GB3900@phenom.dumpdata.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Originating-IP: [10.30.203.1] Cc: "freebsd-xen@freebsd.org" , xen-devel , "freebsd-virtualization@freebsd.org" , "xen-users@lists.xen.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 14:21:42 -0000 On 24/05/13 16:14, Konrad Rzeszutek Wilk wrote: > On Thu, May 23, 2013 at 07:41:50PM +0200, Roger Pau Monné wrote: >> Hello, >> >> I've pushed a new branch, pvhvm_v10 that contains a PV IPI >> implementation for both amd64 and i386. I've also updated the wiki to >> point to the pvhvm_v10 branch: > > I feel a bit stupid to ask this, but how I install 'gmake'? Doing 'pkg_add -r gmake' > tells me there is no package (perhaps I am using a too modern version of FreeBSD > (FreeBSD-10.0-CURRENT-amd64-20130512-r250582-release.iso)? > > The Wiki mentions how to install git but that fails b/c it can't find gmake. Did you install the ports tree during the installation? If so I've always successfully installed git using: # whereis git # cd # make install Maybe the ISO you picked as a broken ports snapshot? From owner-freebsd-xen@FreeBSD.ORG Fri May 24 22:21:56 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 90EC07EA; Fri, 24 May 2013 22:21:56 +0000 (UTC) (envelope-from crodr001@gmail.com) Received: from mail-lb0-f178.google.com (mail-lb0-f178.google.com [209.85.217.178]) by mx1.freebsd.org (Postfix) with ESMTP id DD9C460A; Fri, 24 May 2013 22:21:55 +0000 (UTC) Received: by mail-lb0-f178.google.com with SMTP id w10so5218061lbi.9 for ; Fri, 24 May 2013 15:21:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=eldH7v0aYlUhC+VwCfQX+DCQem+tH0rTvKyEkhfFVnU=; b=Ik8pws0O85ZKCSguySvRZ9JDRC9RgkEyN8iMwMLcRkD+g7seCmkcNsSkXVaLPBAm/L IMlt8iV2Jp87qXRGGTFPqvILNnHPVqEoyLUm7j86IkpSIg6qN2f06cuOnpn+RSiIT8OY WgW5qeBDAttXpxqz2GUXf8Y0C4YozJE7bb1u08x+DCqWLvk+Uggm1EYL8yUSDvfXT583 3JMNL0YBzyRbcrK2r+JN63IW1abmcHowCkQK7Sk+KG7vnNkV7fx3LlFq2bZjICK5JuMg ufKi/gM07Fd6AFG3cE4Ww4+CQVd3GO2WuzXc3w50BvdET87OKSqawFTC5iWC+cWwd1mD wDUQ== MIME-Version: 1.0 X-Received: by 10.112.145.199 with SMTP id sw7mr9785854lbb.131.1369434114274; Fri, 24 May 2013 15:21:54 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.3.102 with HTTP; Fri, 24 May 2013 15:21:54 -0700 (PDT) In-Reply-To: <20130524141400.GB3900@phenom.dumpdata.com> References: <519131D8.9010307@citrix.com> <519E54DE.5090304@citrix.com> <20130524141400.GB3900@phenom.dumpdata.com> Date: Fri, 24 May 2013 15:21:54 -0700 X-Google-Sender-Auth: tnkGgUv2nhyfJVEb5booGBkbfzQ Message-ID: Subject: Re: [Xen-devel] FreeBSD PVHVM call for testing From: Craig Rodrigues To: Konrad Rzeszutek Wilk Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-xen@freebsd.org" , "xen-users@lists.xen.org" , xen-devel , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 22:21:56 -0000 On Fri, May 24, 2013 at 7:14 AM, Konrad Rzeszutek Wilk < konrad.wilk@oracle.com> wrote: > On Thu, May 23, 2013 at 07:41:50PM +0200, Roger Pau Monn=E9 wrote: > > Hello, > > > > I've pushed a new branch, pvhvm_v10 that contains a PV IPI > > implementation for both amd64 and i386. I've also updated the wiki to > > point to the pvhvm_v10 branch: > > I feel a bit stupid to ask this, but how I install 'gmake'? Doing 'pkg_ad= d > -r gmake' > tells me there is no package (perhaps I am using a too modern version of > FreeBSD > (FreeBSD-10.0-CURRENT-amd64-20130512-r250582-release.iso)? > > The Wiki mentions how to install git but that fails b/c it can't find > gmake. > For 10.0-CURRENT, not all the packages are available yet from the main FreeBSD.org ftp site. I am going through a similar setup issue with someone who has signed up for Google Summer of Code, and I need him to use close to the latest 10.0-CURRENT and have a usable system. I wrote this blog post for the student: http://blogs.freebsdish.org/rodrigc/2013/05/24/setting-up-a-vm-for-doing-gs= oc-work/ You may wish to follow those steps to configure your system to download packages from one of the 3rd party pkg mirrors, and then use the "pkg" command to install gmake and whatever other packages you need. Outback Dingo has mentioned using "pkg" command for installing packages in 10-CURRENT, and that is what I am instructing my GSoC to do. Good luck. --=20 Craig From owner-freebsd-xen@FreeBSD.ORG Fri May 24 22:27:38 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6C9338AC; Fri, 24 May 2013 22:27:38 +0000 (UTC) (envelope-from crodr001@gmail.com) Received: from mail-la0-x22b.google.com (mail-la0-x22b.google.com [IPv6:2a00:1450:4010:c03::22b]) by mx1.freebsd.org (Postfix) with ESMTP id B98D4645; Fri, 24 May 2013 22:27:37 +0000 (UTC) Received: by mail-la0-f43.google.com with SMTP id ez20so4995063lab.16 for ; Fri, 24 May 2013 15:27:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=8pFg1gF6AabEK2CQfpYh3jrGA4SU5EJcxC2YmEIIFLo=; b=X1MAxRMPRVMuEbmecV3SSl0WVx96gbPcbXxj3WIFaS94H4VHjWV0C4HFzDcoZp3Zc7 Aas3AvfhaRZd70UikdYmOOWo4UmP9c6ro0oXIUfAX9P3zGtm2ZY07Y8EfiKs5WDA7Sqk xgId0Jbj/Df92lnSWFKHQvTpiUKFARtB9t2lwVaSx72nirODYj5nk9UQyABvfp7+SaLm dRKqxmNkqCfwBgf1RFogE0zjO3lRFeVbiEvHQ5XFFwFVNcwSzh+55keS8Ql7HEbwTzf6 SS6BGvSF5LLyqtlQZtvpwYJUVit1N+rL/UcnJ8ybV+bHkYMAGbtj7owXL40Sxu0UqqYq 5HTg== MIME-Version: 1.0 X-Received: by 10.152.8.37 with SMTP id o5mr9859823laa.1.1369434456622; Fri, 24 May 2013 15:27:36 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.3.102 with HTTP; Fri, 24 May 2013 15:27:36 -0700 (PDT) In-Reply-To: <519E1A0C.3070609@citrix.com> References: <519131D8.9010307@citrix.com> <647F6650-AEED-4784-8A45-98324860EE0A@dckd.nl> <519E1A0C.3070609@citrix.com> Date: Fri, 24 May 2013 15:27:36 -0700 X-Google-Sender-Auth: M0tGXGXQIXLFWwwgwdowDAjc0qE Message-ID: Subject: Re: FreeBSD PVHVM call for testing From: Craig Rodrigues To: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-xen@freebsd.org" , "xen-users@lists.xen.org" , xen-devel , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 22:27:38 -0000 On Thu, May 23, 2013 at 6:30 AM, Roger Pau Monn=E9 wr= ote: > On 23/05/13 15:20, Jeroen van der Ham wrote: > > > > On 13 May 2013, at 20:32, Roger Pau Monn=E9 wrot= e: > >> Also, I've created a wiki page that explains how to set up a FreeBSD > >> PVHVM for testing: > >> > >> http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM > > > > > > You mention on that page that it is easier to install on 10.0-CURRENT > snapshots. > > What are the issues with installing this on 9.1? Is it possible? > > I don't think it is recommended to use a HEAD (10) kernel with a 9.1 > userland. You can always install a 9.1 and then do a full update with > the source on my repository. > Actually in FreeBSD, it is possible to run an older userland on a newer kernel, and a lot of effort is spent in preserving this type of backwards compatibility. So a 9.1 userland with a 10 kernel will work. However, running a newer userland on an older kernel is not guaranteed to work. So running a 10 userland with a 9.1 kernel will most likely not work. However, since you guys are doing very cutting edge stuff with 10-CURRENT, it is better that you do not waste time with 9.1. I recommend you start with a 10.0 CURRENT snapshot ISO and go from there. I am going through a similar setup exercise with a Google Summer of Code student where he needs to have a latest CURRENT system running in a VM. I wrote this blog post: http://blogs.freebsdish.org/rodrigc/2013/05/24/setting-up-a-vm-for-doing-gs= oc-work/ for the steps how to do it. You can follow those steps to get bootstrapped with a working environment if it helps you out. Good luck. --=20 Craig