From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: Dom0 kernel panic when porting xen to new arm soc Date: Fri, 26 Jun 2015 18:27:50 +0200 Message-ID: <558D7D86.3000202@citrix.com> References: <5582D109.2000409@gmail.com> <1434639280.28264.42.camel@citrix.com> <55841799.6000406@gmail.com> <55853E20.6030700@gmail.com> <558573D0.6010207@gmail.com> <55857CF7.4000300@gmail.com> <5587E175.90704@citrix.com> <5587EEE6.7030706@gmail.com> <5588157E.2030701@citrix.com> <55895915.1010601@gmail.com> <558960D7.3000806@citrix.com> <55896582.1030701@gmail.com> <558C0B89.7070809@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <558C0B89.7070809@gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Peng Fan , Ian Campbell Cc: xen-users , Stefano Stabellini , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 25/06/2015 16:09, Peng Fan wrote: > Hi Julien, Hi, > On 6/23/2015 9:56 PM, Peng Fan wrote: >> Hi, >> >> On 6/23/2015 9:36 PM, Julien Grall wrote: >>> Hi, >>> >>> On 23/06/15 14:03, Peng Fan wrote: >>>> I did not enable LPAE for DOM0 kernel, use shor page table. >>>> Following is the full log from uboot to kernel with DOM0 512M: >>> >>> Which CONFIG_VMSPLIT_* do you use? Can you try to use another one? I >>> remembered it had some effect on the offset between physical and virtual >>> address. >> CONFIG_VMSPLIT_2G=y >> >> CONFIG_PAGE_OFFSET=0x80000000 >> >> ok. Will try 3G:1G split. > Later I'll reply with log info about this(Do not have log at hand). > Still panic, maybe something wrong with gnutab configration in my side, > I use default gnutab address/size. Did you check that the gnttab doesn't overlap a device/RAM region of your hardware? I've posted a patch a week ago to find automatically a region for the grant table [1] in DOM0 memory. It will avoid you to go through the datasheet. > Current I met a DomU boot issue, if do not use blk backend, DomU can > boot with ramfs as rootfs. If use an image file as rootfs, DomU can not > boot. > > I am not sure why this happends:" > libxl: error: libxl_create.c:1195:domcreate_launch_dm: unable to add > disk devices > libxl: error: libxl_device.c:799:libxl__initiate_device_remove: unable > to get my domid > " > By using gdb, I found domcreate_launch_dm fails to get domid, then it > reports unable to add disk devices. I am not familiar with xenstore and > etc. Did I miss some configuation? The "unable to get my domid" looks like an issue with xenstore. Is xenstored running? Also, did you built you DOM0 kernel with CONFIG_XEN_BLKDEV_BACKEND? Regards, [1] http://lists.xen.org/archives/html/xen-devel/2015-06/msg02831.html -- Julien Grall