From owner-freebsd-xen@FreeBSD.ORG Mon Oct 18 11:07:11 2010 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C7CE510656DD for ; Mon, 18 Oct 2010 11:07:11 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B4A818FC1E for ; Mon, 18 Oct 2010 11:07:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o9IB7Bi4029519 for ; Mon, 18 Oct 2010 11:07:11 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o9IB7BYv029517 for freebsd-xen@FreeBSD.org; Mon, 18 Oct 2010 11:07:11 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 18 Oct 2010 11:07:11 GMT Message-Id: <201010181107.o9IB7BYv029517@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-xen@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-xen@FreeBSD.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Oct 2010 11:07:11 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/149853 xen [panic] [xen] HYPERVISOR_update_va_mapping o kern/148262 xen [xen] [panic] HYPERVISOR_update_va_mapping o kern/147248 xen [xen] 8.0-RELEASE-p3 i386 Xen DomU filesystem "bufwait o kern/145664 xen [xen] mutex vm page queue mutex not owned 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 o kern/143069 xen [xen] [panic] Xen Kernel Panic - Memory modified after o kern/141328 xen [xen] [panic] gstat exit causes kernel panic from unma o kern/140313 xen [xen] [panic] FreeBSD8 RC2 as PV domU crashes during c o kern/135421 xen [xen] FreeBSD Xen PVM DomU network failure - netfronc. o kern/135178 xen [xen] Xen domU outgoing data transfer stall when TSO i o kern/135069 xen [xen] FreeBSD-current/Xen SMP doesn't function at all o kern/134926 xen [xen] [panic] FreeBSD-current Xen DomU networking pani 14 problems total. From owner-freebsd-xen@FreeBSD.ORG Tue Oct 19 19:13:39 2010 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA4831065670 for ; Tue, 19 Oct 2010 19:13:39 +0000 (UTC) (envelope-from linda.messerschmidt@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 68A3B8FC21 for ; Tue, 19 Oct 2010 19:13:38 +0000 (UTC) Received: by bwz15 with SMTP id 15so546873bwz.13 for ; Tue, 19 Oct 2010 12:13:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=ss2CC5xQZBy1jAT3aSTCPHEKbXzlxKvv+OEFSqksGiA=; b=tEHM2K1x+uvHAJlSj2O44AFRRo3iqVJuL37Bfv9lHJ7I9yH+05nxwA87bWAxQ2FIPa thalbsOQYhB8x/j6dHxz/29jbYbhxWVbRZuYuX2al1imfzvOXLd7qakk84Ndlh6tIHFH WCHqJAIaAuN/AZ9avhbuZ561FtUvHt++tZydk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=mQe1vCbkENSXU9/AvZ25eDZT9G+ZKqL7MXx7tWeaXVySEKh49mX46Dr9IZDfI43Jom sltE5QVBq+bvwqQo9I53pwVjs6bYOCcTdkDHVjQ0KrN4WGbCPA7xQKP0Pd/ZGLQt93BL ZA6+CYssONfGzqsDOkZZ0KogUR6U83O0bhFF0= MIME-Version: 1.0 Received: by 10.204.62.202 with SMTP id y10mr769518bkh.120.1287515618246; Tue, 19 Oct 2010 12:13:38 -0700 (PDT) Received: by 10.204.152.203 with HTTP; Tue, 19 Oct 2010 12:13:38 -0700 (PDT) In-Reply-To: References: Date: Tue, 19 Oct 2010 15:13:38 -0400 Message-ID: From: Linda Messerschmidt To: freebsd-xen@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: No PAE in XEN kernel causes build failure X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2010 19:13:40 -0000 On Tue, Oct 19, 2010 at 2:51 PM, Linda Messerschmidt wrote: > With 8.1-STABLE r214066, building the above kernel succeeds. =A0However, > uncommenting the "nooptions PAE" gets the following errors: Just to be thorough I tried again on -CURRENT and got a slightly different set of errors: cc -c -O -pipe -std=3Dc99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/data/freebsd-current/src/sys -I/data/freebsd-current/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=3D8000 --param inline-unit-growth=3D100 --param large-function-growth=3D1000 -mno-align-long-strings -mpreferred-stack-boundary=3D2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror /data/freebsd-current/src/sys/i386/xen/xen_machdep.c /data/freebsd-current/src/sys/i386/xen/xen_machdep.c: In function 'initvalu= es': /data/freebsd-current/src/sys/i386/xen/xen_machdep.c:1032: error: 'IdlePTDnew' undeclared (first use in this function) /data/freebsd-current/src/sys/i386/xen/xen_machdep.c:1032: error: (Each undeclared identifier is reported only once /data/freebsd-current/src/sys/i386/xen/xen_machdep.c:1032: error: for each function it appears in.) /data/freebsd-current/src/sys/i386/xen/xen_machdep.c:1037: error: 'IdlePTDnewma' undeclared (first use in this function) /data/freebsd-current/src/sys/i386/xen/xen_machdep.c:1040: error: 'IdlePDPTnew' undeclared (first use in this function) /data/freebsd-current/src/sys/i386/xen/xen_machdep.c:1079: error: 'IdlePDPT' undeclared (first use in this function) /data/freebsd-current/src/sys/i386/xen/xen_machdep.c:1080: error: 'IdlePDPTma' undeclared (first use in this function) /data/freebsd-current/src/sys/i386/xen/xen_machdep.c:1080: error: 'IdlePDPTnewma' undeclared (first use in this function) cc1: warnings being treated as errors /data/freebsd-current/src/sys/i386/xen/xen_machdep.c:890: warning: unused variable 'IdlePTDma' *** Error code 1 Thanks! From owner-freebsd-xen@FreeBSD.ORG Tue Oct 19 19:18:22 2010 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1DE321065670 for ; Tue, 19 Oct 2010 19:18:22 +0000 (UTC) (envelope-from linda.messerschmidt@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id AA0338FC08 for ; Tue, 19 Oct 2010 19:18:21 +0000 (UTC) Received: by fxm12 with SMTP id 12so1924039fxm.13 for ; Tue, 19 Oct 2010 12:18:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=DoLFraHhhm7s611h9I7QX7F97MdWV7TlFamW3GzwP/g=; b=JcIhUEbm3iNQXFNf+1gYaiPYVhR+8bK+S2Duc5Uq2xsiZqtTMPbqLwGQS8VCSlb8Xs 4DjNLc+yafldIbo/RYAJCqvO5f1qDn8e+o06+M5HZs8Arky4A0DVjavnixTFW/UNZzC2 PVHTU6h2vn9jpb1zY8uAgaa2gRsXv6H3QAL3I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=rXt1+jsdGjfOnlEIX+IOdD2RwvIgfGIJxWtGW+Zb3M34LpP+2s1qJ6TeimfikqcFFY e2Lk3ljuZ4sdsWKtb23CpfPHLGFTKZLFYjwzJmy3FrUuk9VhUWGjfbS27xdIXXeX0Bbq JYy4s2NkFYxmO4SmJiAxxp4p2aQWeX+j9aytc= MIME-Version: 1.0 Received: by 10.204.52.208 with SMTP id j16mr5200606bkg.133.1287514276155; Tue, 19 Oct 2010 11:51:16 -0700 (PDT) Received: by 10.204.152.203 with HTTP; Tue, 19 Oct 2010 11:51:16 -0700 (PDT) Date: Tue, 19 Oct 2010 14:51:16 -0400 Message-ID: From: Linda Messerschmidt To: freebsd-xen@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: No PAE in XEN kernel causes build failure X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2010 19:18:22 -0000 I'm trying to build a Xen kernel for 8.1. Mostly everything is working so far (with the exception of the known bugs), which is great. :) I cry a little bit that FreeBSD cannot be dom0, but one step at a time. :) I noticed "options PAE" in the provided example XEN kernel. I don't have a lot of experience with PAE, but I have heard it's a dirty hack for getting >4gb on i386 and that it was mostly used with XEN when i386 was the only viable dom0. We are using an amd64 Debian host and running only i386 PV guests with relatively small amounts of RAM. (<3gb). So I thought that may not be needed in our environment. Here's the config file I tried: ------------ START ---------------- include XEN ident XENEX #nooptions PAE nodevice atkbdc nodevice atkbd nodevice kbdmux nodevice psm ------------ END ----------------- With 8.1-STABLE r214066, building the above kernel succeeds. However, uncommenting the "nooptions PAE" gets the following errors: cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror /usr/src/sys/i386/xen/xen_machdep.c /usr/src/sys/i386/xen/xen_machdep.c: In function 'initvalues': /usr/src/sys/i386/xen/xen_machdep.c:1075: error: 'IdlePTDnew' undeclared (first use in this function) /usr/src/sys/i386/xen/xen_machdep.c:1075: error: (Each undeclared identifier is reported only once /usr/src/sys/i386/xen/xen_machdep.c:1075: error: for each function it appears in.) /usr/src/sys/i386/xen/xen_machdep.c:1080: error: 'IdlePTDnewma' undeclared (first use in this function) /usr/src/sys/i386/xen/xen_machdep.c:1083: error: 'IdlePDPTnew' undeclared (first use in this function) /usr/src/sys/i386/xen/xen_machdep.c:1122: error: 'IdlePDPT' undeclared (first use in this function) /usr/src/sys/i386/xen/xen_machdep.c:1123: error: 'IdlePDPTma' undeclared (first use in this function) /usr/src/sys/i386/xen/xen_machdep.c:1123: error: 'IdlePDPTnewma' undeclared (first use in this function) cc1: warnings being treated as errors /usr/src/sys/i386/xen/xen_machdep.c:891: warning: unused variable 'pdir_shadow_ma' *** Error code 1 I took a look at xen_machdep.c and it looks like these values are declared inside an #ifdef PAE and then defined in a later #ifdef PAE, and then referenced at the lines cited above without one. I really don't know if XEN can/should be able to be built without PAE, but I am pretty sure the above means that there's a logic flaw somewhere in the #ifdef arrangements. Unfortunately I don't know what this stuff is so I don't know if the declaration/definition should come out of the #ifdefs or if the references above should go inside one. I thought I would point it out in case there's someone reading who understands this stuff better than I do. I.e. at all. :) As an aside, I also noticed that in the XEN example config the lines "option XEN" appears whereas everything else is the usual "options WHATEVER" and I was wondering if that's significant or if it's just an equivalent alias I haven't noticed before. Thanks! From owner-freebsd-xen@FreeBSD.ORG Fri Oct 22 11:48:33 2010 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 142631065672 for ; Fri, 22 Oct 2010 11:48:33 +0000 (UTC) (envelope-from ykohut@onapp.com) Received: from edgelb.ocscloud.net (edge02.ocscloud.net [91.210.68.36]) by mx1.freebsd.org (Postfix) with ESMTP id AD6438FC16 for ; Fri, 22 Oct 2010 11:48:32 +0000 (UTC) Received: from W01EXHUB01.hosting.tg.local (10.101.22.23) by W01EXEDGE02.hosting.tg.local (91.210.68.36) with Microsoft SMTP Server (TLS) id 8.1.311.2; Fri, 22 Oct 2010 12:48:30 +0100 Received: from [192.168.128.133] (194.44.160.178) by smtpauth.thinkgrid.net (10.101.22.25) with Microsoft SMTP Server (TLS) id 8.1.311.2; Fri, 22 Oct 2010 12:48:30 +0100 From: Yuriy Kohut Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 22 Oct 2010 14:48:27 +0300 Message-ID: <86C62B82-9EEB-418E-B52F-1385E0C1A30B@onapp.com> To: "freebsd-xen@FreeBSD.org" MIME-Version: 1.0 (Apple Message framework v1081) X-Mailer: Apple Mail (2.1081) Subject: FreebBSD 8.1-STABLE i386 PV DomU kernel panic at HYPERVISOR_update_va_mapping X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Oct 2010 11:48:33 -0000 Hi, I have installed FreeBSD 8.1-STABLE paravirtualized Xen DomU according = to the documentation at: http://forums.freebsd.org/showthread.php?t=3D10268 RELENG_8 CVS tag was used to get world and kernel sources. The kernel get into panic while booting: ---- panic: HYPERVISOR_update_va_mapping(((unsigned long)(va)), (pa | 0x002 | = 0x001 | pgeflag | pmap_cache_bits(mode, 0)), UVMF_INVLPG| UVMF_ALL) < 0: = /usr/src/sys/i386/xen/pmap.c:1269 cpuid =3D 0 KDB: enter: panic [thread pid 0 tid 0 ] Stopped at kdb_enter+0x3a: movl $0,kdb_why db>=20 db> where Tracing pid 0 tid 0 td 0xc03e0af0 kdb_enter(c036c678,c036c678,c0390af5,c051ecb4,0,...) at kdb_enter+0x3a panic(c0390af5,c0398fbf,c0398cd1,4f5,0,...) at panic+0x134 pmap_mapdev_attr(0,0,500,6,c051ed44,...) at pmap_mapdev_attr+0x13d pmap_mapbios(0,0,500,1,c051ed44,...) at pmap_mapbios+0x27 x86bios_call(c22ca3c0,0,0,76,c051ed64,...) at x86bios_call+0x212 module_register_init(c03db8f0,7020800,7020800,523000,0,...) at = module_register_init+0xa7 mi_startup(523000,0,0,0,0,...) at mi_startup+0x96 btext() at btext+0x95 ---- DomU details FreeBSD 8.1-STABLE #8 kernel config: /usr/src/sys/XEN i386 xen config: ---- kernel =3D "/var/lib/xen/images/kernel.6jZmCCXlzjBa" memory =3D "512" name =3D "6jZmCCXlzjBa" vcpus =3D "1" vid =3D "17" sanip =3D "10.200.200.19" vif =3D [ 'mac=3D00:16:3e:0a:e2:40, bridge=3Dxenbr0, ip=3D68.169.47.45, = vifname=3D6jZmCCXlzjBa, rate=3D0Mb/s' ] disk =3D [ 'phy:/dev/iscsi_0_17,sda,w', 'phy:/dev/iscsi_0_137,sdb,w' ] extra =3D "boot_verbose=3D1" extra +=3D ",vfs.root.mountfrom=3Dufs:/dev/da0" extra +=3D ",kern.hz=3D100" ---- Dom0 details CentOS release 5.4 (Final) Linux vl-radar-box1.slc.westdc.net 2.6.18-164.6.1.el5xen #1 SMP Tue Nov = 3 16:48:13 EST 2009 x86_64 x86_64 x86_64 GNU/Linux xen-3.0.3-94.el5_4.2 DomU built from RELENG_8_0 booted fine for me. But it is very unstable. = Kernel panics every time DomU is more higher loaded with network, CPU or = memory. I reported several BRs for them, but with no result for the = moment. Could somebody please assist with the panic ? --- Yura From owner-freebsd-xen@FreeBSD.ORG Fri Oct 22 17:52:31 2010 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E8D3D1065696 for ; Fri, 22 Oct 2010 17:52:31 +0000 (UTC) (envelope-from linda.messerschmidt@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 770428FC24 for ; Fri, 22 Oct 2010 17:52:31 +0000 (UTC) Received: by bwz3 with SMTP id 3so1444877bwz.13 for ; Fri, 22 Oct 2010 10:52:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=sM4ZkqSQCjXaZAYxFPhT/hpv81/Mtax+JzKERKBpAQY=; b=RuhcrRhw/zyZXfZ1Ygg5yj8ifWs+4v/HoFh0Dsi6vDZ4Vc36STg4Y1zGNQRusCPDOD KjsYlIH45KOLXRFVN5arGxiY0DF1z8MFSjt3X4a4pzfeF+DtTjjcEeDDsFhszdHlxBpS VoE7+xu4eMykLb63qwmLhxfn/cc+dNBUBBQ+w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=rzCW/sfsRJgH6gnoyNDlSZbMe5xAIkT6uIkpGvJ8uVUBinHGs38JAUlN5uwmjNIT39 JqoJHwbSaCCusk7MAujdxquatDWkoJpuNOP/p6qW69Yth1qqT6dgSsp9RXGtsEBeriqi 7PN/mTtx7p+jL5t4sIxBpGkQKm6HWX9AMSFEU= MIME-Version: 1.0 Received: by 10.204.103.67 with SMTP id j3mr2501396bko.94.1287769949862; Fri, 22 Oct 2010 10:52:29 -0700 (PDT) Received: by 10.204.152.203 with HTTP; Fri, 22 Oct 2010 10:52:29 -0700 (PDT) In-Reply-To: <86C62B82-9EEB-418E-B52F-1385E0C1A30B@onapp.com> References: <86C62B82-9EEB-418E-B52F-1385E0C1A30B@onapp.com> Date: Fri, 22 Oct 2010 13:52:29 -0400 Message-ID: From: Linda Messerschmidt To: "freebsd-xen@FreeBSD.org" Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: FreebBSD 8.1-STABLE i386 PV DomU kernel panic at HYPERVISOR_update_va_mapping X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Oct 2010 17:52:32 -0000 On Fri, Oct 22, 2010 at 7:48 AM, Yuriy Kohut wrote: > The kernel get into panic while booting: > ---- > panic: HYPERVISOR_update_va_mapping(((unsigned long)(va)), (pa | 0x002 | 0x001 | For 8.1 you must build your kernel without the keyboard drivers for the time being. This issue is pretty well documented at this point, so you should be able to find the instructions pretty readily. I've done this and it doesn't seem to hurt anything (the Xen "serial console" for the machine still works fine). From owner-freebsd-xen@FreeBSD.ORG Fri Oct 22 19:35:28 2010 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 603BF106566C for ; Fri, 22 Oct 2010 19:35:28 +0000 (UTC) (envelope-from linda.messerschmidt@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id E61478FC21 for ; Fri, 22 Oct 2010 19:35:27 +0000 (UTC) Received: by bwz3 with SMTP id 3so1537995bwz.13 for ; Fri, 22 Oct 2010 12:35:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=VN5Ve8BhXOszEK32xG3uIDVGUzpCpzGG1Qz4FCl4p4g=; b=GqoOzseYsVX35+AnBL2AzYYM616WIrDglJTH/1aBpOUvuV+Um6sUIigTCtQOPpiaaS 6NpfYXdCycbJrATwY22jM7BULTEj48oEu5ZBR7BOJ2eZwAGOEyo0/6KU/6asCPFacOrx A0f0/d1TlfebduVMJfko7IVFPP+YxGIFSz+jo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=MBeO824kQW8iJLOti28RlwxZ0rI8EMf02/r30PCSy7nWxQfmp9p7xz7KCJbP9IIBk6 HRYBshVr9U4kChMLdFXpDA1UiBbS8YC5W1rDIaIn3JCEviNFfhapOHqc4fnbDc7KgLbf /ZI1XOrVoMr9AxeEN+AC0PPAFJUNt7LXka2pM= MIME-Version: 1.0 Received: by 10.204.52.193 with SMTP id j1mr2534645bkg.52.1287775898686; Fri, 22 Oct 2010 12:31:38 -0700 (PDT) Received: by 10.204.152.203 with HTTP; Fri, 22 Oct 2010 12:31:38 -0700 (PDT) Date: Fri, 22 Oct 2010 15:31:38 -0400 Message-ID: From: Linda Messerschmidt To: "freebsd-xen@FreeBSD.org" Content-Type: text/plain; charset=ISO-8859-1 Subject: Fatal trap 12 on live migrate X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Oct 2010 19:35:28 -0000 Hello, With 8.1-STABLE (r214217) up and running under Xen 4.0.1 on the 2.6.32.24 pvops kernel, this command: xm migrate freebsd8s localhost Produces the following crash: kernel trap 12 with interrupts disabled Kernel page fault with the following non-sleepable locks held: exclusive sleep mutex intr sources (intr sources) r = 0 (0xc051c540) locked @ /usr/src/sys/i386/i386/intr_machdep.c:190 KDB: stack backtrace: X_db_sym_numargs(c0333f0d,c00fbc50,d4667ad4,a,d4667b10,...) at X_db_sym_numargs+0x146 kdb_backtrace(be,3,ffffffff,c04e24d4,d4667b64,...) at kdb_backtrace+0x2a witness_display_spinlock(c0336345,d4667b78,4,1,0,...) at witness_display_spinlock+0x75 witness_warn(5,0,c035da1d,c03b4e7c,c234d2a8,...) at witness_warn+0x1fe trap(d4667bfc) at trap+0x16a alltraps(c2366cc0,f,d4667c78,c02dc08e,83,...) at alltraps+0x1b unbind_from_irqhandler(83,d4667cd8,c02d74d3,c22f7780,c22db03c,...) at unbind_from_irqhandler+0x21 xencons_suspend(c22f7780,c22db03c,c036c3b8,b5,d4667cc8,...) at xencons_suspend+0x1e evtchn_device_upcall(c038d474,c262dc80,2,301,a,...) at evtchn_device_upcall+0x4e3 xs_suspend(0,d4667d38,c032bf9f,345,c234d2a8,...) at xs_suspend+0x1fe fork_exit(c02d9e10,0,d4667d38) at fork_exit+0xb8 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0, esp = 0xd4667d70, ebp = 0 --- Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x21:0x0 stack pointer = 0x29:0xd4667c3c frame pointer = 0x29:0xd4667c5c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 1, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 14 (xenwatch) [thread pid 14 tid 100017 ] Stopped at 0: *** error reading from address 0 *** I am no expert but it looks like some sort of null pointer problem? Maybe it tried to jump to a null address? (eip = 0) I would like to learn more about the inner workings of DomU FreeBSD. How could I help debug this? Thanks! From owner-freebsd-xen@FreeBSD.ORG Sat Oct 23 13:24:54 2010 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A53AE1065679 for ; Sat, 23 Oct 2010 13:24:54 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 372238FC08 for ; Sat, 23 Oct 2010 13:24:53 +0000 (UTC) Received: by wwb24 with SMTP id 24so1786622wwb.31 for ; Sat, 23 Oct 2010 06:24:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=a8w8LeLg+k7egZoUK7nivQdnfmipJv7J5Zh0aPLQLhY=; b=qkUqEttfdvJU6tWD/1XJCffPG97IFI16ipp9ehxmLOiQPT59hiqOEllsKk9DJabSKb XHS16QNswZXdlZVDkbHdYNbWe/h8LtqqSW5OvymekJ2rs3hHppispEw39V6tx/j1EzFk PIJiD+VMmoD6HRom9I+yRL9a2hpLnxrETXs2M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=nysCKzbKzkZ59R2JExJbq5mwkb5RpnF/fU8l6OUfi5lsuZoYEUJJiRNWKFAdWwsjAe xE7cpwtT2LbEXk4RikiVdGFq+QeGvGg/9/hI8uAGpe+c+EME2SP48Wb+QOXxR0SWCAb1 5X8vtGixvyGoWAE/kG+XILSEs2fTb92mLoHXY= MIME-Version: 1.0 Received: by 10.216.52.135 with SMTP id e7mr3870170wec.98.1287838507385; Sat, 23 Oct 2010 05:55:07 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.230.32 with HTTP; Sat, 23 Oct 2010 05:55:07 -0700 (PDT) In-Reply-To: References: Date: Sat, 23 Oct 2010 20:55:07 +0800 X-Google-Sender-Auth: 5dNPs-mf_0XQCIXKFn8SMv0hCUM Message-ID: From: Adrian Chadd To: Linda Messerschmidt Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-xen@FreeBSD.org" Subject: Re: Fatal trap 12 on live migrate X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Oct 2010 13:24:54 -0000 Ah, I need to see if I can dig up the stuff Kip told me a while ago about bringing up gdb to actually debug FreeBSD DomU's over the network. Basically, there's a quick hack that can be done to build a gdb-xenserver process which runs in the Dom0 and exports the DomU as a remote gdb debug stub. You can then attach to it from a debugger on a FreeBSD machine and do things like set breakpoints, check process state, etc. It makes debugging so very much easier. I suggest to start - grab the xen 4.0.1 source tarball and see if there's a gdb-xenserver directory (or something gdb'y and xen'y in there.) If so, figure out how to build it. :-) Then email the list with your results and I'll see what I can help you with via email. Note though - I can't really look at any of this stuff until after mid November due to university studies and exams (which is primarily why I've been quiet about the whole Xen thing this year.) Adrian On 23 October 2010 03:31, Linda Messerschmidt wrote: > Hello, > > With 8.1-STABLE (r214217) up and running under Xen 4.0.1 on the > 2.6.32.24 pvops kernel, this command: > > xm migrate freebsd8s localhost > > Produces the following crash: > > kernel trap 12 with interrupts disabled > Kernel page fault with the following non-sleepable locks held: > exclusive sleep mutex intr sources (intr sources) r =3D 0 (0xc051c540) > locked @ /usr/src/sys/i386/i386/intr_machdep.c:190 > KDB: stack backtrace: > X_db_sym_numargs(c0333f0d,c00fbc50,d4667ad4,a,d4667b10,...) at > X_db_sym_numargs+0x146 > kdb_backtrace(be,3,ffffffff,c04e24d4,d4667b64,...) at kdb_backtrace+0x2a > witness_display_spinlock(c0336345,d4667b78,4,1,0,...) at > witness_display_spinlock+0x75 > witness_warn(5,0,c035da1d,c03b4e7c,c234d2a8,...) at witness_warn+0x1fe > trap(d4667bfc) at trap+0x16a > alltraps(c2366cc0,f,d4667c78,c02dc08e,83,...) at alltraps+0x1b > unbind_from_irqhandler(83,d4667cd8,c02d74d3,c22f7780,c22db03c,...) at > unbind_from_irqhandler+0x21 > xencons_suspend(c22f7780,c22db03c,c036c3b8,b5,d4667cc8,...) at > xencons_suspend+0x1e > evtchn_device_upcall(c038d474,c262dc80,2,301,a,...) at > evtchn_device_upcall+0x4e3 > xs_suspend(0,d4667d38,c032bf9f,345,c234d2a8,...) at xs_suspend+0x1fe > fork_exit(c02d9e10,0,d4667d38) at fork_exit+0xb8 > fork_trampoline() at fork_trampoline+0x8 > --- trap 0, eip =3D 0, esp =3D 0xd4667d70, ebp =3D 0 --- > > > Fatal trap 12: page fault while in kernel mode > cpuid =3D 0; apic id =3D 00 > fault virtual address =A0 =3D 0x0 > fault code =A0 =A0 =A0 =A0 =A0 =A0 =A0=3D supervisor read, page not prese= nt > instruction pointer =A0 =A0 =3D 0x21:0x0 > stack pointer =A0 =A0 =A0 =A0 =A0 =3D 0x29:0xd4667c3c > frame pointer =A0 =A0 =A0 =A0 =A0 =3D 0x29:0xd4667c5c > code segment =A0 =A0 =A0 =A0 =A0 =A0=3D base 0x0, limit 0xfffff, type 0x1= b > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=3D DPL 1, pres 1, def32 1= , gran 1 > processor eflags =A0 =A0 =A0 =A0=3D resume, IOPL =3D 0 > current process =A0 =A0 =A0 =A0 =3D 14 (xenwatch) > [thread pid 14 tid 100017 ] > Stopped at =A0 =A0 =A00: =A0 =A0 =A0*** error reading from address 0 *** > > I am no expert but it looks like some sort of null pointer problem? > Maybe it tried to jump to a null address? =A0(eip =3D 0) > > I would like to learn more about the inner workings of DomU FreeBSD. > How could I help debug this? > > Thanks! > _______________________________________________ > 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" >