From owner-freebsd-xen@FreeBSD.ORG Tue Dec 2 18:39:41 2014 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CAEF96A2 for ; Tue, 2 Dec 2014 18:39:41 +0000 (UTC) Received: from SMTP.CITRIX.COM (smtp.citrix.com [66.165.176.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.citrix.com", Issuer "Cybertrust Public SureServer SV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0E4CDFBA for ; Tue, 2 Dec 2014 18:39:40 +0000 (UTC) X-IronPort-AV: E=Sophos;i="5.07,502,1413244800"; d="scan'208";a="198663909" Received: from [127.0.0.1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.3.181.6; Tue, 2 Dec 2014 12:54:10 -0500 Message-ID: <547DFCC0.6030003@citrix.com> Date: Tue, 2 Dec 2014 18:54:08 +0100 From: =?windows-1252?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: "David P. Discher" , Subject: Re: Attempting to Get Xen FreeBSD Dom0 working References: <481F7D02-BFE9-4E35-A475-5A8A05A801CE@dpdtech.com> In-Reply-To: <481F7D02-BFE9-4E35-A475-5A8A05A801CE@dpdtech.com> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 8bit X-DLP: MIA2 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.18-1 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, 02 Dec 2014 18:39:41 -0000 Hello, Thanks for trying it out. El 02/12/14 a les 17.38, David P. Discher ha escrit: > Hey All - > > Attempting to follow the directions over at : http://wiki.xenproject.org/wiki/FreeBSD_Dom0 > > I’ve confirmed the hard way, not all the bits in the pvh_dom0_v8 -head copy of FreeBSD have been merged into freebsd-head, so running with a working kernel from the repo over at xenbits. However, I’m getting a panic in the AcpiNsWalkNamespace when the Dom0 is booting. I’m willing and have time to do some testing and poking. And suggestions or pointers at what to look at next ? I assume that this box is capable of booting FreeBSD without Xen. > Hardware is: > > Supermicro X8STi > Intel(R) Xeon(R) CPU E5620 @ 2.40GHz > > Panic is: > > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x18 > fault code = supervisor read data, page not present > instruction pointer = 0x20:0xffffffff803376f1 > stack pointer = 0x28:0xffffffff823228d0 > frame pointer = 0x28:0xffffffff82322940 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 0 (swapper) > [ thread pid 0 tid 100000 ] > Stopped at AcpiNsWalkNamespace+0x31: movq 0x18(%rsi),%rax > db> bt > Tracing pid 0 tid 100000 td 0xffffffff8180bbf0 > AcpiNsWalkNamespace() at AcpiNsWalkNamespace+0x31/frame 0xffffffff82322940 > AcpiWalkNamespace() at AcpiWalkNamespace+0xa8/frame 0xffffffff823229a0 > acpi_pci_attach() at acpi_pci_attach+0x154/frame 0xffffffff823229f0 Could you get the file/line number of at least the 3 entries above? Also, could you paste the full log of Xen+FreeBSD when booted using boot_verbose? (up to the point of the panic) Roger.