From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chen Baozi Subject: Fail to Boot Xen on Chromebook Date: Fri, 19 Apr 2013 17:20:15 +0800 Message-ID: <20130419092015.GA17211@cbz-workstation> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: anthony.perard@citrix.com Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org Hi Anthony, I've been analysing xen-arm for Chromebook and related dom0 kernel these days and tried to understand what was going on when it booted. However, without the output after dom0 launched, I haven't got any clues about it. It seems there are three main works done in the present xen for chromebook git repo - 1) codes handling u-boot format image containing xen hypervisor, dom0 kernel and dtb; 2) mmio mappings; 3) ramoops on chromebook. For the last two points, I can hardly know the correctness of those 'magic' address since I have no hardware specification for Chromebook. So I am still not able to boot xen on my chromebook, though your Wiki (in progress) do help me understand it a little more. Would you please show me any clues about hacks needed to boot it? Thanks a lot. Regards, - Baozi