From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: Problems when creating domU on OMAP5 Date: Wed, 18 Sep 2013 15:48:51 +0100 Message-ID: <5239BD53.4050002@linaro.org> References: <20130916131828.GA15286@cbz-workstation> <52384157.1020803@linaro.org> <20130918020644.GA10532@cbz-workstation> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20130918020644.GA10532@cbz-workstation> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Chen Baozi Cc: Xen Developer List List-Id: xen-devel@lists.xenproject.org On 09/18/2013 03:06 AM, Chen Baozi wrote: > On Tue, Sep 17, 2013 at 12:47:35PM +0100, Julien Grall wrote: >> On 09/16/2013 02:18 PM, Chen Baozi wrote: >>> Hi all, >>> >>> I tried to create a domU on OMAP5 today. But it seems there are still some >>> problems to solve before I can successfully creat it. >>> >>> I first cloned Julien's arndale-domU-3.9 branch which mentioned in wiki. >>> Then I modified gic addresses xenvm-4.2.dts to meet OMAP5432 requirement: >>> >>> --- a/arch/arm/boot/dts/xenvm-4.2.dts >>> +++ b/arch/arm/boot/dts/xenvm-4.2.dts >>> @@ -49,13 +49,13 @@ >>> reg = <0 0x80000000 0 0x08000000>; >>> }; >>> >>> - gic: interrupt-controller@2c001000 { >>> + gic: interrupt-controller@48211000 { >>> compatible = "arm,cortex-a15-gic", "arm,cortex-a9-gic"; >>> #interrupt-cells = <3>; >>> #address-cells = <0>; >>> interrupt-controller; >>> - reg = <0 0x10481000 0 0x1000>, >>> - <0 0x10482000 0 0x100>; >>> + reg = <0 0x48211000 0 0x1000>, >>> + <0 0x48212000 0 0x1000>; >>> }; >>> >>> timer { >>> >>> And make the kernel image as wiki said: >>> >>> $ cat arch/arm/boot/zImage arch/arm/boot/xenvm-4.2.dtb > image >>> >>> Write a config file used by xl like: >>> >>> kernel = "/root/domU/image" >>> memory = "128" >>> name = "domU" >>> vcpus = 1 >>> disk = [ 'phy:/dev/loop0,xvda,w' ] >>> >>> Setup loop device: >>> >>> $ losetup /dev/loop0 /root/domU/xen-arm.img >>> >>> which xen-arm.img is the a bootable rootfs. >>> >>> Finally I execute xl to create the domU: >>> >>> $ sudo xl create -f config -d >> Can you to copy the output in pastebin of the following command? >> xl -vvv create -f config -d > > See: http://pastebin.com/kGjQUM86 What is your dom0 linux configuration file? Did you enable at least the following config: /* For dom0 */ CONFIG_XEN_BLKDEV_BACKEND=y CONFIG_XEN_NETDEV_BACKEND=y /* For the guest */ CONFIG_XEN_BLKDEV_FRONTEND=y CONFIG_XEN_NETDEV_FRONTEND=y -- Julien Grall