From owner-freebsd-xen@FreeBSD.ORG Tue Mar 31 03:26:57 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 00D5D71E for ; Tue, 31 Mar 2015 03:26:56 +0000 (UTC) Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com [IPv6:2607:f8b0:4001:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B5A2E8CC for ; Tue, 31 Mar 2015 03:26:56 +0000 (UTC) Received: by igcau2 with SMTP id au2so4943356igc.1 for ; Mon, 30 Mar 2015 20:26:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Tt/MaJl8TtSZZ1/d/jauBMM3ufG5Qyf5XNSvh+MMZJM=; b=mFZzF7jDBaWWgv3sF0MJb9JIkoDkFVBEOvVjwpNwzuy6uuQKDCGa6FIQcoPD6Nrjnb cs4H8kAytGX6c4VR0ax1LZbzRNeEdIY7qD4X+wDdueLidlkRYtG7zNqvXWiN0H171Mb/ 0BxzxrR9RfWXdBU+XTdMQWnw4z2zrI+LZ76geFbZIvSHRGbAynyLQmHsV1hxMqHj0pB3 bH9o0elkYPndebu6uehJGTqbV5Q4GYDYLM3Zkd+Bb624WhGfjYqPCgD/XFwvcX8zHqkQ qqJEAZGmp0CtDUzKGucH/rL80r4MIYSOr8O7dnL1iG2ChGD1TuNPiEIpKqHahGlLjRdG v1zQ== MIME-Version: 1.0 X-Received: by 10.107.46.155 with SMTP id u27mr52080038iou.87.1427772415704; Mon, 30 Mar 2015 20:26:55 -0700 (PDT) Received: by 10.64.59.138 with HTTP; Mon, 30 Mar 2015 20:26:55 -0700 (PDT) Reply-To: araujo@FreeBSD.org In-Reply-To: <551985BB.6050706@citrix.com> References: <55196D2F.8040203@citrix.com> <551985BB.6050706@citrix.com> Date: Tue, 31 Mar 2015 11:26:55 +0800 Message-ID: Subject: Re: Unable to load multiboot kernel. From: Marcelo Araujo To: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-xen 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, 31 Mar 2015 03:26:57 -0000 2015-03-31 1:19 GMT+08:00 Roger Pau Monn=C3=A9 : > Hello, > > El 30/03/15 a les 18.45, Marcelo Araujo ha escrit: > > Hello Roger, > > > > Thanks for the prompt reply and for the patch. > > > > I made a test and now we have a bit more of information. Seems the > problem > > is because the kernel is too large. > > > > OK load /boot/kernel/kernel > > /boot/kernel/kernel Trying to load a RAW file at 0x80001000 Error readi= ng > > /boot/kernel/kernel: file too large > > Unable to load /boot/kernel/kernel as a multiboot payload kernel > > can't load file '/boot/kernel/kernel': invalid argument. > > > > Here is the size of my kernel: > > root@e550:/usr/src/sys/boot # du /boot/kernel/kernel > > 12885 /boot/kernel/kernel > > Mmmm, that's smaller than mine and should load without problems: > > # du /boot/kernel/kernel > 21537 /boot/kernel/kernel > > I think the problem might be that your BIOS is not correctly reporting > the extended memory size, or that the loader is not fetching it > properly. Can you try the following patch to see which values you get? > On one of my boxes that is able to load FreeBSD/Xen I get: > > bios_extmem: 0xd75d8000 memtop_copyin: 0xd76d8000 memtop: 0xd76d8000 > > You can apply the patch on top of the previous one, or standalone, as > you wish. > > Roger. > > --- > diff --git a/sys/boot/i386/libi386/i386_copy.c > b/sys/boot/i386/libi386/i386_copy.c > index 3c05241..4d62282 100644 > --- a/sys/boot/i386/libi386/i386_copy.c > +++ b/sys/boot/i386/libi386/i386_copy.c > @@ -67,6 +67,8 @@ i386_readin(const int fd, vm_offset_t dest, const size_= t > len) > { > > if (dest + len >=3D memtop_copyin) { > + printf("bios_extmem: 0x%x memtop_copyin: 0x%x memtop: 0x%x\n", > + bios_extmem, memtop_copyin, memtop); > errno =3D EFBIG; > return(-1); > } > > Hi Roger, Yes, seems my BIOS is not correctly reporting the extended memory size. The value that I got from my box is: bios_extmem: 0xff00000 memtop_copyin: 0x10000000 memtop: 0x10000000 I did check my BIOS if there is any suspicious options that may mess up with the memory, but I didn't find nothing. I will check if there is any new BIOS version. Do you have any other idea? Best Regards, --=20 --=20 Marcelo Araujo (__)araujo@FreeBSD.org \\\'',)http://www.FreeBSD.org \/ \ ^ Power To Server. .\. /_)