From owner-freebsd-virtualization@freebsd.org Fri Mar 11 13:50:51 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7BC8EACC1A9 for ; Fri, 11 Mar 2016 13:50:51 +0000 (UTC) (envelope-from royger@gmail.com) Received: from mail-pa0-x230.google.com (mail-pa0-x230.google.com [IPv6:2607:f8b0:400e:c03::230]) (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 4D16BE89 for ; Fri, 11 Mar 2016 13:50:51 +0000 (UTC) (envelope-from royger@gmail.com) Received: by mail-pa0-x230.google.com with SMTP id td3so71722282pab.2 for ; Fri, 11 Mar 2016 05:50:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:in-reply-to:message-id:references :user-agent:mime-version; bh=VrGVNrJzG5m4qINDOhq+6TF37l40GBgde+Ee4JA4alY=; b=k1QeOlJ912TqqVVKKOR5VekuP5ALVp4en45+YmeB6cf9GVjrg56F7FNAkBpTq697QJ ZasCfdhsVpQzHWdmRccYP/y1jDfL/fdtq+HMOTs3ANxiJ/WWN2uTukP8QVatxHukSrY7 syG9JnJKl3avBS10fdZfXKwBvDOWrjhyj647JrrdlydK6IaMGS9NjdN+2mkA8w2EYNY9 txmE+1wSt/W1WYNrHdaFsh+AbYvD8ZRH3Ea6HWh/lYAMjceFoh3gTzBZW3r0gjEcFRDv v5ukBJyIV8B5qaXLXX/xCTdo6/PwxnSP13vJCITMpN7Vig2j/I28IEecc0DfOBzp/74c UdVQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:cc:subject:in-reply-to :message-id:references:user-agent:mime-version; bh=VrGVNrJzG5m4qINDOhq+6TF37l40GBgde+Ee4JA4alY=; b=IE1Kl8DBI1DlZAuDS5MrZK+iUTZF/gY1fQbU5AU0og9ZzXJJ2nqcpGo/jLZjc3uz68 8bR0D+4Ibldi4C+B8KLkcaoGbKvHZoP4VOH3HAUGeRAd7cOfYYzNCqASwbo4EFTxYgrc 6XQk3qPXSEI8v1eBVTyJuy1CSpVxo7FMStIom55yip7MNl939dPHXRv/WjNYHazGzC79 4xS0deLy2y54cjibUAvTSWG4IrbtDYTecm+u0yxL9kn+0NwVvif63MoAzQ0SvzG7Vq2h eUcovkh5VB3Isj4Igg3PwoH68vWZboRb4zM54SUn3KrFbPq9l7tYNLOln/Wm/LAs/7fh xl+A== X-Gm-Message-State: AD7BkJJkwr+qKg1xnLCqoOtpa7sgfxiBZuWzAS3atfk5D6wWAOV6AmVze1sjmwIc1ZnniA== X-Received: by 10.66.190.131 with SMTP id gq3mr15427563pac.42.1457704250421; Fri, 11 Mar 2016 05:50:50 -0800 (PST) Received: from [192.168.1.68] (p142030-ipngn11501marunouchi.tokyo.ocn.ne.jp. [220.104.97.30]) by smtp.gmail.com with ESMTPSA id q4sm13219539pfi.75.2016.03.11.05.50.48 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 11 Mar 2016 05:50:49 -0800 (PST) Sender: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= Date: Fri, 11 Mar 2016 22:50:47 +0900 (JST) From: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= X-X-Sender: royger@macbook-air-de-roger.local To: brahmann cc: freebsd-virtualization@freebsd.org Subject: Re: ports/Xen on CURRENT, error: ELF start or entries are out of bounds. In-Reply-To: <56E14066.5080400@lifec0re.net> Message-ID: References: <56E14066.5080400@lifec0re.net> User-Agent: Alpine 2.20 (OSX 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2016 13:50:51 -0000 Hello, On Thu, 10 Mar 2016, brahmann wrote: > Hi all. > I'm trying to run XEN on latest current as dom0. > Did all by manual: http://wiki.xen.org/wiki/FreeBSD_Dom0 (except compiling > from git, cant compile tools, so just used ports xen/xen-tools/xen-kernel) > And stuck with such an error: Yes, using the ports (xen-kernel/xen-tools) is the recommended way, I should update the wiki page in order to note this. > --- > (XEN) elf_xen_addr_calc_check: ERROR: ELF start or entries are out of bounds. > Could not set up DOM0 guest OS > --- > > This only drops on console while xen kernel boots, all other strings are OK > according to manual. > Link to photo of speedy console log: http://imgur.com/a5b9CLE > If need details pls ask. I've just noticied this issue, it's probably due to an issue with kernel linking. It seems like the physical address specified in the ELF program headers is wrong. I'm currently trying to bisect it in order to find the commit that caused it, in the meantime I can confirm that r295683 and older revisions should work fine. Just to confirm, can you paste the output of the following command: $ readelf -l /boot/kernel/kernel With the non-working kernel? Thanks, Roger.