From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Abd-El-Malek Subject: Re: Moving a PV Linux kernel Date: Mon, 10 Mar 2008 15:40:55 -0400 Message-ID: <47D58EC7.8010501@cmu.edu> References: <4B6A24C3-D743-49C8-BDD9-E22F9513CB14@cmu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4B6A24C3-D743-49C8-BDD9-E22F9513CB14@cmu.edu> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel List-Id: xen-devel@lists.xenproject.org I forgot to include the hypervisor's log. Here it is: (XEN) mm.c:1956:d0 Bad type (saw 00000000e8000001 != exp 0000000020000000) for mfn 21d95a (pfn 200) (count = 1) (XEN) mm.c:740:d0 Attempt to create linear p.t. with write perms (XEN) mm.c:1167:d0 Failure in alloc_l2_table: entry 0 (XEN) mm.c:1980:d0 Error while validating mfn 21d3a1 (pfn 7b9) for type 0000000040000000: caf=80000002 taf=0000000040000001 (XEN) mm.c:765:d0 Attempt to create linear p.t. with write perms (XEN) mm.c:1241:d0 Failure in alloc_l3_table: entry 1 (XEN) mm.c:1980:d0 Error while validating mfn 21d3a3 (pfn 7b7) for type 0000000060000000: caf=80000002 taf=0000000060000001 (XEN) mm.c:790:d0 Attempt to create linear p.t. with write perms (XEN) mm.c:1287:d0 Failure in alloc_l4_table: entry 511 (XEN) mm.c:1980:d0 Error while validating mfn 21d3a5 (pfn 7b5) for type 0000000080000000: caf=80000002 taf=0000000080000001 Any pointers would be greatly appreciated. Cheers, Mike Michael Abd-El-Malek wrote: > I'm trying to change where a 64-bit PV Linux kernel resides. So I > changed __START_KERNEL_map from 0xffffffff80000000UL to > 0xffffffffc0000000UL in > linux-2.6.18-xen.hg/include/asm-x86_64/mach-xen/asm/page.h. When I > tried to boot that kernel, I got the following error message from xm > create: > Error: (1, 'Internal error', 'arch_setup_bootlate: pin_table failed (pfn > 0x7b5, rc=1)\n') > > I spent some time trying digging into the hypervisor to understand the > above message, but I didn't get anywhere. > > So I have two questions: > 1) Why is the above error message happening? > 2) Am I forgetting any other place where constants need to change? > (Either in the Linux kernel tree or in Xen.) > > Thanks, > Mike